The onboarding audit.
The first substantive deliverable sets the renewal arc for 12 months. The three-week audit structure, the 12-18 page deliverable format, the custom SWOT slide deck, and the 90-day plan that the client renews against.
Why the onboarding audit anchors everything
The onboarding audit is the first substantive deliverable a new client sees from you, and it sets the renewal arc for the next 12 months. Every working operator agrees on this and almost none of them do it well early in their career. The mistake pattern: deliver the audit as a 30-page document with 80 findings, walk through it for 90 minutes, and then start the actual content work the next month. By month 3, neither party remembers what was in the audit; by month 6, the client wonders whether the engagement is producing results.
The fix is treating the onboarding audit as a structured business artifact, not a technical assessment. It does three things: establishes the baseline measurements you'll report against for the rest of the engagement; produces a custom SWOT presentation the client can show internally; and surfaces 5-8 specific findings the operator will address in the first 90 days. Everything else gets cut.
This lesson covers the audit structure that working multi-client operators have converged on — what to include, what to leave out, how to present it, and how to convert the audit's findings into the 90-day plan that justifies the retainer.
The three-week audit structure
An onboarding audit takes roughly three weeks of operator time spread across the first month of engagement. Compressed timelines (5-day audits) produce shallower findings; longer timelines (6+ weeks) produce findings the client doesn't remember by the time you present them.
Week 1: data collection and automated assessment
Run automated checks first because they're cheap. Reffed audit, schema validation, llms.txt status, robots.txt review, sitemap analysis, page speed benchmarks. All of this is mechanical work that can happen in parallel while you start the qualitative analysis.
The deliverable for week 1 is a raw findings document — not formatted, not prioritized, just an inventory of what you've discovered. Keep it private to you for now; it's input to week 2's analysis, not a client artifact.
Week 2: manual prompt-level audit and competitor analysis
Run the 8-Prompt Map against the client's category on all six AI engines. Document the actual responses — copy and paste them, screenshot the AI Overview, save the Perplexity citations. This qualitative baseline matters more than the numerical scores for client conversations. You'll reference these baseline responses when reporting progress months later.
Add competitor analysis. Pick the three competitors the client named in the kickoff call plus two more the AI engines actually return (often different from the client's list — this asymmetry itself is a finding). Run the methodology from Quickstart Lesson 4.3 on each.
Week 3: synthesis and deliverable production
Convert the raw findings into the structured audit deliverable. The format that works:
- Executive summary (1 page) — current state in three sentences, top 5 findings as a bullet list, recommended priority for next 90 days in one sentence.
- Current state baseline (2-3 pages) — mention rate per engine, share of model versus competitors, citation diversity score, and the qualitative reads of how AI engines actually describe the brand today.
- Competitor analysis (3-5 pages) — what the top 3-5 competitors are doing differently. The gap mapping that becomes the basis for the 90-day plan.
- Top 5-8 findings (3-5 pages) — specific, evidenced, actionable. Each finding gets one page with: what was found, why it matters, what the fix looks like, expected time to impact.
- The 90-day plan (2 pages) — week-by-week deliverables mapped to the findings. This is the document that justifies the retainer.
- Methodology appendix (1-2 pages) — what you measured, how, with what tools. Includes the 8 prompts you ran so the client can verify the work or rerun the audit themselves in 90 days.
Total length: 12-18 pages. Less than 12 feels thin; more than 18 doesn't get read.
The custom SWOT presentation
A 15-20 slide deck distilled from the audit document. This is the artifact the day-to-day contact shows their executive sponsor (Quickstart Lesson 5.3 covered the stakeholder roles). The day-to-day contact needs something they can defend internally — the audit document is too long; a Slack message is too thin; a SWOT presentation is the right format.
SWOT framework adapted for GEO:
- Strengths. Specific GEO assets the client has — entries on Wikipedia or aggregators, citation-active content, strong schema implementation. Name 3-5.
- Weaknesses. Specific gaps relative to competitors. Schema missing on top pages, no Wikipedia presence, weak Reddit citation surface. Name 3-5.
- Opportunities. Specific moves that would produce outsized impact. Categories the brand isn't yet competing in, content that could win citations with modest work, off-page surfaces the competitors haven't claimed. Name 3-5.
- Threats. Specific competitive risks. Competitors compounding faster, category shifts in AI engine behavior, regulatory or industry changes. Name 2-3.
One slide per quadrant works for most audiences. For enterprise clients, expand to detail slides under each. The goal isn't comprehensive; it's decision-ready — enough to justify the priorities you've picked for the next 90 days.
The 90-day plan structure
This is the most consequential single page in the audit. The 90-day plan is what the client renews against — if the work in those 90 days produces visible movement, renewal happens; if it doesn't, renewal is fragile regardless of how good the audit was.
Format
Three months × 4 weeks each, with explicit week-by-week deliverables. Format as a table:
| Week | Deliverable | Maps to finding |
|---|---|---|
| 1-2 | Schema audit + ship core types on top 25 pages | F1 (schema gap) |
| 3-4 | Pillar content piece 1 (highest-traffic gap) | F3 (content gap) |
| 5-6 | llms.txt + crawler access updates | F2 (technical gap) |
| 7-8 | Pillar content piece 2 + first PR pitches | F3, F5 (content + off-page) |
| 9-12 | Off-page sprint: Reddit, aggregators, editorial | F5, F6 (authority) |
Realistic expectations
The plan above is illustrative; the specific deliverables vary by client situation. What's consistent is the structure: explicit weekly outputs, each mapped back to a finding the client agreed mattered in the audit walkthrough. The mapping is critical — it prevents the conversation 60 days in where the client asks "remind me why we're doing this." The audit answered that already.
The audit walkthrough call
60-90 minutes, scheduled within 3 business days of audit delivery. Don't email the audit and hope they read it. The walkthrough is part of the deliverable, not a separate event.
Structure
Three blocks:
- Block 1 (15 min) — Current state baseline. Walk through mention rate, share of model, citation diversity, qualitative reads. Get explicit agreement that these are the metrics you'll report against monthly.
- Block 2 (30-40 min) — Top findings. Walk through the 5-8 findings. For each: what was found, what the data shows, what the fix is, how long it takes. Get explicit agreement on which findings to prioritize.
- Block 3 (15-20 min) — The 90-day plan. Walk through the weekly deliverables. Confirm the implementation owner has bandwidth for what's required from them. Schedule the first month's check-ins right then.
Anti-pattern
Operators who walk through every page of the audit in order produce 2-hour calls that exhaust the client and bury the findings. The structure above forces ruthless prioritization — only 5-8 findings get airtime, only 3 weeks of deliverables get walked through in detail. Everything else stays in the audit document for reference.
Implementation: building your audit template this month
- Week 1. Document your current audit process honestly. How long does it take? What sections does it have? Which sections does the client actually engage with?
- Week 2. Build a standardized audit template (Google Docs or Notion). 6 sections, defined length targets, slot-and-fill so the next audit takes 50% less time.
- Week 3. Build the matching SWOT slide template (Google Slides). 15-20 slides, fill-in-the-blank structure.
- Week 4. Apply the new templates to your next new engagement. Track time saved versus the prior process.
What comes next
Lesson 8.2 covers monthly client reports — the artifact that does more for retention than any other deliverable, and the one most operators produce inconsistently. The five-card format, the right cadence for delivery, and the anti-pattern of the 25-page monthly report no one reads.