Get Real-Time Website Traffic Insights (Page Counter)
How to Use This Page Counter
- Find your sitemap URL — usually
/sitemap.xmlor/sitemap_index.xml. Checkrobots.txtif you are unsure. - Paste it into the box and click Count Pages.
- Check whether the result is an index or a flat list — if the count is suspiciously small, it is almost certainly an index of sub-sitemaps.
- Expand sub-sitemaps if needed — the real page count is the merged total after following every child sitemap.
- Compare against Search Console — sitemap count, indexed count, and actual page count are three different numbers, and the gaps between them are where the diagnostics live.
What This Tool Counts (and What It Cannot See)
A sitemap page counter does exactly one thing precisely: it reads an XML sitemap and counts the URLs listed in it. That is genuinely useful for migrations, audits, and index-coverage baselines — but the number it returns is not automatically the number of pages your site has. The most common mistake is treating the first count as the final denominator.
There are three distinct measurements, and conflating them produces the wrong diagnosis:
- Sitemap URL count — what the tool returns. Either an index of sub-sitemaps or a flat list of page URLs.
- Expanded count — the merged total after following every sub-sitemap referenced in the index.
- Indexed count — what Google actually has in its index, reported in Search Console.
For SEO purposes, the sitemap count sets the denominator for index coverage — it tells you what proportion of your submitted inventory actually made it into search results. Without a reliable denominator, you cannot tell whether a coverage gap is a crawl problem, an indexing problem, or simply a sitemap that lists pages it should not[reference:3].
The Index-Type Trap: Why a Sitemap Can Say 6 and Mean 2,292
This is the single most important thing to understand before trusting any page count. A 2026 audit that pulled six live sites and expanded every index-type sitemap found ratios as extreme as 382:1 and 516:1[reference:4].
| Site type | Raw sitemap count | Expanded page count | Ratio |
|---|---|---|---|
| Index-type sitemap (Site A) | 6 | 2,292 | 382:1 |
| Index-type sitemap (Site B) | 19 | 9,814 | 516:1 |
| Flat-list sitemap | 1,200 | 1,200 | 1:1 |
Source: aiaffer.com, October 2026 audit of six live sites[reference:5]. For an index-type sitemap, the raw file contains only `
The practical rule: if the sitemap count is far smaller than the number of pages you know you published, it is an index — not a page list. Expand it before drawing any conclusion.
The Three-Way Gap: Sitemap vs Indexed vs Actual
Once you have an accurate sitemap count, the next diagnostic is how it compares to the indexed count and to the pages that genuinely exist. A healthy index is not "everything indexed" — it is "everything worth indexing is indexed, and everything else is deliberately excluded."
Two 2026 data points frame the gap:
- In an audit of an 800-post blog, Search Console reported 1,105 submitted URLs and 799 pages that received impressions — roughly 72% real coverage. The "indexed = 0" figure in the Sitemaps API was a deprecated field returning zero for everyone, not a measurement[reference:6].
- Across ecommerce audits, indexed-URL counts averaged roughly 2.4× the number of pages clients intended to rank — the opposite problem, where bloat inflates the index[reference:7].
Both directions are diagnostic. A gap below the intended count means pages you care about are not being indexed. A gap above it means URLs you never intended to index are competing with the ones you do. For a deeper look at the below-intended case, run affected pages through our Google Index Checker.
Sitemap Hygiene: What Belongs in the File
A page counter is only as useful as the sitemap it reads. If the sitemap contains URLs that should not be there, the count is inflated and the coverage ratio is meaningless. 2026 sitemap best practices are unambiguous on what belongs[reference:8][reference:9]:
| Include | Exclude | Why |
|---|---|---|
| Canonical URLs only | Duplicate or parameter variants | Non-canonical URLs send mixed signals and split crawl attention |
| 200 OK, indexable pages | 404s, redirects, 5xx errors | A sitemap should list what can actually be indexed |
Pages not blocked by robots.txt |
Pages blocked by robots.txt |
Listing a blocked URL is a classic self-defeating mistake[reference:10] |
Pages without noindex |
noindex pages |
Inviting a crawler to a page whose only instruction is "go away" wastes budget[reference:11] |
The `
The noindex-in-sitemap mistake is worth calling out specifically because it is so common. In the 800-post audit, 74% of tag hubs were noindexed and listed in the sitemap anyway — 636 URLs, more than half the file, existed solely to invite a crawler to a page that told it not to index. Removing them took the sitemap from 1,742 URLs to 1,099[reference:14].
Orphan Pages: The Crawl-Budget Leak the Counter Cannot See
A page in your sitemap is discoverable, but discovery is not the same as attention. Google's crawl-budget documentation is explicit that pages discovered only via sitemap get lower priority than pages discovered through internal links[reference:15]. A sitemap-only URL is still effectively an orphan for ranking purposes.
The scale of the problem is well measured. 78% of audited sites have orphan-page signals, and Botify's research across enterprise customers put orphan pages at 26% of Googlebot's crawl budget on the average site, up to 70% on the worst[reference:16][reference:17]. That is a quarter of Google's attention going to pages nobody linked to, while the pages you actually want to rank wait in the queue.
This is precisely where a sitemap comparison becomes useful. Cross-reference the sitemap URL list against a full site crawl: any URL that appears in the sitemap but has zero inbound internal links is an orphan candidate. Not every orphan needs a link — some should be redirected, noindexed, or removed — but you cannot make that decision without seeing them[reference:18].
Index Bloat: When a Larger Count Is the Problem
Index bloat is not a raw page count; it is the ratio between the URLs you intended to publish and the URLs Google has actually indexed[reference:19]. A 200,000-page retailer with unique product pages can be clean while a 900-page brochure site is badly bloated, because the benchmark is the site against its own intent, not an absolute number.
The harm is threefold and none of it is a penalty: crawl capacity is spent on URLs that will never earn a visit, near-duplicates compete with the page you want to rank, and at volume a large body of thin templated pages drags on how quality systems assess the domain[reference:20]. The fix order matters because it is ordered by reversibility: consolidate, then canonicalize, then noindex, and only then remove — deletion is the one step you cannot undo[reference:21].
A page counter helps here because it establishes the intended-publish denominator. If the sitemap lists 2,000 pages and Search Console reports 4,800 indexed, the 2.4× gap is the bloat signal — and the excess is almost always filtered views, internal search results, parameter URLs, or pagination artifacts[reference:22].
When a Sitemap Page Counter Is Actually Useful
The use cases below are the ones where an accurate count changes a decision:
- Setting an index-coverage baseline. Compare submitted URLs to pages with impressions to get a coverage ratio you can track quarter over quarter[reference:23].
- Verifying a migration or redesign. Count before and after to confirm no pages silently disappeared from the sitemap.
- Scoping an audit. The sitemap list is the starting inventory for orphan checks, index-bloat ratios, and stratified sampling[reference:24].
- Competitive sizing. A competitor's sitemap count gives a directional estimate of their content volume — with the index-type caveat that the raw number may describe sub-sitemaps, not pages[reference:25].
- Detecting sitemap-generation bugs. A filter that anchors a path incorrectly can silently exclude valid pages; the count is how you notice[reference:26].
Frequently Asked Questions
Is this sitemap page counter free?
Yes. The tool is completely free, requires no sign-up, and runs in your browser. The sitemap URLs you check are not stored on a server.
Why is the count so much lower than the number of pages I published?
Almost certainly because your sitemap is an index-type sitemap — the raw file lists sub-sitemaps, not page URLs. Following each child sitemap and merging the results produces the real count. Ratios of 382:1 and 516:1 have been documented on live sites[reference:27].
Is the sitemap count the same as the number of pages Google has indexed?
No. The sitemap count is your submitted inventory; the indexed count is what Google actually has. They should be compared, not equated. In one audited blog, 1,105 URLs were submitted and 799 pages received impressions — about 72% real coverage[reference:28].
Should my sitemap include every page on the site?
No. It should include only canonical, indexable pages that return 200 and are not blocked by robots.txt or noindex. Listing noindex pages or blocked URLs wastes crawl budget and inflates the count[reference:29][reference:30].
What is an orphan page, and why does it matter for a sitemap count?
An orphan page has no internal links pointing to it. It may still be discoverable through the sitemap, but sitemap-discovered pages get lower crawl priority. Orphan pages consume 26% of Googlebot's crawl budget on the average site, up to 70% on the worst[reference:31]. Comparing the sitemap list to a crawl is how you find them.
What is index bloat?
Index bloat is the ratio between the URLs you intended to publish and the number Google indexed. A 2.4× ratio is common on unoptimized ecommerce sites, driven by filtered views, parameters, and internal search pages[reference:32][reference:33]. It is not a penalty, but it dilutes quality signals and slows discovery of pages that matter.
Related Indexing & Site Architecture Tools
Use these free tools to turn the page count into a diagnosis:
- Google Index Checker — compare submitted URLs against what Google actually indexed.
- Broken Link Checker — find the dead URLs that inflate sitemap counts and waste crawl budget.
- SEO Site Score Generator — see whether index coverage is one of several compounding technical gaps.
- Meta Tag Analyzer — catch the
noindexdirectives that should have excluded pages from the sitemap. - Google Page Speed Checker — slow pages are crawled less often, which widens the submitted-vs-indexed gap.