Make every SKU, collection and filter combination earn its place in the index
A 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.
- Facet URLs
- Policy-controlled
- Product uniqueness
- 8+ own facts
- Lifecycle
- Automated
- Crawl waste
- −50% typical
Only combinations with real demand become indexable.
Minimum before a PDP is allowed into the index.
Out-of-stock and discontinued handled by rule.
After facet and search-page policy is applied.
Modelled at current defaults: 1,922 indexed URLs → 511 orders per month.
What actually hurts in this seat
Catalogue SEO fails in two directions at once: thousands of product URLs with nothing but a supplier description, and thousands of faceted URLs competing with the collection page that actually converts. The fix is a single index policy — which attribute combinations get a crawlable, indexable, internally linked URL, which get canonicalised into a parent, and which are blocked outright — applied consistently across the whole catalogue.
Faceted navigation generating six-figure URL counts nobody planned.
Product descriptions supplied by the manufacturer and shared with 40 competitors.
Seasonal collections that 404 in January and take their backlinks with them.
The four jobs this engagement owns
Write the index policy
One documented rule set covering products, collections, facets, search pages and out-of-stock states — then enforced by the platform, not by memory.
Differentiate product pages
Sizing data, compatibility, materials, delivery windows by region, review summaries and comparison blocks generated from your own data, not the supplier feed.
Build collections that rank
Attribute-based collection pages with buying-guide blocks, filtering logic and genuine editorial intent for the ones with real demand.
Handle lifecycle properly
Discontinued, seasonal and out-of-stock products routed to redirects, parent collections or retained pages depending on link equity and demand.
Four stages, each with a named output
Catalogue and crawl audit
Full crawl mapped against the product database: how many URLs exist, how many are indexable, how many have unique content, how many are facet artefacts.
URL inventory with an indexability verdict per class.
eCommerce Managers workstreams
Bulk product SEO
Making 12,000 product pages individually worth indexing without writing 12,000 descriptions.
OpenCollection page optimisation
Turning collection pages into the highest-converting, highest-ranking layer of the store.
OpenCommerce integrations
Wiring product, review, inventory and merchandising systems into the publishing layer.
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 3,100-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
Catalogue builds where product data is enriched beyond the supplier feed. Indexation is held at a conservative 62%.
- Indexed URLs
- 1,922
- Monthly organic clicks
- 26,908
- orders per month
- 511
- Modelled monthly value
- $39,858
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.
184,000 facet URLs cut to 3,100 indexable
- Setup
- A WooCommerce store where filter combinations had generated a six-figure crawlable URL count.
- Mechanism
- Demand analysis on every facet combination, an index policy allowing only combinations with measurable search volume plus a differentiating block, and robots/canonical enforcement on the rest.
- Result
- Indexable set reduced to 3,100 intentional URLs; crawl requests to revenue pages rose 46% within two months.
How ecommerce managers usually solve this — and what changes
| Dimension | The usual approach | With WpBulkPublishing |
|---|---|---|
| Facets | Crawlable by accident | Indexable only with demand evidence |
| Product copy | Supplier feed | Own attributes, sizing, compatibility, reviews |
| Out of stock | 404 or an empty page | Rule-based retain, redirect or parent |
| Collections | Auto-generated shells | Editorial blocks where demand justifies them |
What the first weeks look like
- Week 1
Scoping call and data review
We look at what ecommerce 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
465–1,085 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
Only if the cut URLs had traffic. We cut on twelve months of impression data and redirect anything with links or history.
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 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 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 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 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 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 ecommerce 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.
