XML Sitemap: What It Does and What It Does Not Guarantee
Direct Answer
An XML sitemap is a machine-readable list of URLs you want search engines to know about, usually the canonical URLs you consider eligible for search. It can support discovery and provide update information, but submitting a sitemap is only a hint: it does not guarantee that Google will crawl or index every listed URL.
Documentation
What an XML sitemap is for
An XML sitemap gives search engines a structured list of URLs and can include extensions for images, video, news, and localized versions. It is especially useful on larger, newer, frequently changing, or weakly linked sites where discovery from normal links may be incomplete.
A sitemap complements crawlable internal linking. It does not replace a navigable site architecture.
Which URLs belong in the sitemap
Include fully qualified, absolute URLs that you want to appear in search. Google recommends listing the canonical URLs rather than every duplicate variation.
Keep the sitemap aligned with the live site. URLs that redirect, return errors, are intentionally noindexed, or are non-canonical create conflicting maintenance signals and should be reviewed.
What submission does not guarantee
Google explicitly describes sitemap submission as a hint. Submission does not guarantee that Google will download the sitemap, crawl each URL, index each URL, or rank any URL.
A sitemap therefore should not be used to “force” indexing. If an important page is absent from search, inspect crawl access, HTTP status, noindex, canonicalization, content quality, and internal discovery instead of repeatedly resubmitting the same sitemap.
Important XML sitemap limits and fields
A single sitemap is limited to 50 MB uncompressed or 50,000 URLs. Larger sets must be split, optionally using a sitemap index.
Google ignores <priority> and <changefreq>. Google says it uses <lastmod> when the value is consistently and verifiably accurate and reflects a significant page update.
Sitemap URLs should be absolute, not relative.
How to publish and verify it
Generate the sitemap from the same source of truth as your live canonical URLs when possible. Host it at an appropriate location, reference it in robots.txt if desired, and submit it through Search Console when useful.
Monitor the Sitemaps report for fetch or processing errors, but evaluate indexing at the URL level as well. A successfully processed sitemap means Google could process the file; it is not an indexing certificate.
Questions & Answers
Does an XML sitemap guarantee indexing?
No. Google says sitemap submission is only a hint and does not guarantee that the sitemap will be downloaded or used to crawl the listed URLs.
Should redirects and noindex pages be in the sitemap?
Generally, list the canonical URLs that you want in search. Redirected, intentionally noindexed, error, or duplicate URLs should be reviewed and usually removed from the canonical sitemap set.
Does Google use priority and changefreq?
Google states that it ignores both <priority> and <changefreq> values.
When is lastmod useful?
Google can use <lastmod> when it is consistently accurate and reflects a significant update to the page, such as meaningful content, structured data, or link changes.
Practical Check
- Include absolute canonical URLs that are intended for search.
- Keep redirecting, error, noindex, and non-canonical URLs out of the preferred sitemap set.
- Split files above 50,000 URLs or 50 MB uncompressed.
- Use accurate
<lastmod>values; do not rely on<priority>or<changefreq>for Google. - Submit and monitor the sitemap, but verify important URLs separately because submission does not guarantee indexing.