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.

Why this lesson matters

Incorrectly configured XML sitemaps can directly impact revenue by hindering timely discovery and indexation of critical pages. Imagine an e-commerce site launching a major seasonal campaign with hundreds of new product pages. If those URLs are missing from the sitemap, or the sitemap itself isn't submitted or kept fresh, Googlebot might take days or even weeks to organically discover them through internal links. This delay translates into lost visibility, missed sales opportunities during peak periods, and a significant competitive disadvantage, directly affecting the bottom line.

Conversely, a well-maintained and accurate sitemap acts as a reliable communication channel with Google, accelerating the indexation of new content and updates. For a news publisher, this is paramount; delayed indexation of breaking stories means losing traffic to competitors. For any business, ensuring Google has an up-to-date map of your indexable content means faster ranking signals can accumulate, and any technical issues leading to orphan pages or content siloing are mitigated, leading to more predictable organic performance and better ROI on content efforts.

Prioritising Sitemap Inclusions for Large Sites

When dealing with extremely large websites, typically those with millions of URLs, the 50,000 URL limit per sitemap file, and the 50MB uncompressed file size limit, necessitate a strategic approach to sitemap generation. Merely including every single URL can dilute the signal for truly important pages. Instead, segment your sitemaps by content type, update frequency, or strategic importance. For instance, separate sitemaps for product pages, blog posts, and category pages allow for more granular control over crawl prioritisation and easier debugging when indexation issues arise within a specific segment.

Consider the 'crawl budget' implication. While sitemaps don't guarantee crawling, they inform Google about your site's structure. For high-priority sections of your site, ensuring they are present in a dedicated, clean sitemap signals their importance. Conversely, pages that don't need immediate indexing, or have a lower business value like archived content, might be omitted or placed in less frequently updated sitemaps. This pragmatic approach ensures your most valuable content receives the attention it deserves from Googlebot, optimising your available crawl budget efficiently.

• Segment by content type (e.g., /products/, /articles/).
• Prioritise sitemaps for rapidly changing or high-value content.
• Exclude pages that are canonicalised elsewhere or have low SEO value.
• Utilise sitemap index files for managing multiple sitemaps.

Do it now

Now, you'll perform an initial check on your current XML sitemaps. The goal is to identify immediate issues that could be hindering indexation. This practical step will solidify your understanding of how sitemap health directly impacts your site's discoverability. We'll refine this further in subsequent exercises, but this initial scan provides crucial insights.

• Access your RankAudit project for your designated website.
• Navigate to the 'XML Sitemaps' report within the 'Indexation' section.
• Identify any sitemap files listed with 'Errors' or 'Warnings'.
• Note down the specific error types and the number of affected URLs for your chosen domain.

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.