The problem this solves
Programmatic SEO looks simple from the outside: pick a pattern like "[industry] marketing agency", generate a page per variation, collect the long tail. In practice the design work is where these projects live or die. Which variations have real demand? Which intents are actually distinct, and which would produce fifty near-duplicate pages that cannibalize each other and read as thin? What fields does the template need so every page says something specific? Skipping those questions produces the sprawling, indexation-poisoning page sets that gave the tactic its bad name.
The design work stays undone because it sits awkwardly between roles. It needs keyword analysis at scale, editorial judgment about intent boundaries, and an engineering-ready specification at the end - so it bounces between SEO, content, and dev until it quietly dies in a planning doc. Meanwhile competitors with a disciplined matrix collect hundreds of qualified long-tail visits a month from pages that took a template and a dataset to build.
How the mission runs
- Pull the full keyword universe for the pattern. Keyword Intelligence expands your pattern into every variation with measurable demand: industries, modifiers, and adjacent phrasings. Instead of guessing which twenty pages to build, you start from the complete demand map with volume attached to every candidate.
- Dedupe intents ruthlessly. The agent collapses variations that share an intent into single pages and flags near-duplicates that would compete with each other. This is the step that separates a durable programmatic set from a thin-content liability - every surviving page has an intent it uniquely owns.
- Define the template fields. For the surviving page set, the mission specifies what the template must contain: which fields vary per page, what data fills them, and what each page needs to say to be genuinely useful rather than a find-and-replace of its siblings.
- Deliver the page list in Sheets. The full matrix lands in Google Sheets: one row per page with slug, target query, volume, intent, and the per-page field values. It is the working inventory your team builds from, filters, and tracks as pages ship.
- Write the build brief in Docs. A companion Google Doc explains the matrix to whoever builds it: the template structure, the field definitions, internal linking rules between pages, and the rollout order. An engineer or CMS operator can start from the brief without reconstructing the reasoning.
The prompt
This is the exact objective the agent receives. Swap the obvious placeholders for your own domain, segment or channel and run it as-is from the console, Slack, or the API.
What comes back
A Google Sheet holding the complete page matrix - every page as a row with its slug, target query, demand numbers, and template field values - paired with a Google Doc build brief covering template structure, linking rules, and rollout sequence. Together they turn a programmatic idea into a specification your team can hand to a developer and start shipping against.
Make it yours
- Change the pattern: run it for "[tool] integration" or "[city] plus your service" pages, and the same matrix discipline applies to the new axis.
- Cap the set: restrict the matrix to variations above a demand threshold so the first release is small, strong, and easy to evaluate.
- Ask for a second axis: cross industry with use case and let the dedupe step decide which combinations deserve standalone pages.
Frequently asked questions
Will this create hundreds of thin pages?
The matrix is designed to prevent exactly that. Intent deduplication removes variations that cannot stand alone, and the template fields force every page to carry specific, differentiated content. The Sheet shows you the full set before anything is built, so scale is a decision you make with the evidence in front of you.
Does the mission build the pages too?
This playbook delivers the design: the matrix and the brief. Building is a separate step because most teams route programmatic templates through their own CMS or dev workflow. Once the matrix is approved, a follow-up mission can generate the per-page content into your CMS as drafts.
How do I judge whether the matrix is worth building?
The Sheet carries demand data per page, so you can total the realistic opportunity before committing engineering time. Many teams greenlight a pilot slice - the top rows by volume - measure how those pages perform, and then release the rest of the matrix in waves.