What should a useful monthly SEO report show?
A report should explain change, locate it on the site and end with a decision. A page of unexplained totals is not enough.

Does your monthly SEO report show charts and percentages, but leave you unsure what changed or what to approve next?
A useful monthly SEO report compares equal dates, defines every number and names the pages and searches behind each change. It keeps Search Console results apart from GA4 visits and enquiries, records the work done, and ends with decisions that have an owner and a check date.
Methodology, checked 7 November 2026: the review covered Google's Search Console Help pages on the Performance report, its filtering and comparison features, impressions, average position and clicks, and the Core Web Vitals report. It also covered Google's guidance on using Search Console with Google Analytics, on debugging drops in Search traffic, and on GA4 key events, plus the current draft of this guide. Not available: ClaroSi client Search Console or GA4 exports, sample client reports, and any figures for a specific site. This guide does not claim rankings, traffic, enquiries or AI citations, and it gives no target percentages.
Which numbers belong in a monthly SEO report?
Every number should answer one question and name its source. Search Console shows how the site appeared in Google and which results were clicked. GA4 shows what happened on the site. The Core Web Vitals report shows real-visitor speed. Your change log explains the work. Check each number against the matrix before it reaches a decision.
| Report item | Source tool | What it can tell you | What it cannot tell you | Action trigger |
|---|---|---|---|---|
| Clicks | Search Console, Performance report | How many times people clicked a Google result to reach the site in the chosen view | Enquiries, sales or visit quality. Clicks that stay inside Google do not count. | Clicks fall while impressions hold: review the titles and snippets of the affected pages. |
| Impressions | Search Console, Performance report | How often a link to the site appeared in results | Visits. Some result types count only when the item has been scrolled into view. | Impressions rise but clicks stay flat: find the pages and queries that gained exposure. |
| Average position | Search Console, Performance report | The average topmost position for the site, page or query in the view | A fixed ranking that every searcher sees. Results vary by searcher, place, device and recent history. | Position moves: read it next to impressions. Do not act on position alone. |
| CTR | Search Console, calculated from clicks and impressions | Clicks divided by impressions for the same view | Whether the result matched the need, or whether the visitor enquired | CTR falls on a page with steady impressions: check that page's title and snippet. |
| Indexed pages | Search Console, Page indexing report | Which URLs Google has indexed, and the reasons others are not | Ranking, traffic, or which version of a duplicate Google chose | Not-found or excluded pages rise: find the cause before more changes go live. |
| Conversions and enquiries | GA4, key events | Counts of actions you have marked as key events, by landing page or channel | Revenue or lead quality. Google does not say that key events equal revenue. Does not prove Google caused it unless the sources agree. | Key events fall while sessions hold: confirm the event still fires and that tracking settings have not changed. |
| Core Web Vitals | Search Console, Core Web Vitals report | Real-user LCP, INP and CLS results, grouped as Good, Need improvement or Poor | Every page. Pages with too little data can be missing. | A group is marked Poor: fix that group first, starting with its worst metric. |
| Work done | Your change log (not a Google tool) | What changed on the site or in the business, and when | The cause of a search movement on its own | Any change in the period: record it beside the chart before reading the result. |
Search Console and GA4 measure different things, so their numbers will not match exactly. Google advises comparing whether the trends move together, not forcing the totals to agree. [4]
What must every monthly report contain?
Every monthly report should state its dates, name each source, define each number, list the work done, ask for the decisions needed and set out next month's plan. If one of these is missing, the reader has to guess. The grouped checklist below covers those five parts.
Dates and comparison
- Exact start and end dates for the period.
- The comparison used: the previous equal period or the same period last year.
- Weekly or monthly grouping for longer views.
- Whether the newest days are still preliminary.
Sources and definitions
- Search Console, GA4 and the Core Web Vitals report named as sources.
- One plain definition beside each number.
- Any filter used, such as page, query, country, device or search type.
- A note of any anonymised or truncated query data.
Work done
- Pages changed, published or redirected, with dates.
- Fixes shipped, and any tag or form changes.
- Business or website changes that could explain movement.
Decisions needed
- Each decision named with the page it affects.
- The evidence behind it, with the report row or date.
- The action proposed and who approves it.
Next month's plan
- An owner and check date for each open item.
- The pages to review again.
- What the next report must show to close each item.
The Performance report shows the past three months by default and may mark the newest data as preliminary. [1] Google recommends weekly or monthly grouping for longer comparisons, and notes that filtering by query or URL can change totals. [2] Write each filter down so the reader can see it.
How do you run the monthly review?
Run the review in the same order each month: pull the data, compare equal periods, explain each change, decide with an owner and record the result. A fixed order makes one month easy to compare with the next. The diagram shows the same loop at a glance.
The monthly SEO report loop
Same order every month
- 1Pull data
- 2Compare equal periods
- 3Explain the change
- 4Decide with an owner
- 5Record and check again
Next month starts again at 1, with fresh data from the same sources.
- Pull the data: take the agreed date ranges from Search Console and GA4 on the same day. Note any preliminary days.
- Compare: set equal periods, and use weekly or monthly grouping for longer views. [2]
- Explain: check the change log, then break the change down by page, query, device, country and search appearance. [1]
- Decide: approve only actions that name a page and the evidence behind it.
- Record: write the owner, the action and the check date. File the report beside the previous month.
What do the numbers prove, and what do they not prove?
A number proves only what it measures, in the view chosen. An average position rise, more impressions or a ranking screenshot does not prove more enquiries. Write the limit beside each claim, so a better month is not read as proof of more business.
| Claim in the report | What it proves | What it does not prove |
|---|---|---|
| Average position is up | The average topmost position for that view moved. [3] | More clicks or enquiries, or a fixed ranking for every searcher. |
| Impressions are up | Links to the site appeared more often in that view. [3] | Visits or enquiries. |
| Ranking screenshot | One search, from one place and device, at one moment. | An average position or a stable ranking. Results vary by searcher. [1] |
| Traffic is up in GA4 | Sessions GA4 recorded for that filter and period. | That Google caused the change, unless the source data agrees. [4] |
| Keyword count is up | More queries appeared in that view. | Traffic or value. Anonymised queries are not shown. [2] |
| Clicks are up | More clicks from Google results in that view. [1] | An enquiry or sale. Those need key events and an agreed record. |
| Core Web Vitals group is Good | The group met the thresholds in real-user data for the period. [6] | That every page is fast, or that search results will change. |
Want a report that ends with actions? See the monthly follow-up.
How do you triage a report that looks wrong?
Start with the symptom and test the narrowest explanation first. Check the data before the strategy. The tree below gives a first investigation path for four common problems. Work through the questions in order and record each result. It does not replace Search Console, GA4 or server evidence.
- Clicks dropped?
Check the Data Anomalies page and compare with the same period last year, using a 16-month view to look for a yearly pattern. If impressions also fell, check the Page indexing report, Crawl stats and any recent site move. If impressions held but clicks fell, review titles, snippets and rich result competition. Sort pages by clicks difference, then filter one query at a time. [5] - Impressions up but clicks flat?
Use the Pages and Queries tabs to find what gained impressions. Check average position for those rows. Check whether the extra impressions came from result types that count only when scrolled into view, such as carousels or image search. [3] Then decide whether the new exposure fits the page's purpose. - Enquiries down but traffic up?
Run the enquiry path with approved test steps. Confirm the key event still fires and appears on the landing pages it should. [7] Check whether the traffic came from Google at all, using the source data. Check tag and consent changes, since missing tags and opt-outs can widen the gap between the two tools. [4] - Data missing?
Check the date range, since the newest days may be preliminary. [1] Check whether a filter has hidden rows, because truncation and anonymised queries change totals. [2] Confirm GA4 tags fire on the affected pages. For Core Web Vitals, "No data available" means too little data for that device type, and a new property can take a few days to show data. [6]
What can you use for next month's report?
Use three short records: one for the report header, one for each headline number and one for decisions. Start with the pages that matter most to the business. Fill them with your own pages and figures, and keep the previous month beside the new one. An owner and a check date turn each finding into work that gets done.
Three records. One report you can check.
Use these cards in a spreadsheet, a project ticket or the monthly review meeting. Fill them with your own pages, numbers and dates.
Set the report header
Fill this in before reading any number.
- Period
- Exact start and end dates
- Comparison
- Previous equal period, or the same period last year
- Sources
- Search Console, GA4, Core Web Vitals report
- Filters used
- Page, query, country, device or search type
- Preliminary data
- Yes or no, and which days
Period: [start] to [end]
Comparison: [previous start] to [previous end]
Preliminary: [last days]
Define each headline number
One row for each number in the report.
- Number
- Clicks, impressions, average position, CTR, key events or indexed pages
- This period
- The value for the period being reported
- Comparison period
- The value for the comparison period
- Difference
- This period minus the comparison period
- What it means
- The plain definition from the matrix
Clicks: [this period], [comparison], [difference]
Means: clicks from Google results only
Turn findings into decisions
Every decision needs a page, evidence, an owner and a date.
- Finding
- What changed and where
- Page
- The address affected
- Evidence
- Report row, date range or chart
- Action
- The decision agreed
- Owner and check date
- Who checks it, and when
Finding: clicks fell on [page] while impressions held
Evidence: Performance report, Pages tab, [dates]
Action: review title and snippet
Owner: [name] · Check: [date]
The examples use placeholders in square brackets. Replace them with your own pages, numbers, dates and owners.
What do readers ask about a monthly SEO report?
The answers below cover four questions a reader may ask when they open a monthly report. Each answer uses only the Google sources cited in this guide. Where Google sets no rule, the answer says so instead of inventing one. Each answer points back to a source already listed in the primary sources.
Why do Search Console and Analytics numbers differ?
They measure different things and count in different ways. Search Console counts clicks from Google results, while Analytics counts sessions using its own time zone, attribution model and bot filtering. Google says to look for similar trends, not equal totals. A large gap is a reason to check tags, consent settings and canonical URLs first.
Is average position a good headline number?
Not on its own. Average position is the average of the topmost spot your link held in each query where it was seen, so it is not a fixed rank. Google also advises against focusing too heavily on exact rank. Read it next to impressions and clicks for the same view before you decide anything.
How often should you compare periods?
Google does not set a required frequency. Its guidance covers the method: compare against the previous period or the same period last year, then click through the tabs to see which pages, queries or devices moved. Use a 16-month view to check for a yearly pattern. Weekly or monthly grouping suits longer comparisons.
Should a monthly report list the work you did?
Yes. Google notes that the effects of site changes can take days to months to show. URL changes can also cause fluctuation while Google recrawls the site. A dated change log lets the reader see what moved after each change, instead of guessing. Record the date, the page affected and what changed.
Primary sources
- Performance report overview, Google Search Console Help. Checked 7 November 2026.
- Performance report: advanced filtering and comparison, Google Search Console Help. Checked 7 November 2026.
- Impressions, position and clicks, Google Search Console Help. Checked 7 November 2026.
- Using Search Console and Google Analytics data for SEO, Google Search Central. Checked 7 November 2026.
- Debugging drops in Search traffic, Google Search Central. Checked 7 November 2026.
- Core Web Vitals report, Google Search Console Help. Checked 7 November 2026.
- About conversions (key events), Google Analytics Help. Checked 7 November 2026.