SEO Audit Report Template (2026): What to Include and How to Present It

A client does not buy an SEO audit. They buy the decision it makes possible: what to change on their site, in what order, and what that will be worth. Most audit reports bury that decision under 40 pages of tool screenshots. The client skims the score, reads the first page, and files the PDF.

This SEO audit report template is built around the first page. Everything after it exists to back up the three to five fixes it recommends. Use it as is, copy the wording, or adapt the structure to your own brand.

What an SEO audit report template is, and why it matters in 2026

An SEO audit report template is a reusable structure for presenting audit findings to someone who did not do the audit: a client, a manager, a developer. It fixes the order of sections, the format of each finding and the level of detail, so every report you send answers the same questions in the same place.

Two changes since 2024 make the template more important than the tool you run the audit with.

Raw audits became a commodity. Free tools, browser extensions and chat assistants can produce a list of technical findings for any URL in seconds. Clients have seen those lists. What they cannot get for free is judgement: which findings matter for their business, in what order, and with what expected return. The report is where that judgement is visible.

Search results got harder to explain. AI Overviews, AI Mode and AI chat answers now sit between a client's page and their customer. A 2026 report needs a line on AI visibility (crawler access, Search Console's generative AI impressions) because clients ask about it, and a report that ignores it looks dated.

The money involved makes the stakes plain. Ahrefs' survey of 439 SEO providers found the most common fee for a one-off SEO project was $2,501 to $5,000. At that price the report is the product, and a client should be able to act on it without you in the room.

The seven sections of an SEO audit report

Every section has one job. If a section does not help the reader decide or act, cut it or move it to the appendix.

1. Scope and method

State the domain, the number of pages crawled, the date, the target keywords for the key pages, and the tools used. One paragraph is enough. This protects you later: if the client asks why a page was not covered, the scope answers it.

2. Executive summary

This is the page the client reads. Keep it to one page and follow a fixed shape: the headline finding, the three to five priority fixes, the expected outcome and the ask. A copy-paste version is below.

3. Baseline metrics

Record the numbers you will compare against in 90 days: indexed pages and the main reasons pages are excluded (from Search Console's Page indexing report), clicks and impressions for the last three months, the average position for the target keywords, Core Web Vitals pass rate from field data, and generative AI impressions if the property has them. Without a baseline, the next report cannot show progress.

4. Prioritized findings

The core of the report: a table with one row per root cause, not per URL. Columns: issue, evidence, impact tier, pages affected, fix, owner, effort and status. Rank it using a consistent method; the one we use is in how to prioritize SEO issues.

5. Page-level detail

For the five to twenty pages that matter most (usually the ones with the most impressions or the most commercial value), show the specific problem and the exact change: the current title and the replacement, the missing H1, the canonical that should be self-referencing. Developers and writers work from this section, so be literal.

6. The 30-60-90 day plan

Group the fixes into three windows: blockers and template fixes in the first 30 days, page-level work in the next 30, content and links in the last 30. Add the check that confirms each one, such as a re-audit or URL Inspection.

7. Appendix

Everything else: the full tool export, a glossary, low and cosmetic findings. Clients rarely read it, but it shows the audit was thorough without cluttering the pages they do read.

How to build the report in 8 steps

1. Agree the scope in writing first: which domain or sections, how many pages, which keywords the key pages should rank for, and the delivery date.
2. Export Search Console data for the last three months (Performance by page and the Page indexing report) and record the baseline numbers.
3. Run the audit with a target keyword for each key page, so findings include relevance as well as technical health.
4. Merge the findings by root cause and assign each an impact tier, then score and rank them.
5. Write the page-level detail for the top pages, with the exact current value and its replacement.
6. Group the fixes into a 30-60-90 day plan with an owner and a verification check for each.
7. Write the executive summary last, and put it first.
8. Export the report as a PDF for the record and share a live link or spreadsheet for the working copy.

Steps 3 and 4 are where an audit tool earns its cost. A keyword-aware audit catches the relevance problems (a category page whose title never names the category) that a generic crawl reports as a pass.

Copy-paste wording for the report

These are ready to adapt. Replace the bracketed values with your client's numbers.

Executive summary

Headline: [Domain] has [N] pages that Google cannot index or rank in their
current state, and they account for [X]% of the site's search impressions.

Priority fixes (next 30 days):
1. Remove the canonical tags pointing to the homepage on [N] product pages.
   Expected: these pages return to Google's index within 2-4 weeks.
2. Add the target keyword to the title and H1 of the [N] category pages.
   Expected: improved position for [keyword] from an average of [P].
3. Link the [N] orphan service pages from the main navigation and related
   pages. Expected: Google discovers and recrawls them.

What we need from you: developer time for fix 1 (about 1 hour), and approval
of the new titles in Appendix B.

One finding row

Issue: Canonical tag points to the homepage
Evidence: 40 product URLs, e.g. /products/blue-widget -> canonical /
Impact: Critical. Google treats these pages as copies of the homepage and
does not rank them.
Pages affected: 40 (45% of search impressions)
Fix: Make each product page's canonical self-referencing. One change in the
product template.
Owner: Developer  |  Effort: 1 hour  |  Status: To do

30-60-90 plan opening

Days 1-30: Fix the blockers and template issues (findings 1-4). Verify with
URL Inspection and a re-audit.
Days 31-60: Rewrite titles and headings on the 12 category pages; add internal
links to orphan pages (findings 5-9).
Days 61-90: Content gaps on the 5 highest-impression pages against the
current page-one results (findings 10-12). Re-run the full audit and compare
with the baseline.

What an SEO audit should include

Clients often ask what they are getting before they agree to an audit, and the honest answer differs by budget. A solid audit covers crawlability and indexing, on-page relevance against target keywords, content depth versus the ranking competition, internal linking, page experience and Core Web Vitals, structured data, and AI crawler access. Larger audits add backlink analysis, log files, competitor gaps and migration risks.

What separates a useful audit from a long one is that every finding comes with a priority and a fix. A scope list you can send to clients, and the deliverables that should be in the final report, is in what does an SEO audit include. The checks themselves are in the SEO audit checklist.

Pricing the audit

The report template also shapes the price, because most of the time goes into analysis and writing, not running tools. Published price guides put a human-reviewed audit of a small site (around 100 pages) at roughly $500 to $2,500, a 1,000-page site at about $1,100 to $4,500, and sites with 100,000 or more URLs from $4,500 to well over $20,000. Buyers often pay less than that: in a 2026 WebFX survey of 250 US businesses, 43% had paid between $101 and $750 for their audit.

The fair way to set your own price is to estimate hours for the sections above (scope, analysis, page-level detail, plan, summary) and multiply by your rate, then add a fixed fee for the call where you walk the client through it. The full breakdown, with sample quotes, is in how much does an SEO audit cost.

Presenting the report to a client

A report that lands in an inbox gets skimmed. A report presented in a 30-minute call gets acted on. The call follows the executive summary: the headline, the three fixes, what each will achieve, and what you need from the client. Screen-share the findings table only when they ask how you decided.

Expect three questions in every presentation: "how long until we see results?", "can we do this ourselves?" and "what happens if we only do the first fix?". Have answers ready for all three. The script, the follow-up email and how to handle a client who disagrees with the priorities are in how to present an SEO audit to a client.

White-label reports for agencies

Agencies and freelancers who audit for clients usually want the report under their own name. A white-label SEO audit report carries your logo, colours and contact details, and no mention of the tool that produced the findings. Most audit tools that offer white-labelling do it at the PDF export stage; some also offer a branded client link or portal.

The things to check before you choose a white-label tool: whether the PDF can be edited or only regenerated, whether the client link updates when you re-audit, whether the report explains findings in plain language for a non-SEO reader, and whether the per-page price works at your volume. The comparison is in white label SEO audit report.

Report formats compared

The same findings can go out in several formats. Most agencies send two: a PDF for the record and a working copy that stays current.

Common report mistakes, and what to do instead

Leading with the score. Wrong: page one is "Your SEO score: 54/100" with a red gauge. Right: page one is the headline problem in business terms ("40 product pages are invisible to Google") and the three fixes. Mention the score as a trend line in the baseline, if at all.

Listing every URL. Wrong: a 600-row table of "missing alt text" findings in the main report. Right: one row, "Product template outputs images without alt text, 600 images", in the findings table, and the full list in the appendix spreadsheet.

Tool language instead of client language. Wrong: "Non-self-referencing canonical detected on 40 URLs." Right: "Forty product pages tell Google they are copies of the homepage, so Google does not show them in search."

No baseline. Wrong: a report with recommendations and nothing to measure them against. Right: a baseline section with indexed pages, clicks, impressions and positions, so the 90-day review can show what changed.

No owner. Wrong: "The canonical tags should be fixed." Right: "Developer, 1 hour, this sprint. We will confirm with URL Inspection on [date]."

Adapting the template to the client

The seven sections stay the same, but the emphasis shifts with who is reading.

Small business owner. Shorten the findings table to the top ten, translate every item into plain language, and make the plan say who does each fix: you, their web developer or them. Owners want to know what to approve and what it costs. Leave the appendix as a spreadsheet they will never open.

Marketing manager at a mid-size company. Keep the full findings table, add a line per finding on the expected effect, and make sure the baseline matches the numbers they already report to their boss. They will forward your summary upward, so it must survive being read alone.

Developer or technical lead. Lead with page-level detail: exact URLs, current values, the required change and how you will verify it. Developers trust specifics and distrust scores, so keep the score out of their copy.

Ecommerce team. Group findings by template (product, category, search, cart) rather than by issue type, because that is how their development work is planned. Show reach as the share of revenue or impressions on each template.

Agency client on a retainer. Treat the audit as month one of an ongoing report: the same baseline metrics, the same finding IDs, so each later update can show issues moving from open to fixed.

A pre-send checklist for the report

Run through this before anything goes to a client. Each item catches a mistake we have seen cost a renewal.

• The executive summary fits on one page and names no more than five fixes.
• Every finding has an impact tier, an owner, an effort estimate and a verification step.
• No finding is listed per URL in the main report; repeats are grouped by root cause.
• Every number in the summary appears in the baseline or findings, with its source and date.
• Page-level detail shows the current value and the exact replacement, not "improve the title".
• Tool jargon is translated: "canonical", "noindex" and "render" each have a one-line explanation the first time they appear.
• The report says what was not covered (backlinks, log files, subdomains) so nobody assumes it was.
• Links in the PDF work, and the client link or spreadsheet is shared with the right people.
• Your contact details and the date of the next review are on the last page.

Tools for building the report

Google Search Console for the baseline: Performance by page, Page indexing reasons, Core Web Vitals and the generative AI performance report.

A docs tool (Google Docs, Word, Notion) for the executive summary and plan, and a spreadsheet for the findings table. The free Excel audit checklist works as a starting point for the findings sheet.

Looker Studio if the client also wants a traffic dashboard alongside the audit.

Seotific produces the findings in the shape this template needs: one row per issue, with the impact tier, evidence and fix already written, sorted by priority. Exports go to PDF and Excel, white-labelled on the Agency plans, and a client portal link shows each new audit as it lands, which covers the "live link" format above. If you audit for clients regularly, see Seotific for agencies and for freelancers.

Frequently asked questions