# Read Search Console performance by device

> Tier: recipe. Operating recipe: real tool sequence, core rules, known traps.

Device cuts on search analytics, mobile-first reality checked.

**Intent.** Organic device split: positions and CTR per device class.

## When to use

- Mobile experience investments.
- CTR anomalies.

## When not to use

- No specific contraindication beyond the preconditions below.

## Sources

Required: Search Console

## Preconditions

- The account is ticked in the dashboard, confirmed via list_accounts.

## Inputs

- `window`: Analysis window. Default: last 30 days.

## Procedure

1. Query by device. — tools: `gsc_query_search_analytics`
2. Compare positions per device on the money queries.

## Decision rules

- **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 requirements

- Every figure carries its account, metric and window.
- Anything below a readable sample size is reported as unjudged, not as zero.

## Human approval boundary

- The readout changes nothing. Any change it motivates goes through Safe Writes: preview, human confirmation, then apply.

## Failure modes

- Device mix shifts move blended CTR with nothing changing per device: read the split, not the blend.

## Output

- **Readout**: The figures, with windows and accounts named.
- **Flags**: What deserves a deeper skill or a human decision.
