Skip to main content
Google Business Profile

Persistent Google Business Profile Phone Verification Server Errors

Technical bug or anti-spam filter: Why the 'Sorry, we are having some issues' message is blocking local merchants.

By September 20, 20265 min read
Cover image for: Persistent Google Business Profile Phone Verification Server Errors
Cover image for: Persistent Google Business Profile Phone Verification Server Errors

Local business owners are reporting a disruptive Google Business Profile verification error that prevents the completion of phone-based authentication for new and existing listings. According to reports from the Local Search Forum (last updated September 18, 2024), users are encountering a persistent message stating, "Sorry, we are having some issues at the moment. Please try again later," before a verification code can even be dispatched.

This specific failure point differs from standard verification issues where a code is sent but never received. In these instances, the system fails internally, effectively locking the business out of its profile management capabilities for weeks at a time. We have observed this pattern affecting various sectors, from a dental practice in Leeds to a 12-location HVAC operator in the United States, suggesting the issue is not limited to a single geography or business category. For the multi-location HVAC operator, this meant that while 11 branches were active, the 12th remained in a state of limbo, unable to appear in the Local Pack despite having all legal documentation ready for review.

Why is the phone verification server error occurring?

While Google has not officially categorized this as a widespread outage, the symptoms suggest a conflict between Google's automated anti-spam filters and the verification gateway. The error frequently appears for Service Area Businesses (SABs) that have previously failed a video verification attempt. When the system reverts to phone verification as a secondary option, it seems to trigger a "dead end" in the verification workflow. This is not merely a case of the user entering the wrong digit; it is a failure of the Google server to initiate the outbound communication to the merchant.

Historically, verification options were more fluid, allowing users to toggle between postcard, phone, and email methods with relative ease. Currently, Google’s systems are increasingly rigid. Compared to the previous decade of local SEO where a postcard was the nearly universal fallback, the current environment relies heavily on AI-driven risk assessments. If a profile is flagged for high-risk activity—common among individual practitioners or home-based services—the system may technically "offer" phone verification while simultaneously blocking the API call required to trigger the SMS or voice call.

Identifying the root cause vs. a temporary glitch

For a 12-location HVAC operator, a temporary glitch might affect one branch due to a local carrier issue or a momentary drop in signal. However, when the error persists across different networks, devices, and user accounts, it points toward a backend database mismatch. In recent months, Google has tightened its verification requirements to combat the influx of fake listings, often resulting in "collateral damage" for legitimate businesses that happen to share characteristics with spam profiles.

In the cases reported, practitioners have ruled out standard troubleshooting steps. The error remains even when switching from a landline to a confirmed mobile number, or when removing suite numbers from the business address to simplify the data. Unlike the "too many attempts" error of the past, this server error appears to be a systemic rejection of the verification request itself rather than a rate-limiting measure. The dental practice in Leeds, for example, attempted verification across three different mobile networks and two desktop browsers, yet the server response remained identical, suggesting the block is tied to the Business Profile ID rather than the user's environment.

Google Business Profile phone verification not working for service providers

The phenomenon of Google Business Profile phone verification not working is particularly acute for service-based industries where physical storefronts are absent. Google's trust algorithms appear to place these businesses in a higher scrutiny bucket. When a plumber or locksmith attempts to verify a home-based office, the system often defaults to video verification. If that video fails due to a lack of permanent signage or professional equipment shown in the recording, the system may offer phone verification as a secondary path.

However, this secondary path frequently fails because the underlying "trust score" of the profile has already been compromised by the failed video attempt. Instead of providing a clear rejection, the interface displays the generic server error. This creates a loop where the merchant is told to try again later, but no amount of waiting will resolve an algorithmic lack of trust. To resolve this, we recommend that businesses ensure their phone number is registered exactly as it appears on their official website and other high-authority directories like Yelp or the Yellow Pages.

Google Business Profile verification error escalation strategies

When standard methods fail for more than 72 hours, agencies must move beyond the automated dashboard. The goal is to force the system to reset the available verification methods. We recommend documenting every failed attempt with timestamps and screenshots showing the specific "Please try again later" message. This documentation is vital when communicating with Google support representatives who may initially suggest the same troubleshooting steps you have already exhausted.

If the dashboard insists on a phone verification that will not trigger, the next step is often requesting a manual review. This is particularly critical for service-based businesses that lack a physical storefront, as they are often scrutinized more heavily by Google's automated integrity systems. In some cases, providing utility bills or business licenses through the official support channel can bypass the broken automated phone gateway entirely.

What this means for local businesses

For operators stuck in this verification loop, the path forward requires a shift from technical troubleshooting to formal support escalation. The following steps are recommended to break the cycle:

  1. Stop repeated attempts: Making more than two or three attempts in a 24-hour period can lead to a temporary IP or account block, further complicating the resolution and potentially flagging your account for suspicious activity.
  2. Verify data consistency: Ensure the phone number provided is not a VOIP or virtual number (like Google Voice), as these are increasingly rejected by the verification gateway. A traditional landline or a registered mobile number is preferred.
  3. Request a method reset: Contact Google Business Profile support via the official help tool to request that video verification be re-enabled or that the phone verification block be lifted manually by a support specialist.
  4. Document the workflow: Keep a log of every verification method offered and the specific error codes received to provide to the support team. This helps them identify that the issue is on their server side rather than a user error.

Sources

Frequently asked questions

What should I do if I keep seeing 'Sorry, we are having some issues' during verification?
Stop attempting the verification for at least 24 hours. Repeated attempts can trigger a security flag on your IP address or Google account. Instead, document the error with a screenshot and verify that your phone number is a standard mobile or landline, as VOIP numbers often trigger these server errors. If the problem persists after a day of waiting, you will need to contact Google Business Profile support to request a manual verification method.
Why does Google Business Profile phone verification fail for my business?
This failure is frequently caused by Google's internal risk-scoring system. If the system has high suspicion regarding the legitimacy of the listing—often due to the business category or a previous failed video verification—it may present the phone option while simultaneously blocking the server from sending the code. This results in a generic server error rather than a specific rejection message, leaving the merchant in a technical loop.
Can I use a Google Voice number for GBP verification?
We generally advise against using Google Voice or any other VOIP service for verification. Google's systems have become increasingly adept at identifying non-traditional phone services, and they often block these numbers to prevent spam. Using a VOIP number is one of the most common reasons the verification server fails to send a code. For the best results, use a number registered to a major cellular or landline provider.
How long should I wait before escalating a verification error to Google?
We recommend waiting no more than 72 hours. If the server error does not resolve itself within three days, it is unlikely to be a temporary glitch. At this point, you should gather your evidence—such as business licenses, utility bills, and screenshots of the error—and submit a support ticket. Ask the representative to reset your verification options or allow for a manual review via email or live video.

Follow us in Google

See Map Observer first in Top Stories

Google lets you choose the publications you want to see more of. Pick Map Observer and our local search reporting is surfaced higher in Top Stories — and badged as preferred in AI Overviews and AI Mode — whenever you search.

The Friday brief

What changed in local search this week.

A short, edited briefing every Friday for local SEO agencies, GBP specialists, and multi-location operators. Google Business Profile updates, Map Pack ranking shifts, reviews policy, and the AI Overviews / AI Mode moves that matter for local. Free, no spam.

Unsubscribe any time. We never share your email.

Related reading