Fix Search Console coverage URLs - #312
Draft
mister-teddy wants to merge 1 commit into
Draft
mister-teddy wants to merge 1 commit into
mister-teddy wants to merge 1 commit into
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
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
.mdpath with the generated docs URL.Why
The Search Console coverage export showed redirect and canonical-related indexing buckets. The root cause was that generated sitemap/canonical URLs omitted trailing slashes, while GitHub Pages redirects those paths to trailing-slash versions. Aligning Docusaurus output with the served URL shape removes those avoidable crawl redirects.
Validation
cd gh-pages && pnpm buildnoindex.Docusaurus still reports existing warnings for inline blog authors, missing truncation markers, and stale Browserslist data; those are unrelated to this fix.