Advertisement
Advertisement
Sitemap Analyzer
Extract meaningful data from any XML sitemap. View total URL counts, structural composition, and canonical HTTP vs HTTPS distributions instantly.
How to Use This Tool
1
1
Enter Sitemap URL
Input the absolute URL of your published XML sitemap (e.g., https://example.com/sitemap.xml).
2
2
Run Analyzer
Click analyze to let our backend fetch, parse, and count the contents of your XML file.
3
3
Review URLs
View the exact number of URLs declared in your sitemap to ensure all expected pages are included.
4
4
Review Architecture
Check whether your file is a standard URL Set or a larger Sitemap Index.
5
5
Review Protocols
Analyze the breakdown of HTTP vs HTTPS canonicals to ensure security compliance.
6
6
Recommended Action
If the URL count is suspiciously low, check your CMS settings for accidental noindex tags.
Data We Extract
URL Volume
We accurately count every single <loc> tag within the file. For large ecommerce sites or publications, this helps you verify if your CMS is accidentally dropping URLs from the index.
Structural Type
We detect whether the provided file is a standard flat XML map (<urlset>) or a parent index file (<sitemapindex>) linking out to child sitemaps.
Protocol Distribution
We parse the scheme of every URL to detect HTTP vs HTTPS. A healthy, modern sitemap should have a 100% HTTPS distribution to prevent canonicalization issues.
Frequently Asked Questions
Why does the URL count differ from Google Search Console?
Our analyzer reads the exact number of URLs present in the XML file at this very moment. GSC often lags behind, showing the number of URLs it processed during its last successful fetch, which could be days or weeks old.
Why is it important to check HTTP vs HTTPS?
If your site migrated to HTTPS, but your CMS plugin is still generating HTTP URLs in the sitemap, Google will be forced to crawl the HTTP version, hit a 301 redirect, and then crawl the HTTPS version. This wastes massive amounts of crawl budget.
Does this tool recursively analyze child sitemaps?
Currently, if you input a Sitemap Index, the analyzer will count the number of child sitemaps (<sitemap> tags) listed within that index, rather than recursively fetching and counting every single URL within the children.
What is considered a healthy sitemap structure?
A healthy sitemap is under 50MB, contains fewer than 50,000 URLs, uses consistent HTTPS protocols, and contains only indexable canonical URLs that return a 200 OK status code.
Can the analyzer detect duplicate URLs?
The total URL count reflects exactly what is in the file. If your CMS is generating duplicate `<loc>` tags, they will be counted. Validating the file can help spot structural duplicate errors.
Why does the analyzer say my sitemap is invalid?
This usually happens if the XML structure is broken, such as a missing closing tag, incorrect namespace declarations, or invalid characters like an unescaped ampersand.
Related Tools
Advertisement
Advertisement