Programmatic SEO service for content managers
A fixed-scope programmatic SEO build for content managers: we design the data contract against WordPress, ship 540 reviewed URLs in the first tranche, and hand you the templates, gates and runbook. Modelled at 1,860 indexed URLs earning roughly 208 MQLs a month at content managers' typical rates.
- Pilot
- from $4,200
- Build
- from $10,900
- Scale
- from $22,700
189–540 URLs
3,000 URLs
12,000+ URLs
The build, not the theory
Content managers get squeezed from both ends: leadership wants coverage numbers, and the brand team wants every page to read like it was written by a human who cares. The resolution is not more freelancers. It is splitting the roadmap into pattern work — pages whose value comes from data being correct and complete — and narrative work, where a writer's judgement is the product. We build the pattern side and give your team the QC surface to govern it. That is the strategy. This page is the service: what we actually do, in what order, at what price, and the conditions under which we tell you not to buy it. Every engagement starts by pointing at one real system you already run — usually WordPress, sometimes Notion — and asking whether its rows can answer a query shape better than a human writing prose. If the answer is no, the engagement stops at the audit and you keep the findings. If the answer is yes, we write the data contract, design one template family against real rows, publish a gated first tranche, and only widen the axis after Search Console proves the pattern indexes. Nothing about this is a retainer: the engine installs on your WordPress, and the MQL path is wired into your funnel, not ours.
- WordPress
- Notion
- Airtable
- Grammarly Business
- Figma
- Slack
- Google Analytics 4
In-house content teams where brand standards are enforced and pages carry real bylines.
Four phases, each with something shipped at the end
Roadmap triage
Every planned page is scored: does its value come from data completeness or from human judgement? The split usually surprises people — roughly 70/30 toward pattern.
Classified roadmap with owner per stream.
- A written data contract mapping WordPress fields to every rendered block, with null-handling rules per field.
- One production template family with 12 blocks, of which 3 vary per row beyond string substitution.
- 540 published URLs with schema, internal links, sitemap entries and IndexNow pings.
- An index-eligibility gate that refuses to publish rows below your evidence threshold.
- Search Console cohort reporting split by template family, not by page.
- A refresh job that rewrites stale rows on a 35-day cycle.
- A content managers-specific runbook: how to add an axis, how to kill one, how to roll back a bad batch.
- Handover session with Notion and Airtable wired into the reporting loop.
- WordPress export or API accessRequired
The rows are the product. Without them there is no page family, only prose.
- One named approverRequired
A single person who can sign off a template without a committee round.
- WordPress admin or stagingRequired
We generate into your environment; we do not host your pages.
- A working MQL pathPreferred
Each page hands the visitor to a real MQL flow — form, checkout, booking or trial.
- Search Console property accessPreferred
Cohort-level indexation data is how we decide what widens and what gets cut.
- Review capacity: one page per family, per batchPreferred
A human signs the sample before the batch publishes. That is the scaled-content defence.
Quote and payback estimator
Defaults are this seat's modelled economics. Move them to your own numbers — the build estimate and payback window recalculate live. It is a model, not a quote; the fixed proposal comes after the scoping call.
- Indexed URLs (62% gate)
- 744
- Clicks / month
- 5,208
- MQLs / month
- 83
- Pipeline value / month
- $21,580
- Indicative build
- $3,100
- Payback
- <1 month
The 62% index rate is the conservative figure we plan against, not a promise. Batches that gate harder index higher.
Three ways to buy this build
Pilot
from $4,200
189–540 URLs
Proving the roadmap honestly axis exists before you fund a build.
- Data audit + contract
- One template family
- Gated first tranche
- Indexation read at day 30
Build
Most boughtfrom $10,900
3,000 URLs
Content Managers with a proven dataset and a live MQL funnel.
- Everything in Pilot
- 4 template families
- Schema + internal link graph
- Refresh job + rollback
- Runbook handover
Scale
from $22,700
12,000+ URLs
Multi-axis surfaces where one bad batch would be expensive to unwind.
- Everything in Build
- Multi-axis expansion plan
- Release drip + quota control
- Quarterly axis pruning
- Named delivery lead
The shape of the surface before a single page is written
/content-managers/Hub. Human-written, links every axis, never generated.
/content-managers/{roadmap}/Primary axis — one page per WordPress row that clears the gate.
/content-managers/{roadmap}/{modifier}/Second axis. Only published where the pair has its own evidence.
/content-managers/compare/{a}-vs-{b}/Comparison family. Capped at pairs with real query volume.
/content-managers/updates/Change log for the dataset — freshness signal, not filler.
Rules that decide whether a row earns a URL
| Gate | Test | If it fails |
|---|---|---|
| Row completeness | ≥ 85% of contract fields present | Below threshold the row renders as a directory entry, not a URL. |
| Evidence density | ≥ 2 unique data points not shared with a sibling row | Fails → folded into the parent page as a section. |
| Demand | A measurable query shape in Search Console, Semrush or paid data | No demand → the axis is dropped before templates are written. |
| MQL path | A working MQL destination for the row | Missing → the page publishes noindex until the path exists. |
| Human sample | One page per family per batch reviewed and signed | Unsigned batches do not leave staging. |
What the first weeks look like
- Week 1
Scoping call and data review
We look at what content managers already hold — systems, exports, APIs — and score each axis for demand and defensibility.
- Week 2
Contract and template design
The data contract is written and the first template is designed against real rows, not placeholders.
- Weeks 3–5
First tranche live
450–1,050 URLs published with schema, internal links, sitemap entries and IndexNow.
- Weeks 6–9
Read, widen, hand over
Indexation and impression data decides what widens and what gets cut. Templates, gates and runbook transfer to you.
Three editors governing 6,800 URLs
- Setup
- An in-house team of three publishing 14 pieces a month against a roadmap of 400.
- Mechanism
- We classified 71% of the roadmap as pattern work, encoded the style guide into two templates, and moved editors from writing to sampled review with data-triggered refresh.
- Result
- 6,800 governed URLs at the same headcount, with editors spending 4 hours a week on QC rather than 40 on production.
Cases where we will not take the build
- Your WordPress data has fewer than 200 usable rows — a hand-written hub will outperform a thin page family.
- The query shape is dominated by one brand's own properties and no third party ranks on page one.
- There is no MQL destination, so the pages would earn traffic you cannot bank.
- You want volume as the goal. We size to evidence, and evidence usually caps the count lower than you hoped.
Buy the whole build, or one piece of it
Editorial pipelines
A two-stream pipeline where pattern pages and narrative pages have different rules, owners and SLAs.
Scope this workstreamE-E-A-T checks at scale
How to keep experience, expertise, authority and trust signals real across thousands of pages.
Scope this workstreamTeam collaboration
Getting writers, SEOs, designers, legal and subject experts through the same pipeline without deadlock.
Scope this workstreamBuying questions content managers ask us
Pilot engagements start at $4,200 and cover the audit, contract, one template family and a gated first tranche. A full build for the 3,000-URL surface starts at $10,900. Pricing is fixed at proposal — we do not bill by page or by hour.
Other seats we scope builds for
Want the content managers surface scoped before you build it?
We'll audit the data source, size the first batch, set the performance budget and tell you honestly if programmatic is the wrong tool for your category.
