Sitemap errors
You handed Google a map. The map is lying.
A sitemap is your site's own testimony about what exists and matters. When it lists dead pages, redirects, blocked URLs — or can't be fetched at all — Google learns to discount your testimony. An honest map is cheap; a lying one is expensive.
Same-day diagnosis. Flat quote before any fix.
What’s actually happening
Sitemaps declare your canonical URLs so crawlers spend budget on what you value. Search Console's sitemap report grades that declaration: 'couldn't fetch' means the map itself is unreachable or malformed; per-URL notes flag entries that 404, redirect, carry noindex, or contradict your canonical tags. Each mismatch is your site testifying against itself.
The common root cause is stale generation: plugin-built sitemaps still listing deleted content types, migrations that changed URLs while the map kept the old ones, or multiple plugins each generating competing maps. The fix is rarely editing entries — it's fixing the generator so the map stays honest by construction.
The usual causes, ranked
After twenty-seven years of these calls, the odds are well mapped. Start at the top.
The map can't be fetched
Blocked by robots rules or a firewall, erroring on generation, or simply absent at the submitted URL. Google's working from memory of an old map — or nothing.
Dead and redirected entries
The map lists URLs that 404 or bounce elsewhere — post-migration sediment testifying that the site doesn't know its own address book.
Contradictory signals
Sitemap says 'index this' while the page says noindex, or lists non-canonical variants — mixed testimony that erodes trust in all of it.
Competing generators
Two SEO plugins, or a plugin plus a manual file, each producing maps — Google reading whichever, you maintaining neither.
What you can safely try first
Nothing below can make things worse — that’s the selection criterion. Anything riskier belongs in professional hands, on a backup.
- 1
Open your sitemap in a browser
yourdomain.com/sitemap.xml (or _index.xml). It should load as structured XML. An error, a blank, or a 404 here explains every downstream symptom at once.
- 2
Read the Search Console sitemap report
It names the failure: couldn't fetch, has errors, or discovered-vs-indexed gaps. The specific verdict picks the specific fix.
- 3
Click five random URLs from the map
Do they load, directly, without redirecting? A map whose samples redirect or die is confessing to staleness.
Stop and call when…
- The generator itself is broken or duplicated — plugin surgery, not entry editing
- The map is fine but 'discovered, not indexed' dominates — that's a quality verdict, different problem
- A migration left hundreds of stale entries — regeneration plus redirect mapping, done once, properly
From there it’s our job: same-day look, flat quote, and the $229 flat repair covers most cases of exactly this.
Single Error Fix — buy it now, skip the hunt.
One error, hunted down and fixed — 500s, white screens, redirect loops, broken pages.
Covers one specific error or broken behavior on one site. Diagnosis, the fix, and a plain-English note on what happened. If we can't fix it, you get a full refund.
Questions we hear a lot.
Do I even need a sitemap?
Small, well-linked sites get found without one — but the map costs nothing when auto-generated and pays real dividends on larger sites, new sites, and anything whose deep pages lack internal links. There's no case against an honest one; there's a real case against a stale one.
Google says 'Sitemap could not be read.' Where do I start?
Fetch it yourself in a browser: unreachable, malformed XML, or firewall-blocked each show differently. Half of these are a security layer treating Googlebot's fetch as suspicious — fixed in the rule, not the map.
Why are indexed pages missing from my sitemap coverage?
Google indexes what it finds regardless of the map — the sitemap is advice, not law. Missing-from-map-but-indexed is untidy, not urgent. The reverse (in the map, not indexed) is the report worth reading closely, and its reasons column says why.
Related symptoms & help
Errors travel in packs. If this one visited, check its friends.
Make the map honest. Keep it that way.
Send the symptom, get a same-day look and a flat quote from the developer who's fixed this exact thing more times than either of us can count.