XML sitemap best practices

A sitemap is a list of the pages you actually want indexed — nothing more. Every URL in it should be canonical, return a 200 status, and be eligible for indexing. Including junk teaches engines to distrust your sitemap and wastes the crawl budget you want spent on real content.

In practice: include only canonical, indexable, 200-status URLs — no redirects, no noindex, no duplicates; use absolute URLs with your preferred protocol and host (https, www-or-not, consistently); set lastmod to the real last-modified date so engines know what to re-crawl; and keep priority and changefreq honest, or omit them, since engines largely treat them as hints.

A single sitemap holds up to 50,000 URLs and 50MB uncompressed. Past that, use a sitemap index file that points to multiple sitemaps — and many sites do this deliberately by section (posts, products, pages) so they can spot crawl issues per area.

Reference your sitemap from robots.txt with a `Sitemap:` line and submit it in Google Search Console and Bing Webmaster Tools. AI engines and crawlers discover sitemaps the same way, so a discoverable, clean sitemap helps GEO too.

Sitemap problems are quiet — pages just don't get indexed, and you rarely get an error. The fixes are simple once you know what to look for.

The usual culprits: listing redirected or 404 URLs, which waste crawl and signal staleness; listing noindex or canonicalized-away pages, which contradicts your own signals; stale lastmod dates that never change, which engines learn to ignore; forgetting to reference the sitemap from robots.txt; and not regenerating the sitemap when content changes.