fix(citations): the 2011 planned-downtime post is gone from Search Central - #158
Draft
jdevalk wants to merge 1 commit into
Draft
fix(citations): the 2011 planned-downtime post is gone from Search Central#158jdevalk wants to merge 1 commit into
jdevalk wants to merge 1 commit into
Conversation
…ntral The maintenance-pages entry cited a January 2011 Webmaster Central post at developers.google.com/search/blog/2011/01/how-to-deal-with-planned-site-downtime. That path no longer resolves to an article — it lands on the Search Central blog index, which only archives back to 2012. Replaced with Google's current, maintained documentation on the same subject, "Temporarily pause or disable a website", which covers 503 plus Retry-After for planned downtime. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Deploying specification-website with
|
| Latest commit: |
fd90c5e
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://bd3ab626.specification-website.pages.dev |
| Branch Preview URL: | https://fix-maintenance-pages-citati.specification-website.pages.dev |
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
1 participant
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 changed
src/content/spec/resilience/maintenance-pages.mdcited a January 2011 Webmaster Central blog post for the "return 503 with Retry-After during planned downtime" advice:That path no longer resolves to an article. It lands on the Search Central blog index, whose archive only goes back to 2012 — the pre-migration Webmaster Central posts were not all carried over. (The original still exists on the retired
webmasters.googleblog.comhost, but citing a decommissioned blog host for advice Google now documents properly would be the worse fix.)Why now
Daily standards scan, citation rotation over
i18n/andresilience/— the two categories not spot-checked in the last week.The replacement
Google Search Central — Temporarily pause or disable a website is the current, maintained documentation on the same subject. It carries the same guidance the page makes ("return an informational error page with a 503 HTTP response status code", use
Retry-Afterwith an expected recovery date), so the claim the citation supports is unchanged.updatedbumped per the convention in the other citation-repair PRs. No body change; the other three sources (RFC 9110 ×2, RFC 6585) are fine.Noted but not bundled
The replacement doc adds a nuance the page does not currently make: do not return 503 for
robots.txtitself during an outage. That is a real content addition rather than a citation repair, so it is left out of this PR — flagged in the scan summary instead.npm run buildpasses.🤖 Generated with Claude Code