RecipeSearch Console
Read Search Console performance the right way
The Search Analytics read done properly: freshness dated, top-N nature acknowledged, brand split out.
IntentClicks, impressions, CTR and position, with freshness checked first.
- 2
- Steps
- 2
- Tools
- 1
- Rules
- 1
- Failure modes
When to use it
Use it when
- Any 'how is organic doing' question.
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.
Check data freshness first.
Query search analytics for the window, split brand from non-brand.
Decision rules
The observable condition, what it lets you conclude, and what takes the conclusion back.
When
The window's tail is fresher than Search Console's lag
Conclude
Trim the unfresh days: partial days read as decline.
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.
- Metrics are a top-N sample by design, not site totals: say so wherever totals are implied.
What the answer contains
- 01Readout
- The figures, with windows and accounts named.
- 02Flags
- What deserves a deeper skill or a human decision.