A topical map: pillar pages and spokes built from your plan

Planned topics grouped into pillar and spoke clusters that follow your plan.

  • Plan itemsNo keyTopics already in the plan for the active site.
  • API keyNo keyNone required for the map itself.
6
stages per node
1
pillar per cluster
0
extra data stored
1
click to Create draft
Search Growth · Plan · Topical mapIllustrative composite

Topical map · 2 clusters

Pillar · 3 spokes

Pillar · 2 spokes

Select a node to see its stage and next action.

Illustrative product composite. Click a node to see its stage action. Topics and stages are invented.

How the map is built

  1. Add topics to the plan

    From product-led topics, keyword research, a competitor gap or Fill my month.

  2. Open the Topical map panel

    BlogFactory groups the plan into clusters on read and labels each pillar with its spoke count.

  3. Check coverage

    A pillar with no spokes is a prompt to plan supporting pages.

  4. Create and link

    Create drafts from the nodes, then link every spoke to its pillar.

What it needs
Plan itemsNo keyTopics already in the plan for the active site.
API keyNo keyNone required for the map itself.
What it will not do
  • Insert internal links for you. It tells you which spokes need to link to which pillar.
  • Guarantee topical authority. A map organises work; search engines decide what they reward.
  • Create drafts without you. Create draft opens the normal form.

BlogFactory never publishes live. Agents propose, people approve, and the furthest an agent goes is a CMS draft.

More: what you get, what changes, limits and questions

A flat keyword list hides structure. The topical map groups the topics in your plan into clusters, picks the shortest term as the pillar, lists the spokes beneath it, and shows where each page stands. It is computed from the plan each time you open it, so it never drifts from the work.

What you get

Clusters from the plan

Planned topics are grouped by theme. The shortest term is the pillar. Nothing extra is stored, so changing the plan changes the map.

Stage at a glance

Planned, Drafting, Review, Delivered, Blocked or Measuring, shown per node with the planned date.

Create draft from a node

Each node without a draft opens Create with the target query prefilled. Existing drafts open in the editor.

What changes

Before

  • A flat keyword list with no pillars and no order.
  • Spokes drafted without a page to link back to.
  • No view of what is planned, drafted or delivered.

With BlogFactory

  • Plan items grouped into clusters, the shortest term as pillar.
  • Each node shows its stage from planned to measuring.
  • Create draft opens the form with the target query filled in.

OutcomeA structure that follows the plan as it changes.

Limits to know

  • Clusters are a heuristic grouping of terms, not a semantic graph. Review them before you commit to a structure.
  • The map shows planned items. Pages you published before using BlogFactory appear only if they are in the plan.

Questions

How does BlogFactory choose the pillar?

The shortest term in a cluster becomes the pillar, and the other terms become its spokes. You can plan a different pillar by adding it as its own topic.

Is the topical map saved?

It is computed from the plan each time, not stored separately. That keeps it consistent with whatever you plan, draft or deliver.

Does it work for a site that already has many posts?

It maps what is in the plan. Overlap checks use existing posts and indexed pages so you do not plan duplicates.

Can I build a map by hand?

Yes. The plan is editable, and the guide on building a topical map walks through doing the same thinking on paper.

Draft-only, whether you self-host or use Cloud.

Cloud starts at $5 a month and AI usage is bring-your-own. The open-source core is free to self-host. The authority boundary is identical in both.