Browse guides

Build a topical map

Turn one seed topic into a pillar page plus three supporting clusters, with intent, priority, a suggested publishing order and internal links.

Before you start

  • A project, and enough credits for a topical map (the button shows the cost).

Steps

  1. Step 1: Open the map form

    Go to Planning and choose Start with a map, or Topical map under The usual path.

  2. Step 2: Describe the topic

    Under Map a topic:

    • Project.
    • Seed keyword or topic — the broad subject you want to own.
    • Language and Target market.
    • Extra context (optional) — angles, audiences or products the map should reflect.

  3. Step 3: Build the map

    Choose Build map for … credits. Once confirmed it cannot be stopped; a failure is refunded automatically one hour later.

  4. Step 4: Read the map

    The finished map has three views:

    • Publishing order — every topic in the order we suggest writing it.
    • Map — the pillar and its clusters.
    • Internal links — which articles should link to which.

    Priority and difficulty are AI estimates, not measurements from a search tool. Treat them as a starting point.

What you’ll see

The map is saved under Planning. Every topic on it has a Generate button — see Write an article from a topical map topic. You can also queue a map’s topics for Autopilot with Import from map — see Set up Autopilot.

Troubleshooting

The map does not have the topics I expected

A map is generated from the seed and your project profile. Build a new map with a narrower seed or more specific Extra context; existing maps are not changed.

I want to remove a map

Open it from Planning, choose Delete, then Delete permanently. Articles already written from it are not affected.

Related guides

  • Set up Autopilot

    Give a project a schedule and a queue of approved topics, and Autopilot writes, illustrates and — if you allow it — publishes an article on each run.

  • Create a content brief

    Research one keyword before you write: title angles, search intent, reader pain points, structure, entities and FAQ ideas.