Website Page Counter
Check how many pages a website has and find all the pages on it in seconds. Auto-discovers the sitemap, follows every nested sitemap, lists each URL by section, and exports the full list as a CSV.
How to check how many pages a website has
There is no single number that answers “how many pages does this website have” — it depends on whether you mean pages the site publishes, pages Google has indexed, or pages that exist but nothing links to. Those three figures are usually different, and knowing which one you are looking at matters more than the number itself. Here are the four ways to find out, and what each one actually measures.
1. Read the XML sitemap (fastest, and what this tool does)
A sitemap is the list of URLs a site formally submits to search engines, which makes it the most direct answer to “how many pages are on this website.” Enter a domain above and the website page counter finds the sitemap the way a crawler does — checking robots.txt for a Sitemap: directive first, then falling back to common paths like /sitemap.xml, /sitemap_index.xml and /wp-sitemap.xml. Index sitemaps that point to dozens of child sitemaps are followed automatically, duplicate URLs are removed, and you get the unique total plus every URL as a downloadable list. It works on any public site, not just your own.
2. Google’s site: operator
Searching site:example.com shows the pages Google has indexed from a domain, and it is the method most people reach for first. It is worth understanding its limits: the “About X results” figure is an estimate that Google has repeatedly said is approximate, it shifts between searches and data centres, and it only ever reflects indexed pages. New pages, noindexed pages, and pages Google chose to drop are all invisible to it. Use it as a sanity check, not a count.
3. Crawl the site’s internal links
A crawler starts at the homepage and follows every internal link it finds. This is the only method that discovers pages missing from the sitemap — but it also misses orphan pages, which by definition nothing links to. Our Visual Sitemap Generator does this and renders the result as a tree, which is the clearest way to see how a site is actually structured rather than how its sitemap claims it is.
4. Google Search Console (your own site only)
The Pages report under Indexing gives the most honest picture for a site you own: how many URLs Google knows about, how many are indexed, and the specific reason each excluded page was skipped. Compare that number against the sitemap total from this tool — the gap between them is usually the most actionable technical SEO finding you will get in an afternoon.
How to find all pages on a website, not just count them
A total is rarely the end goal. Most people who want to find all the pages on a website are doing a content audit, planning a migration, hunting for duplicates, or trying to work out what a competitor publishes. The count above is backed by the complete URL list: expand Browse All URLs to search and filter in the table, or export everything as CSV and pivot it in a spreadsheet.
The section breakdown is usually where the useful findings are. Every URL is grouped by its first path segment, so you can see at a glance that a site has 40 service pages and 2,000 tag archives — a pattern that shows up constantly on WordPress sites and is one of the more common causes of wasted crawl budget. If the shape of that chart surprises you, that is the finding.
Why your page count and Google’s never quite match
Expect these numbers to differ, and read the direction of the gap:
- Sitemap count much higher than indexed count — pages are being submitted but not indexed. Usually thin or duplicate content, or a crawl budget problem on large sites.
- Indexed count higher than the sitemap — Google has found URLs you never submitted. Often parameter URLs, paginated archives, or staging pages that leaked into the index.
- Sitemap listing pages that 404 or redirect — a stale sitemap, which teaches Google to trust it less. The XML Sitemap Validator live-checks a sample of your URLs for exactly this.
- Noindexed pages sitting in the sitemap — a contradictory signal: “please index this” and “do not index this” at the same time.
Does the number of pages on a website matter for SEO?
Not on its own. Page count is not a ranking factor, and a focused 30-page site routinely outranks a sprawling one. What matters is the proportion of your pages that are genuinely useful and genuinely indexed. Large volumes of thin, near-duplicate, or auto-generated URLs spread crawl budget thinly and can weigh on site-wide quality assessment. The practical value of counting your pages is discovering that the number is not what you expected — that is the moment you find the 1,800 tag pages nobody meant to publish.
What a sitemap count cannot see
Worth being clear about the limits, because no page-counting method is complete:
- Orphan and unlisted pages — anything absent from the sitemap is invisible here. A link crawl catches some of these; nothing catches all of them.
- Gated and private pages — content behind a login or paywall is not in a public sitemap, which is normally correct.
- Sites with no sitemap at all — nothing to read. Crawl the internal links instead, and if it is your own site, publishing a sitemap should be the first fix.
- Very large sites — scans are bounded by time and sitemap count. If a scan stops early you will see a “partial scan” label and a note saying so, rather than a confidently wrong total.
Once you have the URL list, the natural next steps are checking which of those pages crawlers can actually reach with the Robots.txt Tester, seeing how Google renders any one of them in the Googlebot Simulator, or pulling page content down as clean text with the URL to Markdown converter.