SEO Reporting: What Belongs in a Monthly Report and What Doesn’t
- Filed November 10, 2026
- Analytics, reporting and testing, guide 7 of 8
A monthly SEO report should answer three questions for the people who pay for the work: did organic search contribute to the business this month, what changed and why, and what happens next. Everything in the report should serve one of those questions. Screenshots of every chart in Search Console, lists of keywords that moved one position, and tool scores without context do not. A report also needs fixed definitions, so that the same number means the same thing every month.
The outline
- Summary (half a page)
- Business outcomes from organic search
- Search visibility and traffic
- AI search visibility (reported separately)
- Changes and their likely causes
- Technical health
- Work completed
- Next month’s priorities
- Definitions and data notes
1. Summary
Three to five sentences: the headline outcome, the main change, the main risk, and the top priority. Example: “Organic leads rose to 142, up 11 percent from last month and 18 percent from a year ago. The gain came from the new pricing guides. Product category impressions fell after a template change that removed internal links; a fix is in progress. Priority for next month: restore category links and publish the remaining comparison pages.”
The figures in that example are illustrative.
2. Business outcomes
| KPI | Definition | Source |
|---|---|---|
| Organic key events | Count of the key events that represent business outcomes (leads, purchases, sign-ups) in sessions from organic search | GA4, session default channel group = Organic Search |
| Organic revenue or pipeline | Revenue or CRM pipeline attributed to organic sessions, with the attribution model named | GA4 or CRM |
| Organic key event rate | Organic key events divided by organic sessions; if a GA4 built-in rate metric is used instead, name it and use its own definition | GA4 |
State the attribution model and lookback window used, and keep them constant month to month.
3. Search visibility and traffic
| KPI | Definition | Source |
|---|---|---|
| Clicks | Clicks on Google Search results to the site | Search Console Performance, web search type |
| Impressions | Times the site appeared in Google Search results | Search Console Performance |
| CTR | Clicks divided by impressions | Search Console |
| Average position | Google's definition: the average position of the topmost result from the site | Search Console |
| Non-brand clicks | Clicks excluding brand queries | Search Console's branded queries filter where available (top-level properties with enough data), otherwise a documented regex query filter |
| Organic sessions | Sessions from Organic Search | GA4 |
Read each with the Performance report’s own definitions, and show each as this month, previous month and the same month last year. Segment by site section or page type, not by hundreds of individual keywords. When brand and non-brand figures are built from query-table rows, remember that query tables omit anonymized queries, so the two sums will not equal the total.
4. AI search visibility, reported separately
AI search measures do not belong inside the organic traffic numbers, and they do not belong in one combined “AI” figure, because each source measures something different.
| Measure | Definition | Source | Not the same as |
|---|---|---|---|
| Google AI feature impressions | Times links to the site were shown in AI Overviews and AI Mode | Search Console Generative AI performance report | Clicks; this report documents impressions |
| Microsoft AI citations | Times the site was cited in Copilot and Bing AI summaries | Bing Webmaster Tools AI Performance | Google data |
| AI assistant referral sessions | Sessions GA4 attributes to AI assistants such as ChatGPT or Gemini | GA4 AI Assistant channel | Google AI Overviews clicks, which GA4 reports under Organic Search |
Label each row with its source. Do not add them together. Google documents the AI Assistant channel, and the placement of its own AI features under Organic Search, in the GA4 default channel group help.
5. Changes and their likely causes
For each significant change, a short entry:
- What changed: “Category page impressions down 22 percent.”
- When: the start date.
- Evidence: reports and data used.
- Likely cause: with the confidence level stated (“likely”, “possible”, “unknown”).
- Alternatives considered: seasonality, Google updates on the Search Status Dashboard, tracking changes, site releases.
- Action: what is being done, or “monitoring”.
This section is where a report earns trust. “Unknown, investigating” is a valid entry; a confident cause without evidence is not.
6. Technical health
Report exceptions, not inventories:
- new or growing reasons in the Page indexing report for important pages;
- Core Web Vitals status changes by URL group;
- manual actions or security issues (if none, say “none”);
- crawl errors from Crawl Stats if material.
7. Work completed
A short list of what was shipped, linked to the outcomes or changes it is meant to affect. Avoid activity counts without purpose (“47 meta tags updated”).
8. Next month’s priorities
Three to five items, each with an owner and the measure that will show whether it worked.
9. Definitions and data notes
Keep a stable section that defines each KPI, the brand filter, the attribution model, time zones (Search Console uses Pacific Time) and any data issues this month (tracking outages, consent changes, Search Console data anomalies).
What doesn’t belong
- Raw keyword ranking lists with daily movements; summarize visibility by group instead.
- Third-party “authority” or “health” scores presented as Google metrics.
- Impressions without clicks or outcomes as the headline.
- Vanity totals that mix AI impressions, organic clicks and referrals into one “visibility” number.
- Unexplained screenshots.
- Promises of rankings or traffic in the next month.
Where reporting ends and program management begins
The monthly report measures and explains. Planning the content program (editorial calendar, team workflow, brief production, quality assurance) is a separate management system with its own KPIs. The report can reference that program’s output, but it should not try to manage it.
A good monthly report is short, consistent and honest about uncertainty. The same definitions every month, outcomes first, changes explained with evidence, and AI measures kept in their own rows: that structure is what lets a reader trust the numbers.