Because a list of four thousand keywords is not a plan. It is sorted by volume, the top fifty are stared at, and the rest is never opened again.
Worse, nothing on it says which page is supposed to rank. Two pages end up chasing the same query, both rank at eleven, and neither is anybody's responsibility.
Queries are grouped by the intent they share and mapped to the one page meant to answer them. A cluster has an owner, a target page and a current position, so it is a unit of work rather than a row.
Where two pages compete for the same cluster, that is flagged as cannibalisation with both pages named, because the fix is an editorial decision rather than a technical one.
The backlog becomes finite. Instead of four thousand keywords there are eighty clusters, each with a page, a position and a gap.
Briefs get better, because the brief for a page is the cluster it must answer — every query in it, in the words people used.
It will not decide your information architecture. It shows where queries overlap and where pages compete; merging, splitting or leaving them is a decision with a person behind it.
It also will not invent demand. A cluster with no impressions is a cluster nobody is searching for, and Growth says so rather than dressing it up as an opportunity.
Nothing here is an integration. Each line is two products reading the same record from different sides.
Queries are grouped by the intent they share and mapped to the one page meant to answer them. A cluster has an owner, a target page and a current position, so it is a unit of work rather than a row.
The backlog becomes finite. Instead of four thousand keywords there are eighty clusters, each with a page, a position and a gap.
It will not decide your information architecture. It shows where queries overlap and where pages compete; merging, splitting or leaving them is a decision with a person behind it.
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.