Google Indexing Time Study: Baseline and First Cohort

01

Dataset and period

This page is the first public status report for the Rank Builder Google Indexing Time Study.

It reports two things:

1. The aggregate Search Console baseline before the new indexing corpus could materially affect performance data.
2. The composition and evidence status of the first URL cohort.

It does not report a median indexing time. The URL-level evidence required for that calculation is not yet available in sufficient quantity.

Pre-expansion baseline

The baseline covers twelve complete Search Console days from July 13 through July 24, 2026.

The data was observed in the internal aggregate analytics store on July 26, 2026, with Search Console data complete through July 24. The bounded query fingerprint for the published calculation is:

d0f7b3208d888d78

The baseline is deliberately sitewide. The current analytics record does not contain page-level indexing events for this period.

Search Analytics can group performance by page and date, but Google notes that its API is internally bounded and does not guarantee every possible row.^[1] The study therefore treats a recorded first impression as affirmative evidence while treating a missing row more cautiously.

First cohort

The first cohort contains 31 active canonical article URLs released across four production batches.

The duplicate Batch 2 troubleshooting hub is excluded because it was archived and redirected to the preserved flagship article.

The cohort spans:

• Search Console indexing statuses
• HTTP and redirect failures
• Canonicalization and discovery
• JavaScript and rendering
• Crawl-budget guidance
• WordPress, Shopify, Next.js, and Cloudflare implementation

This is not a randomized sample of the web. It is a practical cohort of connected technical-SEO pages published on one young domain.

02

Methodology

The full registered protocol appears in Google Indexing Time Study: Methodology.

For this status report, a URL counts as eligible only when it is:

• public on the canonical domain;
• a stable 200 HTML page;
• crawlable and indexable;
• self-canonical;
• present in the sitemap;
• internally linked;
• tied to a verified production commit.

The study seeks the following events:

The URL Inspection API reports information about Google's indexed version. It does not run a live test.^[2] A positive live test may show technical eligibility, but it does not establish that Google has selected the URL for the index.^[3]

Reporting thresholds

The registered gates are:

• At least 10 confirmed indexed URLs before publishing a median
• At least 20 confirmed indexed URLs before publishing percentile estimates
• At least 7 days of follow-up for the first descriptive comparison
• A primary observation window of up to 28 days

Before those gates are met, the page may report counts and individual bounded intervals. It must not imply a stable central estimate.

03

Result

Current evidence status

The current result is therefore:

No indexing-duration estimate is available yet.

That is not a failed study. It is the correct result when a cohort has been registered but the observation system has not yet produced enough URL-level evidence.

What can be concluded now

The site had measurable but weak search visibility before the expansion:

• 298 impressions across twelve complete days
• No recorded clicks
• Average position far outside the range likely to produce meaningful traffic
• Daily impressions between 17 and 36

The new corpus is large enough to support an indexing cohort, but the baseline cannot tell us:

• how many new URLs Google has discovered;
• which URLs have been crawled;
• which URLs are indexed;
• how long those transitions took;
• which pages have received their first impression.

Those questions require the URL-level observation process described in the methodology.

Next update trigger

The first descriptive update may be published when both conditions are true:

1. At least seven days have passed for the earliest active cohort.
2. URL-level observations exist for enough pages to describe state counts without guessing.

The first median remains gated until at least ten URLs have completed confirmed indexing intervals.

04

Limitations

The baseline precedes the large content rollout and therefore cannot measure its effect.

Other limitations include the following. Search Console performance data can lag. Aggregate metrics cannot establish URL-level indexing. The site's early query mix is unknown in the published baseline. Zero clicks does not mean zero indexing. Average position combines different queries and pages. Batch releases share site conditions and are not independent experiments. Some early URLs may have received manual indexing requests that were not recorded prospectively. A URL can be indexed under a different canonical. A URL can be indexed without producing a reported impression.

This page will be updated through versioned observations rather than rewritten into a success story after the fact.

The responsible conclusion is intentionally plain:

Rank Builder has a registered 31-URL cohort and a documented pre-expansion baseline. It does not yet have enough URL-level evidence to claim an indexing time.

References

Sources behind this record

1. Search Analytics: query — Google (accessed July 26, 2026)
2. Method: index.inspect — Google (accessed July 26, 2026)
3. URL Inspection tool — Google (accessed July 26, 2026)

Corrections

Correction history

No corrections recorded.

To report an error, use the public corrections path.