XML Sitemaps Your Site's Index Submission to Google

What belongs in a sitemap

A sitemap should list only canonical, indexable, 200-status URLs that you want in search results. Including noindexed pages, redirects, or non-canonical duplicates sends mixed signals and can lower Google's trust in the whole file over time. Each <url> entry supports <loc> and optionally <lastmod>; the once-common <priority> and <changefreq> fields are now ignored by Google.

Large sites should split sitemaps by type, such as products, categories and blog posts, using a sitemap index file to reference them. This makes it far easier to diagnose indexation problems for a specific section rather than debugging one monolithic file.

• Maximum 50,000 URLs or 50MB uncompressed per sitemap file
• Only include self-canonical, indexable, 200-status URLs
• Keep <lastmod> accurate; false freshness signals get ignored

Submitting and monitoring

Submit the sitemap index URL in Search Console under Sitemaps, and also reference it in robots.txt with a Sitemap: line so any crawler can find it. Search Console then reports 'Discovered' versus 'Indexed' counts per sitemap, which is the fastest way to spot a section with a systemic indexing problem.

A sitemap does not guarantee indexing; it is a discovery hint, not a directive. If a large share of submitted URLs are excluded, the cause is usually quality or duplication, not the sitemap itself.

Dynamic generation and freshness

Sitemaps for content that changes often, such as e-commerce catalogues, should be generated dynamically at request time or on a scheduled job rather than hand-maintained. Update <lastmod> only when the meaningful content actually changes, since Google uses it to prioritise recrawls.

Common errors

Frequent problems include sitemaps that 404, sitemaps blocked by robots.txt, mixing HTTP and HTTPS URLs, and listing URLs on a different domain or subdomain without a verified property in Search Console. Any of these cause partial or total rejection of the file.

Checking sitemap health in RankAudit

RankAudit fetches your sitemap index, validates each nested file against the URL limits, and flags any listed URL that is non-canonical, redirected, or blocked by robots.txt. Use the mismatch report to clean the file before resubmitting it in Search Console.

Key takeaways

• ✓List only canonical, indexable 200-status URLs
• ✓Split large sites into typed sitemaps under a sitemap index
• ✓Reference the sitemap in robots.txt as well as Search Console
• ✓Treat low indexing rates as a content signal, not a sitemap bug

Why this lesson matters

This lesson belongs to Crawling and Indexation Control, the part of Technical SEO Excellence where the goal is: give googlebot precise instructions and confirm every page you care about is actually indexed.

Read it once, then do it straight away on a real site inside RankAudit. Nothing here is theory for its own sake — every step produces something you can show a client.

Do it now

1. 1Open RankAudit with sample data already loaded, so you are not stuck on setup.
2. 2Crawl a site and triage the issue list.
3. 3Run a crawl in RankAudit and cross-check the robots.txt, sitemap and index coverage reports it produces.