Programmatic SEO service for product managers
A fixed-scope programmatic SEO build for product managers: we design the data contract against Linear / Jira, ship 900 reviewed URLs in the first tranche, and hand you the templates, gates and runbook. Modelled at 3,100 indexed URLs earning roughly 391 activated users a month at product managers' typical rates.
- Pilot
- from $3,600
- Build
- from $9,400
- Scale
- from $19,400
315–900 URLs
5,000 URLs
20,000+ URLs
The build, not the theory
Content that scales stops being marketing and becomes a product surface — with a data model, templates that behave like components, and users who arrive with a job to be done. PMs are the right owners for this, and the tooling should give them what any product surface gives: discovery inputs, instrumentation, cohort analysis and an honest way to retire what does not work. 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 Linear / Jira, sometimes Amplitude — 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 activated user path is wired into your funnel, not ours.
- Linear / Jira
- Amplitude
- PostHog
- Dovetail
- Figma
- Maze
- Google Search Console
Product-owned content surfaces where conversion means an in-product activation event.
Four phases, each with something shipped at the end
Jobs and evidence
Query data, tickets, sales calls and recordings synthesised into job statements with evidence counts attached to each.
Job map with evidence weighting.
- A written data contract mapping Linear / Jira fields to every rendered block, with null-handling rules per field.
- One production template family with 10 blocks, of which 5 vary per row beyond string substitution.
- 900 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 product managers-specific runbook: how to add an axis, how to kill one, how to roll back a bad batch.
- Handover session with Amplitude and PostHog wired into the reporting loop.
- Linear / Jira 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 activated user pathPreferred
Each page hands the visitor to a real activated user 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)
- 1,240
- Clicks / month
- 8,680
- activated users / month
- 156
- Pipeline value / month
- $59,280
- Indicative build
- $4,000
- 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 $3,600
315–900 URLs
Proving the real discovery axis exists before you fund a build.
- Data audit + contract
- One template family
- Gated first tranche
- Indexation read at day 30
Build
Most boughtfrom $9,400
5,000 URLs
Product Managers with a proven dataset and a live activated user funnel.
- Everything in Pilot
- 3 template families
- Schema + internal link graph
- Refresh job + rollback
- Runbook handover
Scale
from $19,400
20,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
/product-managers/Hub. Human-written, links every axis, never generated.
/product-managers/{real}/Primary axis — one page per Linear / Jira row that clears the gate.
/product-managers/{real}/{modifier}/Second axis. Only published where the pair has its own evidence.
/product-managers/compare/{a}-vs-{b}/Comparison family. Capped at pairs with real query volume.
/product-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 | ≥ 65% of contract fields present | Below threshold the row renders as a directory entry, not a URL. |
| Evidence density | ≥ 4 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. |
| activated user path | A working activated user 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 product 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
750–1,750 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 families shipped, one sunset on schedule
- Setup
- A PM owning a content surface with eleven page families and no performance visibility.
- Mechanism
- Every family was given a hypothesis, a metric and a review date retroactively; instrumentation was added per template and reviewed quarterly.
- Result
- Three families were widened, one was consolidated into a parent hub, and the surface shrank 18% while conversions rose 24%.
Cases where we will not take the build
- Your Linear / Jira data has fewer than 220 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 activated user 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
Buying questions product managers ask us
Pilot engagements start at $3,600 and cover the audit, contract, one template family and a gated first tranche. A full build for the 5,000-URL surface starts at $9,400. Pricing is fixed at proposal — we do not bill by page or by hour.
Other seats we scope builds for
Want the product 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.
