Plain-language explainer
What is an XML sitemap?
An XML sitemap lists the URLs you want search engines to find, helping them discover and recrawl pages.
The work to plan together
A scope shaped around this requirement.
- Include only indexable pagesScope
- Submit in Search ConsoleReview
- Keep it updated automaticallyCheck
The useful starting point
A sitemap gives search engines a list of preferred URLs to discover. Keep it consistent with canonical tags, redirects and indexing rules so it does not send contradictory signals.
What to review
- Include only indexable pages
- Submit in Search Console
- Keep it updated automatically
- Large sites can use several sitemaps
What to avoid or interpret carefully
A sitemap cannot force indexing. Do not update every lastmod value daily if the underlying page content has not materially changed.
Practical detail
Include useful canonical URLs, not every address
An illustrative sitemap entry for an approved service page is <url><loc>https://example.com/service/</loc></url> inside a valid sitemap urlset.
| Part of the work | Example output | How to review it |
|---|---|---|
| Include | A working, indexable canonical service page | The sitemap URL agrees with the intended public destination. |
| Exclude | Redirects, duplicate parameters and deliberately noindex pages | Listing an unwanted page does not make it useful. |
| lastmod | The date of a significant page change when reliably maintained | Do not reset every page’s date merely because the build ran. |
| Submit and review | Accessible XML plus the relevant webmaster report | Processing and discovery are separate from indexing. |
Use the sitemap protocol namespace on the urlset: http://www.sitemaps.org/schemas/sitemap/0.9. For a large inventory, split files according to the supported limits and validate the complete XML.
Reference guidance: Google sitemap documentation.
List the useful canonical destinations you want discovered
A sitemap helps identify URLs but does not guarantee crawling or indexing. It should represent the site’s intended public pages rather than every generated path. Review the content inventory before accepting an automatically produced list.
Check the list
Sample important services, articles and products. Exclude irrelevant or unsuitable variations according to the site plan. The sitemap should not contradict the intended canonical and indexing setup.
Review the live URLs
Confirm that listed destinations work and provide the expected content. Redirected, missing or intentionally excluded pages indicate that the generator or inventory needs attention.
Maintain the source
Use an update process tied to publication and retirement. Reported sitemap sign-off is not proof that every listed page is indexed. Investigate important exceptions with URL-level evidence.
How to interpret this guidance
For a changing catalogue, the record quality matters as much as the file format. Keep release and publishing responsibilities clear so stale listings do not accumulate.
Will submitting a sitemap get all pages indexed?
No. It supports discovery, but selection depends on the page and search system. Review important URLs individually and address confirmed technical or content problems rather than repeatedly submitting an unchanged file.
Does putting a page in the sitemap guarantee indexing?
No. The file communicates URLs for discovery; search engines still decide whether to index and show them.
Can Tangensys help with the next step?
Yes. Share your website, goal and the issue you are investigating. We can discuss the relevant service and provide a custom quote within 2 working days.
Related reading and services
Let’s agree the right next step.
Tell us your goals and current setup. We’ll recommend a practical starting point and provide a custom quote.
Custom quote within 2 working days