Treat the content surface as a product: roadmap, instrumentation, user research and a kill process
When pages are generated from data, page families behave like features. They deserve the same discovery, the same metrics and the same willingness to sunset.
- Family artefacts
- 4 required
- Instrumentation
- Per template
- Review cadence
- Quarterly
- Sunset process
- Documented
Hypothesis, metric, owner, review date.
Events defined before the family ships.
Every family reviewed or explicitly deferred.
Consolidate, redirect, record the learning.
Modelled at current defaults: 3,100 indexed URLs → 391 activated users per month.
What actually hurts in this seat
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.
Content decisions made on opinion because there is no research input.
No instrumentation on generated pages, so nobody can tell which template is failing.
Nothing ever gets sunset, so the surface accumulates dead weight.
The four jobs this engagement owns
Run real discovery
Search demand, support tickets, sales objections and session recordings synthesised into the jobs each page family must serve.
Roadmap page families like features
Each family gets a hypothesis, a success metric, an owner and a review date — the same artefacts a feature would get.
Instrument properly
Per-template events, scroll and interaction depth, on-page search, and conversion by intent tier, all segmented by family.
Sunset without drama
A documented retirement process: consolidate, redirect, preserve equity, and record what was learned.
Four stages, each with a named output
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.
Product Managers workstreams
Query shapes this surface answers
These are patterns, not a keyword list. Each one multiplies against the entities in your own dataset — which is where a 5,000-URL first batch comes from.
Are you ready to build this?
Not yet. Fix the unchecked items first; publishing now would create pages we would later consolidate.
Size it with your own numbers
Product-owned content surfaces where conversion means an in-product activation event. Indexation is held at a conservative 62%.
- Indexed URLs
- 3,100
- Monthly organic clicks
- 21,700
- activated users per month
- 391
- Modelled monthly value
- $148,580
A model, not a forecast. Move the sliders to your own conversion economics — we will run the same maths against your data on the call.
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%.
How product managers usually solve this — and what changes
| Dimension | The usual approach | With WpBulkPublishing |
|---|---|---|
| Decision basis | Opinion and precedent | Evidence-weighted job map |
| Instrumentation | Retrofitted | Defined in the family spec |
| Underperformers | Left running forever | Reviewed quarterly, sunset cleanly |
| Ownership | Diffuse | Named per family |
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.
Questions we get asked in this seat
When it is generated from a data model and serves a job to be done, the artefacts that make a product succeed are the same ones that make the surface succeed.
Every seat we build for
Each role gets its own data reality, its own template families and its own definition of a good outcome. Pick the seat you sit in.
You do not have a content team. You have a spreadsheet, a product and limited runway. That is enough to publish a few thousand pages that answer real searches.
See the build
You know the query shapes, the entity model and the internal-link plan. What you do not have is a publishing layer that will do it at 40,000 URLs without breaking canonicals.
See the build
The bottleneck in an agency is never the pitch. It is fulfilment cost per client and the senior hours that disappear into repeatable work.
See the buildYour team can produce 12 excellent pieces a month. The keyword plan needs 400. Programmatic covers the pattern work so your writers cover the judgement work.
See the build
You are the one who gets paged when a bulk job locks the database at 2am. So the generation layer needs to be queue-based, idempotent and inspectable.
See the build
The affiliate sites that got hit had one thing in common: pages that existed to hold a link, not to answer a comparison.
See the buildVolume is not your problem. Consistency of markup, byline integrity, archive structure and crawl efficiency across 100,000 URLs is.
See the buildA 12,000-product catalogue is already a programmatic dataset. The question is which slices deserve a URL and which quietly cannibalise the ones that convert.
See the buildThe honest answer for some startups is no. A validation tranche tells you in eight weeks rather than after four quarterly board decks.
See the buildYour product already generates the data these pages need: features, integrations, permissions, limits, changelogs and docs. Most SaaS companies never publish any of it as a page family.
See the buildThe marketing team wants 40,000 pages. You want to know what that does to your infrastructure, your security posture and your team's pager.
See the buildThe board question is never 'how many pages'. It is what this channel returns, when, and what happens to it if you cut headcount.
See the buildEverything upstream of a generated page is a dataset question: fill rates, drift, entity resolution and provenance. That is your domain, not marketing's.
See the build
Listings churn weekly. Neighbourhood, school-catchment, commute and price-trend pages do not — and they are what people search before they search a property.
See the build
In YMYL, an unreviewed page is not a small risk. The architecture has to make clinical sign-off a gate, not a nice-to-have.
See the buildLegal content dies in approval, not production. Build the review path into the template and the volume problem solves itself.
See the buildIn finance, a stale number is a compliance incident. Freshness is not an SEO tactic here — it is the product.
See the buildApplicants compare entry requirements, fees, duration, delivery mode and outcomes. Most education sites publish prose about campus life instead.
See the build
Travel search is the most seasonal, most comparison-driven category there is — and the most punishing to generic destination prose.
See the build
Fourteen locations does not mean fourteen copies of one page with the town name swapped. That is the exact pattern that gets filtered.
See the buildYou do not have a content team. You have a spreadsheet, a product and limited runway. That is enough to publish a few thousand pages that answer real searches.
See the buildYou know the query shapes, the entity model and the internal-link plan. What you do not have is a publishing layer that will do it at 40,000 URLs without breaking canonicals.
See the buildThe bottleneck in an agency is never the pitch. It is fulfilment cost per client and the senior hours that disappear into repeatable work.
See the buildYour team can produce 12 excellent pieces a month. The keyword plan needs 400. Programmatic covers the pattern work so your writers cover the judgement work.
See the buildYou are the one who gets paged when a bulk job locks the database at 2am. So the generation layer needs to be queue-based, idempotent and inspectable.
See the buildThe affiliate sites that got hit had one thing in common: pages that existed to hold a link, not to answer a comparison.
See the buildVolume is not your problem. Consistency of markup, byline integrity, archive structure and crawl efficiency across 100,000 URLs is.
See the buildA 12,000-product catalogue is already a programmatic dataset. The question is which slices deserve a URL and which quietly cannibalise the ones that convert.
See the buildThe honest answer for some startups is no. A validation tranche tells you in eight weeks rather than after four quarterly board decks.
See the buildYour product already generates the data these pages need: features, integrations, permissions, limits, changelogs and docs. Most SaaS companies never publish any of it as a page family.
See the buildThe marketing team wants 40,000 pages. You want to know what that does to your infrastructure, your security posture and your team's pager.
See the buildThe board question is never 'how many pages'. It is what this channel returns, when, and what happens to it if you cut headcount.
See the buildEverything upstream of a generated page is a dataset question: fill rates, drift, entity resolution and provenance. That is your domain, not marketing's.
See the buildListings churn weekly. Neighbourhood, school-catchment, commute and price-trend pages do not — and they are what people search before they search a property.
See the buildIn YMYL, an unreviewed page is not a small risk. The architecture has to make clinical sign-off a gate, not a nice-to-have.
See the buildLegal content dies in approval, not production. Build the review path into the template and the volume problem solves itself.
See the buildIn finance, a stale number is a compliance incident. Freshness is not an SEO tactic here — it is the product.
See the buildApplicants compare entry requirements, fees, duration, delivery mode and outcomes. Most education sites publish prose about campus life instead.
See the buildTravel search is the most seasonal, most comparison-driven category there is — and the most punishing to generic destination prose.
See the buildFourteen locations does not mean fourteen copies of one page with the town name swapped. That is the exact pattern that gets filtered.
See the buildWant this scoped for product managers before you commit?
We audit your data, size the first batch, model the economics and tell you honestly when programmatic is the wrong tool for the job.
