Coverage and page types

Readiness tells you about one page and one query. The coverage panels tell you about the shape of the whole site: which kinds of page carry your presence, and whether being retrieved is turning into being cited.

Coverage by page type

Every discovered page is typed from its URL: home, location, service, landing, blog, product, tool, listicle or other. Coverage by page type shows which of those are serving your fan-out queries.

The useful reading is the mismatch. Most sites find their blog covers informational queries well and their service pages cover nothing, because service pages are written to sell to someone who has already decided. Models asking "which provider should I use" are reading for comparison and evidence, and a page with neither is not a candidate.

Backlink authority

Shown alongside coverage so the two can be read together. It does not feed the readiness score: readiness is about the passage, and authority is about whether anyone trusts the page the passage is on.

It explains the case where two pages both score Ready and only one of them is ever cited. When that happens, the answer is usually not another rewrite.

Cited against retrieved over time

The chart that matters most on this screen. Two lines: how often your pages were retrieved as candidates, and how often they were actually quoted.

• Both rising. Working. Keep going.
• Retrieved rising, cited flat. Models are finding you and not using you. That is a passage problem, and it is the signal that sends you to fixing a page.
• Both flat after work shipped. Either the assistants have not re-fetched yet, which takes days to weeks, or the pages are not reachable. Check discovery before rewriting anything.
• Cited falling. Someone else published something better, or a source you used to beat now carries your competitor.

Linked fanouts

A page carries the list of fan-out queries it has been scored against. Read it as the page's actual job: these are the questions a model might use it to answer.

A page with no linked fanouts is not serving any query you track. That is either a page that should not be in scope, or a gap in your prompt set, and the second is more common than people expect.

Optimizations on a page

Work logged against a page appears here with its date, which is what lets a later citation lift be attributed to something specific. Logging is how the before-and-after comparison gets a start line; without it you have two numbers and no idea which change produced the difference.