RecipeSearch Console
Read Search Console performance by device
Device cuts on search analytics, mobile-first reality checked.
IntentOrganic device split: positions and CTR per device class.
- 2
- Steps
- 1
- Tools
- 1
- Rules
- 1
- Failure modes
When to use it
Use it when
- Mobile experience investments.
- CTR anomalies.
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 by device.
Compare positions per device on the money queries.
Decision rules
The observable condition, what it lets you conclude, and what takes the conclusion back.
When
Mobile positions trail desktop on the same queries
Conclude
Mobile experience or speed signal: route to the site team with the query list.
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.
- Device mix shifts move blended CTR with nothing changing per device: read the split, not the blend.
What the answer contains
- 01Readout
- The figures, with windows and accounts named.
- 02Flags
- What deserves a deeper skill or a human decision.