An XML sitemap is a machine-readable list of website URLs. It can help search engines learn about pages and, where accurate information is provided, understand when content changed.
It complements the website's navigation and internal links. It does not guarantee that listed pages will be crawled, indexed or ranked.
What belongs in a sitemap?
The sitemap should reflect the URLs the business intends search engines to consider. Its contents should align with indexing settings and the preferred versions of pages.
Listing broken destinations, preview URLs or unintended duplicates creates a less coherent signal. Review the generated file rather than assuming automatic output is always appropriate.
Is it different from a visual sitemap?
Yes. A planning sitemap shows the proposed page structure for a project. An HTML sitemap can provide a human-readable directory. An XML sitemap serves a machine-readable discovery role.
The names overlap, but the deliverables have different purposes. Establish which one a brief or supplier recommendation refers to.
Does a sitemap guarantee indexing?
No. Discovery and indexing are separate stages. A search engine can learn about a URL and still decide not to include it in its index.
If an important page is absent from search, also inspect its availability, content, internal links and indexing controls. Repeatedly submitting the same sitemap does not resolve every possible cause.
How does a CMS affect the sitemap?
A platform may generate entries automatically from published pages and collections. Draft state, indexing settings and platform configuration can affect the result.
Test representative records after changing a collection. Confirm that article URLs appear in the intended form and that removed or private content is handled appropriately.
What about modification dates?
Modification information should reflect meaningful changes accurately. Artificially updating dates without substantive changes makes the information less trustworthy.
Consider how the platform generates those values. A site-wide publish date and the actual update date of an individual article may not mean the same thing.
How do you review a sitemap?
Open the current file, inspect important URL groups and compare them with the intended site structure. Check that destinations work and use the correct domain.
For larger sites, group findings by template or collection. Fixing a shared configuration can be more effective than treating every affected URL as an unrelated problem.
What should happen after a redesign?
Confirm that new destinations are represented and that old routes have been handled through the migration plan. Review canonical choices and internal links alongside the sitemap.
Then monitor relevant search reporting. The sitemap is one part of a coherent technical foundation, not a substitute for content quality or reliable page delivery.
Further reading
For reference, see the supporting documentation. Explore related explanations of Internal linking, Technical SEO, Canonical URL.
A practical example
Illustrative example: a new glossary collection is launched with an article template. The team checks that each intended public term has a working URL in the sitemap, while draft records remain unpublished. It also links the glossary from relevant website pages.
Why it matters
A sitemap helps communicate a website's available content to search engines. Accurate generation and review reduce avoidable inconsistencies as the site grows.
