SEO reporting for clients, straight from Search Console

Updated 2026-08-07

A monthly client report built from Search Console alone: which numbers to lead with, which comparison to use, and the four caveats that stop awkward questions.

Most client SEO reports are longer than they need to be and quietly misleading in the same three places every month. Search Console on its own has everything required for an honest one.

Lead with clicks

Clicks are the number a client can connect to their business. Impressions are context, CTR is diagnostic, and average position is the one that will get you into an argument you cannot win.

If you report position at all, report it filtered to a fixed set of named queries. Sitewide average position moves whenever the query mix moves, so it can worsen in a month where everything genuinely improved. Explaining that after the fact never lands well. Why that happens.

Use year-over-year as the primary comparison

Month-over-month straddles seasonality, holidays and varying weekday counts. Same-month-last-year handles all three. Keep month-over-month as a secondary line if the client expects it, but do not let it lead.

Whichever you use, end both periods at least three days back. Search Console's last two days are incomplete, and a comparison against a partial period invents a decline that is not there.

The four sections that are enough

• Headline. Clicks and impressions, this period against the same period last year, with the direction stated in one sentence.
• Movers. Top ten pages and top ten queries by change, not by volume. Volume tables look identical every month; change tables are where the story is.
• Opportunity. Queries in positions 11–20 with real impressions, and the page you plan to work on. This is the section that justifies next month's invoice — see striking distance keywords.
• Done and next. What shipped, what it was meant to affect, what is queued.

Cut everything else. Nobody has ever asked a follow-up question about a Core Web Vitals screenshot.

Four caveats worth putting in writing once

Say these in the first report and reference them afterwards. Each one prevents a recurring conversation:

• The two-day lag. Search Console is never current to today.
• Query rows never sum to the total. Rare queries are withheld for privacy — often 40% or more of traffic on a small or specialised site. The detail.
• Search Console clicks will not match Analytics sessions. A 10–20% gap is normal and expected. Why.
• 16 months is the whole history. If they want a three-year chart, start exporting now.

On automated dashboards. A Looker Studio build connected to Search Console is free and updates itself, and it is the right answer when a client wants to look whenever they like. It does not replace the written interpretation — an unexplained dashboard generates more questions than it answers.

Working across several accounts

Agency properties are usually spread over multiple Google logins, which in the web interface means signing in and out. Anything reading the API can hold several connections at once and show the properties together, which removes the most tedious part of a reporting week.