What Is a Sitemap (and Does Your Site Need One)?

If you have ever read SEO advice, you have probably been told to “submit your sitemap” — often without anyone explaining what a sitemap actually is, where it lives, or whether your site even needs one. This guide answers all three questions in plain language, shows you a real example line by line, and ends with a free way to check a sitemap file for errors.

The short answer: a map you hand to search engines

A sitemap is a file that lists the pages and other files on your website and tells search engines what is there. Think of it as a map you hand to a visitor who is about to explore a large building: instead of wandering every corridor hoping to find each room, they get a list of the rooms that matter, in one place.

Search engines can usually find your pages on their own by following links from one page to the next. A sitemap simply makes that discovery faster and more reliable, especially for pages that are hard to reach through links alone. It also tells search engines when each page was last updated, and can describe special content such as images, videos and news articles.

One thing to understand from the start: a sitemap is a hint, not a command. Submitting one does not guarantee that search engines will crawl every page you list, index them, or rank them. Indexing is a separate decision a search engine makes about each page, based on the page itself. A sitemap gets your pages into consideration; it does not argue their case.

Three things called “sitemap” — and which one this article means

The word “sitemap” is used for three different things, and mixing them up causes most of the confusion around the topic:

• An XML sitemap is a machine-readable file written for search engines, usually found at an address like yoursite.com/sitemap.xml. This is the kind SEO advice refers to, and the subject of this article.
• An HTML sitemap is an ordinary web page that lists links to the main sections of a website, written for visitors who cannot find something through the navigation — a table of contents, not a file of code.
• A design sitemap is a diagram drawn before a website is built, showing the planned pages and how they connect. It is a planning document for the people building the site, and search engines never see it.

From here on, “sitemap” without a qualifier means the XML kind.

What’s actually inside an XML sitemap

An XML sitemap is written in XML, a text format built from tags. Each page gets its own entry, and each entry needs at least one piece of information: the page’s full address. Here is a small example for a fictional bakery website, with every line explained afterwards:

<?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-10-20</lastmod>
  </url>
  <url>
    <loc>https://example.com/menu/</loc>
    <lastmod>2026-10-18</lastmod>
  </url>
  <url>
    <loc>https://example.com/contact/</loc>
    <lastmod>2026-10-12</lastmod>
  </url>
</urlset>

Reading it line by line:

• The first line declares the file as XML in UTF-8 encoding, the character encoding the format requires.
• The <urlset> tag opens the list and names the sitemap protocol, so a search engine knows how to read what follows.
• Each <url> block describes one page. Inside it, <loc> holds the page’s full, absolute address — including the https:// part, not a relative path.
• The <lastmod> tag is optional, and holds the date the page last changed, in year-month-day form. It is the one optional tag that search engines actually pay attention to, and only when it is honest (more on that below).
• The closing </urlset> tag ends the list.

Two more tags sometimes appear in older examples: <changefreq>, which claims how often a page changes, and <priority>, which claims how important a page is relative to the rest of the site. Google ignores both, so leave them out entirely. Writing a priority of 1.0 for every page does not make any of them rank higher.

Large sites need more than one file. A single sitemap file can hold at most 50,000 URLs or 50 MB uncompressed, whichever limit is reached first. Sites that pass either limit split their pages across several files and list those files in a sitemap index — a parent file that points to other sitemap files instead of to pages. This very site works that way: its index lists separate sitemaps for its pages and its blog posts, so a search engine can check each section on its own.

What a sitemap does — and what it cannot do

It helps to be precise about the job, because inflated claims are where sitemap advice usually goes wrong.

What it does:

• It helps search engines discover pages they might otherwise miss, particularly new pages, pages with few links pointing to them, and pages on large or complex sites.
• It tells search engines when pages last changed, which helps them decide which pages are worth re-crawling.
• It can describe images, videos and news articles on your pages, so search engines can understand that content too.

What it cannot do:

• It cannot force a search engine to crawl a listed page, index it, or rank it. A sitemap is a suggestion about where to look, not an instruction.
• It cannot fix a bad page. If a page is thin, duplicated, blocked or broken, listing it will not save it — and listing broken or blocked pages can make your site look neglected.
• It cannot replace internal linking. Clear navigation and links between your own pages remain the main way search engines find pages and understand how they relate.
• It cannot make up for missing content. A sitemap lists what exists; it does not create traffic on its own.

The honest version of the promise is this: a good sitemap removes discovery as a reason your pages are not found. Everything after discovery — crawling, indexing, ranking — still depends on the pages themselves.

Does your site need one?

Google’s own guidance gives a practical decision rule rather than a blanket yes or no. You probably need a sitemap if any of these describe your site:

• Your site is large. On a big site it is hard to guarantee that every page is linked from at least one other page, so some pages risk never being discovered.
• Your site is new and few other sites link to it. Search engines discover pages partly by following links from pages they already know, so a brand-new site with almost no incoming links is easy to miss.
• Your site has a lot of rich media or news content. Sitemaps let you describe videos, images and news articles in a way that plain links cannot.

You might not need one if all of these are true:

• Your site is small — Google puts the threshold at roughly 500 pages or fewer that you want in search results.
• Your site is comprehensively linked internally — every important page can be reached by following links from the homepage.
• You do not have many media files or news pages that you want to appear in search results.

In practice, most sites end up with a sitemap anyway, because the platforms they run on generate one automatically. WordPress sites with an SEO plugin, and stores on Shopify or Wix, typically already have one — which leads to the next question: how do you find it?

How to find and check a sitemap

Finding a site’s sitemap takes about a minute, and the steps work for your own site or anyone else’s:

1. Check robots.txt first. Open yoursite.com/robots.txt and look for a line starting with Sitemap:. Site owners usually declare their sitemap there, and that line gives you the exact address. (For the full story on that file, see our guide to what robots.txt is.)
2. Try the usual addresses. If robots.txt names nothing, try yoursite.com/sitemap.xml and then yoursite.com/sitemap_index.xml. Most generators use one of the two.
3. Open a child file if you find an index. A sitemap index contains no page addresses itself — it lists other sitemap files. Open one of those child files before deciding that pages are missing.

Finding the file is only half the check. A sitemap can open in your browser and still be broken: one unclosed tag, one unescaped & in a URL, or one wrong character encoding can make the whole file unreadable to a search engine. That is exactly the kind of error a paste-in check catches. Our free XML Sitemap Validator checks sitemap XML you paste in: it confirms whether the code is well-formed and follows the sitemap structure, counts the URLs inside, and reports the first error it finds, which is usually the fastest route to the underlying problem. It works on pasted XML only — it does not visit the listed addresses, so it cannot tell you whether they exist, redirect or return errors; those questions belong to your server logs and Search Console.

Seven sitemap mistakes that hurt

1. Listing pages you do not want indexed. A sitemap should contain only canonical, indexable pages. Listing pages blocked by robots.txt, marked noindex, or behind a login sends search engines contradictory instructions.
2. Listing redirects and broken pages. Every address in a sitemap should be the final, working URL. A file full of redirects and errors tells search engines the site is not maintained.
3. Faking or refreshing lastmod. Search engines use lastmod only when it is consistently accurate. Updating it on every build, or stamping every page with today’s date, teaches them to ignore it entirely.
4. Filling in priority and changefreq as if they matter. Google ignores both. Time spent tuning them is time not spent on something that works.
5. Broken XML. One unclosed tag or one unescaped & can invalidate the whole file. Always validate after generating or hand-editing a sitemap.
6. Never submitting the index. If your site uses a sitemap index, submit the index itself in Search Console — the child files are discovered from it. Submitting only a child file leaves the rest of the site undeclared.
7. Expecting indexing from submission. Submission is the start of the process, not the end. If a listed page is not indexed, the reason is almost always the page itself, not the sitemap.

How to submit yours

If you own the site, submission takes two minutes and you only need to do it once per sitemap:

1. In Google Search Console, open Indexing, then Sitemaps, enter your sitemap’s path (for example sitemap.xml) and click Submit. The report then shows when Google last read the file and how many URLs it discovered — a useful diagnostic in itself, because a discovered count far below your page count means the file is incomplete.
2. Add a Sitemap: line to your robots.txt, so every crawler — not just Google — can find the file.

That is it. Do not resubmit the same unchanged file: Google rechecks known sitemaps on its own, and resubmitting does not move you up any queue. Resubmit only after a structural change, such as a site move or a new sitemap index.

FAQ

Does a sitemap improve my rankings?
No, not directly. A sitemap helps search engines discover your pages; rankings depend on the pages themselves, their content and their signals. Think of it as making sure your pages are in the room, not as an argument for why they should win.

Can a sitemap hurt my site?
A correct one cannot. A careless one can: listing blocked, redirected or broken pages, or stale dates, gives search engines a worse picture of your site than no sitemap at all.

How often should I update my sitemap?
Whenever your pages change. If your platform generates it automatically, this happens on its own. If you maintain one by hand, update it when you publish, remove or move a page — and keep lastmod honest.

Do I need a separate sitemap for images or videos?
Not necessarily. Image and video entries can live inside your main sitemap. Separate sitemaps for them are a choice for large media-heavy sites that want to track each type on its own.

Is an HTML sitemap page a substitute for an XML sitemap?
No. An HTML sitemap page helps visitors navigate; search engines read the XML file. A site can have both, and they serve different readers.

Check your sitemap before you submit it

A sitemap is one of the cheapest pieces of SEO housekeeping there is: a single file, generated automatically on most platforms, that makes sure search engines can find every page you want found. The mistakes that undo it are equally cheap to avoid — list only real, working, canonical pages, keep your dates honest, validate the file, and submit it once.

Before you submit yours, run it through our free XML Sitemap Validator to catch the broken tag or bad character that would make the whole file unreadable. And if you are sorting out the file that points crawlers at your sitemap in the first place, our robots.txt guide explains that half of the setup. For everything else on the site, browse the full directory at all tools or the SEO tools category.