Add canonical URL to all pages #4473
Merged
Conversation
This file contains 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
Grafana Cloud documentation wants to reuse this documentation as part of its reorganization. Having duplicate pages can be detrimental to SEO and setting the canonical URL helps by letting search engines only index the canonical page. We do not index /docs/agent/next/ pages, only /docs/agent/latest/, so there is no need to concern ourselves with how this canonical is managed across versions. Pages that are not "latest", automatically have their canonical set to "latest" by the website. I will open a similar PR in the latest version branch to update the current "latest" pages. Signed-off-by: Jack Baldry <jack.baldry@grafana.com>
3 tasks
Signed-off-by: Jack Baldry <jack.baldry@grafana.com>
clayton-cornell
pushed a commit
that referenced
this pull request
Aug 14, 2023
* Add canonical URL to all pages Grafana Cloud documentation wants to reuse this documentation as part of its reorganization. Having duplicate pages can be detrimental to SEO and setting the canonical URL helps by letting search engines only index the canonical page. We do not index /docs/agent/next/ pages, only /docs/agent/latest/, so there is no need to concern ourselves with how this canonical is managed across versions. Pages that are not "latest", automatically have their canonical set to "latest" by the website. I will open a similar PR in the latest version branch to update the current "latest" pages. Signed-off-by: Jack Baldry <jack.baldry@grafana.com> * Reverse changes into template Signed-off-by: Jack Baldry <jack.baldry@grafana.com> --------- Signed-off-by: Jack Baldry <jack.baldry@grafana.com>
clayton-cornell
pushed a commit
that referenced
this pull request
Aug 14, 2023
* Add canonical URL to all pages Grafana Cloud documentation wants to reuse this documentation as part of its reorganization. Having duplicate pages can be detrimental to SEO and setting the canonical URL helps by letting search engines only index the canonical page. We do not index /docs/agent/next/ pages, only /docs/agent/latest/, so there is no need to concern ourselves with how this canonical is managed across versions. Pages that are not "latest", automatically have their canonical set to "latest" by the website. I will open a similar PR in the latest version branch to update the current "latest" pages. Signed-off-by: Jack Baldry <jack.baldry@grafana.com> * Reverse changes into template Signed-off-by: Jack Baldry <jack.baldry@grafana.com> --------- Signed-off-by: Jack Baldry <jack.baldry@grafana.com>
github-actions
bot
added
the
frozen-due-to-age
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Grafana Cloud documentation wants to reuse this documentation as part of its reorganization.
Having duplicate pages can be detrimental to SEO and setting the canonical URL helps by letting search engines only index the canonical page.
We do not index /docs/agent/next/ pages, only /docs/agent/latest/, so there is no need to concern ourselves with how this canonical is managed across versions. Pages that are not "latest", automatically have their canonical set to "latest" by the website.
I will open a similar PR in the latest version branch to update the current "latest" pages.