Client SEO report: what to include, what to cut, and how to prove the work

A client SEO report is a regular update that shows a client what changed on their site, what you fixed, what is still open, and how search performance moved. The best ones are short, honest, and backed by proof for every claim.

This guide gives you a section by section client SEO report template, a worked example, and the mistakes that make clients stop reading.

In this guide

• What a client SEO report is for
• The sections to include
• How to show proof of fixes
• A worked example
• Common reporting mistakes

What is a client SEO report for?

A client SEO report exists to answer three questions the client is quietly asking: is my site healthy, what did you do, and is it working? Everything in the report should serve one of those three questions. Anything that doesn't is padding.

A report is also your record. When a client asks in six months why a section of pages dropped, a history of incidents, fixes and dates lets you answer with facts.

What to include in a client SEO report

Include a summary, search performance, work completed with proof, issues fixed and still open, site health, and next steps. Put the summary first and keep it to a few lines.

Summary

Write it last. One sentence each for the most important result, the most important fix and the most important open risk. If a client reads only this, they should still know where things stand.

Search performance

Use Search Console as the main source, because it reports what Google actually showed and what people clicked. Compare like with like: this month against last month and against the same month last year for seasonal sites. Show the pages that matter to the business, not the whole site average.

Work completed, with proof

List each finished task with a line of proof. "Fixed canonical on 340 category pages, verified 12 Oct" says more than "technical SEO improvements". Proof can be a before and after of the tag, a status code that changed from 404 to 200, or a re-check result.

Issues: new, fixed, reopened, recurring

These four counts tell the real story of site health. New issues show risk coming in. Fixed issues show progress. Reopened issues show fixes that didn't hold. Recurring issues point at a process problem, such as a deploy step that keeps breaking the same thing.

Site health

Report uptime as a percentage for the period, plus each confirmed outage with its start, end and cause. Clients understand outages better than they understand canonicals.

Still open, and why

Be specific about who each item waits on. "Waiting on the client's developer since 3 Oct" is uncomfortable but useful. It protects you and gets things moving.

How to show proof in a client SEO report

Show proof by linking each claim to the exact check that confirms it: the URL, what was wrong, what it is now, and when it was checked. A claim without proof is an opinion.

There are two kinds of "done", and a good report keeps them apart:

• Fix verified: the check that found the problem now passes on every affected URL.
• Search recovery seen: Search Console shows the change, such as pages returning to the index. This can take weeks, because Google has to recrawl the pages.

Mixing these up is how agencies over promise. Report the first as soon as it is true. Report the second only when you see it in the data. Our guide on technical SEO checklist covers the re-check method step by step.

A worked example

Here is an example of a short monthly summary for a fictional online store, written to the template above:

Clicks to category pages rose compared with last month, and impressions on the new guides section started to appear. We fixed and verified the broken canonicals on 340 category pages. One outage on 9 October lasted 17 minutes and was caused by a failed plugin update. Still open: 52 product pages with duplicate titles, waiting on the client's developer since 3 October.

Notice what it does. It gives one result, one verified fix, one incident with a cause and one open item with an owner. It makes no promise about rankings. Every number in it can be traced to a check or a ticket.

How often should you send a client SEO report?

Send a full client SEO report monthly for most clients, and send incident notes as they happen. Monthly matches how fast search data settles and gives fixes time to be verified.

Some clients need a different rhythm:

Whatever the rhythm, send critical news the day it happens. A client should never learn about an outage or a sitewide noindex from the monthly report. The report is the record. It is not the alarm.

Agree the date and format at the start of the work, and keep them stable. A report that arrives on the same day each month, in the same layout, is far easier to compare over time.

How to build the report without losing a day

Build the report from systems that already hold the facts, not from screenshots pasted by hand.

1. Pull search data from Search Console for the agreed pages and period.
2. Export the task list for the period, with status and proof links.
3. Count issues by new, fixed, reopened and recurring.
4. Add uptime and the list of confirmed outages.
5. Write the summary last, from what the sections show.
6. Send a read only link if your tools allow it, so the client sees the same proof you do.

the platform is designed with this in mind. Its Fix Tracker produces a client report with the client's logo and a read only link, built only from real data: new, fixed, reopened and recurring issues, uptime and incident history. It never promises rankings or traffic. To see how tasks get into the tracker in the first place, read Fix Tracker.

Common client SEO report mistakes

These mistakes make clients skim, doubt, or stop reading.

• Leading with a wall of charts. Start with the summary. Charts support it.
• Reporting tool scores. A site health score from a third party tool is not something Google uses. Report findings and fixes instead.
• Claiming credit for every rise. Seasonality, news and algorithm updates move traffic too, as Google's guide to debugging drops in Search traffic points out. Say what you did and what you saw, and keep them separate.
• Hiding what is stuck. Clients notice silence. Name the blocker and the owner.
• No proof. "We optimised 40 pages" invites the question "how?". A before and after answers it.
• Promising rankings. Nobody controls rankings. Promise clear work and proof that the fixes hold.