SEO Audit Report Template: Download a Blank Client Report
Key Takeaways
- Download an editable blank HTML report or copy the Markdown source; both include scope, evidence, client actions and re-check fields.
- The filled example and matching PDF use fictional data, with 10 of 12 discovered pages analyzed.
- Use pass, open, not checked and unknown precisely; an unavailable page is not a passing page.
- Separate scanner observations, agency priority, suggested work and measured outcomes.
This SEO audit report template is a working document you can adapt to a client engagement. It starts with the decision the client needs to make and retains the evidence needed to inspect the recommendation. It does not assume that a score covers every page or that a technical repair guarantees more traffic.
Download the blank report and inspect the filled example
- Download the editable HTML template — open it locally, fill the labeled fields, then print or save as PDF.
- Download the Markdown template — copy it into your preferred document editor or reporting workflow.
- Read the filled illustrative client report and download its matching PDF.
The HTML editor keeps edits in the open page only. Save your work with its “Download edited HTML” button before closing or refreshing. It does not upload client information. The blank template and the filled sample are different artifacts: the template gives you fields to complete; the sample demonstrates one limited, fictional audit.
Section 1: Agency, client and decisions
Complete the agency name, client, website, audit date, report preparation date, reviewer and version. State the business question in the client's language. For example, “Which page-template repairs should we approve for the next release?” is an illustrative question, not a claim about a real engagement.
Write a short executive summary after reviewing evidence. Include what was assessed, the most important observed issue, the action requested and the largest remaining unknown. Ask for a decision: approve work, provide access, review an intentional configuration or defer with a reason. Do not add an unsupported revenue estimate to make an issue sound urgent.
Section 2: Scope and coverage
List the input URL, discovery method, analyzed URLs, failed fetches and unchecked URLs with reasons. A discovered URL belongs to the inventory; an analyzed URL actually contributed supported evidence. Discovered counts are not proof that the inventory is the whole website.
Specify the checks performed, configuration, device, timestamps and optional data unavailable. If using a score, include its rubric, assessed categories and exclusions. Leave it blank when there is no defensible rubric. Do not fabricate backlink, local-search or AI-visibility scores to fill the template.
| Coverage state | Use it when | Client interpretation |
|---|---|---|
| Analyzed | Supported evidence was captured and assessed | Only the disclosed checks on this page were assessed |
| Failed | An attempted fetch or measurement failed | No passing conclusion can be drawn from the failed attempt |
| Not checked | The page or check was excluded, capped or not attempted | It remains outside this assessment |
| Unknown | Evidence cannot establish the required state | Collect evidence or clarify scope before deciding |
Section 3: Findings with inspectable evidence
Give each finding a stable ID, affected URL, rule name, capture time, evidence excerpt and source reference. Keep severity separate from the agency's priority: a technical rule can be serious while a repair is deferred because the page is intentionally retired. Document that decision rather than altering the observation.
Use confidence labels with a reason. “Confirmed in captured HTML” is appropriate for a missing element in the captured source. A single Lighthouse lab result needs a caveat about conditions and repeatability. The web.dev explanation of lab and field data explains why those measurements can differ.
Section 4: Client actions and implementation guidance
For each action, fill the proposed change, owner, prerequisites, estimated effort and who supplied that estimate, approval state, target date and acceptance check. Suggested code is guidance; the implementation owner must review it against the actual CMS, security requirements and intended behavior.
Record why an item is prioritized. It may affect an agreed landing page or a documented user requirement. If the priority relies on Search Console or analytics, attach the separate source, property and date range. Do not claim the scanner measured business importance.
Section 5: Follow-up and exclusions
Schedule a comparable re-check and retain previous evidence. An issue can be marked resolved only when the same relevant URL and check were successfully observed under a comparable method. A missing URL, failed fetch or changed rule can produce not checked or unknown; it cannot establish resolution.
Separate approved, deferred and declined work from technical status. “Client declined” is a decision; the technical finding may still be open. Carry unchecked pages and unavailable sources into the next review as explicit tasks.
What the MendMySEO example actually covers
The current audit scores two dimensions, Technical and On-Page, using six deterministic rule families: homepage HTTPS; viewport presence on analyzed pages; a non-empty title on analyzed pages; and, when measurements are available, homepage mobile Lighthouse performance below 50, LCP above 4 seconds, and CLS above 0.25. The three Lighthouse checks are lab diagnostics from one run. They are not field Core Web Vitals or a prediction of rankings.
The audit samples up to 10 pages. The public sample is explicitly illustrative: 12 discovered, 10 analyzed, 0 failed, 2 not checked, with an illustrative assessed-scope score of 81. Ten analyzed pages do not mean the entire website passed; the two unchecked pages remain unknown. A missing Lighthouse measurement is not a passing measurement.
Canonical checks, title length or site-wide uniqueness, heading completeness, structured-data validation, backlinks, keyword rankings, recurring multi-source dashboards, and AI citation monitoring are outside this six-rule assessment. If your engagement needs them, add separately collected evidence and name its source. MendMySEO does not currently offer custom report domains or an embeddable lead-audit widget. See the tool page for current availability and supported delivery.
Frequently Asked Questions
Can I edit this SEO audit template in Word or Google Docs?
Use the Markdown version as copyable source, or copy the sections from the HTML into your editor. The download is not a native Word or Google Docs file.
Does the blank template run an audit?
No. It provides labeled fields and status definitions. Fill it using evidence from your supported audit and reviewed client information.
How long should the report be?
Use enough space to explain scope, decisions, evidence and next actions. Move long inventories to an appendix with stable finding IDs rather than hiding limitations to meet a page count.
Should I include competitor comparisons?
Only if the same metric, source, configuration and time window were used. Keep separate research labeled; neither the template nor the MendMySEO sample supplies competitor measurements.
Inspect the report before choosing
Open the complete illustrative client report, download its matching sample PDF, or try the branding preview. These examples use fictional data; they do not crawl your website or demonstrate a customer result. Check current access and pricing before planning client delivery.