One seed keyword into a pillar-and-spoke plan.
It reads the live SERP for your seed and organises the cluster into a pillar-and-spoke plan, as validated JSON.
6 steps · runs on demand · added to your workspace as a draft
Grouped by the results they share
Same results? Same page.
Keywords that pull the same ten results want one page, however different they sound.
01 · One seed became eight keywords. Each has a live SERP.
02 · A dot wherever a domain ranks. In this order, it's noise.
03 · Sort the rows by the results they share…
04 · …and three blocks appear. Same results, same page.
05 · A pillar and two spokes, handed back as validated JSON.
keyword × the domains ranking for itseed ordersorted by shared results
cluster.json✓ validated
Pillar · tools
3 keywords · one page
Spoke · tracking
3 keywords · one page
Spoke · pricing
2 keywords · one page
The steps
What happens on every run.
- read_live_serp
- mine_related_subtopics
- group_by_intent
- build_pillar_spoke_plan
- validate_json
- save_plan
6 steps · Runs on demand0 / 6
Run history keeps each step's output and runtime, and the input of every step that completed.
In, and out
You give it one seed keyword. This is what comes back.
- Shape
- 6 steps
- On demand
- run mode
- 1
- click to add
Illustrative output.
What it does
Pre-built, then yours to customize.
Add it to your workspace in one click. Sensible defaults and example inputs are already filled in.
Reads from · writes to
- Web search
The template, step for step
- Trigger
- Web search
- Perplexity research
- LLM call
- Code
- Notify
Added to your workspace as a Draft, with example inputs filled in. Every step is yours to change.
- 01
A real pillar-and-spoke structure, not a flat list
- 02
Grouped by intent, so one page does not chase three jobs
- 03
Returned as validated JSON
- 04
Ready to feed the brief agent per spoke
Before & after
The time this gives back.
The templates that publish put a Human review step before the CMS step, and nothing ever posts to Reddit for you. Review is a step, not a lock: a workflow you build or edit can publish or message a channel without one, so add it wherever you want the sign-off.
Doing it by hand
~4.25 hrs
Cluster keywords & analyze SERP
~30 min
Doing it by handyour team
- Pulling and reading the SERP~1h
- Finding the subtopics~1.5h
- Grouping them by intent~1h
- Drawing the structure~45m
Per cluster, by hand~4.25 hrs
Cluster keywords & analyze SERPLive
- Agent reads and minesauto
- Agent groups and structuresauto
- Agent validates the outputauto
- You sanity-check the plan~30m
One agent run~30 min
FAQ
Questions, answered.
This one starts from a single seed and reads the live SERP, so it discovers the cluster. The planner starts from a list of seeds you already have and organises them. Use this to find the shape, the planner to tidy a list.
Because it is structured JSON meant to feed other agents. A Filter step parses it inside the run, so a malformed plan fails there rather than downstream.
Yes. Each spoke can be passed to the content brief agent, so a cluster becomes a set of briefs without re-entering keywords.
Free to start
Add this agentto your workspace.
Start free. Customize the steps, run it on demand or on a schedule, and approve anything that ships.