Estimate how many pages of a site are publicly indexable by discovering its robots.txt and XML sitemaps, counting the URLs they list, and checking the homepage's index status.
Pro tip: This counts sitemap-listed URLs, not Google's real index; a missing sitemap.xml drags the estimate to zero.
Enter a domain and the tool fetches the homepage, then looks for the site's robots.txt to find any Sitemap: lines it declares. If robots.txt lists sitemaps, those are used; if it does not, the tool falls back to the conventional /sitemap.xml location. It then walks the sitemaps it finds — following a sitemap index to its child files where one exists — and counts the unique URLs listed inside the <urlset> documents. The headline number is that count of indexable URLs.
Alongside the count, the tool checks whether the homepage itself is indexable by reading the robots meta tag in the page head and flagging a noindex directive if present. It reports how many sitemap files it discovered, the robots.txt status, and a sample of the first URLs it found so you can eyeball what is actually listed. This is deliberately different from typing site: into Google. It measures what the site itself declares as indexable, which you control, rather than what a search engine currently has stored.
Run the check on the canonical version of your domain (for example the https, non-www form you actually serve) so the homepage and robots.txt resolve cleanly. If the count looks far lower than your real page total, open the discovery table and confirm the sitemap was found and parsed — a single broken or gzipped sitemap can leave many pages uncounted. Use the sample URL list as a quick quality gate: if you see staging paths, tag archives, or parameter URLs you did not expect, that is a cue to tidy your sitemap before search engines crawl it.
The most common misunderstanding is reading this number as "pages Google has indexed". It is not — it is a count of what the site advertises as indexable through its own sitemaps. A second pitfall is assuming a low number means a problem with the tool when the real cause is a missing, misnamed, or unreferenced sitemap. Finally, remember that listing a URL in a sitemap is a suggestion to crawlers, not a guarantee of indexing; a page can be in the sitemap yet excluded by Google for quality, duplication, or canonical reasons.
It cannot report how many pages Google or Bing have truly indexed — only the search engine knows that, and the official place to see it is Search Console's Indexing report (or Bing Webmaster Tools). Sites with no sitemap, or with sitemaps that omit pages, will produce a low or incomplete estimate. To keep each check fast the tool reads a limited number of sitemap files rather than crawling unbounded sitemap sets, so very large sites may be partially sampled, and the sample URL list is capped. Compressed (.gz) sitemaps or unusual XML formats can also reduce the count. The fetches run on our edge against the public site, so no login-only or private pages are seen.
Input: highseotools.com
Output: 83 indexable URLs · homepage indexable: Yes · 1 sitemap found (robots.txt HTTP 200 → https://highseotools.com/sitemap.xml)
Measured 2026-07-17 on this site's own sitemap; the count changes as pages are added or removed. Cross-check against Search Console for the real indexed total.
Input: example.com
Output: 0 indexable URLs · homepage indexable: Yes · 1 sitemap found · note: "Could not parse sitemap format from https://example.com/sitemap.xml."
Measured 2026-07-17. example.com serves no robots.txt (HTTP 404), so the tool fell back to /sitemap.xml — that URL returns the placeholder page rather than XML, which is why a file is counted as found but no URLs are counted.
No. It estimates indexable URLs from the site's own sitemaps and robots.txt. Only Google Search Console (or Bing Webmaster Tools) reports the true indexed count.
It reads Sitemap: lines from robots.txt first, and if none are listed it falls back to the standard /sitemap.xml location, following a sitemap index to its child files.
It reports whether the homepage carries a noindex robots meta tag. "No" means a noindex directive was found, which would keep the homepage out of search results.
Without a discoverable sitemap there is little to count, so the estimate will be low or zero even if the site has many pages.
The tool reads a limited number of sitemap files for speed, and broken, gzipped, or unreferenced sitemaps are not counted, so large or misconfigured sites can be undercounted.
No. A sitemap entry is a suggestion to crawlers. Search engines may still skip a page for quality, duplication, or canonical reasons.
A site: query reflects a search engine's current index; this tool reflects what the site declares as indexable. The two measure different things.
I document how each check works, where its data comes from, and which parts are only estimates.