Google Business Profile Suspension Bug: What Changed and How to Handle Reinstatement
In October 2022, local businesses and marketers reported a sharp rise in Google Business Profile suspensions after routine edits. Google later confirmed the bug had been fixed, but reinstatement requests were still taking weeks. This guide explains what happened, how to tell a normal reinstatement reply from the bug loop, and how to prepare a stronger case if a profile is suspended.
What the suspension bug did
During the affected period, actions that would normally be low-risk could trigger a suspension. Reported triggers included pressing verify, adding website parameters, editing hours, descriptions, names, categories or addresses, and marking a profile temporarily closed. The pattern was not limited to obvious policy breaches.
Ben Fisher, a Google Diamond Product Expert and owner of Steady Demand, described the change as a rise in false positives. Normally an edit might wait for review, be accepted, require re-verification or cause a suspension. During the bug window, the suspension outcome became far more common for small changes.
Google confirmed on the afternoon of Friday 21 October 2022 that the bug causing small edits to trigger suspensions should be resolved. That fix applied to the trigger, not to the backlog of reinstatement requests already in the queue.
How the problem appeared in practice
The practical effect was that ordinary profile maintenance could put a client relationship at risk. Harmony Huskinson of Portent described a client profile being suspended during a screenshare while a primary category was being updated. Another client needed UTM parameters added to URLs, but that work was paused until the bug was fixed. At the time, one reinstatement had been waiting around three and a half weeks, and some reports suggested waits of up to six weeks.
Ashley Romer of PaperStreet described a client with multiple locations whose new location was suspended immediately after it was added. A reinstatement request had been submitted and followed up, but the case was still unresolved in the fourth week. For smaller law firms in particular, a long absence from the local listing can create real business strain.
Normal reinstatement replies versus the bug loop
Tim Capper, a Google Platinum Product Expert and owner of Online Ownership, drew an important distinction. A long wait for a reinstatement decision was not itself the bug. The bug affected what happened when a response arrived.
A normal response either asks for more information about the business or confirms that the profile can be reinstated with no further action required. The non-standard responses seen during the bug were different: a case being sent to a specialist, or a message saying the profile is live and verified even though it is not when checked.
While the bug was active, replying to either non-standard message produced the same response again a few days later. That repeating pattern is better understood as a reinstatement loop. The progress status could also refresh when a non-standard response arrived, which made it look as though a person was reviewing the case when that was not necessarily true.
The table below is a reader aid for distinguishing the two situations. It is not a Google contract and does not guarantee a response time.
How long reinstatement was taking
The captured evidence from October 2022 described a slow queue. Tim Capper put the response time at around 25–30 business days. Stefan Somborac of Marketing Metrology reported that US submissions were taking three to four weeks, while a Canadian case was resolved in two weeks and an Australian case in less than one week. He suggested patience and suspected a regional factor.
Amy Toman, a Google Gold Product Expert, said most reinstatements were seeing around four weeks in her experience, though this was not a formal Google figure and some cases moved faster. Elizabeth Rule of Sterling Sky described an average wait of 22 days or longer. These are dated observations from the period, not current service levels. Check the latest guidance and your own case status before relying on any timeline.
How to prepare a stronger reinstatement request
The consistent advice was to treat the reinstatement request as a case to be proven, not a quick form to submit. Because responses were slow, a weak first submission could cost weeks.
Use this pre-submission checklist:
- Identify the likely reason for the suspension and correct the underlying issue before submitting.
- Check that the profile complies with Google's guidelines.
- Make sure the supporting paperwork is consistent and correct.
- Provide a thorough explanation with documentation showing that the business is legitimate and located where it says it is.
- Avoid relying only on the argument that the profile has been verified for years. Definitive proof is more useful.
- Keep the case ID and progress status to hand when following up.
Elizabeth Rule noted anecdotally that businesses with substantial proof of legitimacy and location seemed to see quicker action than those with little proof. Amy Toman made the same point from the other direction: sending Google the information it needs at the start should shorten the process.
Reducing the risk of future suspensions
Joy Hawkins of Sterling Sky said her business had not been affected by the suspension bug and was proceeding normally with clients. Her advice for limiting risk was to avoid making many major changes at once. Business name, phone number and website changes should not all be submitted together.
In spam-sensitive industries such as locksmiths, drug rehabilitation or personal injury law, she advised extra care. Adding attributes, a business description and changing categories at the same time could trigger a suspension. Spreading the work out and making one or two edits at a time is safer.
A worked example: the same edit, two different outcomes
Imagine a multi-location law firm adding a new location during the bug window. The profile is created and the verify step is pressed. In normal conditions, that might lead to a review, an acceptance, a re-verification request or a suspension. During the bug, the suspension outcome was far more likely.
The firm submits a reinstatement request with the case ID, proof of the location and a clear explanation of the business. If the reply asks for more information or confirms reinstatement, the case is following the normal path. If the reply says the case is being sent to a specialist, or claims the profile is live and verified when it is not, the case may be in the bug loop. Replying to that message and receiving the same answer again a few days later is the signal to stop treating the progress refresh as human review and to focus on the quality of the evidence already submitted.
Key takeaways
- The suspension bug was confirmed fixed on 21 October 2022, but reinstatement delays continued.
- Small edits and even the verify action could trigger a suspension during the bug window.
- A long wait was not the bug. The bug showed up in the type of response and in repeated non-standard replies.
- A normal response asks for more information or confirms reinstatement. A non-standard response mentions a specialist or claims the profile is live when it is not.
- Prepare a thorough, documented case before submitting, and keep the case ID and progress status available.
- Avoid stacking major profile changes, especially in spam-sensitive industries.
- The timelines in this guide are dated observations from 2022, not current guarantees.
| Signal | Normal path | Bug-loop pattern |
|---|---|---|
| Reply content | Requests more information about the business, or confirms reinstatement with no further action | Says the case is being sent to a specialist, or claims the profile is live and verified when it is not |
| What happens after you reply | The case moves forward or you provide the requested information | The same response arrives again a few days later |
| Progress status | Reflects the case state | May refresh when a non-standard response arrives, creating a false impression of human review |
| What to do | Supply the requested information and keep the case ID | Check the evidence already submitted and avoid treating the refresh as progress |
Dated reference from October 2022. Response wording and case handling may differ now.
Frequently asked questions
Was the suspension bug the same as a slow reinstatement?
No. The bug caused small edits to trigger suspensions. The slow queue for reinstatement decisions was a separate delay. The bug showed up in the type of response a case received and in repeated non-standard replies.
What should I do if I receive a message saying my profile is live and verified but it is not?
Treat it as a non-standard response. Check the profile directly, keep the case ID and progress status, and review whether the evidence in the reinstatement request is complete and consistent. If the same response repeats after you reply, the case may be in the reinstatement loop described in the dated evidence.
How much proof should I include in a reinstatement request?
Enough to show that the business is legitimate and located where it says it is. Consistent supporting paperwork and a clear explanation are more useful than a long history claim without documentation. The expert advice in the captured evidence was to prepare thoroughly before submitting because responses were slow.
Can I keep editing my profile while a reinstatement is pending?
The safer approach is to avoid stacking major changes. During the bug window, experts advised limiting edits to what was critical. For future maintenance, make one or two changes at a time rather than changing name, phone, website, categories and description together.