Google on a virtual number: what gets through the check, and the number you must not lose

The short version

Three things set Google apart from every other service in this catalogue. It is the only one that may not ask for a phone number at all, so the first move is not buying a number — it is finding out whether you need one. When it does ask, it screens harder than WhatsApp, and the refusal arrives before any SMS is sent, which is why retrying the same tier changes nothing.

The third difference is the one that costs people accounts. Google keeps asking. A Telegram session survives on its own and WhatsApp only re-verifies on a reinstall, but Google re-challenges the number on a new device, from a new country, or on any sign-in its own systems find odd — sometimes a year later, and always at the worst moment.

So the rule here is narrower than for anything else on this site. A one-time code is fine for an account you are content to lose. Anything you intend to keep needs a rental you renew, or better a recovery email you control — and the phone kept off two-step verification entirely.

Google answers most failures with a single sentence, which is exactly why so many people retry the wrong thing. The middle column is what actually happened.

Only rows three and four are about your side of the screen. The rest are decisions Google makes about a range, or about a line somebody else already used, before your signup exists — which is why the route and the individual number matter far more than the retry. The general form of these failures is worked through in the delivery guide.

One sentence, three unrelated problems

"This phone number cannot be used for verification" is Google's answer to at least three situations that have nothing to do with each other, and it never says which one you are in. The first is line type: the lookup resolved your number to a cloud-issued range and Google refuses those for new accounts as policy. Nothing was sent and nothing was charged, and a second cloud-issued number in another country is the same answer wearing a different flag.

The second is the quota. Every line carries a limit on how many Google accounts it may verify, and a pooled number arrives with part of that limit already spent by whoever held it before you. Here the range is fine and the individual line is not, so the fix is a different number rather than a different tier — precisely the opposite move to the first case, which is why the same error message sends people in circles.

The third is not about the number at all. A new browser profile on a datacentre address, a form completed in three seconds, or a signup following four others from the same fingerprint will raise a wall no route can climb. When physical and premium routes in two different countries all return the same sentence, stop buying numbers: you are paying to confirm something you already know.

The quota nobody can see

Google limits how many accounts a single phone number may verify. It does not publish the figure, the limit is not the same everywhere, and there is no page anywhere that shows how much of a given line has already been used. What is certain is that the counter belongs to the number rather than to you: a pooled line inherits everything the previous holders did with it.

That is the honest reason a Google code sometimes fails on a route that worked an hour earlier. The tier was never the variable — the individual line was, and the earlier one simply happened to be fresher. It also explains why the cheapest virtual ranges disappoint on Google specifically: they turn over fastest, so their counters run down soonest. Of the 400 routes in this catalogue, 118 are virtual and those recycle hardest.

No provider can check a line's remaining budget before you buy, and any that claims to is guessing. What you can do is spend less time drawing from the pool at all: a dedicated rental is one line held by one person, with a counter you are the only one moving.

Three ways to give Google a number, and they are not three prices for one product. The row that decides it is the second, because Google is the service most likely to ask twice.

The middle column is the honest recommendation for an account you intend to keep, and the left one is right exactly when the account is disposable. What no column fixes is a phone number put on two-step verification, which is the next section and the reason this guide exists. Rental terms and prices run per country and per route.

What a Google code costs, and why

Across the whole catalogue a code averages $0.69. Google averages $0.87 and runs from $0.07 to $6.79 depending on the country and the route — dear for a mail account, and still well under WhatsApp at $3.19 or Telegram at $1.99.

The spread measures acceptance, not margin. Fewer operators still get a Google code through, so the routes that do are scarcer and priced as scarce things are. The cheapest Google line on the list is cheap for a reason: it is the one most likely to come back refused, and on Google the refusal arrives before the SMS does, so the retry is free but the hour is not.

Prices are set per country and per route and they move with stock, so the figure on the Google page is the live one rather than the average quoted here.

Country choice changes the outcome

All 116 countries carry Google routes and they behave nothing alike. At the bottom, a Vietnamese line opens at $0.07 and a Kenyan one at $0.08; at the top, Turkey is $6.79 and Singapore $5.57. That is a ninety-fold spread for the same six digits, and it is not a discount waiting to be found.

Choose on delivery first and price second. The country pages carry live stock and the tier split behind each country, and on Google the tier does more work than the flag: 118 virtual routes, 161 physical and 121 premium, with multipliers running from 0.85 to 2.50 and set out in the delivery guide.

Two-step verification, and the number you must not lose

If you read one section of this guide, read this one. Switching Google's two-step verification on with SMS as the method makes that phone number a key to the account. Do it with a one-time activation and you have locked a door and dropped the key back into a pool that other people draw from.

Two things follow, and the second is worse than the first. You cannot sign in from a new device once the line is gone, which is merely expensive. And whoever holds that number after you can ask for the code — Google will send it, because as far as Google is concerned that line is you. A recycled number is not a lost key. It is a key still lying on the floor.

So the rule is short. Never put a disposable number on two-step verification. Use an authenticator app or a passkey instead — both live on hardware you hold rather than on a line somebody else will hold next month — and if a phone number genuinely must sit on the account, rent one and renew it for as long as the account exists.

The recovery email is the real escape hatch

Telegram has Change Number, WhatsApp has nothing much, and Google has a recovery email — which is stronger than either. It is the only way back into the account that does not run through a phone line, it costs nothing, and it is the first thing to set on any account registered on a number you do not permanently hold.

Set an address you actually control and will still be able to open in two years. A mailbox at a provider that does not itself demand a phone number keeps the whole chain consistent, and an account verified the same way is the usual answer. After that, keep the number on the account current: Google lets you replace it in the contact settings, so a rental can be swapped for the next one before the term lapses — which is exactly the step people forget.

Google Voice cannot be bootstrapped from a virtual number

This catches more people than it should. Google Voice hands out a number, and to get one it asks you to link an existing line — a US one — then screens that line specifically for forwarding and cloud services, which are what it competes with. The refusal is a policy decision rather than a delivery failure, so retrying spends money and teaches nothing.

And if a number that receives codes is all you were after, Google Voice is a long way round to somewhere you are already standing. A rental here is a dedicated line for 7, 14, 30 or 90 days from $4.20, taking unlimited incoming SMS across all 133 services, with no US address, no linked line and no identity check anywhere in it.

YouTube, Play and the second phone check

One Google account, several phone checks. Verifying a YouTube channel for uploads longer than fifteen minutes, live streaming or custom thumbnails is a separate flow with its own screening, and it can refuse the very number the account was created on. It is priced separately here for the same reason: a YouTube code averages $0.64 against Google's $0.87.

The same holds for the checks Play, Ads and Workspace run once money or publishing is involved. Treat each as its own verification with its own odds rather than assuming the account's number carries across — and if the account is one you intend to keep and earn from, that is a rental, not an activation.

When Google does not ask at all

Try before you spend anything, because the phone step on a personal Google account is not always required. Google weighs the connection, the browser profile, the device and the history behind them, and on an ordinary residential line with a normal browser it frequently lets a personal account through with no number requested at any point.

What raises the challenge is what you would expect: a datacentre or VPN exit address, a freshly wiped profile, a form filled unnaturally fast, or several accounts in a row from one fingerprint. Slowing down and using an ordinary connection moves the odds more than any route tier can, and it costs nothing to do.

If the step does appear, it is not a glitch and it will not go away by reloading. That is the moment a number becomes the answer — and the moment the tier decides whether you are buying a code or buying a refusal.

Automating the number side

The REST API requests a number, polls the order until a code lands or the 20-minute window closes, and takes the automatic refund when nothing arrives — so an escalation loop that tries physical and then premium costs nothing per failed attempt. Authentication is a Bearer token on the seed phrase: no keys to rotate, no monthly fee, billing per number only.

Autonomous agents reach the same catalogue over MCP with the same order lifecycle. Worth saying plainly: this is for provisioning the number side of a verification you are entitled to make. Registering Google accounts in bulk is a different activity, it is against Google's terms, and it is not what these endpoints are for.

What this guide will not claim

No provider decides whether Google accepts a number, and anyone selling a guaranteed Google line is selling the part they do not control. What is promised here is narrower and testable: a live line on the route you chose, the code inside the 20-minute window, and the money back automatically when nothing arrives.

A rental holds the line for its term. It does not refill a spent account quota, it does not stop Google refusing a range, and it does not recover an account whose two-step number lapsed — nothing does, which is the entire argument for the recovery email.

And a virtual number does not make an account private. It keeps your personal line off the signup, which is a real and specific gain, and it changes nothing about what Google otherwise records. What we keep, and for how long is a separate question and we answer it in full; the Monero guide covers the payment half of the same chain.