Find out whether search is a real channel for you before you spend a year on it
The honest answer for some startups is no. A validation tranche tells you in eight weeks rather than after four quarterly board decks.
- Test window
- 8–10 weeks
- Tranche size
- 200–500 URLs
- Pass threshold
- Pre-agreed
- Sunk cost
- One tranche
From ship to a defensible expand/stop decision.
Smallest set that produces a readable signal.
Written into the SOW before generation starts.
Not a year of writer retainers.
Modelled at current defaults: 217 indexed URLs → 42 signups per month.
What actually hurts in this seat
Early-stage teams are told content is a long game and take it as licence to avoid measurement. It is a long game to compound, not a long game to test. A minimum viable content strategy targets the narrowest slice of demand your product genuinely serves, ships enough URLs to read a signal, and defines in advance what result would justify a bigger bet — and what result would mean stopping.
Every advisor gives contradictory channel advice and none of it comes with a test design.
The board wants a growth story; you want to know if the channel is real.
Runway makes an 18-month content bet irresponsible.
The four jobs this engagement owns
Design the validation test
One narrow query family, a defined tranche size, a fixed observation window and pre-agreed pass/fail thresholds — written before anything ships.
Ship the MVP surface
The smallest page family that can prove demand exists and that your product converts it, built to production standards so it is not throwaway.
Read the signal properly
Indexation rate, impression breadth, query relevance and conversion, separated so a weak result tells you which part failed.
Make the call
Expand, adjust the axis, or stop. Stopping with evidence at week eight is a good outcome and we will recommend it when the data says so.
Four stages, each with a named output
Hypothesis
Which specific query family should convert for this product, why, and what result would falsify that? If we cannot state a falsifiable hypothesis, we do not start.
Written hypothesis with pass/fail thresholds.
Startup Founders workstreams
Minimum viable content strategy
The smallest content surface that can prove or disprove search as a channel for your product.
OpenContent-led growth
What expansion looks like after a validation tranche passes — and the order of operations that keeps it compounding.
OpenContent in the funding story
How to present an organic channel to investors without overstating it — and what diligence will actually check.
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 350-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
Validation tranches at pre-seed and seed, where conversion is trial signup rather than revenue. Indexation is held at a conservative 62%.
- Indexed URLs
- 217
- Monthly organic clicks
- 1,736
- signups per month
- 42
- Modelled monthly value
- $13,020
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 test that said stop — and saved two quarters
- Setup
- A dev-tools startup convinced that integration pages would drive signups.
- Mechanism
- A 300-URL tranche with pre-agreed thresholds: 50% indexation and 40 relevant-query impressions per week by week eight.
- Result
- Indexation hit 71% but relevant impressions stalled at nine per week — the demand was not there. The team redirected two quarters of planned spend into partnerships instead.
How startup founders usually solve this — and what changes
| Dimension | The usual approach | With WpBulkPublishing |
|---|---|---|
| Commitment | 12-month content retainer | One instrumented tranche |
| Success definition | Decided afterwards | Written before launch |
| Failure handling | Keep going and hope | Documented stop recommendation |
| Reusability | Blog posts | A production template you keep either way |
What the first weeks look like
- Week 1
Scoping call and data review
We look at what startup founders 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
53–122 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
It is short for revenue, not for signal. Indexation rate and query relevance are readable early; we only judge conversion once impressions exist.
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 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 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 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 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 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 startup founders 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.
