How to Check XML Sitemap: 4 Steps for a Complete Audit

Quick Answer: To check an XML sitemap, submit it to Google Search Console, navigate to the Sitemaps report under the Indexing section, review the "Status" and "Discovered URLs" columns, and then inspect specific URLs in the URL Inspection tool to confirm they are indexed. This process takes roughly 10 minutes and reveals whether Google can find, crawl, and index your content through the sitemap.

TL;DR: Checking your XML sitemap is not about validating XML syntax — it's about verifying that Google actually found and indexed the URLs you submitted. Use Google Search Console's Sitemaps report to check status (Success vs. Has Errors), then cross-reference with the URL Inspection tool for individual pages. Common issues include blocked robots.txt, noindex tags, and orphaned URLs that exist in the sitemap but not on your live site.

Key Takeaways

The Sitemaps report in Google Search Console shows "Success" or "Has Errors" — but "Success" does not mean all URLs are indexed.
A sitemap with 500 URLs showing only 50 indexed means you have an indexation problem, not a sitemap problem.
Check for sitemap errors like HTTP status 404, 500, or incorrect XML formatting using the "Errors" tab in GSC.
Cross-check your sitemap against your actual site structure to find missing or orphaned pages.
Use tools like Ahrefs or Semrush to compare sitemap URLs against your live crawl data.
A healthy sitemap should list only indexable, canonical, non-blocked URLs.

Table of Contents

Why Checking Your XML Sitemap Matters
Method 1: Google Search Console Sitemaps Report
Method 2: URL Inspection Tool for Individual URLs
Method 3: Third-Party SEO Tools (Ahrefs, Semrush)
Browser Direct Check
The 3-Layer Sitemap Audit Framework
Common Mistakes When Checking XML Sitemaps
How This Applies in Practice
Frequently Asked Questions
Article Summary
Conclusion

Why Checking Your XML Sitemap Matters

An XML sitemap is your primary channel for telling Google which pages on your site exist and should be indexed. However, many website owners assume that submitting a sitemap guarantees indexation. It does not. Checking your XML sitemap involves confirming that Google has processed the file without errors, and that the URLs listed are actually being crawled and indexed. Without this check, you risk having important pages — new blog posts, product pages, or landing pages — sit undiscovered in your sitemap while Google ignores them.

Method 1: Google Search Console Sitemaps Report

The Sitemaps report in Google Search Console is the most authoritative source for checking your XML sitemap status. It tells you whether Google could read the file, how many URLs were discovered, and whether any errors were encountered during processing.

Step-by-Step Workflow

Log into Google Search Console and select your property.
Click on Indexing > Sitemaps in the left-hand navigation.
Locate your sitemap URL in the table. The "Status" column shows either Success or Has Errors.
Look at the Discovered URLs column — this number tells you how many URLs Google extracted from the sitemap file.
Click on the sitemap URL to open the detailed report, where you can see individual errors per URL.

Expert Tip: A "Success" status means Google could fetch and parse the file. It does not mean those URLs are indexed. A common scenario: you see 1,000 discovered URLs but only 150 indexed pages in the Index Coverage report. The sitemap is technically valid, but you have an indexation bottleneck elsewhere — often caused by low-quality content, thin pages, or technical blockers.

What the Error Types Mean

Error	Meaning	Action Required
404 Not Found	The sitemap file itself returned a 404	Re-upload the sitemap to the correct location or remove the old URL
500 Internal Server Error	Server could not deliver the file	Check server logs, .htaccess, or firewall rules
XML parsing error	Malformed XML tags or encoding issues	Validate the XML structure using a tool like XML Sitemaps Validator
URL blocked by robots.txt	A URL in the sitemap is disallowed in robots.txt	Remove the URL from the sitemap or update robots.txt
URL exceeds 50,000 URLs	Sitemap index file limit reached	Split into multiple sitemap files using a sitemap index

Method 2: URL Inspection Tool for Individual URLs

After confirming the sitemap is error-free, the next step is verifying that specific URLs from the sitemap are actually indexed. The URL Inspection tool in Google Search Console provides the most granular data.

How to Use It

Copy a URL from your sitemap file (look in the <loc> tags).
Paste it into the URL Inspection tool at the top of Google Search Console.
Review the Indexing section:
- URL is on Google — indexed.
- URL is not on Google — not indexed. Scroll down to see the reason (e.g., "Crawled - currently not indexed", "Discovered - currently not indexed", "Excluded due to noindex tag").
Check the Coverage section to see if the sitemap was the discovery source.

Author Insight: The most deceptive status in the URL Inspection tool is "Crawled - currently not indexed." This means Google found the page but decided not to add it to the index. For a sitemap check, this is dangerous — the page exists in the sitemap, Google crawled it, but the content quality or internal linking may be too weak to justify indexation. Fixing this requires improving the page's topical relevance or strengthening internal links from already-indexed pages.

Method 3: Third-Party SEO Tools (Ahrefs, Semrush)

Google Search Console shows you what Google found. Third-party tools show you what your sitemap should contain compared to what is actually live and crawlable. This is useful for catching discrepancies.

Using Ahrefs to Cross-Check a Sitemap

In Ahrefs Site Audit, navigate to Page Explorer.
Apply a filter: In Sitemap: Yes.
Compare this list against your actual site crawl to find pages that are in the sitemap but return 4xx, 5xx, or redirects.
Export the list of sitemap URLs and cross-reference with the Index Coverage report from GSC.

Using Semrush to Check Sitemap Errors

Open the Site Audit tool and run a crawl on your domain.
Go to the Sitemap section under "Audit Issues."
Semrush will flag issues such as:
- Pages in sitemap but blocked by robots.txt
- Pages in sitemap that redirect to other URLs
- Pages in sitemap that return 404 or 5xx
- Missing sitemap entries for important pages

Browser Direct Check

You can also check the raw XML file directly in your browser to verify formatting and content. Navigate to yoursite.com/sitemap.xml or yoursite.com/sitemap_index.xml. The browser will display the XML tree. Look for:

Valid XML syntax — no missing closing tags, no ampersands without encoding (& instead of &).
Complete URL coverage — do all your important pages appear in the list?
Last modified dates — are they accurate? Google uses <lastmod> as a freshness signal.
No non-canonical URLs — avoid listing pages with UTM parameters or session IDs.

The 3-Layer Sitemap Audit Framework

This framework helps you evaluate your XML sitemap systematically across three layers. Apply it during any sitemap check to ensure full coverage and indexation.

Layer	What to Check	Tools	Decision Rule
Layer 1: File Integrity	Is the sitemap accessible, valid XML, and not blocked by robots.txt?	Browser, GSC Sitemaps report, robots.txt tester	If the file returns a 404 or 5xx, fix server access first. If blocked by robots.txt, update robots.txt or move the sitemap.
Layer 2: URL Quality	Do the URLs in the sitemap point to indexable content? Are they canonical? Do they return 200 OK?	GSC URL Inspection, Ahrefs Site Audit, Semrush Site Audit	Remove or replace any URL that returns a 4xx, 5xx, or redirect. Never list non-canonical URLs. Do not include noindexed pages.
Layer 3: Indexation Parity	How many sitemap URLs are actually indexed in Google?	GSC Index Coverage report, "site:" search queries	Aim for parity. If indexed count is significantly lower than sitemap count, investigate content quality, internal linking, and Core Web Vitals.

Common Mistakes When Checking XML Sitemaps

Only checking the "Success" status. You must check individual URLs to confirm indexation.
Ignoring the "URL not found" error inside GSC. Often indicates the sitemap contains deleted pages that were cleaned up but never removed from the sitemap file.
Listing all pages in a single sitemap. For large sites (50,000+ URLs), use a sitemap index with separate files for blog posts, products, and categories. This helps Google prioritize crawling.
Forgetting to update the sitemap after content removal. A sitemap listing deleted pages wastes crawl budget and can cause unnecessary 404 hits.
Assuming Google will always respect the sitemap order. Google uses sitemap priority as a hint, not a directive. Priority tags above 0.5 rarely affect crawl frequency.
Not checking sitemap for paginated or faceted navigation URLs. These can dilute indexation signals for your primary content.

Author Note: One overlooked mistake is including URLs with query parameters in the sitemap. For example, /products?color=red&size=large instead of the canonical /products/red-large. Google may treat these as separate URLs, splitting link equity and reducing the chance of indexation for the main page. Strip all tracking parameters from sitemap entries before submission.

How This Applies in Practice

For a Beginner Blog Website

A beginner running a WordPress blog on a shared host will typically have a sitemap generated by Yoast SEO or Rank Math. The main risk is not checking the sitemap after deleting old posts. If you remove a blog post from the live site but leave it in the sitemap, Google will continue trying to crawl a 404. Run a GSC Sitemaps report monthly and delete any orphaned URLs. For bloggers, the most common issue is low-content posts (under 300 words) that show "Discovered - currently not indexed" — these should either be expanded or removed from the sitemap entirely.

For a SaaS Website

A SaaS company with a documentation site, changelog, and landing pages should use a sitemap index that separates content types. The priority is ensuring that the sitemap includes all major product pages and that changelog entries are regularly updated with accurate <lastmod> dates. A common SaaS mistake is including duplicate landing pages with different URL structures (e.g., /features and /features-new) — use canonical tags and list only the canonical in the sitemap. Use the URL Inspection tool weekly on key product pages to ensure they remain indexed.

For an Ecommerce Store

Ecommerce sites with thousands of product pages face the biggest sitemap challenges. Use a sitemap index that splits product pages, category pages, and blog posts. The critical check is ensuring that out-of-stock or discontinued products are removed from the sitemap immediately. Google Search Console's Sitemaps report should be monitored daily during product launches. A real-world pattern: a store listing 10,000 products in a single sitemap saw only 2,000 indexed because 5,000 products returned 302 redirects to similar products — those redirects were blocking indexation. Remove redirecting URLs from the sitemap.

For a Local Business

A local business (e.g., a dental clinic with a small website) usually has fewer than 100 pages. The mistake here is not submitting the sitemap at all or letting the CMS generate a bloated sitemap that includes tag pages, author archives, and paginated results. Narrow the sitemap to only the essential pages: homepage, about page, services pages, location pages, and blog posts. Exclude tag and category pages unless they contain unique, indexable content. Use the Google Business Profile integration with GSC to verify that the sitemap covers all location-specific pages.

Frequently Asked Questions

How often should I check my XML sitemap?

Check your XML sitemap at least once a month for established sites. For sites that publish content daily — like news sites or ecommerce stores with frequent inventory changes — check it weekly. The key trigger is any change to your site structure: adding a new section, removing pages, or migrating to a new domain. Always re-check the sitemap after these events even if Google automatically discovers changes.

What does "Couldn't fetch" mean in Google Search Console?

"Couldn't fetch" means Google tried to download your sitemap file but failed. This can happen due to a server timeout, a DNS resolution failure, or a firewall blocking Googlebot's IP range. Check your server error logs or use a tool like curl from a remote server to see if the sitemap URL is accessible. If it works fine in your browser but fails in GSC, your server may be rate-limiting Googlebot — review your .htaccess or server configuration to ensure Googlebot is not blocked.

Should I include all pages in my XML sitemap?

No. Only include pages you want indexed in Google. Exclude paginated archives (tag pages, author pages, category pages unless they contain unique content), thin content pages, and pages with noindex directives. Google's guidelines explicitly state that sitemaps should point to pages that are canonical and indexable. Including low-value pages can dilute the signal that your important pages are the priority.

What is the difference between a sitemap and a sitemap index?

A sitemap file can contain up to 50,000 URLs. A sitemap index is a file that lists multiple sitemap files. Use a sitemap index when your site exceeds 50,000 URLs or when you want to separate content types (e.g., sitemap-posts.xml, sitemap-products.xml, sitemap-categories.xml). The sitemap index itself is what you submit to Google Search Console; Google then fetches each sitemap file listed within it. This improves crawl prioritization because Google can assign different crawl budgets to different parts of your site.

How do I fix a sitemap that shows "URL not available" for individual entries?

Click on the sitemap entry in GSC to expand the list of affected URLs. Then use the URL Inspection tool for each URL to see the exact error. Common fixes: remove deleted pages from the sitemap, update the sitemap generation script to exclude noindexed pages, or check if the page's canonical tag points to a different URL. For WordPress, regenerate the sitemap after cleaning up your site's trash. For static sites, rebuild the sitemap file after removing old pages.

Can a sitemap contain HTTPS and HTTP URLs mixed together?

Technically, it can, but it is an anti-pattern. Google prefers that all URLs in the sitemap use the same protocol that your site canonically uses. If your site runs on HTTPS, every URL in the sitemap must start with https://. Mixing HTTP and HTTPS URLs will confuse Google and may prevent some pages from being indexed correctly. Use a search-and-replace step in your sitemap generation process to enforce protocol consistency.

Article Summary

This article covered how to check an XML sitemap using four methods: the Google Search Console Sitemaps report, the URL Inspection tool, third-party SEO tools like Ahrefs and Semrush, and a direct browser check. The core framework introduced — the 3-Layer Sitemap Audit — evaluates file integrity, URL quality, and indexation parity. You learned common mistakes such as ignoring "URL not found" errors and including non-canonical URLs. The practical application section showed how beginners, SaaS sites, ecommerce stores, and local businesses should adapt the audit process to their specific needs.

Conclusion

Checking your XML sitemap is not a one-time setup task — it is an ongoing maintenance workflow that directly affects how Google discovers your content. Use the Sitemaps report in Google Search Console as your primary check, validate individual URLs with the URL Inspection tool, and cross-reference with third-party crawlers to catch discrepancies. Apply the 3-Layer Sitemap Audit framework monthly to prevent indexation gaps. A well-maintained sitemap is a signal of site quality and a practical tool for improving crawl efficiency. Start with a quick GSC check today, then work through the framework to ensure every page you want indexed is actually discoverable.

Recommended Resources

Google Search Central — Official documentation on sitemap requirements and best practices.
Google Search Console — Submit and check your sitemap status directly.
Ahrefs Blog — Guides on sitemap auditing and crawl optimization.
Semrush Blog — Sitemap analysis tools and technical SEO workflows.
Moz Blog — Beginner-friendly tutorials on sitemap submission and indexing.

About the Author

The SMARTCHAINE Editorial Team specializes in SEO, AI Search Optimization, GEO (Generative Engine Optimization), AI Overviews, Structured Data, Technical SEO, and search visibility strategies for modern search engines and AI-powered discovery platforms.