Visibility engine
The visibility engine scores every build across five pillars: SEO, AEO, LLMO, conversion and agent readiness.
It reads the HTML a crawler actually receives rather than the source it was written from. The result is one number out of a hundred, a plain-English sentence for each thing it found, and a button that hands the finding back to the builder as work to do.
Visibility score
90/100
+11 since last build
Conversion
The repairs page asks for a booking twice and never says what it costs.
Fix this
AEO
Two pages open with background instead of the answer.
Fix this
Five pillars
One overall number is what you glance at. Five separate ones are what tell you where the problem is, and they are deliberately not averaged into invisibility.
SEO
Title, meta description length, canonical link, Open Graph, one h1, heading order, alt text, internal links, sitemap, robots policy, and anything that would overflow a phone.
AEO
Answer Engine Optimisation. Whether the first paragraph after the h1 actually answers the page’s question, and whether the questions people ask are visible and marked up.
LLMO
Large Language Model Optimisation. Whether the site states its own purpose in machine-readable form, and whether each page’s topic can be extracted without guessing.
Conversion
The pillar most audits skip. A page can be perfectly indexed and still be a dead end, so this one looks at whether there is a next step, whether it is reachable on a phone, and whether the page says what things cost.
Agent readiness
Increasingly the visitor is an assistant working for a person. This checks whether opening hours, stock, prices and contact routes are available as data rather than only as sentences.
The fix loop
Most audit tools stop at the diagnosis, in a vocabulary that assumes you already know what a canonical link is for. That is fine for a developer and useless for the person who owns the site.
So each finding here is three things: what is wrong, in a sentence; why it costs you something, in another; and a button that sends it back to the builder as work. Approving a fix starts a build with the task already written.
01
The built HTML is read page by page. Nothing is inferred from the source.
02
Each finding says what it is and what it costs, without the jargon.
03
One click turns the finding into a build, and the next report shows whether it worked.
Limits
A visibility tool that will do anything to raise its own number is a liability. These are the things this one refuses.
No FAQ markup without a visible FAQ. No rating without a rating. Both are penalties, and both are easy to get away with until you do not.
It checks whether a page has one clear topic, not whether a phrase appears often enough to look unnatural.
Search and citation crawlers stay allowed. Blocking them removes you from AI answers and protects nothing.
It scores whether a page can be found, quoted and acted on. It does not pretend to know what it deserves.
Q&A
SEO is being findable in a list of links. AEO is being the passage an answer engine quotes when it answers instead of listing. LLMO is a model understanding what your site is for at all, so it reaches for you on the right topic. They overlap, but a page can pass one and fail another, which is why they are scored separately.
Because a component can look correct and still compose into a page with two h1 elements. Crawlers receive the output, so the output is what gets checked.
No. Marking up questions a reader cannot see is a penalty from Google, not a shortcut, and the same is true of a rating that does not exist. If the audit wants an FAQ it asks for a visible one with real answers.
No, and any tool promising that is selling you something. The score measures whether the page is technically able to be found, quoted and acted on. Whether it deserves to rank is about what it says.
On every build, before you publish, and again on the published site. Each report is kept, so the score has a history rather than only a current value.
Yes. Dismissed findings stay dismissed and stop appearing in the report. A tool that keeps re-reporting a decision you have already made is a tool you learn to stop reading.
The audit runs on the preview, not as a report you request afterwards. By the time you decide to publish, you already know what it costs you.