Published pages and indexed pages are not interchangeable metrics. A page can be published, crawlable, and still not be indexed. A page can also be indexed long after it was published, or remain indexed after it has been removed from the site. If you track only one of these counts, you will miss what stage of the pipeline is actually changing.
For SEO leads and growth teams, the useful question is not "how many pages do we have?" It is "where are pages getting stuck between release and indexation?" That is a systems question, not just a reporting question.
Published count is a production metric
Published URL count tells you how many pages have been released into the site’s live system. It is usually controlled by your CMS, database, template logic, or publishing workflow. This number is useful because it reflects output, velocity, and backlog burn-down.
But published count does not say whether the pages are discoverable, eligible, or valuable enough to be indexed. A team can ship 5,000 pages in a week and still have a weak indexation outcome if internal links are thin, the page family is too redundant, or the site is sending mixed signals about canonicalization and importance.
That is why published count should be treated as a production-stage metric, similar to deployment volume. It tells you what entered the system, not what search engines accepted.
If you need a structured way to measure the release side of the pipeline, how to measure SEO publishing velocity is the better companion metric. It helps separate throughput problems from indexation problems.
Indexed count is a search-facing outcome metric
Indexed URL count tells you how many published pages are present in a search engine’s index. This is closer to an outcome metric, but it still needs context. Indexation is not a universal approval signal, and it is not always a stable population. Search engines may index pages unevenly across templates, markets, or page families. They may also deindex pages over time if the site changes, duplicates accumulate, or the page set stops looking distinct enough.
That means indexed count is not just a number to maximize. It is a signal about how much of your published inventory is considered eligible and worth keeping visible.
If you want to understand the delay between release and indexation, use cohort tracking rather than a single snapshot. How to measure time to index for newly published SEO pages covers the mechanics in more detail. The main point here is that the lag itself is often more informative than the raw count.
The gap between published and indexed pages is the real metric
The difference between published URL count and indexed URL count is where the operational story lives.
A widening gap can mean several different things:
- pages are being published faster than they are discovered or evaluated
- internal linking is not distributing importance well
- sitemap coverage is incomplete or inconsistent
- template-level duplication is making the new pages look unworthy of indexation
- canonical, noindex, redirect, or rendering rules are interfering
- search engines are simply slower to process a new cohort than usual
The same gap can also be normal. A site that publishes large batches of low-priority or long-tail pages should not expect every URL to index immediately. The point is not to force the gap to zero. The point is to understand whether the gap is stable, shrinking, or getting worse.
In practice, the gap should be monitored in three ways:
- Absolute gap — published minus indexed URLs.
- Indexation rate — indexed divided by published, ideally by cohort or page family.
- Lag over time — how long newly published pages take to enter the index.
Together, those three views answer different questions. Absolute gap tells you how much inventory has not made it through. Indexation rate tells you how much of a release cohort is being accepted. Lag tells you whether the system is getting slower or more inconsistent.
Track cohorts, not just totals
A sitewide total can hide the problem. Suppose your site has 80,000 published pages and 60,000 indexed pages. That sounds like a 25% gap, but it does not tell you whether the missing 20,000 pages are mostly old dead inventory, a recent rollout, or one broken template family.
Cohort tracking is usually more useful:
- pages published in the last 7 days
- pages published in the last 30 days
- pages grouped by template or directory
- pages grouped by market, category, or product line
- pages with different internal link depth or sitemap treatment
This lets you see whether the indexation gap is concentrated in a specific release wave or spread across the whole site. It also makes it easier to connect the metric to a change in process.
For example, if a new template goes live and the 30-day indexation rate is materially lower than prior cohorts, the issue may be in the template, not the content calendar. If all cohorts slow down at once, the cause may be broader: crawl demand, site architecture, or a technical change that altered how pages are surfaced.
This is where how to audit your SEO publishing infrastructure becomes useful. The gap is usually a symptom of something upstream in the publishing system.
What to use as the primary KPI
There is no single metric that works for every team, but most growth teams should avoid using published count or indexed count alone as the primary KPI.
A better default is:
- published count for delivery tracking
- indexed count for search-visible inventory
- cohort indexation rate and time to index for operational health
If the team only tracks published pages, it can mistake output for impact. If it only tracks indexed pages, it can miss whether indexation is lagging behind a healthy publishing cadence or whether inventory is being added faster than search can process it.
The more pages you publish, the more important it becomes to separate these stages. Large sites usually fail in the gap between them, not at the moment of publication itself. That is why broader infrastructure work matters, especially as page volume grows. Articles like how to build SEO infrastructure for the next 100,000 pages and how to keep a large SEO site healthy over time are useful if you are moving from page-count reporting toward system-level control.
What to watch when the gap changes
If the published-to-indexed gap expands, do not assume the cause is "Google being slow." Start by asking which stage changed.
- Did publishing volume increase sharply?
- Did internal linking change, leaving new URLs isolated?
- Did the sitemap include the pages consistently?
- Did canonical, robots, or rendering behavior change?
- Are the missing pages concentrated in one template family?
- Did the site introduce near-duplicate variants that dilute distinctiveness?
If the gap narrows, that is also worth interpreting carefully. It may mean the new pages are healthier. It may also mean publishing slowed down, so there is less new inventory to evaluate. A shrinking gap is only a good sign if it reflects better indexation efficiency, not just lower output.
The most practical way to think about the two metrics is this: published pages are what you ship; indexed pages are what search systems keep. The distance between them tells you how well your publishing system and search visibility system are working together.
That distance is the signal worth managing.