Technical SEO
Monthly technical work for sites that move fast and break things. Dev support, monitoring, and the unglamorous follow-through that keeps the foundation from cracking when the rest of the company ships.
When ongoing makes more sense than an audit
A one-off audit is great if you have a specific question. But if your site changes weekly, audits go stale fast. By the time you've shipped the fix list, the next set of issues is already live. Ongoing is for teams that want a technical SEO inside the workflow, not a snapshot from three weeks ago.
What's included each month
The work that actually keeps the site healthy
Crawl monitoring & alert triage
Weekly crawl, diff against the last one, surface what changed. Broken canonicals, accidental noindex tags, redirect chains that crept in with the last release. Flagged before they cost rankings.
Log file analysis
One or two deep dives a month. What Googlebot actually crawls, what it ignores, where the crawl budget is leaking. Almost always finds something worth fixing.
Dev team support
Tickets, code review, deployment checks, async questions in Slack. I work directly with engineers in the language they actually speak. No 14-step "implement this" docs for things that take five minutes to discuss.
Core Web Vitals monitoring
Real-user data tracked over time, with alerting when a regression lands. Plus the unsexy part: actually getting fixes prioritised, scoped, and shipped instead of sitting in a backlog.
Schema, hreflang, canonicals
The maintenance nobody else wants to own. Schema validates. Hreflang is bidirectional. Canonicals point where they should. Sitemaps stay in sync with the actual indexable URL set.
Pre-deploy SEO checks
Before any major release. Staging crawl, redirect tests, schema validation, render checks. Catches the issues that would otherwise ship to prod and surface in a Sunday-morning Slack message.
How it works
Async-first. We share a Slack channel or email thread. I review crawls and logs on a regular cadence, and you flag releases as they come up. There's no weekly status meeting unless you want one.
One monthly call to align on priorities and to walk through anything that needs proper discussion. End-of-month note covering what shipped, what's open, and what's coming.
Engagements are typically 3-month minimum to start, then rolling. Most of the value compounds over time, so a one-month sprint usually doesn't make sense.
Who this is for
Fast-shipping product teams
Multiple deploys a week, lots of feature work, no in-house SEO. You need someone catching the SEO regressions before they ship.
Sites with technical surface
Marketplaces, large e-commerce, SaaS with marketing sites and apps, sites in the 50k+ URL range. There's enough going on that things actually need watching.
In-house teams that need a hand
You have an SEO lead but they need backup on the technical side. I plug into your existing process, not replace it.
Want technical SEO that ships?
Tell me about the site, the team, and your release cadence. I'll come back with a realistic scope and price.