What is a sitemap.xml — and does your site need one?

The name is literal: a map of your site. But it's worth being precise about what it does and doesn't do, because a sitemap is often the first thing an SEO checklist asks about — and one of the most misunderstood.

What does a sitemap actually do?

Search engines find pages mainly by crawling: they fetch a page, follow its links, fetch those pages, follow their links, and so on. That works well for pages that are well connected. It works poorly for pages that are new, deeply buried, or barely linked — a fresh blog post, a page only reachable from a menu that's rendered by JavaScript, a section nothing else points to.

A sitemap closes that gap. It tells crawlers directly:

• Which pages exist — the full list of URLs you consider worth indexing.
• When each page last changed (the lastmod field) — so crawlers can prioritize revisiting pages that actually changed instead of re-crawling everything blindly.
• Roughly how pages relate in importance (the optional priority field) — a weak hint that some pages matter more than others.

What a sitemap doesn't do is just as important: it doesn't guarantee indexing, it doesn't improve rankings by itself, and it doesn't override anything. Google treats it as a hint, not a command. A page in your sitemap can still be skipped; a page missing from it can still be found through links.

What does a sitemap look like?

It's a plain XML file, usually at yourdomain.com/sitemap.xml. A minimal entry looks like this:

<url>
  <loc>https://example.com/services</loc>
  <lastmod>2026-07-01</lastmod>
</url>

One <url> block per page. You can look at yours right now: type your domain followed by /sitemap.xml into your browser. If you get a page full of structured text listing your URLs, you have one. If you get a 404, you don't — or it lives at a non-standard address declared in your robots.txt.

What belongs in it (and what doesn't)?

In: every page you'd want someone to land on from a search result — your homepage, service pages, blog posts, location pages, in every language you publish.

Out: pages that shouldn't appear in search results. Thank-you pages, internal search results, login pages, cart pages, duplicate URL variants, and legal boilerplate (a privacy policy ranks for nothing and dilutes the signal). A sitemap full of junk URLs makes the useful hints weaker.

Two rules matter more than the rest:

1. Only canonical, working URLs. Every URL in the sitemap should return the page itself — not a redirect, not an error. Sitemaps full of redirecting or broken URLs teach crawlers to trust yours less.
2. Keep it automatically up to date. A sitemap maintained by hand goes stale the day someone forgets to update it. It should be generated from the site's actual content, so a new page appears in it the moment the page goes live. (This is how ShiftPress sites work — the sitemap regenerates on every publish, so it can't drift out of sync.)

How do search engines find your sitemap?

Two ways, and you should use both:

• Declare it in robots.txt — a line like Sitemap: https://example.com/sitemap.xml in the small text file at your domain root that every crawler reads first.
• Submit it in Google Search Console (and Bing Webmaster Tools). This is more than a submission: Search Console then reports how many of the sitemap's pages were actually indexed, and why others weren't — one of the most useful free SEO diagnostics there is.

After a site migration, resubmitting the sitemap is one of the first things to do: it tells Google to come look at the new structure right away rather than waiting for a routine crawl.

Frequently asked questions