Why Google says 'This phone number cannot be used for verification'
Google's most confusing sign-up error is a decision, not a glitch. Here is what the message really means in each context, how to diagnose it, and what legitimately helps.
By PhoneBorn TeamUpdated 7 min read
"This phone number cannot be used for verification" means Google has decided not to send a code to that number right now. It is not a network error. Usually the number has already verified many accounts, its type or history looks risky, or your attempts look automated. Waiting, fixing the format or using a number you keep usually helps.
Our step-by-step Google verification guide covers the whole sign-up flow. This article zooms in on one message: where it shows up, what each cause looks like, and a diagnosis order that avoids making things worse.
A decision, not an error
Most error messages describe something that broke. This one describes a choice. Before sending a verification code, Google evaluates the number and the attempt around it. If the risk looks too high, it refuses up front and shows the message instead of spending an SMS.
That has two practical implications:
- Retrying immediately rarely helps. The inputs to the decision have not changed.
- Google will not tell you which factor tipped it. You have to reason about it from the context.
Google's wording and screens change over time and differ between devices and countries. The patterns below reflect how the flow behaves as of 2026, not a fixed rulebook.
Where you might see it
The same sentence can appear in different places, and the context changes what it most likely means.
| Where it appears | What Google is doing | Most likely cause |
|---|---|---|
| Creating a new account | Checking the number before a first verification | Reuse limits, number type, automated-looking sign-up |
| Unlocking a flagged account | Asking you to prove you are human | Same as above, plus the account's own risk signals |
| Adding a recovery phone | Linking a number to your account for later | Number already linked widely, or type not accepted |
| Turning on 2-Step Verification | Setting up SMS as a second factor | Number type, or too many recent changes |
If the message appears when you are adding a recovery phone to an account you already use, the stakes are lower. You can add an authenticator app or passkey instead and try the number again later.
The six causes, and how to recognize each
1. The number has verified too many accounts
Google limits how many accounts a single number can verify, and does not publish the exact figure. A family phone that has already verified several accounts, or any number that has been passed around, can hit that limit. Sign: the number worked for you before but refuses now for a new account.
2. The number type is treated cautiously
Google, like many platforms, is careful with some internet-only number ranges and with numbers that cannot receive SMS. The explainer on real mobile vs VoIP numbers shows how a service can tell them apart in milliseconds. Sign: the number is refused immediately, every time, on a fresh device.
3. The number has a poor history
Numbers are recycled. If a number was previously used by someone else for many sign-ups or for abuse, it may carry that reputation. See the glossary entry on number recycling. Sign: a number you only just obtained is refused, while another from the same country works.
4. Your attempts look automated
Several accounts created from one device, very fast form-filling, privacy tools that make a browser look unusual, or a shared network where many people sign up can all raise risk. Sign: the error appears with several different numbers from the same setup.
5. You have made too many attempts recently
After repeated tries, Google may cool down the number, the device or both. The glossary on SMS rate limiting explains the mechanism. Sign: it worked earlier today and now refuses.
6. Formatting or country mismatch
Less common, but easy to rule out. A wrong country selector, a leading trunk zero or a missing digit can produce a number Google will not accept. Sign: the number looks slightly different from how it is written on your SIM or dashboard.
A diagnosis order that works
Go through these in order. Each step is cheap, and later steps depend on earlier ones.
- Check the format. Correct country selected, no leading zero, full number. Entering it in international E.164 format removes most doubt.
- Stop and wait. If you have tried more than two or three times, wait several hours, ideally until the next day. Repeated attempts extend cooldowns.
- Use a normal environment. A standard browser or the Google app on a phone you use every day, on your usual home or mobile connection. Avoid creating several accounts in one session.
- Try a voice call if offered. Some flows let you receive the code by call. It is still a check on the same number, but it avoids SMS delivery issues.
- Skip the phone step if possible. Google does not always require a number to create an account. If there is a skip option, you can verify later once the account has some normal history.
- Use a different number that is genuinely yours. A number that is only yours, that you will keep, and that has not verified a pile of other accounts.
What you should not do is cycle through lists of numbers, switch countries repeatedly or use tools meant to disguise your device. Those behaviors are exactly what Google's checks are designed to catch, and trying to get around them breaks Google's terms.
Why the number you choose matters later
Getting past the error is only the start. Google uses the number you verify with in several later moments:
- Recovery if you forget your password.
- Confirmation when you sign in from a new device or location.
- SMS codes, if you pick SMS for 2-Step Verification.
If you verify with a number you give up a month later, all three routes quietly break. Our guide to keeping your number for 2FA explains how people lose access this way, and why a number you keep is worth more than one that gets you through the form.
Protect the account while the number is refused
If the error appears on an account you already use, for example when adding a recovery phone, you do not have to leave the account unprotected while you sort out the number. Google offers other ways to secure it:
- Passkeys. On supported phones and computers, a passkey lets you sign in with your screen lock. Nothing is sent by SMS, so the number's status does not matter.
- Authenticator app. Codes generated on your own device work offline and are not affected by SMS routing or number checks.
- Backup codes. Print or safely store the one-time codes Google lets you generate. They are the last resort when every other method fails.
- Recovery email. Make sure it points to an inbox you will keep.
Once those are in place, a phone number becomes one recovery option among several rather than the only way back in. You can return to the phone step later, after the cooldown has passed, without any rush. It also means a future problem with the number, such as losing a SIM abroad, will not lock you out. Our guide to keeping 2FA working when you travel covers that scenario.
Where PhoneBorn fits
If your own number has hit Google's limits, or you want a separate number for a work or project account, PhoneBorn offers real mobile numbers assigned to one customer at a time. You keep a plan number as long as you renew, and read incoming codes in a browser. For one-off codes there are single-use OTP numbers, which are refunded automatically if no code arrives. Google makes its own decision about every number, so every plan is backed by a 7-day replacement guarantee: if you see “This phone number cannot be used for verification” within 7 days of purchase, replace the number free from your dashboard with a new one from the same country. For an account you will keep, a plan number is the better fit; see our Google verification page and phone numbers for verification for the options.
FAQ
How long should I wait before trying again?
There is no published figure. Waiting several hours, and ideally until the next day, is a sensible rule. Each extra attempt during a cooldown tends to prolong it.
Does the error mean my account is banned?
No. It refers to the number in that moment. Your account, if you already have one, is not affected by a refused verification attempt.
Can I remove my number from an old account to free it up?
You can remove a number from accounts you control in their security settings. Whether that frees it for a new verification is Google's decision, and it may not happen immediately.
Does a voice call get around the error?
Not reliably. If Google has refused the number itself, the call option is usually refused too. A call helps mainly when SMS delivery, not the number, is the problem.