How do you prove AI search visibility to a client?
How to prove AI search visibility to a client: record what shipped, check it independently, and show the tracked question before and after per engine.
Proving AI visibility means recording what shipped, checking it independently, and showing the same tracked question's answer on each engine before and after. Inciteful's Proof does exactly that, and states what was measured after the work. It never states that the work caused it. That distinction, not a single screenshot, is what makes a client report defensible.
Record what shipped before you claim anything moved
Start with the page itself, not the metric. Proof lists every page shipped for a client, however it was made: reported automatically by the agency's AI coding tool through the AEO Boost, or entered by hand with the page's URL and the question it answers. Without a recorded page, there is nothing for a later number to be measured against.
Check the page independently of the tool that shipped it
A page being live in a CMS is not the same as a page being live on the internet. Proof runs its own check: status, redirects, host and canonical, and whether the page actually answers the question it was built for. Both checks run independently of the tool that shipped the page, the way our methodology describes.
Show the tracked question's answer on each engine, before and after
This is the evidence a client can follow without trusting a summary. Proof freezes the tracked question's answer on each engine from before the page shipped, then shows the same question's answer since. Where AI traffic is connected, a verified AI crawler visit and a citation of the exact page sit alongside it. A visit counts as verified when it comes from an address the vendor publishes: OpenAI and Perplexity both list the IP ranges their crawlers use. Where it is not connected, crawler visits show as not measured, and the rest of Proof still works.
What Proof checks, and the limit of each one
| What is checked | What it shows | What it does not show |
|---|---|---|
| Reachable | An independent check of status, redirects, host and canonical: the page is live where it says it is | That any AI engine has read it yet |
| Answers its question | The page's own content answers the tracked question it was built for | That an engine has cited it |
| AI crawler seen | A verified fetch from an AI vendor's own address, when AI traffic is connected | That the fetch became a citation |
| Cited | The exact page appears as a source in a later tracked answer | That the page caused a rival to drop out |
| Question before and after | The same tracked question's answer on each engine, frozen before the page shipped and shown since | That the page caused the change; only that it was measured after |
Proof's own checks, current as of 20 September 2026.
Say what was measured after the work, never what caused it
An answer can change for reasons that have nothing to do with the page that shipped. Proof states what was measured after the work. It never claims the work caused it. That line, not a bigger number, is what a sceptical client is actually asking the agency to hold to.
Put the evidence where the client can check it themselves
None of this is useful locked in a file only the agency can read. A client report carries the same tracked questions, sources and Proof checks as the dashboard, under the agency's own name on Pro and Agency, or with a small Inciteful badge on Solo. The client can open the report and see the same evidence the agency is describing, not only the agency's summary of it.
What clients ask when they see the report
Is a screenshot enough to prove AI visibility?
A screenshot is useful alongside the record, not instead of it. Pair it with the exact question, the engine, the date and the sources behind the answer. On its own it does not show whether that answer was typical or a one-off.
Can server logs alone prove a page changed an answer?
No. Server logs, when AI traffic is connected, show that an AI system's own address fetched the page. That is a verified visit, not a citation. Proof keeps the fetch and the citation as separate checks, and only the tracked question's answer shows whether a citation followed.
Does Inciteful say a shipped page caused a citation?
No. Proof states what was measured after the work: the tracked question's answer on each engine, before the page shipped and since. It never states that the page caused the change, because answers can move for reasons that have nothing to do with any one page.
Who does the writing: the agency's tool or Inciteful?
The agency's own AI coding tool, using the AEO Boost's fix list, working in the client's repository or CMS. Inciteful's Agent reads a client's measurements and suggests what to win next, but it never writes or publishes a page itself.
What happens if AI traffic is not connected?
Crawler visits show as not measured. Everything else in Proof, the reachable check, whether the page answers its question, citations, and the tracked question before and after, still works without it.
Can the client see the evidence themselves, not just a summary?
Yes. A client report carries the same tracked questions, sources and Proof checks as the dashboard, hosted at a private link, white-label on Pro and Agency. Nothing in the report is a number without the answer behind it.



