A Realistic Timeline For AI Visibility Results
This variability is the main practical trap. Testing without web access and concluding you are invisible measures the training corpus rather than current retrieval, and the two can disagree sharply. Record which mode you used with every run.
Three to Nine Months: Earned Coverage The slowest and most valuable part. Getting into the comparison articles, trade publications and community discussions that assistants actually cite depends on other organisations deciding to write about you, which no amount of budget reliably accelerates.
Weeks: Your Own Pages A rewritten page that answers a question directly can be retrieved and cited within weeks, sometimes faster. Freshness carries real weight here because retrieval is live, so a page updated this month competes on current terms rather than waiting to accumulate authority.
Expect the shape of progress to be uneven rather than gradual. Nothing appears to move for weeks, then several things change at once as a batch of corrected sources is re-crawled. Teams reading a flat month as failure tend to intervene precisely when the earlier work is about to land, which is why the checkpoints matter more than the weekly readings.
What can legitimately be committed to is process: the prompt set will be run on a schedule, the raw answers will be kept, specific technical fixes will be made by a date, a defined number of third party listings will be corrected. Commitments about inputs are honest. Commitments about outputs are not.
Two implications follow regardless of which system you are studying. Being findable by the underlying search step is necessary, and being worth quoting once fetched is what decides whether you are used. Almost everything actionable sits in those two requirements.
Ask to See a Prompt Set The first question is the most revealing. Ask them to show you the prompt set from a current or recent client, with the client's name removed. A team doing real work has this and will show it, because the prompts are craft rather than secret sauce.
Gemini and Google Surfaces Closest to conventional search infrastructure, which has a practical consequence: work that improves your standing in Google search tends to carry over here more than it does elsewhere.
One practical consequence of the variation between systems is worth planning for. If your customers are split across two assistants that behave differently, resist building separate programmes for each. The shared requirements account for most of the achievable outcome, and the effort spent on system specific tactics is usually better spent widening the number of third party sources that describe you correctly.
When to Change Supplier Three conditions justify it individually. Raw answers cannot be produced on request. The prompt set has been changed without disclosure, which invalidates every comparison in every report you have received. Or two quarters have passed with the agreed inputs completed and no movement on citation presence, accuracy or source coverage.
Ask what was done, not what happened. If listings were corrected, pages rewritten and outreach attempted, and the numbers are still flat, that is information about the market. If none of it happened, the numbers were never going to move.
An agency doing the work sends these the same day, because they already exist as a by-product of the measurement. One that does not will explain that the platform does not export in that format, or that the data is summarised in the dashboard.
The Shared Architecture All three now commonly retrieve live sources rather than answering purely from training. Your question becomes one or more searches, a set of pages is fetched and read, and the answer is composed from what was read.
There is a variant of this worth checking separately. Sometimes you appear and the competitor appears above you, which is a different problem from being absent. In that case compare the specificity of the two descriptions rather than the sources: the company described in concrete terms tends to be listed first, because a specific description is easier to justify than a general one.
You will find your own category's pattern, which frequently contradicts the general one. Some industries are dominated by a single trade directory. Others are dominated by one forum. That specific finding is worth more than any general description of how these systems behave.
Before leaving, make sure you take the prompt set, the baseline archive and everything published. If those were not yours under the contract, that is a lesson for the next agreement rather than something to negotiate at the exit.
Discontinued products deserve deliberate handling rather than deletion. Removing a page severs the connection between existing reviews and ai overviews optimization coverage and your catalogue, and it leaves stale third party listings pointing at nothing. Keeping the page, marking it clearly as discontinued and naming the replacement preserves the accumulated evidence and redirects the recommendation rather than losing it.