RecipeSearch Console
Read how SERP features change your clicks
Search appearance trends read for the CTR-without-rank-change cases.
IntentWhether rich results and features move CTR independent of rank.
- 2
- Steps
- 1
- Tools
- 1
- Rules
- 1
- Failure modes
When to use it
Use it when
- CTR moved while positions held.
- After schema work ships.
Do not use it when
- No specific contraindication beyond the preconditions below.
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.
Analyse appearance trends over the window.
Tie feature gains and losses to the affected page sets.
Decision rules
The observable condition, what it lets you conclude, and what takes the conclusion back.
When
A feature loss coincides with the CTR drop at stable position
Conclude
The SERP changed around the page: feature work, not content work.
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.
- Feature reporting granularity is coarse: date alignments are approximate.
What the answer contains
- 01Readout
- The figures, with windows and accounts named.
- 02Flags
- What deserves a deeper skill or a human decision.