A keyword tool that reads your site before it reads a database
Around 120 keywords per run, drawn from the phrases your pages repeat and the wording of the results you compete against, grouped by the URL section that has to rank for them, each with a measured rank and a score that reports its own confidence.
Proof in the workflow
Clusters follow your URLs
Everything under /blog becomes one hub, /case-studies another. The grouping is your own site structure, so a cluster maps to a section someone already owns.
Rank comes from a live search
Every tracked keyword's position comes from a live search, and a keyword that did not appear is recorded as absent.
Research ends with a next step
Brief it, write it, track it, or push the whole cluster into Fabric where each row runs on its own schedule.
What this landing is built to rank for
Coverage comparison against rival domains
It reads the phrases in each competitor's indexed pages and shows which domains write about each one. That is topical coverage, and the column header says coverage. Rank comes from the tracker, on its own schedule.
Clusters with a coverage score
Each hub carries the average semantic match between the pages in it and your seed, so a thin section shows up as a low number.
A priority score that states its confidence
Volume, difficulty, current rank and copy match, averaged over whatever is actually known. A missing input drops out of the average rather than counting as a zero, and the keyword carries the confidence that produced it.
Intent read from the wording
Pricing and buy land in transactional, how-to in informational, brand names in navigational. A phrase whose wording says nothing is marked unknown.
How it works
Give it a seed and a site you own
It crawls the pages, reads the phrases they repeat and the phrases in their titles, and runs the seed and two variants through live search.
Read the constellation
Around 120 keywords arrive already grouped by URL section, with intent classified and phrases carried by most of your pages dropped as site chrome.
Check where you stand
Tracked keywords get a live position. Takeover analysis returns who currently holds the SERP and what those pages contain.
Turn one into work
A content brief, a full draft, a campaign against an existing page, or a cluster pushed into Fabric as scheduled rows.
Best fit use cases
In-house growth teams
Plan the quarter around clusters that map to sections of the site somebody already owns.
Agencies managing multiple sites
Each site keeps its own crawl, clusters and tracked positions, and a run is one seed phrase away.
Teams with no keyword-database budget
The clusters, coverage comparison, rank checks and priority ordering all run without a paid keyword database behind them.
Supporting content
FAQ
What makes this different from a basic keyword database?
A database returns phrases with volume attached and no idea what your site is. This starts from your pages: the phrases they already repeat, the wording of the results you compete against, and the URL sections those keywords belong to. Every keyword arrives attached to a part of the site.
Where does search volume come from?
From DataForSEO when you connect an account. Nothing here estimates volume locally, so the column is blank when you have not connected one. The clusters, coverage comparison, rank checks and priority ordering all work without it, and the priority score reports lower confidence when volume is missing.
How does it decide which keywords a competitor covers?
It reads the phrases in that domain's indexed pages, through a site: search, and compares them against yours. That measures who writes about a topic. It does not measure who ranks for it, and the table is labeled accordingly.
Can this support agencies as well as in-house teams?
Yes. Each site carries its own crawl, clusters and tracked positions, and every plan includes the whole platform. Tiers differ only on monthly volume.