An XML sitemap is a file listing the pages on your site that you want search engines to know about.
That is genuinely all it is. A list, in a format machines read, saying Here are my pages and here is when each was last changed. It sits at a predictable address, usually `/sitemap.xml` or `/sitemap_index.xml`, and search engines check it periodically.
What it is not is a ranking tool. Submitting a sitemap does not make pages rank, and it does not guarantee they will be indexed. It makes them easier to find, which is a smaller claim and the true one.
What is an XML Sitemap?
When it genuinely helps
- Large sites. Thousands of URLs where crawling everything through links alone takes time.
- New sites. Few external links pointing at you, so crawlers have little reason to arrive and less to follow.
- Poorly linked pages. Anything not reachable within a few clicks of your homepage. Though the better fix there is to link it properly, since a page nobody can navigate to is a page nobody reads.
- Frequently updated content. The `lastmod` value signals when something changed, which helps recrawling happen sooner.
- Media-heavy sites. Image and video sitemaps give explicit information about content that is harder to interpret from markup alone.
When it makes little difference
A well-linked twenty-page site will be crawled thoroughly regardless. The sitemap does no harm and is worth having, but expecting a change from adding one is expecting the wrong thing.
What belongs in it
Only URLs you want indexed. That constraint does more work than it sounds like.
Exclude anything that redirects, returns an error, is blocked in robots.txt, carries a noindex tag or canonicalises elsewhere. Each of those is a contradictory instruction: the sitemap says index this, and the page says do not.
A sitemap full of such contradictions signals carelessness about your own site, and it wastes crawl attention that could have gone to pages that matter.
Keep `lastmod` honest. Updating every date whenever anything changes anywhere trains search engines to disregard the field entirely.
The `priority` and `changefreq` values are largely ignored in practice. Setting everything to priority 1.0 conveys nothing.
Sitemap index files
Above 50,000 URLs or 50MB uncompressed, split into multiple sitemaps and list them in a sitemap index file.
Most content management systems do this automatically, splitting by content type. Your post sitemap, page sitemap and category sitemap sit under one index, which is also a useful way to spot whether a whole content type has been accidentally excluded.
Creating and submitting one
On WordPress, your SEO plugin almost certainly generates one already. Check what it includes and, more importantly, what it excludes, since defaults sometimes omit content types you want indexed or include archives you do not.
Submit it in Google Search Console and the equivalent for Bing. Reference it in your robots.txt with a `Sitemap:` line, which lets any crawler find it without being told.
Google’s documentation on building sitemaps covers the format and the limits.
What to check afterwards
Search Console reports how many submitted URLs were indexed. A large gap between submitted and indexed is worth investigating: it usually means thin content, duplication or pages competing with each other rather than a sitemap problem.
Watch for errors, which are commonly URLs that redirect or return errors. These accumulate quietly as a site changes and nobody prunes the list.
Where performance and environmental impact both apply, treat them as the same lever: reducing unnecessary data transfer and processing supports a faster experience while lowering estimated digital carbon, though environmental figures remain modelled rather than directly measured. A clean sitemap contributes modestly by not sending crawlers to pages that no longer exist.
Our search engine optimisation work checks sitemap accuracy as part of technical health, since contradictions between sitemap and page directives are common.