Repository navigation
fix(seo): verify sitemap and robots crawl discovery - #16
Merged
Merged
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.
Diagnosis
Search Console reports "Sitemap could not be read"; the 49 sitemap URLs already match the 49 published HTML index pages and robots.txt correctly advertises the sitemap. HTTP reachability from Google's infrastructure remains unverified. Both offline docs generators stamp every sitemap URL with the build date, making the optional lastmod unreliable.
Changes
Verification
Search Console follow-up
After Pages publishes main, verify live HTTP 200 + XML for /sitemap.xml and then resubmit sitemap.xml in Search Console. A green repository CI does not itself establish Google fetch success.