Property 01
Intent
What the cluster is actually for. Commercial, informational, navigational. It changes what a good page looks like.
Analyzers · Cluster Volatility
Page-level reporting shows you pages. Demand doesn't arrive a page at a time, it moves in topics, and a topic can lose ground while every individual page in it still looks healthy.
Searchscope groups your queries into topic clusters, names the page carrying each one, and scores how completely you cover it. Then it watches the clusters, not just the URLs.
Every run groups your queries into clusters and works out what each one is for. A cluster carries its intent, the number of queries inside it and the demand behind them, so a wobble in something worth twelve thousand searches a month isn't filed next to a wobble in something worth thirty.
Property 01
What the cluster is actually for. Commercial, informational, navigational. It changes what a good page looks like.
Property 02
How many queries sit in the cluster and what they are worth each month, so the queue can rank topics against each other.
Property 03
Which of your pages currently carries the topic. Often not the one you assumed, and occasionally nothing at all.
Ranking for a handful of a cluster's queries isn't the same as owning the topic. Coverage is scored on every cluster so the thin ones surface before they slide, rather than after.
Coverage
The topic is yours across the cluster, not just its head term.
Coverage
Most of the cluster, with gaps worth closing while you hold the position.
Coverage
A foothold on the head term and little underneath it. The most common way a topic quietly leaks.
Coverage
Real demand, no page carrying it. An opening rather than a problem.
Volatility is measured across the cluster rather than the page, against a threshold, so ordinary week-to-week noise stays quiet and a topic genuinely shifting under you doesn't.
Cluster Volatility catches what page-level reporting misses. A dominant page holding its position while the queries around it drift away is invisible in a rankings report, and obvious in a cluster.
Ask the Strategic Advisor what moved and whether the cluster is worth defending, with the demand and your own history already loaded. Send it to Content Studio and the brief arrives knowing which queries in the cluster you don't cover.
Mark it applied and the Impact Tracker takes a baseline, then reports whether coverage recovered.
Connect a site and the analyzers read it end to end, then hand back the short list.