Skip to content

SEO that starts in code

The SEO I care about isn’t “write more content.” It’s making the site understandable to crawlers and people: architecture, rendering, performance, accessibility, structured data—on the stack you actually use.

I work on WordPress/Sage, and also on React, Next.js, headless, and APIs: the constraint is the same (useful HTML, clean routing, CWV, schema). Only where we touch the code changes.

Three engagement levels

Not a fixed price list: three ways of working, chosen by budget and how much you want me in the codebase vs. your team.

Low budget

Audit + roadmap

Technical diagnosis on your current stack (crawl, indexing, CSR/SSR/SSG rendering, CWV, schema, a11y). Deliverable: clear fix priorities, ticket-ready for the team. I don’t rewrite the product—I tell you what to do first and why.

  • Crawl / Search Console / sitemap / canonical / hreflang
  • Rendering and content invisible to Google
  • CWV and performance budgets
  • Schema and semantic markup: gaps and risks

Med budget

Audit + critical fixes

Same as low, plus hands-on implementation of high-impact blocks in the codebase: meta/routing, JSON-LD, HTML templates, critical assets, CWV fixes. WordPress, Next.js, React, or hybrid—where the patch is needed, I ship it or pair with the team.

  • Everything in Low
  • Priority fixes implemented (PR / patch)
  • Structured data and SEO head aligned to the product
  • Post-deploy checks (index, CWV, rich results)

High budget

Structural SEO in the product

Technical partnership: information architecture, content model, rendering strategy, accessibility, and ongoing measurement. Ideal when you’re rebuilding or scaling a product—not a one-off audit, but SEO as an engineering constraint.

  • Everything in Med, on a continuous cycle
  • URL architecture, i18n, faceted / app routes
  • Pairing with frontend/backend on the design system
  • Guardrails: SEO/a11y CI checks, performance budgets

Stack

Next.js / React, WordPress (Sage, headless, classic), APIs and integrations. If the crawler can’t see what the user sees, it’s a technical problem—regardless of framework.

For whom

Product teams, agencies, and founders who want someone who can talk to engineers and Search Console watchers alike—without translating everything into empty marketing.

Tell me about the project