Asset 20 8 2
Does AI recommend your business? Run the free check →

Join 15,000 business owners, marketers and entrepreneurs. The Sunday newsletter you'll be annoyed only arrives once a week.

Article

What Is a Sitemap and Do You Need One?

If you are skim reading
The short version: a sitemap is a file that lists every page on your website so search engines can find them faster, and most small sites need one but won't see much change from it, while large or poorly linked sites can see a real difference within weeks.

The short version: a sitemap is a file that lists every page on your website so search engines can find them faster, and most small sites need one but won't see much change from it, while large or poorly linked sites can see a real difference within weeks.

I know that's not the exciting answer. Everyone wants sitemaps to be some secret SEO lever. They're not. They're plumbing. Useful plumbing, but plumbing.

What a sitemap is

A sitemap is usually an XML file, something like yoursite.com/sitemap.xml, that lists the URLs on your site along with a few extra bits of information: when each page was last updated, sometimes how important it is relative to other pages, sometimes how often it changes. Search engines like Google and Bing read this file to understand what pages exist and where to send their crawlers.

Think of it as a table of contents you hand to a librarian, except the librarian is a bot that visits millions of sites a day and has limited patience for any one of them.

There's also a human-readable version some sites build, an HTML page listing all their content for visitors, but when people ask "what is a sitemap" in an SEO context, they almost always mean the XML one. That's the one Google Search Console wants, and that's the one this post is about.

What's inside the file

A basic sitemap entry looks like this in plain terms: a URL, a last-modified date, and optionally a priority value from 0.0 to 1.0. In practice Google has said for years it mostly ignores the priority and change frequency fields, it cares far more about the URL list and the last-modified date. So if you're hand-building one, don't waste time agonising over whether your pricing page is priority 0.8 or 0.9. Nobody at Google is reading that number closely.

What does matter is accuracy. If your sitemap lists pages that return a 404, or pages blocked by robots.txt, or old URLs you deleted eighteen months ago, you're sending mixed signals. Clean the file or don't bother having one.

Do you need one

Here's the uncomfortable bit nobody wants to say plainly: if you run a small site with good internal linking, say a 12-page consultancy website where every page is reachable within two clicks from the homepage, a sitemap will change almost nothing. Google already finds those pages through your navigation and footer links. I've seen people treat sitemap submission like it's the SEO equivalent of a magic password, and it isn't. It's a convenience, not a requirement.

Where a sitemap earns its keep:

  • Large sites, anything over a few hundred pages, where crawlers might miss deep pages without a direct pointer
  • New sites with few external links pointing in, because sitemaps help crawlers discover content faster than waiting for backlinks
  • Sites with poor internal linking, think a blog with 400 posts but a homepage that only links to the latest 10
  • E-commerce sites where products get added and removed constantly and you want fast discovery and de-indexing
  • Sites using heavy JavaScript rendering, where crawlers sometimes struggle to follow links the normal way

If none of that describes your site, you still might as well have one. It costs nothing, takes ten minutes, and there's no scenario where a clean, accurate sitemap hurts you. The honest answer is: low effort, low but real upside, so just do it.

A worked example

Say you run a furniture retailer with 1,800 product pages across 40 categories, and you've just migrated to a new platform. Before the migration, your old site had 1,800 URLs, each linked from category pages showing 24 products per page with pagination. After migration, your new category pages only show 12 products per page by default, and the pagination links use JavaScript buttons instead of plain href links.

Within three weeks, your organic traffic to product pages drops 30 percent. Why? Crawlers can't click a JavaScript button the way a person can, so half your catalogue effectively vanished from the crawl path. A sitemap listing all 1,800 product URLs directly, submitted through Search Console, would have been your safety net. It wouldn't fix the JavaScript pagination problem, but it would keep every product page discoverable while you fix the underlying navigation issue. That's the real value of a sitemap: it's insurance against your own site architecture mistakes, not a ranking booster on its own.

How to build one

You have a few paths, depending on how your site is built:

  • WordPress with Yoast or RankMath: both generate and auto-update an XML sitemap for you, usually at yoursite.com/sitemap_index.xml
  • Shopify: generates sitemap.xml automatically, you don't need to do anything
  • Squarespace and Wix: both auto-generate one, check their help docs for the exact URL pattern
  • Custom-built sites or ones without a plugin: you'll need to generate the file manually or with a tool

If you fall into that last group, don't hand-code 400 URL tags in a text editor. Use a free XML sitemap generator where you paste your URLs and download the file, upload it to your site's root directory, and you're done in under fifteen minutes. If you're choosing between planning tools for a larger site rebuild, it's worth comparing sitemap planners and AI builders rather than defaulting to whatever your developer suggests first.

Work with me

Want AI doing the heavy lifting in your marketing?

I build the systems that handle the boring 80 percent, so you get your week back. Done properly, with the human kept in.

Submitting it and checking it's working

Having a sitemap file sitting on your server does nothing on its own if no one tells Google it exists. The step people skip is submission. Here's the process:

  • Log into Google Search Console for your verified property
  • Go to the Sitemaps section in the left menu
  • Enter the path, usually just "sitemap.xml", and click submit
  • Wait, Google typically processes it within a few hours to a couple of days
  • Check back for errors: "Couldn't fetch" usually means a permissions or server issue, "Has errors" means specific URLs inside the file are broken

For the full walkthrough on reading what the report tells you once it's live, see this piece on submitting a sitemap and reading the Search Console report. It covers the specific error messages you'll see and what each one means for your indexing.

If you're inheriting a site someone else built, or you're auditing a competitor, you might need to find their sitemap without access to their backend. There's a straightforward method covering this in the guide on finding a website's sitemap on any CMS, which usually comes down to checking robots.txt first since most sites declare their sitemap location there.

What a sitemap won't do

It won't improve your rankings directly. It won't fix thin content. It won't make Google index pages it has already decided are low quality or duplicate. People confuse "crawled" with "ranked" constantly, and a sitemap only ever helps with the first part. If your product pages are 40 words of manufacturer description copied from ten other retailers, a sitemap gets Google there faster, it just gets to see the same weak page faster too.

It's also worth separating this from the newer conversation around AI crawlers and large language models reading your site. That's a different file entirely, and if you're setting up your technical SEO in 2026 it's worth understanding what llms.txt is and whether your site needs one alongside your standard sitemap, since AI tools like ChatGPT and Perplexity use different signals to decide what to read and cite.

The maintenance nobody mentions

A sitemap isn't a set-and-forget file if you're managing it manually. Every time you delete a page, merge content, or restructure categories, your sitemap can quietly go stale, still listing pages that no longer exist. Most CMS plugins handle this automatically. If yours doesn't, put a quarterly check in your calendar: open the file, spot-check ten URLs, confirm they resolve. It takes five minutes and it's the kind of small maintenance task that separates a tidy technical setup from the slow rot most small business sites accumulate over two or three years.

And while you're in there checking technical basics, it's worth a related gut check on tracking: a lot of businesses assume their analytics setup is fine and never revisit it, which is its own blind spot worth reading about in this piece on whether you need to add Google Analytics code to every page.

Frequently asked questions

Does every website need a sitemap?

Not strictly, a small site with clean internal linking will likely get crawled fine without one, but there's no downside to having one, so most sites should just set it up.

Will submitting a sitemap improve my Google rankings?

No, a sitemap only helps search engines find and crawl your pages faster, it has no direct effect on where those pages rank once indexed.

How often should a sitemap update?

If you're using a CMS plugin like Yoast or a platform like Shopify, it updates automatically whenever you publish or remove content, manual sitemaps should be checked and regenerated every time you make structural changes to the site.

What's the difference between an XML sitemap and an HTML sitemap?

An XML sitemap is built for search engine crawlers and submitted through tools like Google Search Console, an HTML sitemap is a visible page on your site listing links for human visitors, and most businesses only need the XML version for SEO purposes.

Run a business, a brand or a blog? I feature tools, products and expert guest posts for an audience of 15,000. See how it works

Published and maintained by the Lilach Bullock team, covering marketing, AI and business growth.
Your buyers are asking AI who to use. Does it say you?

See for free whether ChatGPT, Claude, Perplexity, Gemini and Google name you, and get the plan to become the answer.

Check my AI visibility →
Sundays only

Get the Sunday newsletter.

One email a week. AI experiments, marketing tactics, and the workflows Lilach is building right now in her own business.

Subscribe free

Let’s get your marketing running on AI.

Book a free 30-minute call

We figure out what you need, where AI fits in, and what working together would look like.

Book the call →

Or take the 30-second calculator

You’ll see the hours and the money quietly leaking out of your week, and the three workflows worth building first.

Take the calculator →

Or grab the free AI resource library

Prompt packs, templates, checklists, and swipe files. The exact tools I build for paying clients. Yours, free.

Get the library →
Keep reading

More from the blog.