Free tool
Turn one topic into a linked content map.
Enter a seed topic and this builds a hub-and-spoke cluster around it across seven intent branches, then plans which page should link to which. Paste the titles of pages you already have and it marks what is covered and what is missing.
- Seven intent branches around one hub
- Internal link plan for every node
- Covered vs missing against your existing pages
- Copy as CSV or Markdown
Runs entirely in your browser. Nothing you paste or type is sent to Gadex or stored anywhere. Close the tab and it is gone.
Output
Enter a seed topic and the map appears here: a pillar page, spokes across seven intent branches, the funnel stage of each, and the internal links between them. Nothing is sent anywhere.
Methodology Exactly what this tool checks, and what it cannot tell you
It is template expansion, not keyword research
Your seed topic is inserted into a fixed taxonomy of intent patterns that recurs across almost every B2B and local-service market. Nothing is looked up. There is no search volume, no difficulty score, and no SERP check behind any suggestion, because the page makes no network calls at all. What you get is a structure to argue with, not a validated list.
The seven branches
Pillar (the hub itself), definitional (what it is, how it works), comparison (versus alternatives, best for a segment), how-to and process (choosing, implementing, migrating), commercial (pricing, cost, worth it), problem-led (mistakes, failures, what to do when it goes wrong), and proof (examples, case studies, benchmarks). Together they cover the arc from someone who has just heard the term to someone comparing two quotes.
Funnel stage is assigned by branch, not by guesswork
Each branch maps to a fixed stage: definitional and problem-led sit at the top, how-to and comparison in the middle, commercial and proof at the bottom, and the pillar spans all three. This is a convention, not a measurement. It is there so you can see at a glance whether your cluster is all top-of-funnel reading material with nothing that helps someone buy.
The internal link plan is the part worth keeping
Every spoke links up to the pillar and sideways to one or two siblings inside its branch or an adjacent one. The pillar links down to every spoke. Most people can guess the titles; far fewer plan the linking before publishing, which is why clusters end up as a pile of unconnected posts. Use the link column as the brief instruction, not an afterthought.
How coverage matching works, and where it is wrong
If you paste existing page titles, each is reduced to lowercase word tokens with stopwords and your seed words removed. A suggested node is marked covered when enough of its distinguishing tokens appear in one of your titles. It is a blunt string comparison: it cannot tell that "What our booking system costs" covers the pricing node, and it will happily call a thin 300-word post covered. Treat every match as a prompt to go and look at the page.
What you still have to do yourself
Validate demand. Some of these nodes will have no search volume in your market and some will have far more than you expect; the tool cannot tell you which. Cut the ones nobody asks about, merge any two that would answer the same question, and rewrite every title in your own language before briefing anything.
Sources behind these rules
The checks on this page are our reading of how search and answer engines describe their own behaviour. These are the primary documents behind them — read them rather than taking our word for it. Platforms revise this guidance without notice.
- Google Search: creating helpful, reliable, people-first content — why coverage depth matters more than page count
- Google Search: intro to structured data markup — making the relationship between hub and spoke pages explicit
Questions
About this tool
Is this using AI to generate the topics?
No. It is deterministic template expansion running in your browser — the same seed topic always produces the same map. There is no model call and no network request. The value is the intent taxonomy and the link plan, not novel wording.
Does it show search volume?
No, and it cannot. There is no keyword data behind any suggestion. Take the map into a keyword tool or your own Search Console data and cut whatever nobody is actually searching for.
How many pages should I actually build?
Fewer than the map shows. The map is deliberately complete so you can see the whole shape of a topic. Most teams build the pillar plus five to eight spokes, choosing the ones closest to a buying decision first, then extend once the hub is earning something.
What does covered actually mean?
That one of the titles you pasted shares enough distinctive words with the suggested node. It is a word-overlap check, so it says nothing about whether the existing page is any good, current, or long enough to compete. Use it to narrow down what to review, not as a verdict.
Is any of this sent to Gadex?
No. Everything runs in the page. Your seed topic and your page titles never leave the browser, nothing is stored, and closing the tab discards it.
Want the map built and the pages written?
A free competitor search gap report shows which of these clusters your competitors already win, which ones are open, and what is worth publishing first — researched for your market rather than expanded from a template.
Get a free gap report