Add ahrefs connection option.#22573
Merged
leonidasmi merged 2 commits intotrunkfrom Sep 19, 2025
Merged
Conversation
Pull Request Test Coverage Report for Build 72a32f83bd538175ded6eb1e0a0b39690d232b9fDetails
💛 - Coveralls |
leonidasmi
reviewed
Sep 17, 2025
Contributor
leonidasmi
left a comment
There was a problem hiding this comment.
CR:
- One minor thing, to remove
Ahreffrom the search keywords - We could add a
Ahrefs_Presenter_Testclass in the PR
Acceptance:
- We should probably have
ahrefinstead ofAhrefin the input label and help text? At least judging from Manuel's answer here. - Not entirely sure about this, so better to double check with UX, but I think we have the inputs in Site Connections in alphabetical order on purpose? If that's the case, maybe we should keep that (same with the order in
Yoast\WP\SEO\Integrations\Front_End_Integration)
| fieldLabel: __( "Ahrefs", "wordpress-seo" ), | ||
| keywords: [ | ||
| __( "Webmaster", "wordpress-seo" ), | ||
| __( "Ahrefs", "wordpress-seo" ), |
Contributor
There was a problem hiding this comment.
I think adding the name of the setting is not necessary:
Suggested change
| __( "Ahrefs", "wordpress-seo" ), |
Contributor
Author
There was a problem hiding this comment.
I have changed everything except the lowercase name. I think that was a mistake from Manuel in the comment since everything is capitalized and Ahrefs is a name so it would make no sense to not do it.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Context
Summary
This PR can be summarized in the following changelog entry:
Relevant technical choices:
Test instructions
Test instructions for the acceptance test before the PR gets merged
This PR can be acceptance tested by following these steps:
Go to /wp-admin/admin.php?page=wpseo_page_settings#/site-connections
Add
123123abcabcto theAhrefsfield.Save and make sure you see
<meta name="ahrefs-site-verification" content="123123abcabc" class="yoast-seo-meta-tag" />under our schema output.Copy the entire meta field like in the instruction above and paste it in the
Ahrefsfield in the settings. Make sure only the123123abcabcends up in the field.Also try to add a non-valid character there, like
&or%, etc. Confirm you get a warning about it.finally make sure the shortlink goes to
https://yoa.st/ahrefs-verification-code.Relevant test scenarios
Test instructions for QA when the code is in the RC
QA can test this PR by following these steps:
Impact check
This PR affects the following parts of the plugin, which may require extra testing:
Other environments
[shopify-seo], added test instructions for Shopify and attached theShopifylabel to this PR.Documentation
Quality assurance
Innovation
innovationlabel.Fixes #