An XML sitemap lists the URLs you want search engines to know about. It aids discovery. It does not cause crawling, does not cause indexing, and does not make pages rank. Most sitemap problems come from expecting it to do one of those things.
What it actually does
- Tells search engines URLs exist, which helps on large sites and for pages with few internal links.
- Provides a last-modified signal that can influence recrawl priority.
- Gives Search Console a set to report indexation against, which is its most practical benefit.
That reporting value is underrated. Submitting a segmented sitemap means Search Console can tell you what proportion of each content type is indexed, which is far more actionable than a site-wide total.
What a good sitemap contains
- Only canonical URLs. Not parameter variants, not redirecting URLs, not pages that canonicalise elsewhere.
- Only indexable pages. Listing a noindexed URL is a contradiction and is reported as one.
- Only URLs returning 200. Dead entries waste crawling and dilute the signal.
- Accurate lastmod dates. Dates that update on every build regardless of change make the field worthless.
- Under the size limits, split into an index file where needed.
Segmenting it, which most sites do not
A single sitemap listing everything tells you the site is eighty percent indexed. Segmented sitemaps tell you which parts are not, which is the difference between knowing there is a problem and knowing where.
- Products, categories and content in separate files on a store.
- Services, locations and resources separately on a service site.
- Then compare submitted against indexed per segment in Search Console.
Common faults
- Auto-generated and never reviewed, so it lists whatever the plugin decided, including archives you excluded.
- Contains noindexed URLs, a direct contradiction between two signals.
- Contains redirecting URLs after a migration, because the sitemap was not regenerated.
- Not referenced in robots.txt, a small omission that costs nothing to fix.
- Stale after a restructure, pointing at URLs that no longer exist.
- Treated as a substitute for internal linking. A page listed only in a sitemap reads as unimportant.
That last point is the most consequential. Sitemaps aid discovery; internal links signal value. A page nothing links to will not be rescued by listing it.
What it will not fix
- Pages discovered but not crawled. They are already known; the constraint is capacity.
- Pages crawled and passed over. That is a content judgement.
- Crawl budget problems, which sitemaps do not increase.
- Ranking, which sitemaps have no bearing on.
Frequently asked questions
Do I need an XML sitemap?
Small, well-linked sites function without one. Large sites, stores and sites with poor internal linking benefit. The reporting value in Search Console makes it worth having regardless.
Will submitting it get my pages indexed?
No. It helps them be discovered. Indexing is a separate decision based on whether the page is worth including.
Should I include every page?
Only canonical, indexable pages you want found. Including filters, paginated views or noindexed pages contradicts your other signals.
How often should it update?
Automatically as content changes. What matters more is that lastmod dates reflect genuine changes rather than updating on every deployment.
Consulting CTA
If your sitemap contradicts your other signals or you cannot tell which parts of the site are underindexed, book an SEO consultation.