Gmail registration often gets stuck at phone verification. This guide covers five workable approaches, why your account details need to be consistent, and the order to troubleshoot three common causes: an abnormal environment, an exhausted phone number, and overly rapid actions.
Gmail is a common gateway to the global internet. YouTube, ChatGPT, Gemini, Claude, and GitHub all support sign-in with a Google account, so getting one account effectively opens several doors at once.
Over the past two years, Google has tightened the registration process. The most common sticking point is phone verification: you may be shown a device check that requires scanning a QR code, or receive the message “This phone number cannot be used for verification.” The problem is usually not the domestic number itself. Google looks at your IP, device information, language, region, and time zone together. If any one of these does not match the pattern of a stable, ordinary long-term user, the verification requirements become stricter.
Make sure your account details hold up first
Every field you submit in the form is retained. For the name, use Pinyin plus a common English name; choose an adult birth date; and provide a recovery email that you can access and sign in to over the long term. A recovery email is not a formality. If something goes wrong with the account, recovery will largely depend on it. Using a disposable email means giving up that fallback in advance.
The same applies to the phone number. It should remain under your control for the long term because it becomes part of the account's security information. If you discard the number after using it, no one can help you prove ownership if you later face another verification step or need to appeal.
Five workable approaches
Using the Gmail app on a phone with a domestic number is currently one of the approaches that receives relatively good success feedback. The app is less likely than the web version to trigger QR-code verification. First set the phone's language, region, and time zone to match the node you are using, and avoid changing them repeatedly on the registration day and for the next few days. Then connect through a clean residential IP or a higher-quality node, install the official app from an official app store, and follow Add account → Google → Create account → For my personal use. Enter your details, choose +86 on the verification page, and enter the domestic number. The code normally arrives within 1–2 minutes. If it times out, request another code, but do not keep clicking repeatedly.
If you need an overseas number that can receive codes over the long term, you can use a physical SIM or an eSIM. The value of this kind of number is its general usefulness: Gmail registration may be only the first use, and you can keep using the same number later on other platforms that require an overseas number instead of searching for a new one each time.
If you already own a domain, Workspace is a more formal option. You can create a Google account with your own domain, using an address such as name@yourdomain.com, with an experience that is not very different from regular Gmail. Prepare a credit card that supports foreign-currency payments and a registered domain, go to workspace.google.com, start the free trial, choose to use an existing domain when entering your information, and add the verification record through your domain registrar or DNS panel as instructed. It normally takes 5–10 minutes to take effect. A domestic number can generally also pass the phone verification step.
If you already have a Google account, you can add a new account directly from the Gmail app while signed in: profile picture → Add account → Google → Create account. Fill in the information as prompted and use a +86 number to complete verification. The new account will appear in the same app, where you can switch between accounts, and you can later sign in normally on a computer as well. Because the device itself is already in a trusted state, this step usually has a higher success rate.
If you must work on a computer, or need to prepare accounts in bulk for a team, a stable and consistent environment is the key. Create a separate fixed environment for these accounts: keep the IP location, time zone, language, and browser fingerprint consistent, and do not mix it with the browser you normally use on the same computer. As much as possible, complete both registration and later sign-ins in the same environment to reduce secondary verification triggered by environmental changes.
Three common situations that lead to a block
The first is an abnormal environment. A heavily shared IP, a language or time zone that does not match the exit region, or fingerprint data that changes every time can all be treated as risk signals. Changing the phone number will not help in this case; fix the environment first.
The second is an exhausted number. If the same number is repeatedly used for registration within a short period, or if it has already been used to register elsewhere, the page may reject it outright. In that situation, the phone-number resource is what needs to change. Repeatedly resubmitting only wastes time.
The third is acting too quickly. Repeatedly pressing resend, immediately performing bulk actions after registration, or switching regions within a few minutes can push automated checks toward a higher-risk judgment. Simply slowing down can resolve some of these problems.
Troubleshooting order: environment first, number second, pace last
When verification is blocked, go through the checks in this order: first confirm that the network exit is clean and that the region matches the account's positioning; next check whether the phone number has already been used as a registration resource; finally slow down your actions and do only the registration on the registration day. Jumping between changes often makes things more confusing, because every change shows the system a slightly different version of your environment.
Why buying accounts and using SMS-receiving services is not worth it
Pre-made accounts have unclear origins, and sellers often still retain the original binding information, which may let them recover the account at any time. That leaves both the money you paid and any later operational investment at risk. Numbers from SMS-receiving services are reused repeatedly, so the chance of Google rejecting them or treating the resulting account as abnormal is not low, and such accounts often have a short usable life. More importantly, buying and selling accounts itself violates platform rules, and when it is detected, more than just one account may be affected.
Separate environments when managing multiple accounts
When managing multiple accounts at the same time, it is more reliable to place both registration and everyday sign-ins in separate browser environments. Tools such as PurpleMark browser can bind a separate proxy to each environment, configure language and region parameters, and open directly to preset pages so the accounts do not interfere with one another.
Which approach to choose depends on how many phone numbers you have, how long you plan to use the accounts, and whether you need one account or multiple accounts. If you only register one or two occasionally, the mobile app with a domestic number is enough. For long-term use, an overseas number or your own domain is more convenient. If you are running multiple accounts in parallel, do not skip environment separation.
