Your sitemap is a direct instruction to search engines about which URLs matter. When it's full of redirects, 404s, and noindex pages, that instruction becomes noise. Here's how to keep your sitemap clean and what the audit checks.
A sitemap is the one place you explicitly tell search engines "these are my pages." If that list includes URLs that redirect, error, or carry noindex, you're handing crawlers a contradictory map.
The XML sitemap is the one place you get to hand search engines an explicit list and say "these are the pages I care about." It's a discovery aid, especially valuable for large sites, new sites without many backlinks, and pages buried deep in the structure. It doesn't directly boost rankings, but it shapes what gets found and how quickly. The principle is simple: your sitemap should list exactly the canonical, indexable, 200-status URLs you want in search, no more, no less.
The damage comes from contradiction. When a sitemap includes URLs that redirect, error, or carry a noindex, you're telling crawlers "index this" while the page itself says the opposite, which erodes trust in the whole sitemap. The three habits below keep it clean.
Every URL in the sitemap should be canonical, indexable, and return 200. No redirects, 404s, noindex pages, or non-canonical URLs.
The sitemap should mirror your indexable URL set: indexable pages missing from it get under-crawled; stale URLs in it waste attention. Generate it, don't hand-maintain it.
Reference it in robots.txt and submit it in Search Console. Keep it valid XML, under the 50,000-URL limit (use a sitemap index above that), with truthful lastmod dates.
The simplest test: would you want this exact URL to appear in Google? If not, it shouldn't be in the sitemap.
Everything that belongs in a clean, useful sitemap, and what to keep out.
Grounded in the real checks the crawler runs.
A sitemap should contain only the URLs you want indexed: canonical, indexable, 200-status pages. Exclude redirects, 404s, noindex pages, non-canonical URLs, and anything blocked by robots.txt.
The reason is consistency of signal. A sitemap mixing indexable and non-indexable URLs tells crawlers to index pages you have separately told them to ignore, and that contradiction devalues the whole file. On size, each sitemap holds up to 50,000 URLs or 50MB uncompressed; larger sites use a sitemap index pointing to child sitemaps.
A sitemap does not help rankings directly. It is a discovery aid rather than a ranking factor, and no page ranks better for appearing in one.
What it does is help search engines discover pages faster and understand which URLs you consider canonical. That matters most for large sites, new sites without many backlinks, and pages buried deep in the structure, where crawling alone may take a long time to reach everything. Declaring it in robots.txt and submitting it in Search Console makes sure it is actually found and used.
Include every page you want indexed, and nothing else. The sitemap and your indexable URL set should match exactly, in both directions.
Both kinds of mismatch cost you. An indexable page missing from the sitemap may be crawled less often and discovered later, which is why the audit flags those. Non-indexable URLs appearing in the sitemap send the contradictory signal described above and should never be there.
The lastmod date does matter, but only when it is accurate. A truthful lastmod helps crawlers prioritise genuinely updated pages over ones that haven't changed, which is exactly the prioritisation you want on a large site.
Its usefulness collapses if it isn't honest. If every URL shows today's date or a future date, the field carries no information and crawlers learn to ignore it entirely, including on the pages where it would have been true. The audit flags missing and future-dated lastmod for this reason.
Free to start. Find redirects, errors and non-canonical URLs hiding in your sitemap.
Start my free audit