Evaluate a publishing layer the way you would evaluate any vendor: blast radius, exit cost, on-call load
The marketing team wants 40,000 pages. You want to know what that does to your infrastructure, your security posture and your team's pager.
- Blast radius
- Batch-scoped
- Rollback
- Tested quarterly
- Data egress
- Scoped & logged
- Exit cost
- Near zero
A failed run affects its batch, not the site.
Snapshot per job, restore drill documented.
Read-only credentials, enumerated fields.
Content persists as native posts.
Modelled at current defaults: 15,500 indexed URLs → 853 qualified opportunitys per month.
What actually hurts in this seat
A content publishing decision becomes an engineering decision the moment it touches your infrastructure. The questions that matter are not feature comparisons: what is the blast radius of a bad generation run, who is on call when it fails, what data leaves your perimeter, what does the exit look like, and what would building this in-house actually cost over three years. We answer those in writing before you commit.
Marketing tooling arriving through a credit card and becoming your on-call problem.
Vendors who cannot answer basic questions about data residency or access scope.
Build-vs-buy debates settled by opinion because nobody costed the alternative.
The four jobs this engagement owns
Contain the blast radius
Generation runs in batched workers with checkpoints, capability-scoped access, staging-first workflow and a rollback that has been tested rather than assumed.
Define the data boundary
Exactly what data is read, where it is processed, what is retained and for how long — documented and enforced by scoped credentials.
Cost the alternative honestly
A three-year TCO model for building the same capability in-house, including the maintenance nobody puts in the original estimate.
Plan the exit
Content stays in your database as normal posts. If you remove the layer tomorrow, the pages still render and the templates are yours.
Four stages, each with a named output
Architecture review
How generation executes, where it runs, what it writes and how it degrades. Includes load characteristics at your target URL count.
Architecture document + load profile.
CTOs workstreams
Hosting, scaling & DevOps
What a 10k, 100k and 1M URL site actually needs from infrastructure — and where the cliffs are.
OpenAudit, compliance & access
The security artefacts a review board needs before content tooling touches your stack.
OpenWhy WBP vs building in-house
A three-year TCO comparison you can take to a build-vs-buy discussion, including the case for building.
OpenQuery 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 25,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
Enterprise builds where marketing owns the outcome and engineering owns the platform. Indexation is held at a conservative 62%.
- Indexed URLs
- 15,500
- Monthly organic clicks
- 77,500
- qualified opportunitys per month
- 853
- Modelled monthly value
- $1,194,200
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.
A rollback drill that actually restored
- Setup
- An enterprise team requiring a tested restore path before approving any content-generation tooling.
- Mechanism
- Failure injection mid-batch on a 40,000-row staging run, then a full rollback from job snapshots with a row-level diff against the pre-run state.
- Result
- Restore completed in 11 minutes with zero divergent rows; the drill became a quarterly requirement in their runbook.
How ctos usually solve this — and what changes
| Dimension | The usual approach | With WpBulkPublishing |
|---|---|---|
| Build in-house | 2–4 engineer-quarters plus perpetual maintenance | Weeks to a pilot, maintenance externalised |
| Failure mode | Whatever the intern shipped | Checkpointed batches with tested rollback |
| Access | Shared admin account | Capability-scoped, enumerated, logged |
| Exit | Rewrite the CMS layer | Deactivate; content persists natively |
What the first weeks look like
- Week 1
Scoping call and data review
We look at what ctos already hold — systems, exports, APIs — and score each axis for demand and defensibility.
- Weeks 3–4
Contract and template design
The data contract is written and the first template is designed against real rows, not placeholders.
- Weeks 5–8
First tranche live
3,750–8,750 URLs published with schema, internal links, sitemap entries and IndexNow.
- Weeks 9–14
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
Sometimes you should — if generation is core to your product. If it is marketing infrastructure, the three-year TCO model usually favours buying, and we will show you the model either way.
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 build
Your 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 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 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 buildWhen pages are generated from data, page families behave like features. They deserve the same discovery, the same metrics and the same willingness to sunset.
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 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 buildWhen pages are generated from data, page families behave like features. They deserve the same discovery, the same metrics and the same willingness to sunset.
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 ctos 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.
