Do I need a sitemap.xml?
Not strictly. It helps discovery on larger or poorly-linked sites, and it costs nothing — but it will not fix a site that cannot be crawled.
No site strictly requires one. It helps when a site is large, new, poorly interlinked, or contains pages that are hard to reach by following links. It is close to free to generate, so the practical answer is usually yes — while remembering it aids discovery, not ranking.
What it does and does not do
- Does: tell search engines which URLs exist, so they can be discovered without following a link chain.
- Does: supply a
lastmoddate that helps engines prioritise recrawling. - Does not: affect ranking. A listed page does not rank better for being listed.
- Does not: guarantee indexing. Listing a page is a suggestion, not a commitment.
- Does not: override a block. A page in your sitemap and disallowed in robots.txt is still blocked, and the contradiction is itself a fault.
When it genuinely matters
- Large sites, where crawl budget is real and discovery through links is slow.
- New sites with no inbound links, where nothing would otherwise lead a crawler to you.
- Sites with deep pages more than three or four clicks from the homepage.
- Sites where navigation is client-side, so links are not discoverable in the HTML.
- Sites with content that is not linked from anywhere — archives, standalone landing pages.
For a well-linked twenty-page site, the sitemap adds very little. It still costs nothing.
Getting it right
- Serve it at
/sitemap.xml, or anywhere as long as you reference it. - Reference it from robots.txt:
Sitemap: https://example.com/sitemap.xml. - Include only canonical, indexable URLs that return 200.
- Use accurate
lastmoddates. Setting them all to today, every day, is noticed and discounted. - Keep each file under 50,000 URLs and 50 MB uncompressed; use a sitemap index above that.
- Submit it in Search Console, which also reports parsing errors.
Priority and changefreq
Both are effectively ignored by Google. priority was always relative and self-declared, so it carried no information. changefreq was routinely inaccurate. Include them if your generator emits them; do not spend time tuning them. lastmod is the one field that is genuinely used, and only if it is honest.
What our audit reports about this
Every item below is measured directly, not inferred. Run it against your own site and the result names the exact rule or header responsible.
- Whether a sitemap exists, parses, and is referenced from robots.txt.
- Every URL it lists, with whether each is reachable and whether it is linked from the page audited.
- Whether listed URLs contradict robots.txt or carry noindex.
- Whether lastmod dates are present and plausible.
For agents and scripts, the same measurement is at
/api/v1/discoverability?url=yoursite.com —
see the API documentation.
Related questions
Does a sitemap improve ranking?
No. It is a discovery aid. A page ranks on its merits whether or not it appears in a sitemap.
Should I include images and videos?
Image and video sitemap extensions exist and are worth using if visual content is a meaningful source of traffic for you. For most sites the ordinary sitemap is enough.
How often should it be regenerated?
Whenever content changes. Most CMSs and static generators do it automatically on publish, which is the correct arrangement — a manually maintained sitemap goes stale within weeks.
Read next
Why is my website not showing on Google?
Work through it in order — not indexed, indexed but not ranking, or ranking but not for anything you noticed.
ReadHow do I fix robots.txt blocking Google?
How to read the file correctly, what the precedence rules actually are, and the three mistakes that cause almost every accidental block.
ReadWhat is a canonical URL and why does it matter?
It tells search engines which version of a page is the real one. Get it wrong and you can de-index your own site.
ReadHow can I improve my SEO?
The work that actually moves rankings, ordered by effect per hour spent — and the popular tasks that do almost nothing.
Read