Calculate indexation rates against useful URL cohorts instead of dividing one unreliable site-wide count by another.
For seo agencys, the practical goal is simple: Report indexation by page type, value, and action rather than chasing one vanity percentage.
Related FreeIndexer reading:
- Analytics And Reporting For SEO Growth
- Indexing Vs Traffic Reporting
- Monthly SEO Reporting Dashboard
Quick Answer
Use a defined denominator: canonical, indexable URLs in a specific cohort and date range. Then compare it with the best available indexed count for that same cohort. Do not mix redirects, noindex pages, duplicates, and utility URLs into the target set.
Signals That Matter
- A meaningful denominator excludes URLs that the site does not want indexed.
- Search Console reports and URL Inspection samples answer different reporting questions.
- Rates should be segmented by template, sitemap, business value, and publish age.
- A lower rate can be healthy after sitemap cleanup or deliberate consolidation.
Step-By-Step Workflow
| Step | Check | Evidence To Capture | Next Action |
|---|---|---|---|
| 1 | Define the cohort | Canonical indexable URLs by page type | Freeze the list for the reporting period. |
| 2 | Choose the source | Page indexing report, API, samples, or warehouse | Document coverage and limitations. |
| 3 | Calculate the rate | Indexed target URLs divided by eligible target URLs | Keep excluded-intent URLs outside the denominator. |
| 4 | Segment the result | Template, age, priority, and reason | Find where action is possible. |
| 5 | Report movement | Newly indexed, removed, fixed, and pending | Explain operational changes behind the percentage. |
A useful tracker keeps the evidence and the conclusion separate. Record what the URL returned, what the tool reported, what changed, who owns the next action, and when the page should be reviewed again.
Worked Example
An ecommerce site reports 52% indexation using every discovered parameter URL as the denominator. After limiting the cohort to canonical products and categories in approved sitemaps, the rate is 88%, while the remaining gap is concentrated in thin category pages.
The point of the example is not the exact numbers. It is the sequence: verify the real page, classify the issue, make one defensible change, and preserve enough evidence to evaluate the result later.
Common Mistakes
- Using site: result counts as an exact indexed total.
- Changing the denominator every month without noting it.
- Combining newly published pages with mature evergreen pages.
- Treating 100% indexation as a universal goal.
Where FreeIndexer Fits
FreeIndexer submission logs can be one operational input, but keep submitted, crawled, indexed, ranking, and traffic metrics in separate columns.
Implementation Notes For Each Step
1. Define the cohort
Capture canonical indexable urls by page type before making a conclusion. Freeze the list for the reporting period.
Keep the evidence tied to the exact canonical URL and the date of the check. If the issue affects a shared template or URL pattern, record the pattern as well so the team fixes the system instead of repeating the same manual task.
2. Choose the source
Capture page indexing report, api, samples, or warehouse before making a conclusion. Document coverage and limitations.
Keep the evidence tied to the exact canonical URL and the date of the check. If the issue affects a shared template or URL pattern, record the pattern as well so the team fixes the system instead of repeating the same manual task.
3. Calculate the rate
Capture indexed target urls divided by eligible target urls before making a conclusion. Keep excluded-intent URLs outside the denominator.
Keep the evidence tied to the exact canonical URL and the date of the check. If the issue affects a shared template or URL pattern, record the pattern as well so the team fixes the system instead of repeating the same manual task.
4. Segment the result
Capture template, age, priority, and reason before making a conclusion. Find where action is possible.
Keep the evidence tied to the exact canonical URL and the date of the check. If the issue affects a shared template or URL pattern, record the pattern as well so the team fixes the system instead of repeating the same manual task.
5. Report movement
Capture newly indexed, removed, fixed, and pending before making a conclusion. Explain operational changes behind the percentage.
Keep the evidence tied to the exact canonical URL and the date of the check. If the issue affects a shared template or URL pattern, record the pattern as well so the team fixes the system instead of repeating the same manual task.
Turn The Findings Into An Action Queue
A diagnostic result is useful only when it changes what the team does next. Move each URL into one of four clear queues:
- Ready: the URL is useful, canonical, public, technically accessible, and ready for submission or normal monitoring.
- Fix: the URL has a correctable technical, content, linking, rendering, or reporting problem with an assigned owner.
- Exclude: the URL is intentionally redirected, noindexed, removed, duplicate, private, or otherwise outside the indexing target set.
- Escalate: the issue affects infrastructure, templates, migrations, security controls, or a large URL cohort and needs engineering or product input.
For this topic, the release rule is: Report indexation by page type, value, and action rather than chasing one vanity percentage. Do not leave a URL in a vague pending state. Give it an owner, one next action, and a review date based on the evidence available.
Evidence Log To Keep
| Field | What To Record | Why It Matters |
|---|---|---|
| Canonical URL | The final normalized URL checked by the operator | Prevents variants and redirects from splitting the investigation. |
| Cohort | Page type, template, campaign, locale, or backlink group | Reveals whether the issue is isolated or systemic. |
| Evidence source | Live response, URL Inspection, crawl, log, sitemap, or provider record | Makes the conclusion reproducible. |
| Change made | The exact technical, content, link, or workflow update | Separates action from assumption. |
| Owner and review date | Who is responsible and when the URL will be checked again | Stops the queue from becoming passive reporting. |
Keep submission dates in their own field. A submitted URL has completed an operational step; it has not automatically completed crawling, indexation, ranking, traffic, or conversion milestones. That separation makes the report more accurate and makes failed outcomes easier to diagnose.
Final Action Checklist
- [ ] Define the cohort: Freeze the list for the reporting period.
- [ ] Choose the source: Document coverage and limitations.
- [ ] Calculate the rate: Keep excluded-intent URLs outside the denominator.
- [ ] Segment the result: Find where action is possible.
- [ ] Report movement: Explain operational changes behind the percentage.
- [ ] Confirm the final URL and evidence date in the tracking sheet.
- [ ] Remove excluded or unresolved URLs from the active submission batch.
- [ ] Schedule one follow-up review instead of repeating untracked checks.
Primary Sources
FAQ
What is the formula for indexation rate?
Indexed eligible URLs divided by total eligible URLs, multiplied by 100.
Should noindex pages count in the denominator?
No, not when noindex is intentional and the report measures desired indexation.
How often should I report it?
Use a cadence that matches publishing volume and crawl behavior, with enough time to observe meaningful change.
Next Step
Report indexation by page type, value, and action rather than chasing one vanity percentage.
Keep the final report honest: document what was fixed, what was submitted, what evidence changed, and what still requires time or a separate SEO decision.
