Refresh sitemap lastmod to trigger recrawl - #11
Draft
pranayesse wants to merge 1 commit into
Draft
Conversation
Bump lastmod to 2026-07-25 for the homepage, blog index, and links pages (the pages that change over time) to give Googlebot a fresh signal to re-fetch the sitemap and re-crawl the site. Post entries keep their real publish dates. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01M9pM96QL7pcGD31DbYkdhP
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
2 participants
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.
What
Bumps
lastmodto2026-07-25for the three living pages insitemap.xml— the homepage (/), blog index (blog.html), and links page (links.html). Individual post entries keep their real publish dates.Why
Context: Google Search Console reported the sitemap as "Couldn't fetch" and only 1 of 8 pages is indexed. Investigation showed the sitemap file itself is byte-perfect (no BOM, valid XML, correctly served at the repo root by the Pages deploy), so this is not a file/server defect — the "Couldn't fetch" is a GSC-side transient/pending or property-mismatch state that is resolved by resubmitting in Search Console.
This change is a recrawl nudge, not a fix for the fetch error: refreshing
lastmodon the pages that actually change over time and redeploying gives Googlebot a fresh signal to re-fetch the sitemap and re-crawl the site.Not changed
lastmoddates (left at their genuine publish dates).🤖 Generated with Claude Code
https://claude.ai/code/session_01M9pM96QL7pcGD31DbYkdhP
Generated by Claude Code