This page explains how IndexVero defines, measures, and reports backlink-indexing outcomes without treating campaign processing as proof of Google indexing. It is a public reporting standard, not a disclosure of IndexVero’s proprietary routing, bulk-checking algorithms, infrastructure, or anti-abuse controls.
The measurement model
IndexVero reviews indexing work as a sequence of distinct events:
submitted URL → campaign processing completed → dated observation → recheck or remediation
Each event answers a different question. Keeping them separate prevents an operational status from being presented as a Google indexing guarantee.
1. Submitted URL
A submitted URL is an eligible URL accepted into an IndexVero campaign. Submission records workload; it does not prove that the delivery workflow finished, that Google crawled the page, or that the page was observed in search results.
2. Campaign processing completed
Campaign processing completed means IndexVero’s delivery workflow has finished. A campaign marked completed is operationally complete, but that status does not mean every URL was indexed. Google independently controls crawling, canonicalization, indexing, and serving.
3. Dated observation
An index observation is a time-stamped check of a public URL performed without access to the site’s Google Search Console property. It records what the configured checker could observe at that time. It is not privileged access to Google’s internal index database and must not be translated into a specific Search Console exclusion reason.
4. Recheck or remediation
Index visibility can change. A URL not observed on one check may appear later, while an earlier observation may change after canonicalization, removal, or other processing. Rechecks create a dated history; remediation investigates discovery, availability, directives, canonicalization, or source-page quality where appropriate.
Observation classes
IndexVero keeps four outcomes separate:
- Exact URL observed — the submitted URL was observed in the checked public results.
- Alternate or canonical form observed — Google surfaced another URL representation associated with the submitted page. This is reported separately because it is not an exact-URL match.
- Not observed — neither an eligible exact nor alternate representation was observed at check time. This is a time-bound negative observation, not proof of permanent deindexing.
- Unavailable — the check could not produce a valid verdict. Unavailable checks are excluded from negative-result counts and must not be converted into “not observed.”
How IndexVero calculates an observed index rate
Unless a report explicitly states otherwise, the combined observed rate is calculated as:
(exact URL observations + eligible alternate/canonical observations) ÷ eligible completed observations
A defensible report must state its denominator, date range, observation window, exact-only or combined definition, exclusions, and treatment of unavailable checks. First-check and recheck rates must not be mixed without disclosure.
Published operating baseline
To date, IndexVero has recorded 3,364,494 submitted URLs across 30,264 completed campaign workflows. These are cumulative totals; they describe operational volume, not confirmed indexing.
Across 737,787 URLs checked between 3 July and 15 September 2026, the checker recorded 55.51% as indexed. The denominator is observations, not unique websites, customers, or the whole web.
Measured week by week over the ten complete calendar weeks in that period (5 July–6 September; the partial opening week and the still-running current week are excluded from this range but included in the cumulative totals above), the observed index rate ranged from 42.03% to 62.62%. The 55.51% figure is the aggregate for the period, not a level the checker holds steady at.
The match-type split has not been recomputed for this period. The most recent split available is the earlier July 2026 sample of 166,988 dated observations, in which there were:
- 65,148 exact-URL observations;
- 15,416 alternate/canonical-form observations; and
- 86,424 not-observed outcomes.
Exact plus alternate observations represented 48.25% of that earlier sample.
Scope and limitations
- The published figures use aggregate, non-personal operating records. Customer URLs and personal data are not published.
- The observed population is mixed and self-selected. It should not be generalized to every website, delivery channel, link type, or future period.
- An external observation is not Google Search Console ground truth.
- Observed indexing does not guarantee ranking, traffic, link value, or permanence.
- Campaign processing does not guarantee crawling or indexing.
- Changes between checks are observational. They do not, by themselves, prove that an IndexVero action caused Google to index or remove a URL.
What remains proprietary
To protect customers, platform security, operational relationships, and IndexVero’s competitive methods, this public methodology does not disclose:
- internal service-channel selection, routing, integrations, commercial terms, or channel-specific configurations;
- internal query construction, batching, fallback, retry, prioritization, or matching algorithms;
- scoring thresholds, fraud and abuse controls, capacity rules, or infrastructure topology; or
- customer-level campaign data, URLs, account activity, or channel responses.
These details are not required to interpret the public metrics. The reporting definitions, denominator, date range, result classes, and limitations above are the reproducibility boundary for published claims.
How to read an IndexVero report
A client-ready report should include the project or cohort name, eligible URL count, campaign-processing state where relevant, check date, observation method version, exact matches, alternate matches, not-observed items, unavailable checks, exclusions, and the rate definition used.
For practical workflows, see Bulk Index Checker, tracking backlink indexing over time, and proving an index rate to clients.
Methodology updates
Version 1.2 — September 15, 2026. Refreshed the published operating baseline to 3,364,494 submitted URLs / 30,264 completed campaigns and 737,787 checked URLs (55.51% indexed, 3 July–15 September 2026). The match-type split still uses the July 2026 sample below; it has not been recomputed for this period. Added Dataset structured data for this page.
Version 1.1 — August 2, 2026. Public methodology covering campaign-processing separation, dated observation classes, combined observed-rate calculation, aggregate baseline, limitations, and the proprietary-method boundary.