What Is an XML Sitemap and Does Your Website Need One?

An XML sitemap is a file that lists the URLs on your website, helping search engines discover and crawl your content more efficiently. Think of it as a map you hand to Google — rather than leaving it to find every page by following links, you give it a comprehensive list of where everything is.

While Google is capable of crawling most websites without a sitemap, having one is considered best practice and becomes increasingly valuable as your site grows. This guide explains exactly what an XML sitemap is, what it should contain, and the situations where it makes a meaningful difference.

What an XML sitemap contains

An XML sitemap is a structured text file written in XML format. At its most basic, it contains a list of URLs. More detailed sitemaps also include optional metadata for each URL: the date it was last modified, how frequently it changes (daily, weekly, monthly), and a priority score relative to other pages on your site.

Google uses this information as a signal — not a directive. If you tell Google a page changes daily but it never actually changes, Google will notice the discrepancy and reduce its trust in your sitemap data. For this reason, it’s better to provide accurate metadata or omit it entirely rather than guess.

Large websites can also use a sitemap index file: a single XML file that points to multiple individual sitemaps, each covering a different section of the site. This is necessary because Google limits individual sitemaps to 50,000 URLs and 50MB. E-commerce sites with large product catalogues often use separate sitemaps for products, categories, and blog content.

What to include — and what to leave out

Your sitemap should contain the URLs you want indexed: your main pages, service or product pages, blog posts, and any other content you want to appear in search results. It should not contain URLs you’ve set to noindex, URLs behind login walls, redirect URLs, or URLs you’ve blocked in robots.txt. Including non-indexable URLs in your sitemap sends conflicting signals to Google.

Canonical URLs are particularly important to get right. Only include the canonical version of each page — if a page has a canonical tag pointing elsewhere, include the destination URL, not the duplicate. Submitting duplicates to your sitemap undermines the canonical signal you’re trying to send.

Pagination is a common area of confusion. For paginated series (page 2, page 3 of a blog archive), opinion is divided on whether to include them. Google’s general guidance is that you can include them, but they’re lower priority. The key pages — your most important standalone content — are what sitemaps are really for.

Does your website actually need a sitemap?

Google says sitemaps are most useful for large websites, new websites with few external links, sites with rich media content, and sites with lots of pages that aren’t well linked internally. If your site is small (under 500 pages), well-structured, and has good internal linking, Google will almost certainly find all your content without a sitemap.

However, a sitemap is easy to create — most CMS platforms and SEO plugins generate one automatically — and has no downside. Even for small sites, having a sitemap and submitting it to Google Search Console means you can monitor indexing status and spot crawl errors more easily. The small effort is almost always worth it.

For new websites especially, a sitemap is valuable. Without external links pointing to your pages, Google relies more heavily on sitemaps to discover your content. Submitting a sitemap shortly after launch can accelerate the time it takes for your pages to appear in search results.