Build a Topical Map for a B2B Website Around Buyer Tasks

A topical map for a B2B website is a table that lists the decisions your buyers make, the page on your site that answers each one, and what to do about the gaps. Build it from three inputs you already have: your product families, the questions sales hears, and your existing URLs. A spreadsheet is enough.

The usual way to build one, by exporting a few hundred keyword variations and assigning a page to each, produces a long list of near-identical articles. Organising by buyer decision produces fewer pages, each with a reason to exist.

What goes in the map

One row per buyer task. Seven columns:

Column	What it holds
Buyer task	The decision, in the buyer's words: "choose a grade for outdoor use"
Product family	Which part of your range it concerns
Stage	Learning, specifying, comparing suppliers, ready to quote
Existing URL	The page that answers it today, or "none"
Gap	What that page fails to say
Evidence owner	Who in the company can confirm the answer
Action	Create, improve, merge, defer

Keyword data, if you have it, goes in an eighth column as supporting evidence. It informs priority. It does not define the rows.

Build it in five steps

1. List product families and the applications you really serve

Start from what you sell and to whom. Ask sales and engineering to confirm the applications, because a broad industry label hides very different requirements. If an AI tool suggests "aerospace" because your product is made of aluminium and you have never shipped an aerospace part, it does not go on the map.

2. Write the decisions buyers make for each family

For most custom-product suppliers the decisions repeat across families:

• Is this within the supplier's range?
• Which material, grade or finish suits my application?
• What do I have to specify?
• How does the process work, and what does it cost me in time and tooling?
• How do I know the supplier can do it?
• What do I send to get a price?

Add the questions buyers use to express them. The sales-question method gives you a ledger for collecting those. Search queries are a second source; keep them in their own column so that a sales observation is never mistaken for search demand.

3. Put every existing URL on the map

List product pages, capability pages, guides, downloads and old blog posts. Open each one and write down the job it does, judged from the body. A page titled "Material Guide" that contains two paragraphs and a photo covers nothing.

Assign each URL to the row it answers. Three things will show up:

• Rows with no URL. Real gaps.
• Rows with two or more URLs. Overlap. These pages may be competing with each other; keyword cannibalization explains how to check.
• URLs that fit no row. Posts written for a keyword and no buyer. Candidates to merge or leave alone.

4. Record the gap and who can fill it

For each row, write what is missing in one line and name the person who knows the answer. "Missing minimum order quantity; owner: sales manager" is a task. "Needs more depth" is not.

A row is ready to write only when its evidence owner has agreed to supply the facts. A frequently asked question with no one able to answer it is blocked, however high it scores.

5. Choose one action per row

• Create when no page answers the task and the task needs its own format or evidence.
• Improve when a page exists for the same reader and decision but falls short.
• Merge when two pages answer one task; keep the stronger URL and redirect the other.
• Defer when the evidence is not available or the task is outside your range.

Update an old post or write a new one goes through the create-or-improve choice in detail.

Example: a complete map for one supplier

Example (fictional supplier). Calder Precision is an invented CNC machining shop making custom aluminium and stainless parts. Its site has six product and capability pages, a contact page and seven old blog posts. Here is its map after an afternoon's work.

Buyer task	Stage	Existing URL	Gap	Action
Is my part within your size and material range?	Comparing	Capabilities page	Lists machines, not part limits	Improve: add envelope, materials, what is declined
6061 or 7075 for a structural bracket?	Specifying	Blog: "Aluminium grades explained"	Describes grades, gives no recommendation	Improve: add conditional recommendation by load and corrosion
304 or 316 for washdown equipment?	Specifying	None	No page	Create: comparison article
Which tolerances are worth paying for?	Specifying	Two blog posts, both on "tight tolerances"	Overlap; neither says what drives cost	Merge into one guide
Which finish for an outdoor housing?	Specifying	Finishing services page	Lists finishes without selection advice	Create: selection guide, linked from the services page
How should I dimension a drawing for machining?	Specifying	None	No page	Create: guide with marked-up example
What does a first-article inspection include?	Comparing	Quality page	One sentence	Improve: describe the report, attach a blank template
Can you provide material certificates?	Comparing	Quality page	Not mentioned	Improve: add after quality manager confirms
What do I send for a quote?	Ready	Contact page	Email address only	Create: RFQ checklist with completed example
How long do prototypes take?	Ready	None	Owner has not agreed a figure to publish	Defer until owner decides
What changes between prototype and production pricing?	Ready	None	No page	Create: explanation of cost drivers, no prices
Industry news roundups (four old posts)	None	Four blog URLs	Fit no buyer task	Leave; do not update

Twelve rows produced five pages to create, four to improve, one merge, one deferral and four posts to stop maintaining. Before the map, the plan had been "publish two posts a month".

Three things in this example are worth copying. The RFQ checklist came out as the most valuable new page though it would never top a keyword list. The tolerance overlap was invisible until both posts sat in one row. And the prototype lead-time row is deferred, not written around: with no figure approved by the owner, an article on that question would be padding.

From map to publishing order

Sort the rows by three questions, in this order.

1. Is the evidence owner ready? If not, the row waits.
2. How close to an inquiry is the task? "What do I send for a quote" helps every buyer who is about to write to you. Start at the ready-to-quote end and work back.
3. Is it an improvement or a new page? Improvements to pages that already receive visits are faster and safer than new URLs.

Resist turning this into a weighted score. A formula that multiplies "demand" by "fit" will rank a row with missing evidence above one that is ready, and hide why.

If the site has Search Console data, add it now: a row whose existing page already appears for relevant queries but is rarely clicked moves up. The Search Console content plan shows how to read that report. Blogo automates this part, recommending what to write next from the site's pages and its Search Console data; see what to write next.

Link the pages along the buyer's route

The map also tells you which pages should link to which. Follow the order of decisions: product page to selection guide, selection guide to specification guide, specification guide to RFQ checklist, checklist to inquiry form. And back: every guide links to the product page it supports.

Use anchor text that says what the reader will find. Google's link best practices ask for anchor text that is descriptive and relevant to the destination, and note that links help Google discover pages as well as understand them. "See the RFQ checklist for machined parts" does both jobs; "click here" does neither.

You do not need every page in a group to link to every other. Link where a reader at that point would want the next page. Internal linking for B2B blogs covers placement and anchor wording.

Keep the map alive

Review it when something changes: a new product family, a discontinued one, a question sales starts hearing, a page that gets merged. Quarterly is enough for most suppliers. Each time a page is published or improved, update its row, so the map stays a record of what the site says and not a plan from last year.

FAQ

What is the difference between a topical map and a keyword list?

A keyword list records what people type. A topical map records what buyers are trying to decide and which page answers it. Ten keywords can belong to one row.

How many pages should one topic group have?

As many as there are distinct buyer tasks. The example above has five rows under "specifying" because there are five different specification decisions. Choosing a number first and filling it with variations creates overlap.

Does a topical map improve rankings?

The map is a planning document; it changes nothing by existing. What it does is stop you publishing overlapping pages and show you where a buyer's question has no answer. Whether the resulting pages rank depends on the pages and on the competition.

Do we need a tool to build one?

No. A spreadsheet with the seven columns above is enough for a site with fewer than a few hundred pages. A crawler helps only with listing URLs on larger sites.

Should we include topics outside our product range?

Only when your buyers need them to make a decision about your product and someone on your team can answer accurately. A CNC shop explaining anodizing choices for its own parts is in range. A CNC shop publishing a guide to injection moulding is writing for someone else's customers.