Topic cluster map
Every pillar and its spokes laid out with the intent each page serves and how it links to the rest of the cluster.

SEO / Content strategy
Pillar and spoke clusters, editorial calendars tied to publishing capacity, and refresh cycles that stop content from decaying quietly for years.
Most content plans are a list of blog post ideas ranked by keyword volume. That produces a pile of disconnected articles that compete with each other, dilute topical authority, and go stale the moment a competitor publishes something more current. Content strategy, done properly, is architecture first and writing second. You decide the shape of the topic before you decide what to write about it.
The shape we use is pillar and spoke. A pillar page covers a broad topic completely enough to rank for its core term and to serve as the hub other pages link into. Spoke pages go narrow, answering the specific sub-questions the pillar cannot cover in depth without becoming unreadable. Every spoke links back to its pillar, and the pillar links out to every spoke, so authority moves in both directions instead of pooling on one page.
Editorial calendars exist to make that architecture achievable on a real production schedule, not to fill a content quota. We map the cluster first, then sequence publication by commercial priority and by what your writing and subject matter expert capacity can actually sustain. A calendar that outpaces your ability to produce well-researched pages produces thin content faster than it produces rankings.
The same pages built this way serve a second audience without any extra work: AI answer engines pulling structured, well-sourced content into their responses. A pillar page with clear headings, direct answers, and genuine expertise is exactly the shape both a search crawler and a language model are looking for. We are not building two content programs. We are building one, correctly.
What it is
Architecture, calendar, refresh discipline, and dual-purpose structure.
Topic clusters start with a full map of the questions your buyers ask, grouped by intent rather than by keyword string. Each cluster gets one pillar page and a set of spokes sized to the actual depth of demand. Thin topics get one page. Deep topics get a dozen, each one earning its place by answering something the pillar could not.
Editorial calendars sequence that map against reality. We prioritize clusters closest to revenue first, since a page that helps close a sale matters more in month one than a page that only builds general awareness. Publication cadence is set by what can be researched and written well, not by an arbitrary number of posts per month.
Refresh and consolidation cycles are the part most programs skip entirely. Content decays. Statistics go out of date, competitors publish something more thorough, and search intent shifts under a page that used to rank well. We run scheduled reviews that either refresh a page with current information, merge it into a stronger page covering the same ground, or retire it if the topic no longer earns its place.
The dual-purpose structure is not a separate workstream, it is a standard we hold every page to. Direct answers near the top, clear headings that map to real sub-questions, cited sources, and genuine subject matter expertise instead of restated competitor copy. That structure is what both a search algorithm and an AI assistant reward, because both are ultimately trying to find the page that answers the question best.
Fit
We would rather say no early than sell a program that cannot work.
Deliverables
A documented architecture, not a running list of post titles.
Every pillar and its spokes laid out with the intent each page serves and how it links to the rest of the cluster.
Full outlines for each pillar page defining scope, headings, and which spoke topics it needs to reference rather than cover in depth.
A sequenced publication schedule tied to commercial priority and realistic production capacity, reviewed monthly.
A standing calendar of which existing pages get reviewed and when, based on age, performance decline, and shifts in the topic.
A list of overlapping or underperforming pages that should be merged into a single stronger page instead of left to compete with each other.
A written content standard covering direct-answer openings, heading structure, and sourcing that every new and refreshed page follows.
How we run it
Five stages, run as an ongoing cycle rather than a one-time deliverable.
We map every question your buyers ask across the funnel and group them by real intent, not by keyword string similarity alone.
Questions get organized into pillar and spoke clusters sized to actual demand, with the internal linking pattern defined before a word is written.
Publication is sequenced by commercial priority and matched to real writing capacity, with subject matter expert interviews built into the schedule.
Every page ships with a direct answer near the top, clear heading structure, and cited sourcing, so it serves search and answer engines from day one.
On a recurring schedule we review performance and freshness, then refresh, merge, or retire pages so the cluster stays sharp instead of accumulating dead weight.
A pillar page covers a broad topic completely and links to narrower spoke pages that each answer one sub-question in depth. Spokes link back to the pillar. This structure concentrates topical authority instead of spreading it across disconnected, competing articles.
Where this connects
It supplies the material other SEO programs depend on.
Cluster architecture only works once the query research is intent-sorted, which comes from keyword research before any pillar or spoke gets outlined.
Published clusters need to actually be crawlable and indexable, which is the job of technical SEO running underneath the content layer.
Well-built pillar pages become the assets we pitch for coverage in link building since journalists link to content worth citing.
Return to the SEO hub to see how content strategy fits alongside the other eleven programs in a full build.
The same answer-first structure this program produces is what makes a page eligible to be cited under answer engine optimization since AI assistants pull from pages structured to answer a question directly.
Questions
We map the clusters before we write a single page.