Ship the fix. Then prove what moved.
Proof of the AEO work you ship: every page in one list, checked independently, with its question before and after, engine by engine.
Trusted by
“The workflow is great. We’re not technically minded, so having the Agent able to check site health and assist in executing the changes is incredibly productive for us. We grew call bookings by around 30% in the first month.”
How do you prove AEO work? In plain words.
You prove AEO work by recording what shipped, checking it independently, and measuring the same questions before and after. Proof lists every page shipped for a client, confirms it is live and answers its question, and shows that question on each engine before the page shipped and since.
It is the retainer conversation, with evidence.
- ChatGPT
- Google AI Overviews
- Perplexity
- Copilot
- ClaudeGeminiGoogle AI ModeAdd-ons
It reports itself. Then we check it.
- 01
Your AI tool ships a page
Claude Code or similar, in the client’s own repository or CMS.
- 02
It reports the page back
An authenticated call with the question’s token and the URL.
- 03
Two independent checks
Is it live, does it answer its question, is it on the client’s own host.
- 04
It appears in Proof
With the question’s baseline frozen from before it shipped.
What you shipped. What was measured after.
- For the retainer conversation
- Pages shipped, reachable, seen by AI crawlers, cited, and the question now named.
- You choose what the client sees
- Nothing appears in the client report until you pick it.
- However the page was made
- Reported by your AI tool, or recorded by hand.
PlanOn every plan. The AEO Boost that reports pages for you is on Pro and Agency.See pricing
Before and after. Engine by engine.
What moved, after the page shipped.
When a page ships and visibility then moves, Proof shows what was measured after it, question by question and engine by engine.
- A three-run verdict, with its basis
- “No run yet” when there is nothing to compare
- Crawler visits read “not measured” without AI traffic connected
- Pages shipped
- Whatever recorded them: your AI tool, a page pasted in by hand, or a retrofit.
- Reachable
- An independent check of status, redirects, host and canonical.
- AI crawler seen, page cited
- Visits since it shipped, and citations of that exact page.
- You choose what the client sees
- Nothing appears in the client report until you pick it.
Questions about Proof, answered plainly.
How do you prove AEO work to a client?
To prove AEO work, record the page that shipped, check it independently, and show the tracked question before and after on each engine. Proof does all three, and states what was measured after the work.
Why “measured after” and not “caused by”?
Because an answer can change for reasons that have nothing to do with your page. Proof reports what was measured after the page shipped, with a three-run verdict and its basis, and leaves the causal claim out.
What is checked on each page?
Whether it is reachable, with an independent check of status, redirects, host and canonical. Whether it answers its question. AI crawler visits since it shipped. Citations of that exact page. And its question before and after, per engine.
Do I have to use the AEO Boost?
No. A page can be recorded by hand: paste the published page and, if you like, the tracked question it answers.
What if AI traffic is not connected?
Crawler visits read “not measured”. Everything else in Proof works as normal.
What goes into the client report?
Only the pages you choose. Each page has a “Show in the client report” control, and nothing appears until you use it.
