Loading
Because a number out of a hundred does not say what to write. It rewards word count and keyword density, so pages get longer and less useful, and the score goes up while the page gets worse.
The writer is left guessing which of the fifteen suggestions actually mattered.
A page is compared against the cluster it is meant to answer: which queries reach it, which of those it addresses, and which it does not. The output is a list of unanswered questions in the words people used to ask them.
A brief is that list plus the page's current position and what the pages above it cover that this one does not.
Writers stop optimising and start answering. "This page never says what happens to existing data during migration, and forty impressions a week ask" is a sentence somebody can act on.
Measurement gets honest too: the page is re-checked against those same queries, so improvement means the questions are now answered.
They will not write the page. Growth can tell you what is missing; whether the answer is a paragraph or a rebuild is an editorial judgement.
They also will not give a score. There is no number, deliberately — a number is what teams optimise instead of the content.
Nothing here is an integration. Each line is two products reading the same record from different sides.
A page is compared against the cluster it is meant to answer: which queries reach it, which of those it addresses, and which it does not. The output is a list of unanswered questions in the words people used to ask them.
Writers stop optimising and start answering. "This page never says what happens to existing data during migration, and forty impressions a week ask" is a sentence somebody can act on.
They will not write the page. Growth can tell you what is missing; whether the answer is a paragraph or a rebuild is an editorial judgement.
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.