The XML Sitemap Audit Most People Never Do

The file your SEO plugin made and you never opened

If your site runs Rank Math, Yoast, or almost any SEO plugin, you have an XML sitemap. It was generated automatically the day you installed the plugin, it’s been quietly updating ever since, and there’s a good chance nobody has ever looked at it. That’s fine — until it isn’t.

Let me pop the hood on the XML sitemap audit: what the file actually does, the specific ways it goes wrong, and the fifteen-minute check that often speeds up indexing more than anything else you could do this month.

What a sitemap actually does (and doesn’t)

An XML sitemap is a machine-readable list of the pages on your site you want search engines to know about. It’s a discovery aid — you’re handing Google a table of contents instead of making it find everything by following links.

Two things it does not do, because this trips people up constantly:

• It doesn’t guarantee indexing. Being in the sitemap means Google knows the page exists. Whether it indexes and ranks it is a separate judgment about quality.
• It doesn’t boost rankings directly. There’s no ranking bonus for having one. The benefit is discovery speed, which matters most for new sites and new content.

Google’s own sitemap documentation is clear that sitemaps help most on large sites, new sites with few external links, and sites with pages that aren’t well linked internally. For a small business site, that middle case is usually the relevant one — which is exactly why the internal linking work and the sitemap work reinforce each other.

The five things that go wrong

1. It was never submitted

The most common failure by far. The plugin generated the sitemap, but nobody ever told Google Search Console it exists. The file sits there doing very little. Submitting takes about two minutes and is the single highest-value item on this list — especially for a site publishing regularly, where the difference between fast and slow discovery compounds every week.

2. It’s full of pages that shouldn’t be there

Default settings often include things you don’t want competing in search: tag archives with one post in them, author archives on a single-author site, attachment/media pages, thin category pages, thank-you and confirmation pages. Every junk URL in your sitemap is you telling Google “this is worth your attention” about a page that isn’t. Trim them.

3. It’s missing pages that should be there

The reverse problem. Sometimes important pages get excluded — a service page accidentally set to noindex, a section the plugin didn’t pick up, pages behind a structure the generator missed. Worth confirming your money pages are actually listed.

4. It contains contradictions

This is the subtle one. A URL in your sitemap that is also set to noindex sends Google mixed signals: “index this / don’t index this.” Same with sitemap URLs that redirect elsewhere, return 404s, or canonical to a different page. None of these are catastrophic, but they waste crawl attention and muddy the signal.

5. Nobody watches the coverage report

Once submitted, Search Console tells you how many sitemap URLs it discovered versus indexed. A large gap is a real diagnostic — it means Google is seeing your pages and declining to index them, which is a content quality signal worth taking seriously. Most owners never look.

The fifteen-minute audit

1. Find your sitemap. It’s usually at yoursite.com/sitemap_index.xml or /sitemap.xml. Open it in a browser.
2. Skim what’s in it. Are there tag, author, or attachment sections you don’t want? Note them.
3. Confirm your key pages are present — home, every service page, your main content.
4. Trim the junk in your SEO plugin’s sitemap settings. Rank Math and Yoast both let you toggle post types and taxonomies on and off.
5. Submit it in Google Search Console under Sitemaps. Two minutes.
6. Check back in a week at the coverage report and look at discovered versus indexed.

The related file worth a glance

While you’re in there, look at your robots.txt (at yoursite.com/robots.txt). It should reference your sitemap location, and it should not be blocking anything you want indexed. Occasionally a site gets left with a blanket disallow from a staging environment, which is quietly catastrophic and takes ten seconds to spot. It’s the same category of boring infrastructure as schema markup — invisible when right, expensive when wrong.

Final Thoughts

Your XML sitemap was generated automatically and probably never audited. The five failure modes — never submitted, full of junk URLs, missing key pages, contradicting your noindex tags, and unwatched coverage — are all fixable in about fifteen minutes.

If you do one thing: open Search Console and confirm your sitemap is actually submitted. On a site publishing regularly, that alone can be the difference between new content getting found in days versus weeks. Boring infrastructure — nobody notices it working, everybody feels it when it isn’t.