Why Your Sitemap Is Costing You Rankings (And How to Fix It)
A neglected sitemap quietly wastes crawl budget and confuses Google. Here are the sitemap mistakes I find most often, and exactly how to fix each one.
Your XML sitemap is the map you hand Google of your site — and most businesses have one that’s actively working against them without realizing it. It’s an unglamorous file, which is exactly why it gets neglected. Here are the sitemap problems I find most often, and how to fix each.
Mistake 1: It’s stale
Many sites run a hand-written sitemap that was accurate the day it was made and has drifted ever since. New pages don’t get added, deleted pages linger. The fix is to generate the sitemap from your real pages at build time, so it’s always current. A generated sitemap can only ever list pages that actually exist.
Mistake 2: It points at pages that 404
This is the one that quietly burns trust. I’ve audited sites whose sitemap listed dozens of URLs that returned 404 — telling Google to crawl pages that aren’t there. Google notices, and it stops trusting your sitemap. Every URL in the file should return a 200.
Mistake 3: No priority, changefreq, or lastmod
A bare sitemap just lists URLs. A good one tells Google which pages matter most (priority), how often they change (changefreq), and when they last changed (lastmod). That last one is the most valuable — a real lastmod date is how you signal “this page was genuinely updated, come re-crawl it.” Faking it backfires, but using real dates helps a lot.
Mistake 4: Ghost sitemaps from a migration
When a site moves off WordPress, the old Yoast sitemap URL (/sitemap_index.xml) often stays submitted in Search Console long after the site stops producing it. Now you’ve got a dead or duplicate sitemap confusing crawlers. Part of any migration is cleaning these up so there’s one canonical sitemap.
Mistake 5: Submitting the wrong URL
If you submit a sitemap URL that 404s or redirects, Google can’t use it. Submit the single URL that returns a direct 200 for your setup — and only that one. An index sitemap already points crawlers to its children, so you never submit the children separately.
The fix in practice
A clean sitemap is generated, current, lists only 200-returning pages, carries real priority/changefreq/lastmod, has no ghosts, and is submitted correctly in Search Console. It’s a small file, but getting it right is part of the technical foundation every ranking site stands on. If you’re not sure what shape yours is in, that’s exactly the kind of thing I audit.
Sitemap and technical fixes like these are part of my SEO services.
