Local Businesses And The AI Recommendation Problem

These names go directly into the prompt set and into any comparison content, and getting them wrong sends the entire measurement effort in the wrong direction. If you lose to a low cost regional operator rather than to the market leader, say so.

Absence is not disqualifying on its own, since their category is crowded and they may serve a niche. But they should have an interesting answer, and the answer should not be defensive. A practitioner who has run this test on themselves will have thought about it and will tell you what they found.

A bot management product quietly challenging retrieval agents produces exactly this symptom: competitors named, you absent, no error visible to anyone internally. It is worth ten minutes of checking before anybody writes a content plan.

Ask to See Their Own Position This one is unfair and revealing. Ask an assistant to recommend an agency for ai overviews optimization this kind of work, using a prompt a buyer would write, and see whether the company sitting in front of you appears.

The Rendering Question This is the one real technical constraint. Content that only exists after JavaScript executes may be invisible to a retrieval fetch, which is not a browsing session and does not always run scripts.

Then add the structural markup, then check the whole thing with a reader in mind rather than a crawler. If a page has become harder for a person to use, something has gone wrong and the change should be reversed.

Ask What Happens in Month One A proposal that opens with content production has skipped the diagnosis. There is no way to know what to write before you know which questions matter, which assistants answer them badly and which sources they draw on.

The useful move here is to stop auditing yourself and start auditing them. When a competitor is consistently named and you are not, the answer is sitting in plain sight in the citation list, and it is usually not what the brand expects.

Assume the pitch is good. Everyone's pitch is good, and the vocabulary in this field is easy enough that a competent salesperson can hold a convincing conversation without anyone behind them who can do the work.

Ask How They Price It Retainers dominate this field and mostly make sense, because the work is continuous and the third party portion is slow. What matters is what the retainer covers and whether the scope is written down in units you can count.

Build the Task List From What You Found The teardown usually produces four workstreams, in this order of cost: fix any access problem, claim and correct your listings on the recurring sources, rewrite your equivalent pages to lead with specifics, and start the slower work of earning coverage on the sources where you cannot simply claim a profile.

Being missing from the five pages that generate your category's answers is a complete explanation on its own, and it is fixable without anyone's permission on the platforms that accept claims and corrections.

Finally, be prepared for the teardown to produce a finding nobody wants. Sometimes the competitor is genuinely better documented because they have been answering customer questions in public for years while your team answered them on the phone. There is no shortcut around that, and the only useful response is to start doing the same thing now rather than looking for a technical explanation that would be easier to fix.

They will not quote statistics without sources, and they will not present a tool's sampled estimate as a count of what happened. If none of these boundaries come up unprompted, ask directly and listen for whether the answer sounds rehearsed or considered.

The answer you want describes a baseline: a prompt set built from how your customers actually speak, run across the assistants that matter, with raw answers and cited sources recorded. Everything after that should be justified by reference to what the baseline showed.

It is also worth doing while your category is boring. An audit run during a period of stability produces a clean baseline. One run in the middle of a competitor's campaign or immediately after a site migration measures the disruption rather than the position, and you will not know which you have unless you took the earlier reading.

Ask how they will handle being wrong. Every engagement in this field produces at least one confident recommendation that does not work, because the systems change and the published research is thin. What matters is whether that gets reported or quietly dropped from the next deck, and asking the question directly at the outset makes it considerably more likely to be reported.

The Argument Against Waiting The usual counterargument is that assistant traffic is still small in most categories, which is often true. But the audit is not primarily about capturing that traffic. It is about finding out whether you are mechanically invisible, whether your identity is coherent, and which third party pages your category's answers are built from.