What belongs in a business website sitemap?
A sitemap should list preferred, indexable pages that exist and return the intended content.
AI-assisted practical guide · Editorial approach
The useful starting point
A sitemap should list preferred, indexable pages that exist and return the intended content. Keep it aligned with canonical URLs and meaningful modification dates. Submission helps discovery; it does not guarantee indexing, rankings or enquiries.
Understand the decision
Compare the sitemap with the built website rather than a source-code route list alone. Exclude retired, duplicate, private and non-indexable URLs. Include useful service, industry and article pages that can be reached through navigation. Check that modification dates reflect real content changes rather than the date a build happened to run.
A practical approach
Start from the page a customer actually needs rather than a list of near-identical keywords. Check that its main answer is available in the rendered page, that relevant pages link to it and that the preferred URL is consistent. Record technical checks separately from outcomes: a successful HTTP response or valid sitemap proves availability, not indexing or rankings. Use Search Console to inspect discovery and performance after release.
- List canonical indexable pages.
- Verify every listed page exists.
- Use accurate modification dates where available.
- Submit and inspect discovery separately.
Illustrative example
A business adding a practical article library could include each canonical article and topic hub. It would verify that the exported pages exist and that every sitemap entry uses the intended host. A successful XML response alone would not show that these pages had been indexed.
A mistake to avoid
Do not fill a sitemap with every historical URL or update all dates after a cosmetic build. That makes the file less representative of meaningful content changes.
What to review
Review sitemap processing, discovered pages and indexing reports alongside on-site link coverage; distinguish each stage from search performance.
Turn the guide into a working brief
Maintain a small page register: preferred URL, purpose, audience, content owner, source of facts and last meaningful change. Review pages that receive the wrong queries or fail to help visitors take a useful next step. Consolidate overlapping content instead of publishing every wording variation as another page. Follow the search engine’s current documentation when changing crawler rules, canonical signals or structured data; do not rely on unsupported ranking shortcuts.
Common questions
What should I prepare before asking for help?
Start with this checklist: List canonical indexable pages. Verify every listed page exists. Use accurate modification dates where available. Submit and inspect discovery separately. Add your business context, existing materials and the decision you need to make. A useful initial brief can include uncertainty; you do not need to invent answers before discussing scope.
How should I judge whether the work helped?
Review sitemap processing, discovered pages and indexing reports alongside on-site link coverage; distinguish each stage from search performance. Keep the observation period and definitions visible. Use the responsible team's evidence alongside the website journey; do not attribute every change in results to one asset or article.
Sources & scope
AI-assisted practical guide. Examples are illustrative; business-specific facts and sector claims need the responsible owner’s approval.
- Google Search Central: SEO Starter Guide
Reference for search discovery and page organisation. Availability, indexing and commercial outcomes are separate checks.
Use this guide to start your brief.
Share your business context, existing materials and what is still unclear. The guide title will be included so the conversation starts with the right problem.
Prefer email? Send a brief with this guide’s context.Related guides
How to map search intent to the right website page
Map search intent by the task a person wants to complete: understand a problem, compare options or contact a provider.
Read the guide →Writing page titles that match the actual content
A page title should clearly identify the page's subject and distinguish it from related pages.
Read the guide →Meta descriptions that help people judge a result
A meta description should summarise what the page helps the reader do and include important scope context.
Read the guide →