Related keywords for content clusters

Related keywords are nearby search ideas tied to one seed phrase. You use them to plan a content cluster: one pillar page for the core topic, then spoke pages for distinct intents that still belong to the same subject. A thin list of synonyms is not a cluster. You need phrases people actually type, grouped by job, with enough volume to justify a URL. Primary demand for “related keywords” itself is modest in the US (~110/mo). The stronger planning heads sit on keyword cluster / keyword clustering (~480) and topic cluster (~260). This guide shows how to expand a seed, read depth and credits on Related keywords, validate targets in Keyword overview, and avoid thin duplicate pages.

What related keywords mean for a content cluster

Related keywords come from “searches related to” style ideas around your seed. They are not only the same words shuffled. A seed like robots.txt can surface policy phrases, generator language, crawl-block questions, and sitemap adjacency. Each of those can become its own page if the intent differs.

A content cluster (often called a topic cluster) is a deliberate map: one hub that covers the main question, plus supporting URLs that answer narrower jobs and link back. Related keywords feed that map. You collect candidates, drop junk, then assign each keeper to pillar, spoke, or “mention only in a section.”

People also search “keyword cluster” and “keyword clustering” when they want software that groups a giant list by similarity. That product job overlaps your planning job. You still need a human pass: same intent on two URLs hurts you more than missing a low-volume synonym.

Treat related keywords as input for architecture. Treat density checkers and title length tools as polish after the outline exists.

Why one page cannot cover every related phrase

One long article can answer several related questions. It cannot own every SERP. When related terms pull commercial intent (“generator,” “checker,” “tool”) next to pure how-to intent, Google often splits the results. Stuffing every phrase into one H2 list creates a page that ranks for none of them.

Clusters fix that by giving each distinct job a home. The pillar owns the overview. Spoke pages own the jobs that need steps, examples, or a different promise. Internal links tell crawlers and readers how the pieces connect.

Related searches at the bottom of a Google SERP (~880 monthly for the bare phrase in Ads data) are a useful sanity check, but they are a UI label with mixed intent. Some people want YouTube tags. Some want SEO lists. Use them as hints, then confirm with a research table that includes volume and difficulty.

If two related phrases share the same answer, keep one URL and use the second phrase in a section heading or FAQ. If the answers diverge after the first paragraph, split the pages.

How to choose a seed and search depth

Start with the phrase you want the pillar to own, not the longest long-tail you can invent. A clear seed keeps related branches readable. Vague seeds (seo, marketing) explode into noise that burns credits and time.

Pick a market that matches your site (US English for Toolsy’s default research). Then set depth. Depth controls how far the related-to graph walks from the seed. Shallow depth stays close. Higher depth walks into farther branches and costs more credits on Toolsy.

Start shallow (depth 0-1)

Depth 0-1 usually costs 1 research credit per run on Plus. Use it when you need a first pass for a known topic: alternate phrasings, nearby jobs, and obvious spoke ideas. Export the CSV. Highlight anything that feels like a separate searcher problem.

Ignore brand navigational junk (competing tool logins, YouTube tag diggers) even when volume looks fine. Those rows do not belong in your editorial calendar.

When to raise depth (2-4)

Depth 2+ usually costs 2 credits per run. Raise depth when the first pass is too thin for a real cluster: you have a pillar title and almost no spoke candidates, or the topic has many adjacent jobs (privacy, formats, audiences).

Do not max depth on every seed. Deeper graphs add volume of rows, not quality by default. Run depth 2 after you already know what pillar you will publish. Stop when new rows stop suggesting new page jobs.

Walkthrough: find related keywords on Toolsy

Open Related keywords. You need a Plus account and available research credits for live Labs data. Free Toolsy on-page tools stay free. This research desk does not. Plus includes 200 research credits per month. Identical lookups within 7 days reuse cache at 0 credits.

Enter one seed. Choose market. Set depth. Run the lookup. The table returns related phrases with volume, CPC, difficulty, and intent when available. Export CSV into your brief or spreadsheet.

Plus, Pro, and credit honesty

Pro covers file conversion tools. Plus adds the SEO research desk on top (about $19/mo or $169/yr; see /pricing). Live related-keyword runs spend 1 or 2 credits by depth. If you exhaust the monthly pool, you can buy a 100-credit top-up for the current month. Do not plan a 40-seed audit at depth 4 on day one; plan seeds, then spend.

Logged-out visitors can read the page, but live lookups stay behind Plus. That is intentional. Teaser free daily Labs lookups are off for this wave.

Read the table before you outline

Sort by volume if you need demand signals. Then read intent columns and the wording of each row. A high-volume commercial phrase may deserve a tool landing, not a blog spoke. An informational how-to with modest volume may still earn a spoke if it matches a real gap on your site.

Cross-check keepers in Keyword overview (the search volume checker) when you want up to 10 candidates compared side by side. One credit covers that batch. Use overview after related expansion, not instead of it.

Turn related keywords into a cluster outline

Take the CSV and create three buckets: pillar candidates, spoke candidates, and “section only.” Pillar candidates are broad enough to introduce the topic and link outward. Spoke candidates need their own steps or audience. Section-only phrases live as H2/H3 or FAQ lines inside an existing URL.

Sketch the internal links while you assign buckets. Every spoke should link to the pillar. The pillar should link to each live spoke with descriptive anchors. Orphan spokes waste the cluster idea.

Pillar vs spoke pages

The pillar answers “what is this topic and how do the pieces fit?” Keep related phrases that describe the whole subject near the pillar title and introduction. Put generator, checker, API, or audience-specific jobs on spokes when those SERPs look different.

Example pattern for on-page SEO helpers: a pillar on structured data strategy, then spokes for FAQ JSON-LD paste, title length, and robots basics. Wave 4 already ships several of those spokes as separate guides (see links below). Your related-keyword pass is how you decide which jobs deserve a URL next.

Group by search intent

Informational rows become guides. Commercial rows often become tool landings or comparison sections. Navigational rows (brand names) rarely belong in your cluster unless you own that brand.

When intent is mixed on one phrase, open a SERP. Soft path when live: SERP preview before you write (K03) and the Google SERP checker. Confirm whether rank #1 is a tool, a definition, or a how-to before you assign the URL type.

Check volume and difficulty before you write

Related lists tempt you to invent ten thin posts. Volume and keyword difficulty push back. Paste your shortlist into Keyword overview. Drop zeros that only look clever. Keep mid-volume phrases with clear intent even when KD is high if you can win with better specificity.

Difficulty is a relative fight score, not a ban. A KD of 80 on a head term still allows a spoke with a tighter angle. A KD of 20 on a phrase nobody asks for still wastes a publish slot.

After you lock titles, write. Then use free polish tools: keyword density on the draft, meta title length guidance plus the title and meta length checker, and FAQ schema without a plugin when the page has real Q&A. Deduplicate pasted keyword dumps with Line sort for deduping keyword lists before you outline spokes.

Mistakes that break clusters or waste credits

Running depth 4 on every brainstorm seed burns the monthly 200 credits and fills sheets with noise. Start shallow. Raise depth on the seeds you already plan to publish.

Publishing five spokes that answer the same question cannibalizes your own site. If two related keywords share an outline, merge them. If they diverge after the intro, keep both and cross-link.

Treating “LSI keywords” as a magic ranking list is outdated. People still search that phrase (~390/mo). Use related and semantic neighbors as coverage clues, not as a stuffing checklist.

Calling live Labs data “free related keywords” misleads readers and your own team. Manual related searches in Google are free. Toolsy’s live related table needs Plus and credits. Say that up front in briefs.

Skipping the SERP check produces outlines that fight tool pages or definition pages. Read what already ranks. Adjust the promise before you draft 2,000 words.

Next checks after you pick targets

Once the cluster map exists, finish on-page jobs that the wave already covers. Check title length with the 2026 practical limit guide. Add FAQ markup only when the page shows matching Q&A, using the no-plugin JSON-LD path. Soft-link a SERP read (K03) before you lock the pillar outline if that post is live.

Keep research on Plus tools and polish on free checkers. That split matches how Toolsy ships the desk.

Frequently asked questions

What are related keywords?

Related keywords are search ideas connected to a seed phrase through related-to style relationships, not only exact-match long tails. They help you see alternate jobs and phrasings around one topic. You use them to plan coverage, then you validate volume and intent before you create URLs.

How do I find related keywords for a content cluster?

Pick the pillar seed, run a related expansion at shallow depth, and export the list. Bucket rows into pillar, spoke, and section-only. Confirm keepers with volume and a quick SERP read, then outline internal links before you write.

Do I need Plus to use Toolsy related keywords?

Yes for live lookups. The Related keywords tool is a Plus research feature and spends monthly research credits. You can open the page without an account, but live Labs data stays behind Plus. Free Toolsy tools for density, titles, and FAQ schema remain free.

How do related keywords credits work?

Depth 0-1 usually costs 1 credit per run. Depth 2 or higher usually costs 2. Plus includes 200 research credits each month, and identical lookups within 7 days can hit cache at 0 credits. Check /pricing for Plus and optional credit packs.

Related keywords vs keyword suggestions: what is the difference?

Related keywords pull broader related-to ideas that may not contain your exact seed wording. Keyword suggestions return longer queries that must include your seed. Use related for cluster breadth. Use suggestions when you need long-tail variants of a locked phrase.

What is a keyword cluster or topic cluster?

A keyword or topic cluster is a planned set of pages around one subject: a pillar plus supporting spokes that link together. “Keyword clustering” as a search term often means software that groups a large keyword list by similarity. Both ideas serve planning; you still assign URLs by intent, not by algorithm alone.

Are LSI keywords the same as related keywords?

No. “LSI keywords” is an old SEO label people still search. Modern practice uses related terms, entities, and clear coverage of the topic. Do not paste an LSI list for density theater. Expand related ideas, then write for the jobs those phrases represent.

Should every related keyword get its own page?

No. Many related phrases belong in a section or FAQ on an existing URL. Create a new page when the searcher needs a different answer, format, or commercial path. Duplicate outlines split your own rankings and waste publish time.

Can I use related searches at the bottom of Google instead?

You can skim them for free as a hint. The phrase “related searches” has high raw volume but mixed intent, including non-SEO jobs. A research table with volume, difficulty, and export beats screenshots when you build a real cluster calendar.

What should I do after I build the related keyword list?

Validate volume in Keyword overview, assign pillar and spokes, soft-check the SERP for the pillar query, then write. Finish with title length, density, and FAQ schema only where the page earns those checks. Link spokes back to the pillar when you publish.

After you ship the cluster map, keep polishing with live wave-4 guides on meta title length and FAQ schema without a plugin, and open Related keywords whenever a new pillar seed needs a spoke list. For the overview-before-outline pass, see Keyword overview before you write the outline.