What this check inspects
This is the one list that merges the others. Shipwork runs the opportunities check, which itself chains the near-miss list into a content-gap comparison and real-user speed, and the consolidation check, then folds every signal onto the page it belongs to and ranks the pages by urgency, with the reasons shown so the order can be audited. A page can carry a near-miss query, a missing subtopic, poor real-user speed, a duplicate conflict, a query two of your pages fight over, rank or click decay, or a query and a page that do not match on intent, and its place in the list reflects how many of those it has. It also clusters your whole query set into topics and flags the weakest high-demand topic, where the content is thin across a subject rather than on one page.
What a failure means
It invents nothing: a missing signal contributes nothing to a page score rather than being guessed. With no connected search property it still ranks the structural conflicts, but says plainly that demand could not be included rather than presenting the order as if it were demand-aware. If neither of its inputs can run there is no list to give, so it reports a reason instead of an empty success. The weakest topic is only flagged when the best query in that topic still sits off page one.
How to fix it
- Work the first page on the list. It is the one carrying the most urgent combination of signals.
- Read the reasons next to a page before editing, since the order is only as good as the evidence behind it.
- Where the list was structural rather than demand-aware, connect a search property and run it again for a ranked order.
- For the weakest topic, treat the whole subject as thin, not just one page, and plan several pages rather than one edit.
A typical failure, worked through
The setupA store connects its search property. One product page has a query at position 12, is missing two subtopics its competitors cover, loads slowly for real visitors, and shares a query with an older page.
What the check reportsThe check puts that page first and lists the reasons: the near-miss query, the missing subtopics, the poor speed and the duplicate conflict. It adds the weakest high-demand topic underneath.
The pointFour checks would have produced four lists pointing at the same page. This ranks that page once and shows why it is first, so the work starts in the right place.