Report Structure Template

# [Client] SEO Audit & Prioritized Recommendations
Prepared: [date] | Scope: [scope] | Data sources: [1-line list with link to Appendix A]

## SEO Health Score: [0-100]/100 ([Tier])  ← page 1, right after title
Per-category table (Content Coverage 22%, Technical SEO 20%, On-Page 18%,
Performance 12%, Schema 10%, AI Visibility 10%, pSEO 8%).
1-2 sentences naming the highest-impact levers.
Calibration note: AI-assessed, not a Google ranking factor; compare a site only
against its own history. Re-run tracker: date / score / tier / delta.

## Leadership Summary          ← 60-second entry point
Decisions required this week (3 max). Biggest commercial opportunity (1 sentence).
Core strategic observation about how the site is currently functioning vs. how it should.
What success looks like at 90 days — outcome framing, not a list of fixes.

## Executive Summary
Opens with the 1-2 findings that reframe the client's situation. One paragraph on what's
working. The findings that determine priority order. Realistic 90-day expectation with hedges.

## 90-Day Execution Plan            ← page 2, not the end
Week 1 table: highest-risk / fastest-to-fix items
Month 1 table: highest-ROI items
This quarter: strategic content and authority building (bullet list)
Deprioritized for now: explicitly named items + reason (bullet list)

## Top Revenue Opportunities        ← elevates commercial findings before technical
5-row table: Priority / Opportunity / Why it's the top lever / Where in report

## Key Findings                     ← supports the executive summary with specifics
Performance & technical / Indexing / Traffic & conversion / Content lifecycle decisions /
Backlink baseline / Historical SERP environment / SXO Analysis. Include Crawl Stats only when
it produces a useful verdict; detailed URL rows stay in evidence/appendices.
Include internal-search indexability only when the conditional check produces a finding;
separate any unsafe reflected-input evidence and state that the harmless check is not a pentest.

## Additional Findings from Skills  ← secondary layer; grounded in client data

## Security & Platform Risk Findings ← OPTIONAL; default OMIT

## What NOT to Do                   ← client-specific anti-patterns; prevents backsliding

## Prioritized Recommendations      ← single-layer, no duplicate matrix
Each item: #N. Title / Impact / Effort / Issue / Actions / Verification (no Owner field — don't invent assignees)
Tier 1 → Tier 2 → Tier 3. Each item appears once.

## Programmatic SEO — Growth Initiatives
Launch order table only. "See Appendix B for full playbook detail."

## Phase 2 — Defer
Short bulleted list. Each item: what it is + why it needs more data.

## Content Standards                ← only if client is scaling pSEO content production

## Acquisition Channel Q&A          ← closing strategic section; answered LAST, from all sources
Goal framing: "turn this website into a predictable acquisition channel."
Explicit Q&A pairs for the runbook §5.7 questions (structure / conversion / product pages /
landing pages / lead magnets / SEO opportunities / content strategy + buyers-vs-traffic and
blog → lead magnet → demo/trial). Every answer cites data or names the gap + its Tier 1 action.
Ends with: website improvement roadmap, lead magnet plan, 6-month content priorities.

## Verification & Tracking
Baseline snapshot and persistent change journal (dated action/deploy IDs, scope, target metric,
acceptance result, analytics changes, and Google incidents). Monthly content lifecycle register,
fixed historical SERP panel, separate backlink baselines, and conditional Crawl Stats review.
Content merge/prune actions stay Red and every new/refresh/merge action uses an approved evidence
brief. Schema actions revalidate live, then compare the same GSC Enhancement/Search Appearance type
at 2/4/8 weeks, keeping validity, eligibility, and display separate.

## From Audit to Action
Link to `./<client-slug>-seo-action-runbook-YYYY-MM-DD.md`, generated locally beside this report after report QA.
Explain that it was compiled from this report, classifies every recommendation by how the
AI can help, requires current best-practice research, manages approved batches, verifies
live changes, measures at 2/4/8 weeks, and preserves history across future audit cycles.
Include the start command:
"Follow <client-slug>-seo-action-runbook-YYYY-MM-DD.md and show me the Action Capability Map and recommended first
batch. Research anything that may have changed. Do not change anything until I approve
a batch."

---

## Appendix A: Data Sources         ← full table of what was collected and when
## Appendix B: pSEO Detailed Playbooks  ← full templates, URL structures, scale estimates
## Appendix C: [Comprehensive findings, if client wants it]

What to Adapt Per Client

ElementWhat to change
Top Revenue OpportunitiesFind the client’s actual conversion data first
Search/security statusCheck GSC Manual Actions and Security Issues; verify crawler warnings separately
Content cluster head termThe term the client should rank for but doesn’t
Competitor comparison Format 4Top 2 incumbents in their specific category
pSEO integrations clusterOnly if client has confirmed, real integrations
AI Overview defenseCheck informational pages with CTR ≤1.5% at positions 6–12

What Stays Consistent Across Clients

  • Default WordPress robots.txt — always needs expanding
  • Author archive and feed URLs consuming crawl budget
  • Thrive or Elementor theme pagination bugs generating 404s
  • Schema present but invalid — Organization.logo as object not string
  • No comparison or alternative pages — almost always absent
  • Internal nofollow links — frequently misconfigured in page builders
  • Mobile performance drag from third-party scripts
  • Dev/localhost URLs in production HTML