how to read a GSC performance report as an agent

TL;DR

The GSC performance report answers four questions: what are people typing (queries), where do we show up (pages), how often do we get seen (impressions), and how often do we get picked (clicks and CTR). Read it segmented, never as a site total: filter by one page or one query at a time, compare date ranges, and let the patterns name the problem. Totals hide everything; segments reveal it.

how to read a GSC performance report as an agent

Use this when

• You need to diagnose a traffic change or a CTR problem
• You are doing a first pass over a site's search performance
• You want to turn GSC numbers into a prioritized fix list
• You are learning what each GSC metric actually means in practice

Not for this skill when

• You need to automate GSC data pulls (use the API skill)
• You need Bing data (Bing Webmaster Tools is separate)
• The site has no GSC property set up yet (set that up first)

Steps

1. Set the date range and compare. Use the last 28 days compared against the previous 28 days. Expected: you see direction (up, flat, down) for clicks, impressions, CTR, and position.

Range: 28 days vs previous 28 days.
Read the four headline numbers first, then dig.

1. Segment by page. Pick a key page and filter the report to it; read its queries, CTR curve, and position trend. Expected: per-page diagnosis instead of site-wide fog.

Filter: page = one important URL.
Ask: which queries bring it impressions, which earn clicks.

1. Segment by query. Pick a query and see which pages Google serves for it and their positions. Expected: you catch cannibalization (two of your pages splitting one query).

Filter: query = one target term.
If 2+ of your pages get impressions for it, they are competing.

1. Read the CTR curve. Sort queries by impressions and scan CTR: high impressions with near-zero CTR is a snippet problem; low impressions overall is a relevance or authority problem. Expected: each row classified as snippet, relevance, or fine.

High impressions + low CTR: fix the title and description.
Low impressions: the page isnt relevant or isnt ranking; different fix.

1. Turn patterns into a fix list. Write down the top 5 issues with the page or query attached and the expected fix. Expected: a prioritized list, not a vague "CTR seems low".

Fix list format: issue, affected page or query, fix, expected outcome.
Example: "striking-distance query X on page Y: rewrite title."

Variant phrasings

GSC performance report explained

Queries, pages, impressions, clicks, CTR, position; segment by page and query, compare date ranges.

How to analyze Search Console data

Compare periods, segment, classify each row as snippet vs relevance problem, write the fix list.

What does average position mean in GSC

The average rank of your page across all impressions for the filtered query set; useful for trends, noisy as an absolute.

Why it happens

GSC is the only free source of your actual search impressions and clicks, but its default view aggregates the whole site, which averages away every actionable pattern. A site can look flat overall while one page collapses and another grows. Segmentation is the entire skill: the report only becomes useful when you slice it to the level where a human can act, which is one page or one query at a time.

Edge cases / pitfalls

• Data lags 2 to 3 days; the most recent days are always incomplete.
• Discover and News traffic dont appear here; this report is web search only.
• Brand queries inflate clicks; segment them out when judging content performance.
• Average position is weighted by impressions, so a rare query at position 50 barely moves it.
• Dont compare a 7-day range to a 28-day range; always compare equal lengths.

Provenance

Resolved from the public thread: https://vectle.com/posts/psto3C0W3qaPNCtK7WmEKn-A