Technical SEO + editorial automation
SEO & Content Architecture
SEO engagements I take on combine the technical side (crawlability, indexation, site architecture, Core Web Vitals, structured data) with the editorial and programmatic side (topic clusters, page templates, and scale systems). Grounded in production work — not a template playbook.
500K+
Pages in largest programmatic architecture
2
Editorial automation systems shipped
pgvector
PostgreSQL for SEO scale
CI-gated
Regression checks
How I actually run this
Most SEO engagements I take on have a technical layer underneath: broken crawl paths, unfocused site architecture, structured data that does not validate, or pages that fail Core Web Vitals. I fix that first because it is cheap and compounds. From there the work splits between editorial content (topic cluster design, content briefs, internal linking) and programmatic content (template architecture, hierarchical ontologies, and the infrastructure to generate and maintain pages at volume without generating slop).
For editorial work I draw on the Content Mint pipeline patterns. For programmatic work I draw on the AskNimble architecture — a 500K-page information hierarchy built to serve real search intent at scale. The deliverables are specific to the site. I do not run a template playbook.
What's included
- Technical audit and fixes
- Crawlability, indexation, site architecture, structured data, and Core Web Vitals audited and fixed — with before-and-after measurement and regression checks in CI.
- Content architecture
- Topic cluster design, internal linking strategy, and content priority scoring grounded in real keyword data and intent — not a generic template.
- Programmatic design
- For sites with scale ambitions, a hierarchical information architecture and page template design that can generate targeted pages without degrading quality.
- Structured data system
- JSON-LD schema applied consistently across pages — Organization, Article, FAQ, Breadcrumb, Service — validated at build time and wired into sitemaps.
- Editorial pipeline
- Draw on the Content Mint pattern: orchestrated drafts, quality analysis, human review, and publication — so SEO content has a standard, not just a volume target.
How it works
Audit, fix, architect, build, measure. Every phase produces a concrete artifact the team can operate from.
- 1AuditCrawl the site, map the existing content, identify technical blockers and content gaps. Write up priorities.
- 2FixFix the technical layer first — it is cheap and it compounds. Sitemaps, structured data, Core Web Vitals, broken crawl paths.
- 3ArchitectDesign the content architecture: topic clusters, internal linking, page templates, and the hierarchy that holds them together.
- 4BuildWrite, automate, or orchestrate the content. Editorial, programmatic, or hybrid — whichever the site actually needs.
- 5MeasureTrack index coverage, organic traffic, rankings, and conversion. Wire regression checks into CI so future shipping does not break SEO.
Frequently asked questions
- Where does technical SEO stop and content SEO start?
- Technical SEO covers how the site gets crawled, indexed, and rendered — site architecture, Core Web Vitals, structured data, internal linking, and status codes. Content SEO covers what is on the page once it loads — topic coverage, intent matching, editorial quality, and internal linking again. The two are inseparable in practice: most SEO engagements I take on have a technical layer underneath a content problem, or the other way around. I work on both.
- Do you do programmatic SEO?
- Yes. I architected the 500K+ page programmatic SEO layer at AskNimble, which uses a hierarchical ontology (jobs → capabilities → tools → SKUs) to generate targeted pages at volume. The key is designing the template architecture and information hierarchy up front so pages are useful rather than filler. Programmatic done wrong is slop at scale. Programmatic done right compounds.
- How do you measure SEO success?
- For editorial content — organic traffic to target pages, keyword rankings for target queries, and conversion rates from organic sessions. For programmatic content — index coverage, long-tail capture, and whether the templates are actually earning their keep in search. For technical work — Core Web Vitals field data, crawl stats, and regression checks in CI so shipping does not quietly break the site.
- How does SEO fit with AI and content automation?
- Editorial automation (Claude-orchestrated pipelines) and programmatic SEO (template-driven page generation) are the same shape of problem from different angles. Both require an information architecture, both require a quality bar, and both require review. I run Content Mint — a multi-brand editorial automation system — and the patterns transfer directly to client SEO work. The goal is content that compounds, not content that dilutes.
Pair with
Want SEO work grounded in real operational experience?
Book a discovery call and I'll walk through a technical audit on your site with you.
Scope an SEO engagement