--- title: "Free Website Page Counter: Count Pages on Any Site" description: "Count pages on any website via XML sitemaps. Get total count, per-directory breakdown, and exportable URL list. Free, no signup. 5 checks per hour." url: https://serpview.com/tools/website-page-counter --- Free · No signup # Website Page Counter Free website page counter. Enter any domain. We discover all pages via sitemap.xml, sitemap\_index.xml, and robots.txt, follow sitemap indexes, and return a total count, per-directory breakdown, and exportable URL list. 5 free checks per hour per IP. No signup. ## How it works A short, focused workflow — input, run, read the result. 1. 01 ### Enter a domain Type any domain like example.com or https://example.com. We auto-https it. You can also paste a direct sitemap URL (https://example.com/sitemap.xml) to skip discovery. 2. 02 ### Click Count Pages We fetch /robots.txt first, parse every Sitemap: directive, then try /sitemap.xml and /sitemap\_index.xml. Each discovered sitemap is followed recursively. Sitemap indexes are auto-resolved to find all child sitemaps. Per-IP rate limit is 5/hour to keep the public endpoint cheap. 3. 03 ### Review the breakdown Total URL count, per-directory breakdown (top 10 directories shown with counts), the list of sitemaps we found, and the full deduplicated URL list. Duplicate URLs across sitemaps are detected and removed. 4. 04 ### Copy or download Copy the full URL list to clipboard, or copy an individual sitemap block. The data is also available as JSON in the raw response, useful for piping into a spreadsheet or audit tool. ## What is a website page count, and why does the sitemap gap matter? A website page count is the number of URLs declared in your XML sitemaps. It is not the same as what Google has indexed, and the gap between the two is one of the most useful diagnostics in technical SEO. If your sitemap says 500 and Google indexes 120, 380 URLs are being excluded for a reason worth investigating. Every site with a sitemap exposes a number: how many URLs the owner wants search engines to consider. The count is reachable from three places: /robots.txt (where Sitemap: directives live), /sitemap.xml (the standard path), and /sitemap\_index.xml (a wrapper that points at multiple child sitemaps). Most modern CMSes ship all three automatically. The total count is the deduplicated union of every entry across every child sitemap.The number rarely matches Google Search Console's Pages report. The sitemap count is what you told Google to consider. The indexed count is what Google chose to actually index. The gap is caused by thin content, noindex directives, duplicate URLs, crawl blocks, soft 404s, redirect chains, and pages Google discovered through links but never saw in your sitemap. The gap is also caused by URLs in the sitemap that no longer exist, which is its own problem.Our counter reads robots.txt, follows every Sitemap: directive, recursively opens every child sitemap, deduplicates across them, and returns a total count with a per-directory breakdown. Useful for spotting categories you forgot existed, audit prep, and quarterly site-size tracking. 5 free checks per hour per IP. 3 Sources for sitemap discovery (robots.txt, sitemap.xml, sitemap\_index.xml) 5/hr Free checks per IP, no signup required 50K+ URLs the counter handles on large ecommerce catalogs ## What this website page counter checks Every source of declared URLs on your domain, with deduplication and per-directory breakdown. - robots.txt Sitemap directives — reads every Sitemap: line in /robots.txt first. This is where most large sites list all of their child sitemaps. - Standard sitemap.xml — auto-fetches /sitemap.xml when present. Works for sites that ship one sitemap file with all URLs. - Sitemap index files — follows /sitemap\_index.xml and recursively opens every child. Recursion depth capped to avoid loops. - Deduplication — URLs appearing in more than one sitemap are counted once. Common on sites that maintain separate news, product, and page sitemaps. - Per-directory breakdown — groups URLs by top-level path (/blog/, /products/, /docs/api/) with counts. Surfaces category sprawl you forgot existed. - Exportable URL list — full deduplicated list with a copy-to-clipboard button. JSON output available in the raw response for piping into a spreadsheet or audit. - Missing sitemap detection — explicitly reports when no sitemap is found. Most modern CMSes (WordPress Yoast, Shopify, Wix, Squarespace, Webflow) generate one automatically. ## Who uses this website page counter Anyone who needs to know how big a site actually is, for audits, migrations, and competitive research. Technical SEOs ### You're starting a 2000-page site audit and need to know the total URL count plus per-directory breakdown before scoping. Get the count and the directory split in 30 seconds. Use the numbers to scope the crawl budget, set priority tiers, and write the audit proposal. In-house SEOs ### Your sitemap says 800 pages but Google Search Console's Pages report shows 240 indexed, and you need to know why. Run the counter on your own domain, compare 800 vs 240, then dig into Google Search Console's Pages report to see which exclusion applies to each URL. Agencies ### You're pitching a 12-client portfolio review and need a one-page size summary per domain. Generate the count for each client, paste the per-directory table into the deck, and have a comparable baseline across the whole portfolio in an afternoon. Ecommerce managers ### You're migrating a 50,000-URL Shopify catalog to a new platform and need a precise count to size the migration. Confirm the source catalog size, identify category sprawl you want to consolidate, and avoid the classic migration surprise of shipping 30K redirect rules you did not need. Developers ### You're building a static site and want to confirm your build pipeline is emitting the right number of pages. Run the counter against the staging domain after each build, catch any page that is missing from the sitemap before deploy. Content marketers ### Your blog has grown to 600 posts over 4 years and you have no idea how many actually exist vs how many are draft or unpublished. Get the count, see which directories still have old URLs from a 2019 redesign, and clean up the sitemap before the next quarterly crawl. ## Related glossary terms Want a deeper dive? These glossary entries explain the concepts behind this tool. - [XML Sitemap](https://serpview.com/glossary/xml-sitemap) - [Crawl Budget](https://serpview.com/glossary/crawl-budget) - [Indexability](https://serpview.com/glossary/indexability) ## Frequently Asked Questions Everything you need to know about counting pages on a website via XML sitemaps in 2026. Three sources, in order: (1) every Sitemap: directive in /robots.txt, (2) the standard /sitemap.xml path, (3) the /sitemap\_index.xml path. We fetch each one, detect if it's a sitemap index (contains ), and recursively follow every child entry. The final URL list is the union of all entries across every child sitemap, with duplicates removed. Most CMS platforms (WordPress, Shopify, Wix, Webflow) generate one of these automatically. Almost never exactly, and that's actually useful. Our count = URLs declared in your sitemaps (what you told search engines to consider). Google's index count = URLs Google chose to actually index (which may be less (thin content, duplicates, noindex directives, crawl blocks) or more (pages Google discovered through links but weren't in your sitemap). The gap between the two numbers is one of the most useful things to investigate in a technical SEO audit. If sitemap count is 500 and indexed is 120, 380 URLs are being excluded. Check Google Search Console's Pages report for why. We can't count pages on a site with no sitemap, there's no authoritative list of URLs to read from. The tool will tell you so explicitly. The fix: most modern CMSes (WordPress via Yoast/RankMath, Shopify, Wix, Squarespace, Webflow) generate a sitemap automatically. If yours doesn't, install a sitemap plugin or generate one via a static-site generator plugin, then run the counter again. XML sitemaps are a foundational SEO best practice. They help search engines discover every page on your site, especially new ones that don't have inbound links yet. Yes, the per-directory breakdown groups all discovered URLs by their top-level path (everything after the domain, up to the second slash). For example, /blog/, /blog/seo/, /products/, /docs/api/ would each get their own row with a count. The full deduplicated URL list is also shown below the breakdown, with a copy-to-clipboard button. For a 50,000-page e-commerce site, expect the per-directory view to surface categories you forgot you had, common finding during site audits. Free, yes. 5 checks per hour per IP, no signup, no daily limit, no email gate. Privacy, mostly: the domain you enter and the fetched sitemaps pass through our Vercel serverless endpoint. We don't log request bodies, don't store the sitemap contents, and don't use them for training any AI model. The in-memory rate-limit counter is the only state kept, and it resets on cold start. If you want to verify, open DevTools → Network while using it: only one POST to /api/website-page-counter/count leaves your browser, returning the structured breakdown. ## More free tools Free, no signup required. Built by the team behind SERPView. [Google SERP Simulator ToolSimulate exactly how your page appears in Google search results. Live SERP preview with title, URL, and description, plus character and pixel-width warnings before you publish.Try it free](https://serpview.com/tools/serp-simulator)[Meta Description GeneratorGenerate 5 AI meta description variants from your page title. See the live SERP preview and copy the winner to your CMS.Try it free](https://serpview.com/tools/meta-description-generator) ## Want this automated across your whole site? SERPView monitors title tags, meta descriptions, and structured data for every URL — alerting you the moment something breaks or could be improved. [Get started free](https://app.serpview.com/auth)