Findings is one front door for everything open across your site. The score could read 99 and “Excellent” while five separate screens quietly held work you had never seen; this tab gathers all of it into a single ranked list, so the first row is always the one worth doing.
What lands here
Two kinds of things, merged into one list:
- Pages losing a click they already earn — read from the search engines’ own numbers: pages one push from page one, pages on page one being scrolled past, and several pages splitting one search between them.
- Anything the setup checks caught — whatever Readiness would flag, stated as the work it actually is.
Every row says what to do in plain words and carries the button that lands where the fix actually lives: content findings hand their exact pages to the worklist below, and search findings open the matching card on Visibility → Search.
How it is ranked
By what each finding costs you — visitors lost, AI assistants turned away, or a page underselling itself — never by which part of the plugin noticed it. Findings move through three stages on the one screen: what needs you, what is finished on your side and waiting on a search engine, and — briefly, at the top — what has actually improved.
The count in the nav
The Findings tab carries its own count, and that count only ever measures work you can do something about. Anything merely waiting on a later report gets a quiet dot instead of a number — a number in a nav is a promise that doing the work makes it go down, and waiting is not workable. Clients waiting on an allow-or-block verdict are not findings; they stay with the bell.
Your content, one row at a time
Beneath the ranked list sits the content worklist: one row per post, page or anything else you publish, saying what that piece is actually found for, whether it answers that, and anything else it needs. Anything not meant to be cited can be set aside — parked on its own ledger, listed and counted rather than merely absent, so “not meant to be cited” stays a decision you can review instead of a hole in a list.
Connected agents can read the same ranked list over MCP with the read-findings tool — the same rows, the same order, bounded at twelve.