RecipeSearch Console
Sample a large site's index status sensibly
The sampling plan for large sites: sections, strata, quota budget, then bulk inspection on the sample.
IntentReliable index conclusions on a million-page site without a million inspections.
- 2
- Steps
- 2
- Tools
- 1
- Rules
- 1
- Failure modes
When to use it
Use it when
- Sites too large for exhaustive inspection.
- Before big migration verdicts.
Do not use it when
- Small sites: inspect directly, sampling adds error for nothing.
What it needs first
Required
Preconditions
- The account is ticked in the dashboard, confirmed via list_accounts.
Inputs
window- Analysis window.Default: last 30 days.
Procedure
In order. Every tool named is one the gateway ships, and links to its reference.
Plan the sample across sections and templates.
Run the bulk inspection on the sample.
Decision rules
The observable condition, what it lets you conclude, and what takes the conclusion back.
When
A stratum's sample shows systemic failure
Conclude
Extrapolate to the stratum only, with the interval: not to the site.
Evidence every conclusion must carry
- Every figure carries its account, metric and window.
- Anything below a readable sample size is reported as unjudged, not as zero.
Where the agent stops
- The readout changes nothing. Any change it motivates goes through Safe Writes: preview, human confirmation, then apply.
How it goes wrong quietly
The cases where the analysis is wrong and still looks right. Read them before trusting a number.
- Convenience samples (recent pages, top pages) are biased by construction: strata exist to prevent exactly that.
What the answer contains
- 01Readout
- The figures, with windows and accounts named.
- 02Flags
- What deserves a deeper skill or a human decision.