SEO client report template

An SEO report is a decision document. It should tell a client what you did, what the search data shows for a defined period, what you recommend next, and where you are unwilling to claim a cause. A slide deck of unlabelled charts, or a tool export pasted into email, usually fails that test because the client cannot act on them.

By Roman Klymentiev · Updated 11 November 2026

This is a reusable template for agencies and freelancers who report on a small number of sites. Copy the section list into your own document. There are no sample percentages, no invented “average client” results, and no promise that a template will win retainers. Traffivio’s note for agencies describes how approvals and a shared project can sit beside this report, not instead of it.

Who the report is for, and how often

Write the document for the person who approves the work—often the owner, sometimes a marketing manager. Owners usually want what changed, whether anything important broke, and what you will do next. One report can serve both audiences if the first page is a short narrative and the rest is an appendix.

Monthly is the right default for most small clients. Weekly reporting only helps when you shipped a specific change or a migration is in flight. Daily screenshots teach the client to react to incomplete Search Console days. Lock the date range in advance (each calendar month, or a rolling 28 days versus the previous 28) and reuse it so months can be compared.

State the property you used. Domain and URL-prefix properties do not contain the same rows; if you switched mid-year, say so, and do not chart the two series as one line.

Template sections

Use these eight sections in this order. If a section has nothing to say, keep the heading and write one honest sentence (“No title changes were approved in this period”) rather than deleting it. A stable outline is easier to recognize the next month.

1. Period and scope

Name the site, the Search Console property, the search type (usually Web only), any country or language filter, and the exact dates. If you include a comparison, name that range too. Note anything that makes the period unlike the previous one: a migration, a tracking outage, a seasonal campaign, or a week of no access. This short section is what keeps later charts from being misread.

2. Work completed this period

List the work that actually shipped, by URL: titles and meta descriptions, on-page copy, indexability fixes (noindex, canonical, robots, sitemap), content published or retired, and technical issues you resolved. For each item, say whether it is live and when it went live. Include work that is still waiting—“three title drafts are in preview, pending your approval” is more useful than a silent gap. If you use an approve-before-apply workflow, point to it here; Traffivio keeps drafts in preview until you approve them, and the same idea applies whether or not you use that product. Do not list unapproved drafts as results.

3. Search visibility

This is the Search Console Performance section, not a live rank table. Report clicks, impressions, and CTR for the period and the comparison period, then show the queries and pages that matter for this client, not the entire export. Call out lasting moves and the URLs they attach to, new queries with a meaningful number of impressions, pages with many impressions and few clicks if you will recommend a snippet change, and brand versus non-brand when brand queries would hide a change the client cares about. You do not need a perfect brand classifier; you need a consistent rule and a sentence that says what you did.

Average position can appear as supporting context, not as the headline. As the Search Console basics guide notes, it is an average across the filtered rows, not “the rank” for a keyword. If the last few days of the range are still filling in, say that—do not treat an incomplete week as a verdict on last Tuesday’s title change.

4. Indexing and technical status

Summarize the Page indexing report for URLs in scope: new exclusions that affect money pages, reasons that grew, and reasons you are deliberately leaving alone (retired URLs, parameter variants, alternates). Mention sitemap errors and Inspection results for pages you published or fixed. If a money page is not indexed, say so plainly. Keep tool scores in the appendix unless a Core Web Vitals or crawl issue is actually blocking a page the client cares about.

5. Content and on-page

Describe pages that were improved or published, and pages still too thin to recommend as a search target. If you declined to create near-duplicate location pages, record that decision and why. Connect this to the work log in section 2; do not repeat the ship dates.

6. Risks and blockers

List anything that slowed the work or could undo it: delayed approvals, missing Search Console access, a staging site left indexable, legal review on copy, a plugin that overwrites titles, or a migration still in progress. Clients can act on blockers. They cannot act on a vague “there were challenges this month.”

7. Recommended work for the next period

Propose a short, ordered list, each item tied to evidence from this report. Include what you will not do yet, and why. A list that could be copied onto any other domain is too generic to belong here.

8. Appendix

Put definitions, full exports, screenshots, and method notes at the back: how you split brand queries, which property you used, and links to the live Search Console reports. If you attach screenshots, leave the date range visible. The first page should still make sense if nobody opens the appendix.

How to present Search Console numbers honestly

Clients remember the causal sentence, not the chart. Be conservative:

A narrative clients will actually read

Lead with the story, then show the evidence. Open with two or three sentences on what you completed, whether anything important is off track, and the one decision you need from the client. Then walk the eight sections in order. Use a screenshot only when it clarifies a point, and repeat the recommendation list at the end so a skimming reader still sees it.

Plain language beats jargon. “This service page is shown for these queries but the title does not mention them” is clearer than “we observed snippet CTR degradation on a mid-funnel landing asset.” Keep a glossary in the appendix if needed; do not make the first page a glossary.

A skeleton you can copy

The eight headings above are the skeleton. Paste them into a document and fill them for one site; leave the prompts in your working notes, not in the client-facing file, once you have written the real sentences. If a month was quiet, a short report that says so is better than a long report that restates last month’s charts.

Reporting next to a weekly agent

Some teams now get a weekly list of draft changes from an agent, then approve or reject them in a workspace. That rhythm helps the work log in section 2, because you can show what was proposed, approved, and went live. It does not replace Search Console, and the report still has to explain the period in the client’s language and refuse causal claims the data cannot support. If you use Traffivio for that weekly pass, keep approvals in the product and keep this report as the client-facing story. See pricing and the agencies page for how the workspace is sold, and use a free SEO audit in the appendix when you need to show the live HTML for a title or robots issue.

For the Search Console habits behind sections 3 and 4, start with Google Search Console basics. If you also serve small-business owners directly, the small business SEO checklist is the client-side list this report should not have to repeat in full.