1. Fix & Implement
Most audits fail because the client’s developers are too busy to implement them. This removes that dependency. I don’t hand over recommendations—I write the fixes.
What I work on
- Core Web Vitals—LCP, INP, CLS, diagnosed to the specific cause rather than the score
- CDN and caching—configuration review, cache rules serving stale or uncached HTML
- Redirect hygiene—chains, loops, soft 404s, protocol, and trailing-slash inconsistency
- Rendering and hydration—content that exists for users but not for crawlers
- Crawl budget—faceted URLs, parameters, pagination logic
How I work with your team
Hands-on implementation on WordPress, where I go straight into the codebase. On other stacks—Next.js, Shopify, custom builds—I deliver ticket-ready developer specs instead: the file, the change, the reason, and the test. Your engineers merge faster than an outsider would, and nobody’s production environment gets touched by someone who didn’t build it.
Staging first, always. Every change is a documented, reviewable diff.
2. AI Search & AEO Readiness
Generative engines don’t rank pages. They assemble answers from sources they can parse, verify, and attribute. That’s a technical problem before it’s a content problem, and most sites fail it at the substrate.
What I build
- JSON-LD schema architecture—typed, nested, connected. Organization, product, FAQ page, article,
sameAsand@idrelationships that let a machine resolve who you are across sources. Not a plugin’s default output. - Entity optimization—stating unambiguously what the site is authoritative on, in a form a model can extract as a claim rather than infer from prose
- AI crawler rules—GPTBot, ClaudeBot, PerplexityBot, Google-Extended, CCBot. Explicit allow/disallow decisions, because most sites are either blocking them by accident or allowing everything by neglect.
- Knowledge graph validation—verifying the declared entity actually resolves and reconciling contradictions across third-party sources
- Citation baseline—where the site currently surfaces in AI answers for its core queries, and which competitor appears instead
3. Programmatic SEO
Database-driven page systems at scale. Hundreds or thousands of pages generated from a modeled data source, each genuinely useful rather than a template with a variable swapped in.
What I build
- Data modeling and entity structure—the part that determines whether this works or produces thin junk
- Template architecture with real per-page differentiation
- Database-to-CMS pipelines, including ongoing sync where source data changes
- Automated structured data generated from the underlying records
- Indexation control for dynamic subdirectories: thresholds, noindex logic, sitemap segmentation
- Internal linking logic that scales with page count instead of degrading with it
4. SEO Care Plans
Sites break every time a product team ships—usually in ways nobody notices for a quarter.
A template refactor drops canonical tags. A config merge inverts a robot’s rule. A new script pushes LCP past three seconds on mobile. A redesign removes the internal links carrying authority to revenue pages. None of it throws an error. Traffic just erodes, and by the time it shows up in a monthly report, the responsible deploy is eighty commits back.
What’s included
- 24/7 uptime and crawl monitoring, alerting on anomalies rather than thresholds
- Monthly technical regression testing across templates
- Pre-launch staging review before any significant deploy
- Index coverage and Search Console error monitoring, with triage
- Core Web Vitals field-data tracking, not lab scores
- Schema and structured data validation
- Monthly report, written for humans