Every engagement, every component.
Four engagements. Same engineer. No handoffs. Each one breaks down into its component parts. Pick the level of depth that matches your decision.
Audit
$25,000Diagnostic only. No code ships. Walk away with revenue mapped per fix, not a deck.
- // audit · 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.
Open - // audit · 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.
Open - // audit · 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.
Open - // audit · 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.
Open - // audit · 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.
Open
Sprint
$70,000+Production code ships. Schema architecture, JSON-LD per template, validator-clean structured data live in your codebase with CI gates.
- // sprint · 01Full @graph architecture
One consolidated JSON-LD @graph per page, designed across templates, with @id and sameAs chains stable enough for AI engines to merge entities cleanly.
Open - // sprint · 02Per-template JSON-LD
I write the schema generation code for every priority template, ship it through your CI, and pair with your engineers so they can extend it after I'm out.
Open - // sprint · 03Entity resolution and AI emulation
I emulate how each AI engine actually parses your @graph, find where entities fail to resolve, and fix the schema so resolution happens deterministically.
Open - // sprint · 04Validator suite in CI
Schema validation runs on every pull request. If a change breaks a Schema.org rule or a custom @graph rule, the build fails before it ships.
Open - // sprint · 05Engineer pair sessions
I pair directly with your engineers through the Sprint so they review every PR, understand the architecture, and own the work after I'm out.
Open - // sprint · 06Pre/post citation measurement
I run the same AI visibility query set before and after the Sprint, so the engagement has a measured outcome instead of a vibes-based one.
Open
Retainer
$10,000-$25,000/moOn-call engineering. Schema decays. I keep it from decaying. Both engines stay clean.
- // retainer · 01Schema regression monitoring
RankLabs and your CI watch for schema breakage on every deploy. When something regresses, I see it before your traffic does.
Open - // retainer · 02AI citation tracking
Continuous monitoring of your citation share across five AI engines. We watch the trend, not just the snapshot, so drift gets caught early.
Open - // retainer · 03Monthly pair sessions
60 minutes a month with your engineering team to review what regressed, what moved, and what's worth shipping next.
Open - // retainer · 04Slack channel with SLA
Direct Slack access to the engineer who shipped your Sprint. 24-hour response on Standard, 4-hour on Enterprise.
Open - // retainer · 05Quarterly architecture reviews
Every 90 days we step back from incident response and ask whether the @graph design still fits the business as the site has evolved.
Open
Quick Scan
$4,5005 days. Single AI engine. Get a written report on what's broken before you commit to anything bigger.
- // quick-scan · 01Top 5 template schema review
I pick your five highest-traffic or highest-revenue templates, extract the JSON-LD, and score it the way an AI engine would.
Open - // quick-scan · 02Single AI engine visibility scan
Pick one AI engine. I run your priority queries, capture citation share, and show you what the engine actually says about you.
Open - // quick-scan · 03Written 8-12 page report
A real written document, not slides. Findings, priorities, and engineering effort estimates in prose dense enough for an engineer to act on.
Open - // quick-scan · 04Engineering effort estimates
Every finding gets a days-of-engineering estimate, so your team can decide what fits in a sprint and what needs scoping.
Open
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.