RecipeSearch Console
Read Search Console performance by page
The page dimension read with position and CTR, ranked by clicks.
IntentWhich pages carry organic, the page-side of the query view.
- 2
- Steps
- 1
- Tools
- 1
- Rules
- 1
- Failure modes
When to use it
Use it when
- Content reviews.
- Template comparisons.
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.
Query search analytics by page.
Group by template or directory and rank.
Decision rules
The observable condition, what it lets you conclude, and what takes the conclusion back.
When
One template's pages underperform the site's CTR at equal positions
Conclude
Template-level snippet problem: one fix, many pages.
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.
- Pages with many queries average their positions into mush: read top queries per page for truth.
What the answer contains
- 01Readout
- The figures, with windows and accounts named.
- 02Flags
- What deserves a deeper skill or a human decision.