Answer readiness
Whether each page carries the structured data, freshness signals and quotable structure that AI assistants lift answers from.
Answer readiness
Visibility Flux → AI Visibility → Answers asks a different question from the rest of the plugin: not can an assistant reach this page, but once it has the page, can it use it?
An assistant answering a question does not read your page the way a visitor does. It looks for a claim it can quote, a date it can trust, a structure it can navigate, and a publisher it can verify. A page can rank well and still be useless to it.
Eleven signals, all deterministic — no API key, no AI call.
Structured data
| Signal | What it means |
|---|---|
| Valid JSON-LD | The page carries schema markup that actually parses. Broken JSON-LD is ignored entirely, and nothing warns you |
| Describes the content | The schema describes this page — an Article, Product or FAQ — rather than only site-wide boilerplate like Organization |
| Names author and title | The two fields an assistant needs to attribute a quotation |
Trust
| Signal | What it means |
|---|---|
| Verifiable publisher | The organisation behind the page can be checked from outside your site |
| Author links to a page | The author is a resolvable identity, not a bare string. An assistant weighing two contradictory sources prefers the attributable one |
Freshness
| Signal | What it means |
|---|---|
| Machine-readable date | A date in the markup, not only rendered as text a parser has to guess at |
| Updated recently | The page has been touched recently enough to be treated as current. Assistants discount stale pages heavily on anything time-sensitive |
Structure
| Signal | What it means |
|---|---|
| Has headings | Real heading elements, so the page can be navigated rather than read start to finish |
| Question headings | Headings phrased as questions map directly onto what people ask |
| Quotable opening | The page answers its own question near the top, in a passage short enough to lift. A page that takes four paragraphs to reach the point rarely gets quoted |
| Lists or tables | Structured passages an assistant can extract cleanly |
Reading the score
Each page gets a score out of eleven with the failing signals named. Sort worst first and start there.
Do not expect eleven everywhere. A homepage is not an article and will legitimately score lower — it has no author, no publication date, and nothing to quote. Judge article and product pages by this; judge landing pages by whether the important signals are present.
What to fix first
- Valid JSON-LD — the cheapest fix with the widest effect. If it is broken, everything built on it is invisible
- Quotable opening — answer the question in your first two sentences. This is a writing change, not a technical one, and it is the one that most changes whether you get cited
- Machine-readable date — usually a theme template fix, applied site-wide at once
- Author links to a page — give authors real profile pages
Visibility Flux Pro can generate JSON-LD for a page directly from the AI Editor. The remaining signals are theme and writing changes, and the audit tells you which pages need them.
How this relates to the other tabs
- Access Check — can an assistant fetch the page
- Answer readiness — can it use what it fetched
- AI Traffic — did it send you a reader
The three answer the same question at three stages. A page failing the first makes the other two moot.