A clean XML sitemap is short, only lists canonical live pages, and updates its lastmod date honestly. Most sitemap problems are not exotic; they come from sitemaps that list URLs the site itself no longer treats as canonical.

Sitemap examples

This guide covers sitemap examples for SaaS teams: what it means, why it matters, and the practical steps to get it right.

A minimal, correct sitemap entry

<url>
  <loc>https://example.com/pricing/</loc>
  <lastmod>2026-09-01</lastmod>
  <changefreq>monthly</changefreq>
</url>

That is genuinely all Google needs: the canonical URL and an honest last-modified date. changefreq and priority are optional and largely ignored by modern crawlers — do not spend time tuning them.

A sitemap index for a multi-section site

<sitemapindex>
  <sitemap><loc>https://example.com/sitemap-pages.xml</loc></sitemap>
  <sitemap><loc>https://example.com/sitemap-posts.xml</loc></sitemap>
  <sitemap><loc>https://example.com/sitemap-tools.xml</loc></sitemap>
</sitemapindex>

Splitting by content type (not by date or arbitrary batch) makes it easy to spot which section has a problem when Search Console reports errors against one sub-sitemap instead of the whole site.

What a broken sitemap looks like

  • A URL that 301-redirects instead of returning 200 directly — the destination should be listed, not the redirect.
  • A URL that 404s because the page was deleted months ago and the sitemap was never regenerated.
  • A non-canonical URL (a tracking-parameter or paginated variant) listed alongside its canonical version.
  • A lastmod date that never changes, which trains Google to stop trusting the field on your site entirely.

Run your live sitemap through the Sitemap Checker to catch these automatically instead of spot-checking URLs by hand. For redirect chains specifically, see why 3xx redirects in a sitemap hurt crawling.

Quick recap: Sitemap examples

Sitemap examples usually comes down to a short, repeatable checklist. Use this whenever sitemap examples comes up again:

  • Diagnose sitemap examples by checking the relevant report first, not assumptions.
  • Confirm the current setup is actually causing sitemap examples before you change anything.
  • Re-check sitemap examples again after the fix ships, not before.

Treat sitemap examples as an ongoing signal rather than a one-time fix. For background on the platform rules behind this, see Google Search Central.