AI Summary: A sitemap gives search engines a structured inventory of important pages and selected metadata, but it does not replace internal links or guarantee crawling and indexing. Keep URLs canonical, public, current, and consistent with robots and page status; use lastmod only when it reflects a meaningful update.
What a sitemap communicates
Google describes a sitemap as a file that provides information about pages, videos, and other files, including relationships and selected update metadata. It can help search engines discover URLs, especially on larger, newer, complex, or media-heavy sites. [1]
The core rule is consistency. Include canonical, indexable URLs that return the status you intend. Do not list redirects, blocked routes, login-only pages, thin duplicates, or URLs that canonicalize elsewhere. Keep lastmod tied to a meaningful content or document change rather than refreshing every timestamp on every deployment. [2]
Sitemap and internal links work together
Google notes that properly linked pages can often be discovered without a sitemap, while a sitemap can improve discovery for larger or more complex sites. [1] Keep important pages reachable from navigation or contextual links, then use the sitemap to provide a clean machine-readable inventory. robots.txt should point to the same sitemap URL, and the sitemap's host and scheme should match the canonical site.
| Check | Expected condition |
|---|---|
| URL set | Only public canonical pages intended for discovery |
| Status | URLs return the intended success response without avoidable chains |
| Dates | lastmod changes when the document meaningfully changes |
| Consistency | Robots, canonical links, internal links, and sitemap agree |
| Delivery | XML is reachable, valid, and served with an appropriate type |
Verification checklist
Fetch the sitemap as an unauthenticated client and parse every <loc>. Compare the set with public navigation and the robots directive. Validate XML syntax, duplicate removal, host consistency, and meaningful date values. Treat a submitted sitemap as a successful publication step, not as proof that a crawler or AI system has fetched every URL.
A truthful sitemap is quiet infrastructure: easy to fetch, hard to misinterpret, and maintained as part of the same release process as the pages it lists.