What is Indexation Rate?

Indexation rate: turning coverage into a speedometer

Indexation rate quantifies how efficiently URLs convert into indexed pages—and how quickly that happens after publish or recrawl. Where index coverage shows static buckets in Search Console, indexation rate is the operational KPI SEO engineers and growth teams track week over week:

• What percentage of our indexable inventory is indexed?
• How fast do new URLs achieve indexed status?
• Is crawl-to-index conversion improving after fixes?

Without rate thinking, teams celebrate crawl spikes while indexed counts stall.

Two complementary rate definitions

Practitioners use indexation rate in two related senses—label them clearly in dashboards:

Stock rate (point-in-time)

Indexation rate (stock) =
  Indexed URLs in scope
  ───────────────────────── × 100
  Indexable URLs in scope

Example: 36,100 indexed ÷ 40,000 indexable PDPs = 90.3% stock indexation rate.

Flow rate (velocity)

Indexation rate (flow) =
  URLs newly indexed in 14 days
  ─────────────────────────────── × 100
  URLs published in 14 days

Example: 280 of 350 new articles indexed within 14 days = 80% flow indexation rate.

Stock measures portfolio health; flow measures launch pipeline performance.

The crawl-to-index conversion funnel

Indexation rate sits at the bottom of a funnel:

Indexable inventory     40,000   100%
Discovered by Google      38,500    96%
Crawled (28d)             37,200    93%
Indexed (GSC)             36,100    90%  ← stock indexation rate

A weak crawled → indexed step with strong crawl is the signature of low indexation rate despite healthy bots.

Benchmarking indexation rate by template

Site-wide percentages hide template disasters:

Weighted indexation rate (revenue tiers):
  Tier A URLs:  98.2%  (SLA: >95%)
  Tier B URLs:  87.4%
  Tier C URLs:  41.0%  (acceptable if deprioritized)

Executive SLAs should anchor on tier-A stock rate, not sitewide averages diluted by junk.

Measuring indexation velocity after publish

Content and product teams care about time-to-index:

Publish date: 2026-08-01
First crawl:  2026-08-02  (t+1d)
Indexed:      2026-08-05  (t+4d)
Velocity SLA: indexed within 7d → PASS

Track distributions, not only means:

Long p90 tails on new URLs indicate weak internal linking or low site authority—not necessarily page-level defects.

Data sources for indexation rate models

Join publish dates from CMS with first-seen indexed dates from weekly GSC exports to compute flow rate credibly.

Factors that raise or lower indexation rate

Indexation rate responds to architecture and quality, not keyword density on a single page.

Indexation rate vs crawl rate

High crawl + low indexation = fix quality and duplication, not beg for more crawl.

Low crawl + low indexation = fix discovery and crawlability first—rate math fails upstream.

Setting indexation rate SLAs

Example enterprise SLAs:

Tier-A URLs:
  Stock indexation rate ≥ 95%
  Flow: 90% indexed within 14 days of publish

Tier-B URLs:
  Stock ≥ 80%
  Flow: 70% within 30 days

Non-strategic facets:
  Stock ≤ 20% (noindex/canonical program)

Review SLAs quarterly as catalog depth and locale count change. Pair rate changes with absolute counts—a 2% gain on 50 URLs differs from 2% on 50,000.

Common indexation rate mistakes

• Denominator pollution — including non-indexable faceted URLs inflates "low rate" panic.
• Ignoring intentional exclusions — subtract noindex inventory from denominator.
• Single site-wide number — masks template-level collapse.
• Confusing with ranking — 100% indexation on zero-demand pages yields no traffic.
• Daily overreaction — GSC lag makes daily rate noisy; use weekly rolls.

Improving indexation rate: prioritized playbook

1. Clean the denominator — noindex or canonical junk URLs you never want indexed.
2. Fix top revenue URLs not indexed—highest ROI on stock rate.
3. Accelerate new URLs — hub links, sitemap, Inspection requests after quality pass.
4. Resolve crawl→index rejects — sample "crawled — currently not indexed" weekly.
5. Re-measure after 28 days — allow indexing pipeline lag before declaring failure.

How Crawlox helps

Crawlox tracks which URLs are indexable, how they link internally, and where duplication or noindex depresses conversion before you compute indexation rate from Search Console. Use Crawlox to define a clean indexable inventory denominator, flag orphans that slow flow rate, and validate that template fixes actually lift crawl-to-index conversion on the next GSC export cycle.