Part of the SiteMap Series
If you’ve ever set up a website, opened the settings panel of an SEO plugin, or read an article about how Google works, you’ve probably come across the word “sitemap”. It tends to show up alongside other technical terms like “crawl”, “index”, and “robots.txt”, often without anyone stopping to properly explain what a sitemap actually is.
That’s what this lesson is for.
We’re going to take this from the ground up. By the end, you’ll have a clear mental model of what a sitemap is, what it does, what it doesn’t do, and whether you need one. This is the foundation of the whole series, so I’m not going to rush it. Everything we build in later lessons sits on top of what we set up here.
Let’s start with the simplest possible definition.
A sitemap, in plain terms
Strip away all the technical wrapping, and a sitemap is one thing: a list.
Specifically, it’s a list of the pages on your website that you give to search engines so they know what exists. That is its entire purpose. The XML format we’ll see in a moment, the technical specifications we’ll cover later, the protocol behind it all, every detail in this series is just dressing on top of that simple idea.
A sitemap doesn’t do anything magical. It doesn’t fix broken websites. It doesn’t push your pages to the top of Google. What it does is hand over a list. You give the list to search engines. They use it to make sure they know what pages your site contains.
If the idea of a list still feels too abstract to picture, the next section makes it concrete.
The mental model
Here’s the easiest way I’ve found to picture what’s actually happening when a sitemap does its job.
Imagine you’ve just opened a new bookshop. You stack the shelves, put the kettle on, switch the open sign to green, and unlock the door. A customer wanders in. They drift past the cookbooks, get pulled into the travel writing display, browse the new releases for a few minutes, and eventually leave the shop without ever realising you had a whole basement floor dedicated to crime fiction.
That’s how search engines move through websites. They follow links. They wander from page to page. They miss things, especially the things that aren’t well-connected to the obvious places. A page sitting three clicks deep from your homepage, hidden behind a filter, with no other website linking to it, might never get found.
A sitemap is the equivalent of you handing the customer a printed map of the shop as they walk through the door. Here’s the ground floor. Here’s the basement. Here’s where the rare editions sit. The customer might still wander where they like, but now they at least know what exists.
That’s the simplest way to think about a sitemap. You’re handing search engines the floor plan of your site. They’ll still wander, follow links, peek into corners. But the sitemap makes sure they know about every page you want them to see.
With that picture in mind, we can now look at what a sitemap actually looks like as a file.
What a sitemap looks like
At this point you’re probably wondering what one of these “lists” looks like when it’s written down. Let’s see one.
The most common kind of sitemap is an XML sitemap, written in a format called XML. We’ll get into XML properly in lesson three, so don’t worry if the format looks unfamiliar right now. The point of showing it here is to make the idea real.
<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
<url>
<loc>https://example.com/</loc>
<lastmod>2026-05-27</lastmod>
</url>
<url>
<loc>https://example.com/about/</loc>
<lastmod>2026-05-20</lastmod>
</url>
</urlset>
Don’t worry about understanding every line of that yet. What I want you to see is the shape of it.
Two URLs on a website, each with a date next to it showing when the page last changed. That is a working sitemap. If you saved that text as a file, uploaded it to your site, and submitted the file’s address to Google Search Console, Google would know about both of those pages.
The file extension is .xml. The standard filename is sitemap.xml. The conventional location is the root of your domain, so the full web address usually ends up looking like https://yoursite.com/sitemap.xml. None of these conventions are strict rules. They’re just what crawlers expect by default.
Now that you’ve seen what one looks like, it’s worth pausing to clear up a few things people commonly get wrong about sitemaps before we go any further.
What a sitemap is not
There are a handful of misconceptions about sitemaps that come up constantly, and getting them wrong is what leads to wasted effort later. So before we move on to why sitemaps matter, let’s clear up what they’re not.
- The first misconception is that submitting a sitemap guarantees your pages will be indexed. It doesn’t. A sitemap tells search engines that a page exists. It does not tell them they have to put it in their index, rank it, or even visit it. They might. They often do. But if they decide a particular page isn’t worth indexing, the sitemap will not change their mind.
- The second misconception is mixing up XML sitemaps with HTML sitemaps. There’s a separate thing called an HTML sitemap, which is just a regular web page with links to other pages on the same site, designed for human visitors to browse. That’s a different tool, doing a different job. In SEO conversations, when people say “sitemap”, they almost always mean the XML kind. The two get confused often enough that we’ll dedicate the next lesson to clearing it up properly.
- The third misconception is that having a sitemap helps you rank higher in search results. It doesn’t. Having one will not improve your rankings, and not having one will not hurt them. A sitemap is about discovery, meaning helping search engines find your pages in the first place. Discovery and ranking are different things. One gets your pages noticed. The other decides where they appear once they have been noticed. Confusing them is one of the most common mistakes I see when reviewing other people’s SEO work.
- The fourth misconception is that sitemaps are how Google finds your pages. They’re usually not. Most of the time, Google finds pages by following links, both from pages on your own site and from other websites that link to you. The sitemap is more of a backup channel. It’s there to make sure nothing slips through the cracks, not to be the main way pages get discovered.
With those four misconceptions cleared up, the obvious next question is, given all of that, why does anyone bother having a sitemap at all?
Why a sitemap still matters
If a sitemap doesn’t guarantee indexing, isn’t for humans, doesn’t improve rankings, and isn’t even the primary way Google finds your pages, you could be forgiven for asking whether they matter at all.
The honest answer is that sitemaps still earn their keep, but for reasons that are smaller and more practical than most SEO content suggests. Three reasons stand out, and I’ll walk through them in roughly the order I’d argue they matter in practice.
- The first reason is finding new pages quickly. Imagine you publish a fresh blog post this morning. If that post isn’t linked from your homepage or from one of your category pages, Google might not stumble across it for days or even weeks. By including it in your sitemap, you surface it immediately. The same goes for pages buried deep inside your site or pages that only appear after a visitor clicks a filter or runs a search. The sitemap is your way of telling search engines “these exist, please come and look”.
- The second reason is crawl budget. This phrase sounds technical, but the idea behind it is simple. Search engines don’t crawl every page of your site every time they visit. They have limits, especially when sites get large. When your sitemap includes accurate dates showing when each page last changed, search engines can spend their limited time on the pages that have actually been updated, rather than wasting it on pages that haven’t been touched in months. For small sites this barely matters. For large sites it can make a real difference.
- The third reason is the one that most SEO content under-sells, and it’s the one I’d argue matters most in everyday practice. Once you submit a sitemap to Google Search Console, Google gives you a report back. The report tells you how many of the URLs in your sitemap were indexed, how many were not, and the specific reasons for the ones that weren’t. That kind of feedback is genuinely hard to get any other way. For anyone doing Technical SEO seriously, the diagnostic insight you get from a sitemap report is reason enough to have one, even if you don’t really need it for discovery.
That covers what a sitemap is, what it isn’t, and why it still earns a place in your setup. The last question to answer before we close this lesson is whether you, specifically, need one.
So do you actually need one?
This is the practical question every reader of this lesson eventually arrives at, so let’s address it before signing off.
The simple answer is that if your site has more than around ten pages, publishes new content with any regularity, or contains pages that aren’t tightly linked from your main navigation, you want a sitemap. That description covers almost every commercial website, every blog, every content-driven platform, and every e-commerce site you’re likely to come across.
If you’ve got a small five-page brochure site with a clean navigation menu linking to all five pages, then Google will find every page just by following your menu. You can skip the sitemap and nothing will break. The trade-off, though, is that you lose the Search Console diagnostic visibility we just talked about. For that reason alone, even very small sites often benefit from having one.
We’ll come back to this question of “do I need a sitemap?” more fully in lesson four, where the answer changes depending on the type of site you’re running. For now, the working assumption is: if you take your site seriously enough to be reading this lesson, you probably want one.
Where this leaves us
We’ve covered the foundation. A sitemap is a list of URLs you give to search engines so they know what exists on your site. The XML format is just the agreed convention for how to write that list down. Sitemaps don’t guarantee indexing or improve rankings, but they help with discovery, crawl efficiency, and diagnostics in Search Console. Almost every real website benefits from having one.
In the next lesson, we’ll map the territory properly. There are several types of sitemaps, not just one, and knowing the landscape upfront makes everything that follows in the series easier to grasp.
Up next: Types of Website Sitemaps and When Each One Matters →
This is Lesson 1 of The Sitemap Series, a Technical SEO series on sitemaps from first principles, built for the AI Search era.