13 Dead Sitemaps in GSC, Cleaned in Two Minutes

A B2B services company came in for a migration audit on their WordPress site. Their crawl coverage in Google Search Console looked noisy and they could not explain why the same URLs kept getting flagged.

Thirteen sitemap URLs were still registered in GSC from a 2018 Yoast setup. Every one of them returned 0 indexed URLs. The site had since moved to the WordPress native sitemap, and that sitemap was not registered in GSC at all. Google was being asked to crawl thirteen empty sitemaps and was never told where the real one lived.

Step one was the Search Console sitemaps report. The 13 dead Yoast URLs showed up immediately, all with the same status (zero indexed URLs, last fetched years ago).

Step two was confirming the current sitemap. We pulled /wp-sitemap.xml directly and verified it was generating correctly with current URLs.

Step three was the cleanup. Each dead Yoast sitemap was deleted from GSC. The native WordPress sitemap was submitted and verified.

Within days the noise in the GSC coverage report cleared. New crawl activity started landing on real, current URLs. The site had not had a clean crawl signal since the Yoast deprecation, and a two-minute cleanup restored it.

The sitemap report went from 13 dead entries (all 0 URLs indexed) to one active sitemap reflecting the live site.

The Setup

A B2B services company on WordPress came in for a migration audit. Their crawl coverage in Google Search Console was noisy. Pages they expected to see were getting flagged and they could not figure out why.

What We Found

Thirteen sitemap URLs were still registered in GSC. All of them dated back to a 2018 Yoast SEO plugin setup. Every one returned 0 indexed URLs.

The site had since moved off Yoast and was running on the WordPress native sitemap (/wp-sitemap.xml). That sitemap was not registered in GSC. Google was being asked to crawl 13 empty files and was never told where the live sitemap lived.

The Diagnostic

Three steps. Each one took under a minute.

1. Open the Sitemaps report in Google Search Console. The 13 dead Yoast URLs were sitting at the top of the list.
2. Hit the live native sitemap directly to confirm it was generating correctly with current URLs.
3. Cross-check robots.txt to make sure it was pointing at the right sitemap. It was not.

The Fix

Two minutes total.

• Deleted all 13 dead Yoast sitemaps from GSC.
• Submitted /wp-sitemap.xml as the active sitemap.
• Updated robots.txt to point at the native sitemap.

Outcome

Within days the GSC coverage report cleared. New crawl activity started landing on real, current URLs. The site had not had a clean crawl signal in years, and the fix took less time than the email confirming it was done.

Lessons

• Sitemap registrations outlive plugins. When a site migrates off a SEO plugin, the sitemaps that plugin generated stay registered in GSC unless someone removes them. They quietly waste crawl budget for years.
• GSC will not warn you. Dead sitemaps with 0 indexed URLs do not trigger an alert. They sit there forever until someone audits the report.
• The native WordPress sitemap is real. Since WP 5.5 it is generated automatically. If a site moved off Yoast or RankMath without registering the native sitemap, Google has no current map of the site.
• Migration audits catch this. Every WordPress migration audit Content Cucumber runs starts with the GSC sitemap report. It is the cheapest, fastest signal in the entire toolkit.

Brent’s Take

Two minutes of cleanup undid years of crawl noise. The slow burn problem is the worst kind. Nothing breaks visibly, but nothing works correctly either. A migration audit is exactly when you find these.