GSC Crawl Stats Show Old URLs Often Stall Expired Domain Sitemap Fetches
In October 2026, the OP tested two domains on the same server: a brand-new domain whose GSC sitemap status flipped to "Success" within 10 seconds, and a recently purchased expired domain whose sitemap stayed stuck on "Couldn't fetch" for 5 days.
Wayback Machine history showed nothing suspicious on the drop, and Bing Webmaster Tools parsed the exact same sitemap.xml file without errors, ruling out server failure.
GSC Crawl Stats logs expose why old URLs from a previous owner often stall expired domain sitemap fetches while Googlebot sometimes throttles crawl frequency after an ownership change.
The expired domain's Crawl Stats report logged only 23 requests in 4 days, with 57% returning 404 across Refresh crawls and zero Discovery requests.
The 404 log listed only leftover thumbnail URLs and ads.txt from the previous owner — where 404 is the expected response and needs no fix — with zero requests for sitemap.xml, indicating the "Couldn't fetch" label was probably stale in a slow queue rather than a spam flag.
Because expired domains often carry lingering crawl delays or legacy baggage from the previous owner, isolating a true fetch block from a throttled queue requires four diagnostic checks in order:
- Inspect
Settings > robots.txtandSecurity & Manual ActionsinGSCto verify the last fetchedrobots.txt— whichGooglebotrefetches roughly once a day — has no leftover disallow rules on the sitemap path, trigger a recrawl if stale, confirm the sitemap excludes disallowed legacyURLsand does not time out from file size, and checkManual Actionsfor unsurfaced prior penalties. - Break down
Settings > Crawl statsby file type and open both the404row and theUnknownfailed-requests row to see whethersitemap.xmlfailed on anhttp-vs-httpsorwww-vs-non-wwwmismatch, or never appeared becauseGooglebothas not requested it yet. - Open the sitemap URL in a private window and check
HTTPheaders to confirm a plain200response with zero redirects matching the exactGSCproperty, no strayX-Robots-Tagnoindexdirective, and validSSL,CDN, and firewall rules covering the expired domain. - Run a live test in
URL Inspectionon the sitemap URL to verifyGooglebotcan reach the file; a passing live fetch alongside a"Couldn't fetch"report confirms the sitemap is waiting its turn in the queue.
A fresh Discovery crawl moves a queued expired-domain sitemap along over a few days: add a Sitemap: https://yourdomain/sitemap.xml directive to robots.txt, request indexing via URL Inspection on the homepage, the sitemap URL, or the 2 or 3 most important pages, and point a link to the domain from a site Google already crawls often.
On whether resubmitting the file in GSC accelerates that queue, one specialist notes that resubmitting will not speed up a queued sitemap once the live test passes, whereas another webmaster reports that removing and re-adding the sitemap around 5 to 10 times can force the status from "Couldn't fetch" to "Success".