Home › Tools › The Backlog Rescoring Check
Free check · 6 items · live rescoringDoes your backlog score survive contact with citation data?
Enter one backlog row and this runs both scores side by side: the legacy volume-and-difficulty score, and the citation-aware one. If the multiplier is constant across your set, the new score is doing no work.
Our own numbers, and the published rank-to-citation curve
The curve below is the one our own scoring runs on: position 1 cites at 58%, position 2 at 54%, position 3 at 35%, position 10 at 14%, and everything from 11 down is capped at 14%. The cliff between position 2 and position 3 is the largest single drop on it.
| Measured | What it is |
|---|---|
| median 6.81 days, P90 37.10 days | How long citations lag publicationThis is the reason a 45-day evaluation window beats a 30-day one: at 30 days you are reading the lag, not the result. Third-party measurement, not ours — and we hold it second-hand, so treat it as directional. · Profound, 2026, as reported in LinkedIn's 2026 AI Search Visibility guide |
| 14 of 17 | Top-10 pages with zero AI citationsOur own estate: 17 pages ranked in Google's top 10 (average position 10 or better), and 3 of them were cited by an AI engine. · Indexable, 7 September 2026, n = 223 pages |
The curve is calibrated to published research (AirOps and Growth Memo, 2026), not to your estate. The scores it produces are a prioritisation aid, not a forecast — and a constant multiplier across your set means the new score is not reordering anything.
A score nobody downstream can read changes nothing
The rescoring is arithmetic. Getting the citation-point delta onto the ticket, and the 45-day gate into the release process, is the part that takes a conversation.