SEO

What Is a Sitemap and Why Does Your Website Need One?

You publish a new page, wait a week, search Google for it, and find nothing. The page exists. The content is good. Google just never found it. A sitemap is the simplest fix for that: a small file that hands Google a list of every page you want found, instead of leaving the search engine to stumble across them on its own. This guide explains what a sitemap is in plain English, the two types that exist, when one actually matters, and how to set one up without touching a line of code.

The Short Answer: What a Sitemap Actually Is

A sitemap is a file that lists the important pages on your website so search engines can find them and add them to their index. Think of it as a table of contents you hand directly to Google.

When you search Google, you are not searching the live web. You are searching Google's index, the pages it has already found and stored. If a page never makes it into that index, it cannot show up in search results, no matter how good the content is. A sitemap is one of the two main ways pages get in. The other is links, and a sitemap is the backup route that catches whatever the links miss.

That backup route matters, because Google's crawler does not always find pages: pages buried deep in your navigation, pages nothing links to, and pages on a brand-new site can sit undiscovered for weeks. Our guide to getting your website on Google covers the full indexing picture.

XML vs HTML Sitemaps: Two Files, Two Different Jobs

The word "sitemap" covers two different things. They share a name, but they serve different audiences.

An XML sitemap is for search engines. It is a machine-readable file, usually at yoursite.com/sitemap.xml, that lists your URLs in a format Google and Bing can read. Humans never see it. Alongside each URL it can record the date the page was last changed, which helps Google decide when to come back. Google also accepts RSS feeds and plain text files as sitemaps, though XML is the standard.

An HTML sitemap is for visitors. It is an ordinary page on your site, often at /sitemap, that lists your pages as clickable links for people who cannot find what they need through the main navigation. It once carried real SEO weight. It does not anymore. In 2022, Google's John Mueller said plainly that HTML sitemaps "should never be needed" and that a site needing one should fix its navigation instead. That is blunt, and for most small sites it is right: if visitors keep needing a full list of your pages, the navigation is the problem.

A sitemap is not the same thing as schema markup. A sitemap tells Google where your pages are; schema tells Google what those pages mean. Our plain-English schema guide covers the second half.

How Google Finds Your Pages Without One

Google does not need a sitemap to find your pages: its crawler follows links from one page to the next, and a well-linked site will get most of its pages found eventually. The trouble is "eventually." Link-following has blind spots: a page that nothing links to, known as an orphan page, is invisible to a crawler that only follows links. Google also has a daily crawl budget for every site, and on a big site it can run out before reaching the pages that matter. A sitemap runs alongside links, handing Google the full inventory up front.

When a Sitemap Matters Most

Your site is brand new. A new site has no backlinks and no crawl history. Submitting a sitemap to Search Console right after launch tells Google the site exists and which pages to look at first. Without it, a new site can take weeks to show up at all.

Your site is large. Past a few hundred pages, keeping every page reachable through clean internal links gets hard, and a sitemap fills the gaps the navigation misses.

You have orphan pages. If a page exists but nothing on your site links to it, the sitemap is often the only way Google ever finds it.

You run an online store. Products come and go and pages get retired. A self-updating sitemap keeps Google's picture of your catalog current, so new products get discovered and dead ones stop wasting crawl budget.

You publish often. A site that posts daily benefits from accurate last-modified dates, which Google uses to decide how often to come back.

When It Matters Less (The Honest Part)

Here is the part most SEO articles will not tell you: a sitemap will not rank your pages higher. A sitemap gets a page into the consideration set for ranking; content quality, backlinks, and the visitor experience decide positions.

And if your site is ten pages, well linked, with a few decent backlinks, Google will find and index those pages through normal crawling whether you have a sitemap or not. Having one is still good practice and costs nothing. But content and links move rankings, not sitemaps.

What Is Actually Inside an XML Sitemap

The URL itself (<loc>). The full, canonical address of the page, including https://. This is the one field that is required.

The last modified date (<lastmod>). When the page was last meaningfully changed. This is the field Google actually pays attention to, because it tells the crawler whether a revisit is worth its time. Record real updates here, not a date you bumped to look fresh.

Two other fields show up in most examples and both are effectively dead weight: priority (<priority>), how important a page is, and change frequency (<changefreq>), how often it changes. Google ignores both and uses its own signals, so leave them out. One limit is worth remembering: a single sitemap file holds up to 50,000 URLs or 50 MB uncompressed, and bigger sites split their lists across several files tied together by a sitemap index.

How to Create and Submit a Sitemap

Before you build anything, check whether you already have one: type your domain followed by /sitemap.xml into a browser. If nothing loads, check /robots.txt for a line starting with "Sitemap:". WordPress sites with Yoast or RankMath use /sitemap_index.xml instead.

If your platform handles it, you are mostly done: Shopify, WordPress with an SEO plugin, Wix, and Squarespace all generate and update sitemaps automatically as you publish. Then just submit it. In Google Search Console, open the Sitemaps section, enter the address, and click Submit. Bing Webmaster Tools has the same option. Our step-by-step Search Console guide walks through setup if you have not verified your site yet.

If your site has no built-in generator, a free online tool like XML-Sitemaps.com will crawl a small site of up to 500 pages and hand you a file to upload. For larger sites, a desktop crawler like Screaming Frog, free for up to 500 URLs, does the same with more control over which pages make the cut. Upload the file to your public root directory so it loads at yoursite.com/sitemap.xml, and confirm it opens before you submit it anywhere.

One warning: the file a free generator produces is static, a snapshot of your site on the day you ran it. The moment you publish or delete a page, that snapshot is out of date, and a stale sitemap is worse than a slightly incomplete one. If your site changes often, an automatically updating sitemap is worth more than a free download. If you would rather not deal with any of this yourself, our web design services include sitemap setup, robots.txt configuration, and Search Console integration as standard.

Five Mistakes That Waste Your Crawl Budget

A sitemap full of bad entries wastes the crawl budget Google set aside for your site:

Including pages you told Google not to index. If a page carries a noindex tag, keep it out of the sitemap. Listing it says "here is this URL" and "do not index this page" at the same time, and the contradiction burns crawl budget.

Including redirected URLs. Only the final destination belongs in a sitemap. If a page moved, list the new address, not the old one.

Including broken pages. URLs that return a 404 or a server error tell Google your sitemap is stale, so audit it after any redesign or migration. Our migration guide covers redirects when URLs change, which is exactly when this mistake creeps in.

Never updating it after site changes. Add, remove, or rename a page and the sitemap should reflect it. Automated sitemaps do this by default. Manual ones depend on someone remembering, which is why most go stale within a year.

Spending time on priority values. As covered above, Google ignores them. The hours spent fine-tuning priority scores would buy more rankings spent on one good article.

How to Tell If Your Sitemap Is Actually Working

Submitting a sitemap is not the end of the job. Search Console shows what happened next: the Sitemaps report tells you how many URLs Google read from your file and whether it hit any errors. A "Success" status means Google read the file. It does not mean your pages are indexed.

For that, check the Page indexing report filtered by your sitemap, where you will see the gap between submitted and indexed. The gap is the useful part. If you submitted 200 URLs and only 120 are indexed, the other 80 have a reason: thin content, duplicates, a robots.txt block, a noindex tag, or a crawl queue that has not reached them yet. A sitemap full of errors is not a failure. It is a diagnostic tool pointing at exactly which pages need attention. If the report shows errors you do not understand, talk to us and we will tell you what they mean in plain English.

The 50,000-URL limit and Google ignoring priority and changefreq are both in Google's own guidance, summarized in Shopify's 2026 sitemap guide.

The Bottom Line

A sitemap is a small file with a simple job: make sure Google knows your pages exist. It will not rank a bad page, and a small, well-linked site can survive without one. But it costs nothing and takes minutes to set up.

If your site has been live for months and some pages still do not show up on Google, check the sitemap first. If you would rather have someone handle the technical side, from the sitemap and robots.txt through to Search Console, talk to us and we will take a look and tell you honestly what your site needs.

Need a website built? You can hire us on Fiverr for any type of website. Tell us what your business needs and we will build it for you.

Frequently Asked Questions

Does every website need a sitemap?

Not strictly. A small site with clear internal links and a few good backlinks will get its pages found through normal crawling. But a sitemap costs nothing, speeds up discovery for new pages, and gives you a diagnostic view of indexing problems in Search Console, so every site should have one.

Do sitemaps help with SEO rankings?

Only indirectly. A sitemap helps Google index your pages, and a page that is not indexed cannot rank at all. But a sitemap does not make a low-quality page rank. Content quality, backlinks, and the visitor experience on the page decide positions.

How do I find my website's sitemap?

Try your domain followed by /sitemap.xml in a browser. WordPress sites with Yoast SEO or RankMath usually use /sitemap_index.xml instead. If neither works, check your robots.txt file for a line starting with "Sitemap:" that points to the file.

What is the maximum number of URLs in a sitemap?

One sitemap file can hold up to 50,000 URLs or 50 MB of uncompressed data. Larger sites split their URLs across several files and list them all in a sitemap index file, which Google reads as the master list.

Keep Reading