Your SEO audit is 40 pages. You've done six of them.
We're not another audit. We run the fixes — recipe schema, internal links, the 200 small things nobody has a free Tuesday for. You keep cooking.
Built on a real food blog first. Still is.
- Add cookTime + prepTime to recipe cards47
- Link orphaned posts into category hubs12
- Compress hero images over 400kb88
- Rewrite meta descriptions over 160 chars31
- Flag recipes losing position 3→8 since June9
- Draft update briefs for 2019 posts still ranking14
Four stations. You approve, they execute.
Nothing publishes without your sign-off. You are the chef — we don't write your recipes and we don't post as you.
Technical & schema
The unglamorous layer that decides whether Google renders your recipe card at all.
- Recipe, Article, FAQ schema
- Core Web Vitals + image weight
- Crawl waste and index bloat
Content ops
Finds which existing posts are worth your time, and tells you exactly what to change.
- Decay detection on old rankings
- Update briefs, not drafts
- Internal link architecture
Gap analysis
What your readers search that you haven't made yet. You decide what's worth developing.
- Seasonal demand ahead of curve
- Competitor coverage holes
- Search + AI retrieval visibility
Social & distribution
Pinterest, short video, newsletter. Opening to a founding cohort.
- Reserve a spot on the pricing page
Two add-ons run alongside the stations: Get Cited by AI and Get Published.
We broke our own site before we'd touch yours.
our food blog is ours. A 33-page audit landed on 1,500 posts — a $70,000 job by hand. We built agents to run it, then updated 926 posts in a single month and watched Google treat it as a mass change. Everything we do now is shaped by that.
across the archive
the audit by hand
audit on 1,500 posts
The ones people actually ask.
Are you going to publish AI content on my blog?
No. We don't write recipes and we don't publish as you. The agents do implementation and analysis — schema, links, technical fixes — and produce briefs telling you what's worth developing. Every change routes through your approval before it goes live. We learned why that matters the expensive way, on our own site.
What do you need access to?
Search Console, Analytics, and a WordPress account with editor permissions. We'll ask for admin only if a specific fix requires it, and we'll tell you which one and why.
How is this different from a VA at $50/hour?
A VA executes what an audit tells them, at the speed a person can work. This runs continuously and catches decay the month it starts rather than the year you get around to re-auditing. If you already have a VA you like, we'll work alongside them — the prep list is the handoff.
What if my traffic drops?
Every change is logged with a date so anything can be reversed. We report what moved and what didn't, including the misses.
Do I own what you build?
Yes — content, schema, configuration, all of it. If you leave, it stays.