What is a sitemap and why do I need one?

Q: What is a sitemap and why do I need one?

A sitemap lists the URLs you want search engines to find. Large, new and media-heavy sites gain most; a small, well-linked site may not need one.

A sitemap is a file, usually XML, that lists the pages on your site you want search engines to know about, often with the date each one last changed. It helps Google discover URLs it might otherwise miss and crawl your site more efficiently. Google says a small site with good internal links may not need one, but large sites, new sites with few links pointing to them, and sites rich in video or images benefit most.

What does a sitemap look like?

The most common format is XML. A minimal file with one page looks like this:

<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
  <url>
    <loc>https://www.example.com/pricing</loc>
    <lastmod>2026-09-28</lastmod>
  </url>
</urlset>

Each <url> entry holds one full address in <loc> and, optionally, the date of its last meaningful change in <lastmod>. Google also accepts RSS or Atom feeds and plain text files with one URL per line, and XML sitemaps can carry extra details for images, videos and news articles.

Do I need a sitemap?

Google's sitemaps overview gives a clear rule of thumb:

A sitemap is likely to help if	You may not need one if
Your site is large	Your site is small: about 500 pages or fewer that you want in search results
Your site is new and few other sites link to it	Every important page is reachable through links from your other pages
You publish a lot of video or images, or appear in Google News	You have no media or news content you need found separately

Even when it is optional, a sitemap costs little, most platforms generate one for you, and it gives you a per-file report in Search Console showing whether Google could read it.

What a sitemap does not do

It does not guarantee indexing. Google says plainly that not every item in a sitemap will be crawled and indexed, and its guide to building sitemaps calls submitting one "merely a hint".
It does not boost rankings. It helps Google find pages; whether they rank depends on the pages.
It does not replace internal links. Google mainly discovers pages through links, so a page listed only in the sitemap is still poorly connected.
It does not set crawl frequency. Google ignores <priority> and <changefreq>. It uses <lastmod> only when your dates are consistently accurate, so update it for real content changes, not for a new copyright year.

Which URLs belong in it?

List the URLs you want to appear in Google's results, in their canonical form. In practice that means pages that load with a 200 status: leave out redirects, pages marked noindex, duplicates and URLs blocked by robots.txt. One sitemap holds up to 50,000 URLs or 50 MB uncompressed; beyond that, split it and list the parts in a sitemap index file.

Where to go next

How do I create a sitemap? covers platform-generated sitemaps, generators and writing one by hand.
How do I submit a sitemap to Google Search Console? walks through the Sitemaps report.
What does "Sitemap could not be read" mean? helps when Google cannot fetch it.

How AutoPSEO helps

Sitemap Performance joins each sitemap's URL list with your Search Console data, showing the clicks each sitemap earns, how many of its URLs got no click, and how many never appear in Search Console at all. When the content engine starts on your site, its scan reads robots.txt and every sitemap to build an inventory of the pages you already have, so it does not write an article you have already published.