Blog / Web management /
Year-end client reports: what to include
Traffic chart. Rankings chart. Another traffic chart, different date range. That’s a year-end report that’s turned into a pile of screenshots. The client gets plenty of numbers and still doesn’t know what changed, why it matters or what happens next.
I think of a good report as a decision document. It shows the work, the evidence and the limits of what that evidence can tell you. With several client sites on different platforms, goals and levels of measurement, no single chart explains every site. Keep the structure consistent enough to compare, make the interpretation specific to each client, and never expose one client’s data to another.
Start with the agreed purpose
Before opening analytics, restate what the work was meant to support: organic discovery, ecommerce revenue, leads, reliability, content operations or a mix. Use the goals agreed with the client, not new measures introduced at year-end because they look impressive.
Define the period and the comparison. A year-on-year comparison helps with seasonality, but only if tracking and business conditions are comparable. If measurement changed, the site migrated or a campaign skewed the period, say so. Two unlike periods aren’t a controlled experiment.
Show the work before claiming the outcome
Summarise the work completed: audits, fixes, content updates, migrations, training, maintenance. Be precise about what and when. Keep recommended-but-not-done items separate, so no outcome seems to follow from an action that never happened.
Use a small number of measures tied to the purpose. Search Console can show search impressions and clicks; analytics may show sessions, key events or ecommerce activity, depending on setup. Uptime or issue logs can describe reliability work. Explain the source and any known gaps. A report should not imply perfect measurement when consent settings, tracking changes or platform limits affect the data.
Be careful with causal language. If organic clicks rose after a page update, report both facts and discuss the context, but don’t claim the update caused it unless you can isolate other factors. Demand, seasonality, paid campaigns and stock all move results.
Make the data readable
Choose charts that answer a question. Label axes, dates and units. Don’t put clicks beside sessions, or revenue beside conversion rate, on one scale without explanation. A dashboard screenshot preserves data but rarely gives a reader enough context. When I write a report I’d rather add two plain sentences under each chart.
Under each chart, say what moved, what didn’t and what deserves attention. Call out a tracking issue instead of hiding it. If a metric is unavailable, don’t estimate it without a defensible method. State the limit and suggest better measurement for next time.
Keep raw tables or detailed exports in an appendix if the client needs them. The main report should guide the discussion, not force the reader to find a conclusion in a spreadsheet. Use consistent names for pages, channels and events so the story is understandable from one section to another.
Include the operational picture
For a website, performance and availability can affect the work’s foundation. Summarise relevant incidents, updates or fixes if you have records, but do not inflate routine maintenance into a dramatic achievement. Explain what is still open, who owns it and what dependencies remain. If an issue requires a client decision or developer time, make that visible.
For ecommerce sites, include product and checkout context where available: stock changes, promotion periods, checkout issues or measurement gaps. Keep customer details private. Aggregate information at an appropriate level and avoid publishing personal or commercially sensitive data in a report that may be forwarded.
End with decisions, not a wish list
Each recommendation needs a reason, an owner and a next step. Separate urgent risks from improvements that can wait. Estimate effort only with a reasonable basis; otherwise say scope needs confirming. A long unprioritised list makes it harder for a client to act.
Consider what should continue, stop or be investigated. A recommendation might be to improve a page that already attracts relevant search activity, repair a technical issue affecting important URLs, or establish better event tracking. Tie each suggestion to an observed problem or opportunity. Do not promise that an action will produce a specific ranking or revenue result.
Keep the report honest
Check the dates, filters, source definitions and screenshots before sending. Remove client names or data from any example that is not intended for that client. Confirm that a number has not been copied from a different property or period. If a result is uncertain, say what you know and what would be needed to validate it.
The report is also a record for next year. Store the final version, data sources, assumptions and agreed actions where the team can find them. A clear trail prevents the same question being answered from scratch and helps the next review start with context.
Related reading
- GA4 benchmarking: comparing your site with others
- Monitoring website changes you didn’t make
- Managing several client websites at once: the system I use
If a client reads only one page of your year-end report, what decision should that page help them make?