Someone Can Remove Your Firm From Google's AI Answers in Two Clicks

On August 31, Google finished a rollout it had been running quietly since June. Three separate Google documents — the Search blog, the Search Central developer blog, and a Search Console help page — each picked up the same new sentence: "As of August 31, 2026, we've rolled out this control to all websites worldwide."

The control is a toggle in Google Search Console. It decides whether your site is allowed to appear in, and help ground, Google's generative AI features: AI Overviews, AI Mode, and AI Overviews in Discover. It shipped first to a subset of UK site owners on June 3. As of the end of August it exists on every property on earth, including your firm's.

Most immigration practices have never opened Search Console. A good number could not say who at their firm — or outside it — currently has access.

What the switch actually does

Google's language is unusually blunt for a product announcement. Sites that opt out "will not receive traffic or impressions from our generative AI features." Not reduced. None.

The second half matters just as much: Google states the control is not used as a signal for search results outside those generative AI features. Flip it off and your ordinary blue-link results are untouched. Your pages still show up where they always did. You simply stop existing inside the AI answer sitting above them.

That asymmetry is the whole problem. There is no error page, no drop in your traffic dashboard that screams misconfiguration, no email to the managing partner. The site looks identical. Someone searching your firm by name still finds you. What disappears is the layer where a stranger asks a question — can I file for adjustment of status while my H-1B extension is pending — and an engine composes an answer out of a handful of sources.

Google reports AI Overviews now reaches over 2.5 billion monthly users and AI Mode has passed one billion. That is the surface the toggle governs.

This is an access problem, not a marketing problem

Think about who has touched your firm's Search Console property over the years. The web developer who built the site in 2019. A marketing contractor from a two-month engagement. A former intake coordinator who set up analytics and then left. Possibly a consultant hired precisely because they were worried about AI companies using firm content.

Any of them, if still listed as a user with the right permission level, can flip this switch. And a privacy-minded advisor might genuinely believe they are doing you a favor — the control was built in response to publisher demand and regulatory pressure from the UK's Competition and Markets Authority. Opting out is a legitimate choice for some businesses. It is a catastrophic default for a practice that depends on being found by people who do not yet know its name.

The realistic failure mode is not sabotage. It is a well-meaning person making a defensible-sounding decision on a property nobody at the firm actively owns, and no one noticing for two quarters.

The half nobody is talking about

The same rollout included something more useful: a generative AI performance report inside Search Console. It shows impressions, which pages appeared, and breakdowns by country, device, and date for your content inside AI responses.

Note the omission — there is no click data. Google has said it will add metrics over time. So this is not yet a full picture of what AI visibility returns to your practice. It is, however, the first time a small firm can answer the basic question at all: do our pages appear in AI answers, and which ones?

Until now that question required a third-party tool and a fair amount of inference. Now it is a report in an account you already have the right to claim.

Do this week

1. Confirm the firm owns the property. Log into Search Console. If nobody at the firm can, verify the domain fresh — DNS TXT record, ten minutes with whoever controls your registrar — and make a named attorney the verified Owner.
2. Audit the user list. Settings → Users and permissions. Remove every person and agency no longer working with you. Write down who remains and why.
3. Check the toggle. In Settings, find the generative AI control and confirm your site is opted in. Screenshot it with the date visible.
4. Pull a baseline from the AI performance report. Export the last three months of impressions and the page-level breakdown. You cannot tell later whether something changed if you never recorded where you started.
5. Note which pages appear. If your practice-area pages are absent while a thin FAQ page shows up, that is a content signal worth acting on separately.
6. Put it in the vendor agreement. One clause: no changes to Search Console settings, permissions, or AI controls without written approval from a named partner. This costs nothing and closes the gap permanently.
7. Calendar a quarterly recheck. Fifteen minutes. Same four screens.

An hour total, most of it waiting on DNS.

The shape of the risk has changed

For two years, visibility inside AI answers was something that happened to your firm. There was no dial, no documentation, no account setting — only guesswork about what the models had absorbed and whether your pages were among it.

That era ended on August 31. There is now a documented control surface with an explicit on and off, and a report telling you which side you are on. That is a real improvement; opacity was worse.

But it moves the risk. When there was no switch, no one could throw it. Now the plausible way an immigration practice vanishes from AI answers is not that it was never interesting enough to cite. It is that a setting nobody was watching got changed by someone who no longer works there.

Fifteen minutes in an account you may never have opened is a strange thing to call urgent. This week, it is.

Clientory helps immigration law firms become visible to the families and individuals who need them most — turning AI search into consultations, and consultations into clients.

Check who has access to your Search Console property today. Then check the switch.