How To Audit Whether AI Recommends Your Brand
Most engagements are judged too late, on a final outcome that arrives after the point where anything could have been corrected. The first quarter has its own deliverables, and knowing what they are lets you tell early whether you have hired the right people.
Set Up So You Do Not Fool Yourself Open a signed out session, or a fresh one with memory and personalisation disabled. This matters more than anything else in the method. An account that has spent the week researching your own company will show you a flattering picture that has nothing to do with what a stranger sees.
One preparation step is worth the effort. Before the meeting, check whether anyone in the business has already noticed something relevant: a customer who mentioned an assistant, a support ticket citing wrong information, a salesperson who was asked about a competitor comparison they had not seen. Internal anecdote carries disproportionate weight because nobody can dismiss it as vendor material.
Save the document and the date. In three months you will run the same ten prompts again, and the comparison is the only thing that will tell you whether anything you did in between mattered. where to find a good ai seo services company
Ask for a Small, Bounded Commitment Do not ask for a year. Ask for one quarter with a defined scope: run the baseline, fix access problems, correct the listings on the sources that appeared, publish two pages that answer the questions your baseline showed were answered badly.
Show the Cheap Failures First Before asking for a programme, ask for permission to check whether you are readable. Crawler access, rendering without JavaScript, listing accuracy on the sources your prompts cited.
Frame It as Insurance Where Appropriate For businesses whose category shows light assistant use, the honest framing is not growth. It is that the cost of entering rises as third party coverage fills in, and that a baseline taken now is what will let you attribute any future decline.
Bring one other person from the business, ideally from sales. They will spot inaccuracies in how you are described that a marketing reader skims past, and they will tell you within minutes whether the prompts sound like real customers. That second opinion costs half an hour and prevents the most common flaw in a self run audit, which is a set of questions written in the company's own language.
You asked it to recommend a supplier in your category. It named four companies, two of which you consider inferior to yours, and one you had never heard of. Your name did not come up, and it did not come up on the follow up question either.
Assistant measurement is not there yet. There is no console reporting how often you were named, answers vary between sessions and accounts, and referral traffic is attributed inconsistently across assistants. The honest approach is a fixed prompt set run on a schedule, with the raw answers kept, and any tool metric attributed to the tool that produced it.
Those recurring domains are the pages your category's answers are being built from. Visit each one, look for yourself, and note whether you are absent, listed with stale details, or filed under the wrong category. That list is your task list, and you did not have to guess at it.
One warning about testing. If you fix something and immediately re-run a prompt in the same session, the assistant may repeat its earlier answer from context rather than retrieving afresh. Start a new session, and run the prompt several times, before concluding that nothing changed. where to find a good ai seo services company
Freshness Counts More Than You Expect Because retrieval happens at answer time, a page published or updated this week can be cited this week. This is a meaningful difference from ranking systems where authority accrues slowly.
One thing to establish in week one is where everything lives. The prompt set, the baseline archive, the raw answers and the correction log should sit somewhere you control from the beginning rather than in the agency's systems. Retrieving them later is a negotiation. Having them from the start is an administrative decision nobody objects to at the outset.
This frequently produces the first result of the engagement, because access failures are total and fixing them can change answers within days. It should also be short. A fifty page technical audit at this stage is usually padding drawn from a generic template.
Check your robots file, then check your server logs for the relevant agents and see what status codes they receive. A site that returns a challenge to every non-browser request is invisible to this entire channel, and nobody involved will have thought of it as a marketing decision.
The difficulty with this proposal is that it asks for money before the problem is visible in any report the business already trusts. That is a genuinely hard sell, and overselling it is the fastest way to lose credibility when the numbers stay small for two quarters.
Perplexity is unusually useful to study because it shows its working. Every answer arrives with numbered citations you can click, which means you can reverse engineer what it rewards without guessing. Most assistants hide this. Perplexity puts it on the page.