If your Local Services Ads account shows an access error or an unexpected Business Profile link, record the exact symptom before changing connections or creating another account.
Check three things separately: who can sign in, which profile the account shows and whether the office can see and respond to leads. A problem in one place does not establish that every part has failed.
What the September report actually established
In a public September account report, advertiser Jack Hepp described a profile disconnection and intermittent LSA access errors. Google's Ads Liaison Ginny Marvin replied that Google had identified a bug and was working on it, separately saying it was unrelated to the migration.
Search Engine Roundtable's report also said the exact issue covered by that confirmation was still being checked. Those statements do not establish that all disconnections, access errors and reporting problems had one cause.
For a Canadian advertiser reviewing an error today, this is historical context. It is not proof of a current Canadian outage or the diagnosis for your account.
Confirm the intended account and user
Open the account through your normal signed-in route. Check the account identity and the user who is meant to manage it.
If another authorised person has a different view, record that difference. It may help distinguish an individual access problem from an account-wide issue.
Do not share passwords, invite extra users or grant broader access as a speculative fix. Use the normal account-management process if an actual permission issue is identified.
Capture the link state you can actually see
Record the connected Business Profile shown in the account, any warning text and the time observed. Save a screenshot privately with the relevant account identifiers.
A similar business name is not enough to confirm the right profile. Compare the specific account and profile references you already use to manage the business.
Document the visible connection and error before changing settings.
Check the effect on ordinary work
Ask the office whether new enquiries are arriving and whether staff can access the records needed to respond. Keep what people observed separate from a conclusion about the cause.
A fall in calls does not, by itself, prove an unlinking problem. An unavailable dashboard also does not tell you which charges or lead records were affected.
Preserve the reports you can access, with their periods and capture dates. Handle customer information through the business's approved storage arrangements.
Give support a precise case
Prepare a short record with:
- The affected account and Business Profile references.
- The exact error or unexpected link state.
- When it last worked and when the issue was observed.
- The authorised users and surfaces checked.
- The operational effect you confirmed.
- Any changes already made and the existing support reference.
Ask official support to identify the issue affecting that account and the next action. Keep the actual response and outcome. Avoid opening duplicate cases or repeatedly unlinking and relinking while the cause is uncertain.
Keep migration questions separate
Google's current migration guidance lists non-US accounts for 2027. Follow your own account's notice. Do not treat an access error as evidence that a Canadian account has migrated.
If support recommends a consequential setting or access change, have the authorised account owner review it before applying it.
Confirm the recovery you need
After a fix, verify the account, profile connection and enquiry handling again. Record which parts are confirmed and which still need attention. A support message saying “resolved” is useful context; the office still needs a working route for actual enquiries.
For help reviewing the account and lead handoff, learn more about Local Services Ads management. Tell us the exact symptom and what support has already confirmed.