Google acknowledges an LSA bug after reports of account disruption

What changed

Jack Hepp's original LinkedIn post describes an LSA account becoming disconnected from its Google Business Profile, followed by intermittent errors and an inability to find the account in associated Google Ads accounts. He said support had helped restore the profile connection. Those are observations from his accounts, not a published estimate of the number of advertisers affected.

In the accessible comment thread, Ginny Marvin said Google had identified a bug and was working to resolve it, and explicitly separated it from the LSA migration. Barry Schwartz's Search Engine Roundtable report preserves the same distinction and says the exact issue covered by that confirmation was still being checked. The available statements do not establish that all access failures, profile disconnections and migration questions had a single cause.

For an affected business, keep three checks separate: who can sign in, which Business Profile is connected, and where the LSA activity is visible. Repeatedly changing account links while troubleshooting can make a before-and-after record harder to interpret. Our suggested response is to document the specific symptom and seek an account-level answer before treating a migration announcement as its explanation. The linked report is a record of the incident, not confirmation that the problem remains active today.

Why it matters for advertisers

Access disruption can obscure lead handling even when the underlying advertising account still exists. The immediate business question is whether staff can see and respond to leads, rather than whether a dashboard is merely slow. A precise support case should separate that operational effect from assumptions about the migration.