SaaS SEO · Technical SEO
XML sitemap: what Google actually does with it on a SaaS site
An XML sitemap is a file that lists a site's important URLs to help Google crawl it more efficiently. It improves page discovery, without guaranteeing crawling or indexing. Google only asks for one in three cases: a large site, a new site with few external links, or a site rich in video, image or news content. Below roughly 500 well-linked pages, it is optional.
Franck Gordi
· 8 min read
Canonical URLs
XML sitemap
Page discovery
Key takeaways
- A sitemap helps Google discover your URLs, but guarantees neither crawling nor indexing.
- Google says a site of roughly 500 pages or fewer, properly interlinked, can do without a sitemap.
- Google ignores the priority and changefreq tags; it only uses lastmod when the date is accurate and verifiable.
- A sitemap is limited to 50,000 URLs or 50MB uncompressed; beyond that, split it with an index file.
- The sitemap should only list canonical, absolute URLs, in UTF-8, ideally hosted at the site root.
What is an XML sitemap for, in SEO terms?
Google's sitemap documentation defines it simply: a file where you provide information about the pages, videos and other files on your site, and the relationships between them, so search engines can crawl your site more efficiently. A sitemap can also carry additional information, such as a page's last update date or its alternate language versions.
The key point: if your pages are properly linked together, Google usually discovers most of your site without a sitemap. The file becomes a safety net when linking alone is no longer enough, which happens fast on a SaaS that accumulates a blog, documentation, integration templates and use-case pages.
When does a SaaS actually need a sitemap?
Google lists three situations where a sitemap helps, and one where it is dispensable. The boundary is not company size but site structure.
Google's criteria
Four situations, one decision
- Large site
- On a large site, it is hard to ensure every page is linked from at least one other. Googlebot may miss recent pages.
- New site, few links
- Googlebot discovers the web by following links. A new site with no external links risks staying invisible without a submitted sitemap.
- Rich media content
- Videos, images, news: a sitemap lets you supply Google with additional information taken into account in Search.
- Small, well-linked site
- Below roughly 500 pages, with complete internal linking and few media files, Google says a sitemap is not necessary.
Which sitemap format should you choose?
Google accepts three format families and states it has no preference: the choice depends on your setup.
XML sitemap, the most versatile
It is the only extensible format: it can describe images, videos, news and the localized versions of your pages. Most CMSes generate it automatically. Its drawback: it becomes cumbersome to maintain on a large site whose URLs change often.
RSS, mRSS and Atom 1.0, the easiest to provide
If your CMS already generates an RSS or Atom feed, you can submit its URL as a sitemap. Limitation: these feeds only describe recent URLs, and only carry information about videos, not images or news.
Text sitemap, the most minimal
A plain .txt file with one absolute URL per line. Easy to produce and maintain, but limited to HTML pages and indexable textual content, with no metadata at all.
The technical rules Google applies
Google's documentation on building a sitemap stresses three often-overlooked best practices: size limits, file location and the nature of the URLs included.
- Limits: 50MB uncompressed or 50,000 URLs per file, across all formats. Beyond that, split into multiple sitemaps grouped in an index file, which also lets you track each sitemap's performance in Search Console.
- Location: the file must be UTF-8 encoded. Unless submitted through Search Console, a sitemap only affects descendants of its parent directory. Google therefore recommends posting it at the site root.
- URLs: only fully qualified, absolute URLs, which Google will attempt to crawl exactly as listed. Include only the URLs you want in search results, meaning the canonical ones.
Lastmod, priority, changefreq: what Google really reads
Google is explicit: it ignores the priority and changefreq values. Filling in these fields changes nothing about your crawling.
The lastmod tag, however, is used provided it is consistently and verifiably accurate, for example by comparing it to the page's actual last modification date. It should reflect the last significant update: the main content, structured data or links on the page. Changing the footer copyright date does not count. An artificially inflated lastmod loses its value as a signal.
The most common sitemap errors on a SaaS
Diagnosis
Four errors, four fixes
- Non-canonical URLs listed
- The sitemap mixes parameterized versions, duplicates and variants. Fix: list only canonical URLs, consistent with each page's canonical tag.
- Auto-generated lastmod
- A date refreshed on every deploy, unrelated to content. Google stops using it. Fix: a date reflecting a real modification.
- Sitemap outside the root
- Placed in a subdirectory without a Search Console submission, it only covers that directory. Fix: publish it at the root or submit it in Search Console.
- Noindexed or blocked pages included
- The sitemap sends signals that contradict robots.txt or robots meta tags. Fix: only list indexable pages.
Consistency between the sitemap and the canonical tag is the most frequently broken point: Google states the sitemap is one of the signals that help it pick the canonical URL. On a multilingual site, the sitemap can also carry hreflang annotations, and its crawling scope connects to crawl budget questions.
How to check your sitemap before submitting it?
- Content: only canonical, absolute, indexable URLs returning a 200 status.
- Size: under 50,000 URLs and 50MB per file, otherwise split with an index file.
- Encoding: UTF-8, with values entity-escaped per XML rules.
- Lastmod: real dates, aligned with significant content changes.
- Submission: declared in Search Console, which then lets you track each sitemap's coverage.
If Search Console reports many URLs as "Discovered, currently not indexed", the sitemap is not the culprit: it did its discovery job. The cause usually lies in the perceived value of the pages or in the architecture. A technical SEO project fixes those bottlenecks, and an SEO audit tells you whether the issue comes from the sitemap, the linking or the content.
Frequently asked questions about XML sitemaps
Does a sitemap guarantee my pages get indexed?
No. Google states that a sitemap helps discover a site's URLs, but does not guarantee they will be crawled or indexed. It improves discovery; the indexing decision then depends on the quality and value of each page.
Does my site really need a sitemap?
Not necessarily. According to Google, a site of roughly 500 pages or fewer, where every important page is reachable through internal links, can do without one. A sitemap becomes useful if the site is large, new with few external links, or rich in video, image or news content.
Does Google use priority and changefreq?
No. Google says it ignores the priority and changefreq values in XML sitemaps. It does use the lastmod value, provided it is consistently and verifiably accurate, for example by comparing it to the page's actual last modification date.
What are the size limits of a sitemap?
All formats are limited to 50MB uncompressed or 50,000 URLs per file. Beyond that, you split into multiple sitemaps, optionally grouped in a sitemap index file that you submit to Google.
Should I list every URL of my site in the sitemap?
No. Google asks you to include only the URLs you want to see in its search results, meaning the canonical URLs. If the same content is reachable under several URLs, pick the one you prefer and include only that one.
Which sitemap format does Google prefer?
None in particular. Google accepts XML sitemaps, RSS, mRSS and Atom 1.0 feeds, and plain text files, and says it has no preference. XML remains the most versatile format because it can carry information about images, videos, news and localized versions.
Sources and scope
Documentation accessed October 8, 2026. This article relies on Google's public guidance; it presents no client case and no measured gain.
About the author

Franck Gordi
Independent SEO and GEO consultant for B2B SaaS. He helps software companies become visible on Google and cited by AI engines.
LinkedIn →