Not “write more content”: make the product understandable to crawlers and people — architecture, rendering, performance, accessibility, schema — on the stack you actually use, with content delivered wherever it needs to go via APIs.
Technical diagnosis on your current stack (crawl, indexing, CSR/SSR/SSG rendering, CWV, schema, a11y). Ticket-ready priorities for the team.
Same as low, plus high-impact implementation in the codebase: meta/routing, JSON-LD, HTML templates, critical assets, CWV fixes — Next, React, or WordPress.
Everything in Low
Priority fixes implemented (PR / patch)
Structured data and SEO head aligned to the product
Post-deploy checks (index, CWV, rich results)
Technical partnership: IA, content model, rendering strategy, a11y, and ongoing measurement. 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