Skip to main content

The AI visibility checklist: 33 checks, in scoring order

Every binary check that decides whether AI engines can fetch, parse, trust, and cite your site, organized by the nine sections of the audit rubric and ordered by weight. Work it top to bottom.

A clipboard of checklist rows with mint check squares filling in one after another
By Lars Nyman7 min readUpdated

1. Fetch, render, and URL integrity

The gate. If these fail, nothing below matters, which is why this section carries the heaviest weight in the score.

2. Bot access and control plane

Whether you have invited engines in or locked them out, sometimes by accident.

3. Off-site presence and mentions

What the rest of the web says. The hardest section to fake and the slowest to fix, which is why it starts now.

4. Structured data

The weakest dimension in the benchmark: the average audited site scores 49/100 here and a quarter score 5 or below, effectively shipping nothing.

5. HTML extractability and main content clarity

Whether a parser can pull clean text without fighting your markup.

6. Entity clarity

Whether a machine can tell who you are. Ambiguity here is how engines recommend your competitor while describing your product.

7. Trust and security

Accountability signals plus the security surface. Engines prefer recommending sites that look operated.

8. Content freshness and authority

The section where the benchmark's top decile separates hardest from the median: 32 points of gap.

9. Content answerability

Whether the writing is shaped so an engine can lift an answer.

Most sites do not lose AI visibility on the hard problems; they lose it on un-shipped basics that take an afternoon each.

How to work the list

Sequence by section, not by ease

A perfect FAQ on a JavaScript-only page is invisible perfection. Clear sections 1 and 2 before polishing 9.

Most items are afternoons

Of the 33, roughly two thirds are config or template changes. Off-site presence (section 3) is the only multi-quarter discipline.

Re-check quarterly

Deploys silently break checks; engine policies shift. The score is a maintained property, not a finished project.

What to do next

Run the free audit and let it mark this list for you, with your actual pass-fail per check and the fixes ranked by weight.

Frequently asked

Questions