Website Page Counter
Find out how big a website is. The counter discovers the site’s XML sitemap through robots.txt or the usual locations, follows sitemap index files to their child sitemaps and counts the pages listed – then breaks them down by the first folder of the URL, such as /blog/ or /products/, and by the year they were last modified. Because it reads the sitemap, it counts the pages the site itself wants search engines to find.
- Encrypted connection
- No sign-up
- Free to use
How to use Website Page Counter
- Enter a website.
- Click “Count pages”.
- Read the total and the sections.
- Export or validate the list if needed.
Website Page Counter features
Sitemap-based
robots.txt and default locations.
Sitemap indexes
Up to 20 child sitemaps.
Sections
Pages per folder.
Freshness
Pages by last-modified year.
Safe fetching
Public addresses only, with size and time limits.
No crawling
One sitemap request instead of thousands of pages.
When to use Website Page Counter
- Sizing a site before an audit or migration.
- Competitor research.
- Checking that all sections are in the sitemap.
- Planning content work.
Website Page Counter FAQ
Is this the exact number of pages?
It is the number listed in the sitemap. Some sites leave pages out; others list pages that no longer exist.
What if there is no sitemap?
The tool says so; then only a crawl or the search engines’ index can estimate the size.
Why not count indexed pages?
Search engines do not offer exact counts publicly; the “site:” search shows rough estimates.
How many pages can it count?
Up to 50,000 URLs from up to 20 child sitemaps.
Counting pages sensibly
Crawling a large site page by page is slow and puts load on its server. The sitemap is the site owner’s own list and gives a quick, polite answer.
Large differences between the sitemap and what you expect point to missing sections or forgotten pages.
How it works: our server downloads the page once through a guarded fetcher that only connects to public addresses, follows a limited number of redirects and stops after a size and time limit. The HTML is then analysed in your browser as inert text – scripts on the page never run and nothing is stored.
What it cannot see: content and resources that a page adds with JavaScript after it loads, pages behind a login, and servers that block automated requests. For those, open the page in your browser, use its developer tools, or paste the page source where the tool offers a paste option.
Use the results as a starting point: fix the items marked red first, review the yellow warnings in context, and run the check again after a change. Requests are rate-limited to keep the service fair; if you check many pages in a row, wait a few minutes.
Related checks on this site cover the rest of a technical review – speed and Core Web Vitals, security headers, structured data, accessibility and SEO signals – so you can work through a whole site audit one topic at a time.
Who it is for: site owners checking their own pages, developers debugging a release, SEO and marketing teams auditing clients or competitors, and students learning how the web works. No account or installation is needed, and the results are plain text and tables you can copy into a report or ticket.