Revise copy for settings page description of Paired URL Structures #6229
Conversation
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
|
Plugin builds for 3f67835 are ready 🛎️!
|
westonruter
force-pushed
the
add/paired-url-structure-docs-copy
branch
2 times, most recently
from
90d18a7 to
da825e6
Compare
Co-authored-by: Joshua Wold <[email protected]>
westonruter
force-pushed
the
add/paired-url-structure-docs-copy
branch
from
da825e6 to
bcd5a69
Compare
westonruter
reviewed
May 17, 2021
westonruter
added a commit
that referenced
this pull request
May 17, 2021
…6229) Co-authored-by: Joshua Wold <[email protected]>
|
QA Passed Revision can be seen on page:
|
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.
Summary
In #6227 we updated the copy to explain how the paired URL function works. This has been approved, with one small typo to update the wording of
is is.In addition I reviewed the text and have a few wording suggestions.
Before:
When using Transitional or Reader template modes, your site is is in a “Paired AMP” configuration where your canonical URLs are non-AMP and then you have separate AMP versions of your pages with AMP-specific URLs. The structure of the paired AMP URL is not important, whether using a query parameter or path suffix. The use of a query parameter is the most compatible across various sites and it has the benefit of not resulting in a 404 if the AMP plugin is deactivated, so that is why it is the default. Please note that changing the paired URL structure can cause AMP pages to disappear from search results until your site has been re-indexed. So if the current structure of your paired AMP URLs works for you, there is no need to change. If you're migrating from another AMP plugin that used a different paired URL structure than the default, then you may want to change this setting. Learn more.
After:
When using Transitional or Reader template modes, your site is in a “Paired AMP” configuration. Canonical URLs are non-AMP and separate AMP versions of your pages have AMP-specific URLs.
The structure of a paired AMP URL is not important, whether using a query parameter or path suffix. The use of a query parameter is the most compatible across various sites and doesn't result in a 404 if the AMP plugin is deactivated. Note: Changing the paired URL structure can cause AMP pages to disappear from search results until your site is re-indexed.
If you're migrating from another AMP plugin with a different paired URL structure, then you may want to change this setting. Otherwise we recommend leaving it as is. Learn more
--
Here's a screenshot of the diff: https://d.pr/i/KLOuEo
Checklist