Loading
Because a list of four thousand rows is not a plan. It gets sorted by volume, the top fifty are examined, and the long tail — where most of the opportunity is — is never read.
A cluster is a group of queries that share an intent and should be answered by one page.
Queries group by the intent they share, judged on the results they return as well as their wording. Each cluster gets a target page, an owner and a current position.
Four thousand queries reduce to eighty clusters. That is a backlog a team can actually work through, and each item is a page rather than a row.
It will not choose your site structure. It shows which queries belong together; whether that is one page, a hub or a section is an editorial decision.
Its target page's record, the brief written from it, its position and impressions, and any competing pages flagged as cannibalisation.
Yes. Automatic grouping is a starting point, not a verdict.
Flagged rather than forced, because the split is usually a content decision.
No — separate clusters per language, since intent differs.
Fourteen days, every module, no card. Or half an hour with someone who will run it on your own records and tell you where it does not help.