Audit
Diagnostic only. No code ships. You walk away with revenue mapped per fix, not a deck.
The audit is the first engagement. Two to three weeks of structured-data, crawlability, and AI search visibility analysis across your top templates. What you get back is a remediation roadmap with revenue impact mapped per fix, so you can decide what to ship, in what order, and what to skip.
No code ships in this engagement. The deliverable is understanding. What's broken at the schema layer. Why it's broken. What the fix order is. How much revenue is sitting on the table.
About 70% of audit clients move directly into a Sprint to remediate the top findings, but you can also take the audit and execute internally, or pause and revisit. The roadmap is yours regardless of next step.
Risk reversal: if the audit doesn't surface at least 5 high-revenue-impact fixes, you don't pay for the audit.
What's included
- Schema graph audit · @type, @id, entity relationships across all top templates
- AI visibility scan across 5 engines (Google AI Overviews, ChatGPT, Perplexity, Claude, Gemini)
- Crawlability + indexation review · robots.txt, sitemaps, canonical, hreflang
- Core Web Vitals + crawl budget analysis
- Per-template field-level schema audit
- Prioritized remediation roadmap with engineering effort estimates per fix
- Per-fix projected revenue impact
- 60-min walkthrough call with your engineering team
What’s not included
- Production code changes (those are Sprint scope)
- Schema implementation work
- Ongoing monitoring (that's Retainer scope)
- Content strategy / editorial recommendations (you have a content team for that)
What the Audit actually consists of
Each line item below is its own deep-dive page. Open the ones that matter to your decision. Skip the rest.
- // component 01Schema graph audit
Field-level review of every JSON-LD block on your top templates, plus the entity relationships that connect them into a single resolvable graph.
Read the deep-dive - // component 02AI visibility scan
I run your top queries against five AI engines and measure where you appear, where competitors appear instead, and what your citation share looks like today.
Read the deep-dive - // component 03Crawlability and Core Web Vitals
Robots, sitemaps, canonicals, hreflang, render budget, and CWV scored for every top template, with the issues that block schema from being discovered.
Read the deep-dive - // component 04Revenue impact per fix
Every finding gets a projected revenue range based on query volume, current visibility, and recoverable position. Not a guess. A model with the inputs visible.
Read the deep-dive - // component 0590-day remediation roadmap
Findings sequenced into a 90-day plan with engineering effort estimates, dependencies, and the order to ship if you only have 30 days of capacity.
Read the deep-dive
Why is the audit a separate engagement?
Because schema implementation that ships before architecture is settled is how this work goes wrong. The audit lets us scope the problem before committing 4-6 weeks of engineering. If you're certain you need a Sprint, we can skip the audit, but most clients regret skipping.
Can I just buy the audit and have my team execute internally?
Yes. About 30% of audit clients do this. The roadmap is engineer-readable. If your team has structured-data experience, they can execute it without me. If not, the Sprint exists for a reason.
Does the audit fee credit toward a Sprint?
Yes, but capped. $12,500 of the $25,000 audit fee credits toward a Sprint if you book within 60 days. (The audit is real engineering work; I'm not giving it away to make a Sprint sale. Half-credit is the right number.)
What if my schema is mostly fine and I only need a small fix?
Then you don't need an Audit. You need a Quick Scan ($4,500, 5 days, single engine, written report). If the Quick Scan reveals deeper structural issues, the $4,500 credits 100% toward an Audit within 30 days.
Stop pouring budget into a broken foundation.
If your SEO retainer hasn’t compounded, your AI citations have stalled, or your last technical audit ended in a deck nobody read, that’s not a content problem. It’s an engineering problem. The same engineer who diagnoses ships the fix.