RecipeSearch Console
Find this period's organic winners and losers fast
The losses-and-gains comparison as a weekly habit, the trigger for deeper triage.
IntentWhat moved, ranked by click impact, in one pass.
- 2
- Steps
- 1
- Tools
- 1
- Rules
- 1
- Failure modes
When to use it
Use it when
- Weekly.
- After algorithm update chatter.
Do not use it when
- Windows under 14 days on small sites: noise wins.
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.
Run losses and gains over comparable windows.
Escalate real losers to organic-decay-triage.
Decision rules
The observable condition, what it lets you conclude, and what takes the conclusion back.
When
Losses cluster in one directory or template
Conclude
Structural, not editorial: name the pattern before assigning rewrites.
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.
- Comparing across seasonal boundaries manufactures losses: align the windows.
What the answer contains
- 01Readout
- The figures, with windows and accounts named.
- 02Flags
- What deserves a deeper skill or a human decision.