SEO Reporting for a Report Nobody Logs In to Read
A one-off SEO report has no meeting attached to explain it. Six rules for a document a stranger reads once, alone, and has to act on with no analyst.
Writing an SEO report people read once, alone
Table of Contents9 sections
You paid a fixed price, a report arrived, and now you're reading it alone on a Tuesday, with no dashboard login and no analyst on a call.
The short version: a one-off SEO report has to carry six things a monthly deck can leave out: the date, market, device and tools behind the data; findings ordered by what to fix first; the reasoning behind each recommendation; what wasn't checked; an owner and effort per finding; and the data's own limits.
Almost every guide to SEO reporting assumes an agency, a retainer and a monthly meeting. It assumes you're a marketer explaining last month to your boss, and its advice is about which widgets to put on the dashboard so that the explanation goes smoothly and nobody in the room asks the awkward question.
The far more common document is a one-off, with no next month in which anyone will clear anything up. If that document doesn't work on its own, it doesn't work, and the rules below are for SEO reporting that has to survive without anyone in the room to explain it.
Key Takeaways
- Search Console performance tables stop at 1,000 rows and leave out rare queries, so a keyword table is a sample, and its rows will never add up to the chart total.
- Search Console keeps 16 months. GA4 standard properties keep 2 or 14 and delete the rest automatically, so a baseline you export at the start is the only way your comparison survives.
- Collected data normally shows up within two to three days, so the last days of every reporting period are incomplete.
- Average position is an impression-weighted average, and it isn't a rank. An average of 8.4 can mean third place for a handful of queries and thirtieth for hundreds.
- Google says no one can guarantee a number one ranking. A report that forecasts specific positions is a warning sign.
Who SEO Reporting Advice Is Written For
Look at the top results for SEO reporting and you can work out who they're written for. The reader they picture wants four things:
- white-label templates to put an agency's name on
- automated scheduling that sends the deck out every month
- connectors that pull several platforms into one deck
- a way to show month-over-month movement
Every one of those needs is real. Every one belongs to a retained relationship, and you probably don't have one.
None of it helps you if you're holding a standalone report.
But your problems are different. You can't ask a follow-up question without paying for it.
You won't see next month's chart. And which of the twenty findings do you start with? Nobody's around to say.
Your agency's monthly deck can be thin, because the conversation around it carries the meaning. A one-off report has no conversation, so the document has to carry everything, its own limits included.
That matters to your wallet too. Google's own guidance on hiring an SEO tells you to ask whether a provider will share every change they make and explain their recommendations and the reasoning behind them.
A monthly dashboard rarely answers that. A written report is the format where your provider's reasoning fits, and where you can check it. It's why our marketing audit ends in a written report with ranked findings you can act on alone. If you're still deciding what to buy, here's how a marketing audit differs from an SEO audit.
What the Data Underneath Will Not Tell You
So start with what the source data doesn't contain. Most reports present it as complete. It isn't, and Google says so in writing in its documentation on Search Console data.
Four things follow from that. If your report leaves them out, it's overselling its own numbers.
A keyword table is a sample. Search Console shows at most 1,000 rows and leaves out rare queries to protect user privacy, which Google calls anonymized queries.
So the rows won't add up to the chart total. The tail isn't empty. It's missing.
The last few days always read low. Google says collected data is normally available within two to three days. A report you pull on the first of the month, in your own account or mine, describes a month that hasn't finished arriving.
History expires. Search Console keeps the last 16 months. Google Analytics 4 standard properties keep event-level data for two or fourteen months and delete it automatically every month:
| Data | How long Google keeps it | After that |
|---|---|---|
| Search Console performance data | 16 months | Gone |
| GA4 standard property, event-level data | 2 or 14 months, chosen in settings | Deleted automatically every month |
| The last two to three days of any period | Not complete yet | Fills in later |
If nobody changed that setting when your property was created, the comparison you'll want a year from now won't exist, and you can't get it back.
Two tools will disagree. Sampling, attribution and retention all differ between them. I'd rather give you a report that explains the gap in one sentence than one that picks the flattering number and says nothing.
Average Position Is Not a Position
The most-reported metric in SEO reporting is also the most misread. Average position in Search Console is an impression-weighted average of where your result showed up, and Google's performance report documentation notes that results depend on the time, place, device and recent history of the person searching.
So an average position of 8.4 doesn't mean you're eighth. It can describe a page that ranks third for a few queries and thirtieth for hundreds of others, and it moves whenever the mix of queries changes, even when no ranking has moved at all.
Report it as a rank, month after month, and you get a line that rises and falls for reasons nobody in the meeting can name.
Then someone attaches a target to it. Google's hiring guidance says it plainly:
No one can guarantee a #1 ranking on Google.
It also warns you about providers who claim otherwise. A report built on a metric that isn't a position, chasing a promise nobody is allowed to make, is two mistakes stacked on top of each other.
So report position as a distribution instead. Or report the specific queries your business cares about, one by one, with the date and device stated.
Both take more work. Neither comes out of an export button.
What a Standalone Report Has to Carry
| A retained monthly deck | A standalone one-off report |
|---|---|
| Last month's traffic and ranking movement | The date, tools and market the data came from |
| Work completed in the period | Findings ordered by what to fix first, not by category |
| Next month's planned tasks | What was not checked, and why |
| Dashboard links the client can open | The reasoning behind every recommendation |
| Commentary finished verbally on the call | Effort and who has to do it, plus the limits of the data |
Six rules cover most of it.
1. Date and Scope Everything, on the Page
Which country, which device, which date range, which tool? Results differ across all four, and country matters more than most reports admit: selling into one country from another changes which results you can reach at all. Without that context, nobody can reproduce your screenshot, including whoever reads it next year.
2. Order the Findings by What to Do First
Grouping by category is every tool's default output, and it's useless to someone with limited hours. Somebody has to decide what matters most for you. That judgement is a big part of what you paid for.
3. Publish the Reasoning, Not Only the Recommendation
This is what Google's hiring guidance tells you to ask your provider for. It's also the part you'll still use after the specifics go stale.
4. Say What You Did Not Check
A report with no stated boundary implies everything got checked. That's never true.
Naming the gaps is the cheapest credibility you'll find. I always do.
5. Give Every Finding an Owner and an Effort Estimate
A list a small business can't act on is decoration. If a fix needs a developer, say so before they find out.
6. State the Limits of the Data Inside the Report
The row cap. The retention window. The two to three day lag.
If your reader later finds your numbers don't tie out, and you never explained why, they'll trust the whole document less.
The Numbers Worth Reporting
Your honest short list is smaller than most decks. Clicks and impressions for the queries that map to money, and the pages that earn them, grouped by topic if your site is built around content pillars.
Conversions that are actually tracked, described honestly where tracking is partial. Technical defects that block your pages from being indexed, which pass or fail and don't trend. And a plain statement of what changed since the work started, with the start date on it.
Still, most of what you'll see is filler. A domain authority score your tool vendor invented. A bounce rate with no target.
A keyword count. A chart of a metric moving on its own. Post 03 in this series looked at what SEO actually costs, and you'll find the same pattern there: the impressive number is rarely the one you can act on.
You can see the format as example rows on our audit page, ranked the way this section describes.
What to Do in the First Week After a Report Lands
- Check the report states its date, market, device and tools, and ask for them if it doesn't.
- Find the section listing what wasn't checked, because a report without one claims more coverage than it has.
- Pick the top three findings only and put them in the diary, since a twenty-item list attempted at once finishes nothing.
- Separate what you can do yourself from what needs a developer, and get quotes for the second group before agreeing to any retainer.
- Save a copy of your current Search Console and Analytics figures now, because the 16-month and 2-or-14-month windows mean today's baseline won't be retrievable later.
Step five is the one I'd underline. Whatever your report says today, the data under it expires on a rolling schedule nobody at your business controls.
One export of where you stand now costs half an hour. It's the only way to answer the obvious question a year later. Did any of it work?
Common Questions
What should an SEO report include if there is no monthly retainer behind it?
Everything, because there's no meeting to explain it: the date, market, device and tools behind the data, findings ordered by what to fix first, the reasoning behind each recommendation, what wasn't checked, an owner and effort for every action, and the data's own limits. A monthly deck can be thin because a conversation completes it.
Why do the rows in a Search Console keyword table not add up to the total?
Because the table isn't the whole data set, and Google says so. Tables show at most 1,000 rows, and rare queries are left out to protect user privacy, though they still count toward the chart total. Any SEO reporting that presents a keyword table as everything a site ranks for is misreading the source.
Does average position in Search Console tell me what rank I hold?
No. It's an impression-weighted average across every query that produced an impression, so 8.4 can mean third for a few queries and much lower for many others, and it moves when the query mix changes. Report the queries that matter, with date and device, or report the distribution.
How far back does the data behind an SEO report actually go?
Search Console keeps performance data for the last 16 months, the ceiling on any comparison you try to make after the fact. GA4 standard properties keep event-level data for 2 or 14 months, and Google deletes the rest automatically every month. So export a baseline when your project starts.
How often should SEO reporting happen for a small business?
Less often than most retainers bill for, because search work rarely shows real month-over-month movement early on, and a monthly report on a small site mostly documents noise. I'd do a detailed report at the start, a light check at 90 days, and a proper one at six months. It costs you less, and it's easier to act on.
Can an SEO report guarantee the rankings it forecasts?
No, and you should treat a report that forecasts positions as a warning sign. Google says no one can guarantee a number one ranking, and tells you to be wary of providers who claim otherwise or claim a special relationship with Google. Honest SEO reporting commits to the work and to measuring what happened, never to a position.
Want to see the format before you read more about it? The audit page shows example rows, and the audit itself is a flat-price marketing audit with no retainer attached.
Sources
- Google: About Search Console data, on the 1,000-row table cap, anonymized queries, and the two to three day data lag
- Google Analytics Help: data retention, on the 2 and 14 month event-level retention options for standard properties and automatic monthly deletion
- Google Analytics Help: connect Search Console to Google Analytics, stating that Search Console keeps data for the last 16 months
- Google Search Central: do I need an SEO?, on ranking guarantees and asking a provider for the reasoning behind recommendations
- Google: Performance report, Search results, on average position and on results varying by time, place, device and search history
