Does my website need an XML sitemap?

What a sitemap does and doesn’t do

An XML sitemap is a file listing the URLs you want search engines to know about, often with the date each was last changed. It helps crawlers discover pages, especially ones that aren’t well linked internally.

It doesn’t force indexing and it doesn’t improve rankings directly. Google treats it as a hint. If a page is thin or blocked, being in the sitemap won’t change that. Think of it as a delivery list, not a recommendation.

When it matters more

Google’s own guidance is that small sites with good internal linking may not need one. In practice, I add one to every site anyway because it costs nothing and makes problems easier to spot.

It matters more when the site is new and has few links pointing to it, when you publish regularly, when you have many pages like location or product pages, or when some pages sit deep in the structure. It’s also how Search Console tells you how many of your submitted pages are actually indexed.

Getting it right

Include only pages you want indexed: canonical, live URLs that return a 200 status. Leave out redirects, 404s, noindexed pages, thank-you pages and duplicates. A sitemap full of junk sends mixed signals.

Reference it in your robots.txt with a Sitemap: line, and submit it under Sitemaps in Search Console. Wix, Squarespace and Shopify create one automatically. WordPress does too, and SEO plugins extend it. On a custom site it should be generated at build time so it never falls out of date.

Every site I build generates its sitemap during the build, from the same list of pages that gets prerendered, so it can’t drift out of sync. It’s referenced in robots.txt and submitted in Search Console on launch day.

A few weeks later I compare submitted against indexed. If there’s a gap, the sitemap has done its job: it’s shown me exactly which pages Google is hesitating on.