# [Agency name] — SEO client audit report

Blank working template • Version [report version] • Prepared for [client name]

**How to use:** Replace every bracketed field with reviewed client information or write “Not provided / not checked” with a reason. Duplicate finding and action rows as needed. This template does not collect data, run an audit or provide a scoring rubric. Remove these instructions before delivery. Preserve evidence references and material limitations.

Filled illustrative example: https://mendmyseo.com/samples/white-label-seo-audit
Matching example PDF: https://mendmyseo.com/samples/white-label-seo-audit/pdf
The example uses fictional data: 12 URLs discovered, 10 analyzed, 0 failed and 2 not checked. Its illustrative score is 81 within the disclosed assessment. It is not a customer result or a full-site audit.

## 1. Report identity and client decision

| Field | Complete this field |
| --- | --- |
| Agency / reviewer / contact | [agency] / [reviewer] / [contact] |
| Client / decision maker | [client] / [approving person] |
| Website and input URL | [website] / [input URL] |
| Audit capture time and timezone | [YYYY-MM-DD HH:MM timezone] |
| Report preparation time and timezone | [YYYY-MM-DD HH:MM timezone] |
| Report version / prior report reference | [version] / [prior reference or none] |
| Business question / agreed objective | [decision this report supports] |
| Decision requested / approval date | [approve work, provide access, review configuration or defer] / [date] |

### Executive summary

- **Assessment:** [what was actually checked and where]
- **Observed issue:** [highest-priority finding, ID and evidence reference]
- **Agency recommendation:** [why this action is prioritized; separate judgment from observation]
- **Client action:** [decision, owner and next step]
- **Largest limitation:** [missing evidence, excluded URLs or checks]
- **Business outcomes:** [not measured, or separately sourced measure and method; no unsupported forecast]

## 2. Scope, method and coverage

| Field | Complete this field |
| --- | --- |
| Discovery / URL selection method | [method and known inventory limitations] |
| Tool / collector / configuration | [source, version and relevant settings] |
| Assessed dimensions and rules | [exact checks supported and performed] |
| Collection conditions | [device, location, rendering, authentication, timestamps] |
| Optional unavailable sources | [source, reason and consequence] |
| Discovery count | [count, boundary and source] |
| Analyzed count | [count with usable supported evidence] |
| Failed count | [attempted but failed count] |
| Not checked count | [excluded, capped or unattempted count] |
| Count reconciliation | [explain overlaps or different denominators; do not silently mix them] |
| Score / rubric / weights | [score if supported; rubric reference; otherwise not scored] |
| Score exclusions | [unassessed dimensions, unavailable checks, page boundary] |

A discovered URL is not proof of a complete website inventory. An analyzed page is assessed only for the disclosed checks. Missing or unavailable evidence is not a pass. Lab measurements and field measurements must be labeled separately.

### URL inventory — duplicate rows as required

| URL | Coverage state | Evidence / capture time | Reason if not analyzed | Follow-up owner |
| --- | --- | --- | --- | --- |
| [URL] | [Analyzed / Failed / Not checked / Unknown] | [reference and timestamp] | [reason or n/a] | [owner] |

## 3. Findings — duplicate this block per finding

### Finding [stable ID]: [short observed issue]

| Field | Complete this field |
| --- | --- |
| Affected URL(s) and scoped count | [URLs and count; sampled or full inventory] |
| Rule / version / source | [check name, version and evidence producer] |
| Capture timestamp | [time and timezone] |
| Observation | [what the collector actually observed] |
| Evidence excerpt / reference | [captured value or source excerpt; stable reference] |
| Confidence and caveat | [confirmed / likely / uncertain, with evidence basis] |
| Technical severity / reason | [severity and stated rubric; no traffic forecast] |
| Agency priority / reason | [priority and client-specific judgment] |
| Suggested change | [reviewed guidance; not an automatic deployment] |
| Prerequisites / risks | [permissions, dependencies and implementation caveats] |
| Technical status | [Open / Resolved / Not checked / Unknown] |

## 4. Client actions and decisions — duplicate rows as required

| Action / finding ID | Proposed change | Owner / dependencies | Effort estimate / estimator | Approval / reason | Target date | Acceptance check / re-check date |
| --- | --- | --- | --- | --- | --- | --- |
| [action ID / finding ID] | [change] | [owner / dependencies] | [effort / who estimated] | [Pending / Approved / Deferred / Declined; reason] | [date] | [observable technical criterion / date] |

Implementation is included only if the agreed statement of work says so. A suggested fix must be reviewed and deployed by an authorized implementation owner. Technical acceptance is separate from ranking, traffic or revenue outcomes.

## 5. Follow-up verification and unresolved work

| Finding ID | Previous evidence / date | Re-check evidence / date | Comparability / limitations | Result | Owner / next action |
| --- | --- | --- | --- | --- | --- |
| [ID] | [reference / date] | [reference / date] | [same relevant URL, rule, conditions; explain changes] | [Open / Resolved / Not checked / Unknown] | [owner / action] |

### Definitions to retain in the client report

- **Analyzed:** Usable evidence was captured and the disclosed supported checks were assessed. This is not a whole-page or whole-site pass.
- **Failed:** A requested fetch or measurement was attempted and failed. No passing conclusion can be drawn from it.
- **Not checked:** A page or relevant check was excluded, capped, unavailable or not attempted. Its condition remains unverified.
- **Unknown:** Available evidence cannot determine the required state. Obtain evidence or clarify scope.
- **Open:** The relevant supported check still observes the issue. It can be open even if work is deferred or declined.
- **Resolved:** A successful comparable re-check confirms the relevant issue is no longer observed. Changed scope, missing evidence or disappearance from a list alone does not establish resolution.
- **Pending / Approved / Deferred / Declined:** Client decision states, separate from technical finding status. Record an owner and reason.

## 6. Exclusions, separate sources and final review

| Item | Complete this field |
| --- | --- |
| Unchecked URLs and next action | [URL / reason / owner / next step] |
| Checks outside the agreed scope | [explicit list] |
| Separate analytics / competitor / business sources | [system, property, date range, configuration and evidence reference; or not included] |
| Implementation obligations | [included work and excluded work, with owner] |
| Report/PDF consistency review | [reviewer / date / matching version and counts] |
| Client-information and access review | [reviewer / date / intended recipients] |
| Next review | [owner / date / required input] |

**Reviewer sign-off:** [name / date / limitations accepted]

**Client decisions recorded by:** [name / date]