XML sitemap

An XML sitemap is a file that lists the URLs on your site you want search engines to find, often with the date each page last changed. A SaaS company's sitemap at /sitemap.xml might list its pricing page, every integration page and every blog post.
What is an XML sitemap?
An XML sitemap is a file on your site that lists the URLs you want search engines to crawl and index. It usually lives at yourdomain.com/sitemap.xml, and each entry holds a page's address and, often, the date it last changed in a meaningful way.
Think of it as the list you'd hand a new hire on day one: here are the pages that matter. Search engines find most pages by following links, but the sitemap makes sure they know about the ones links might miss.
Here's the format, based on the example in Google's sitemap guide, with two typical SaaS pages:
<?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-11-02</lastmod>
</url>
<url>
<loc>https://www.example.com/integrations/salesforce/</loc>
<lastmod>2026-10-18</lastmod>
</url>
</urlset>Why XML sitemaps matter for B2B SaaS
Google says a sitemap helps most when a site is large, when it's new with few links pointing to it or when it has pages that aren't well linked from the rest of the site. Plenty of B2B SaaS sites fit at least one of those. Integration directories, template galleries, docs and programmatic pages can add hundreds of URLs that sit several clicks from the homepage.
A sitemap won't force Google to index a page. Google says plainly that it doesn't guarantee every listed URL gets crawled and indexed. What it does is put your important pages on Google's list and give you a report in Search Console showing which ones made it into the index.
Here's where I see it help most:
- New pages get found sooner: When you publish a comparison page or a new integration page, the sitemap tells Google it exists before any links point to it.
- Deep pages don't get lost: Docs and integration pages buried under filters and tabs are easy for crawlers to miss. The sitemap lists them directly.
- You get an index check: Search Console shows how many sitemap URLs are indexed, so you can spot a section that Google keeps skipping.
- Updates get noticed: An accurate lastmod tells Google which pages changed since its last visit, which helps after a content refresh.
How to build a good XML sitemap
Most CMS platforms and SEO plugins generate a sitemap for you. The real work is making sure it lists the right URLs. Here's my process:
- List only pages you want in searchInclude canonical URLs that return a 200. Leave out redirects, 404s, noindex pages, thank-you pages and URLs with tracking parameters.
- Use full, absolute URLsGoogle asks for fully qualified URLs like https://www.example.com/pricing/ and says to avoid relative paths like /pricing/.
- Keep lastmod honestChange the date only when the page content really changes. Google uses lastmod only when it's consistently and verifiably accurate.
- Split big sites by sectionGoogle limits each file to 50,000 URLs or 50MB uncompressed. I split by page type, like blog, docs and integrations, and list the files in one sitemap index.
- Submit it in two placesAdd it in Search Console's Sitemaps report and add a Sitemap line to your robots.txt, so every crawler can find it.
Google also says it ignores the priority and changefreq tags, so don't spend time tuning them. Many plugins still add them by default, and leaving them in does no harm.
An XML sitemap example
Perceptric's own site is a simple real example. One sitemap at perceptric.com/sitemap.xml lists the pages we want found, from service pages to blog posts and glossary terms. Our robots.txt points to it with one line: Sitemap: https://perceptric.com/sitemap.xml.
A site with a few hundred URLs doesn't need more than one file. A bigger SaaS site should split up. Let's say you run a test automation platform with 400 blog posts, 2,000 docs pages and 150 integration pages. Here's how I'd lay it out:
| File | What it lists |
|---|---|
| sitemap-index.xml | The four files below and nothing else |
| sitemap-pages.xml | Homepage, product, pricing, comparison and about pages |
| sitemap-blog.xml | All 400 blog posts |
| sitemap-docs.xml | All 2,000 docs pages |
| sitemap-integrations.xml | All 150 integration pages |
Splitting by section makes the Search Console reports far more useful. If the docs sitemap shows 2,000 pages submitted and 900 indexed, you know exactly where to look.
How to measure an XML sitemap
Search Console has everything you need. Here's what I check every month:
- Read status: The Sitemaps report shows when Google last read each file and whether it hit errors. A sitemap Google couldn't fetch is a sitemap it isn't using.
- Indexed against submitted: Filter the Page indexing report by sitemap to see how many listed URLs are indexed. A big gap in one section is your next technical task.
- Reasons pages are left out: The same report lists why pages aren't indexed, like "Crawled, currently not indexed" or "Duplicate without user-selected canonical". Those reasons tell you whether to fix the content or the duplicates.
Common XML sitemap mistakes
- Listing URLs that redirect or 404: After a redesign, old URLs often stay in the sitemap. Every one sends Google to a dead end and makes the list less useful. Swap in the final URLs after any 301 redirect work.
- Including noindex pages: A sitemap that lists a page while the page says "don't index me" gives Google two opposite instructions.
- Changing lastmod on every deploy: Google uses lastmod only when it's accurate. A date that changes on every release, whether the page changed or not, gives Google nothing to go on.
- Forgetting new sections: A new docs subdomain or a new templates folder needs its own sitemap entry. Check after every launch.
- Still pinging Google: Google announced in June 2023 that it was retiring the sitemap ping endpoint. Old scripts that ping it do nothing now, so submit through Search Console and robots.txt.
- Expecting it to fix weak pages: A sitemap helps Google discover a page. It won't make Google index a thin or duplicate one.
Here's a quick check you can run today. Open your sitemap, pick five URLs at random and load them. Do all five land on a page you'd want a buyer to see?
Read more
FAQ
Do small websites need an XML sitemap?
Google says a site with about 500 pages or fewer that's well linked internally might not need one. Most sites still benefit, and most CMS platforms create one for free.
How many URLs can one XML sitemap hold?
According to Google, a single sitemap can hold up to 50,000 URLs or 50MB uncompressed. Larger sites split their URLs into several sitemaps and list them in one sitemap index file.
Does Google use priority and changefreq in a sitemap?
No. Google says it ignores both. It uses lastmod when the date is consistently and verifiably accurate.
How do I submit an XML sitemap to Google?
Submit it in the Sitemaps report in Google Search Console and add a Sitemap line to your robots.txt file. Google retired the old sitemap ping endpoint after announcing the change in June 2023.



