. Regenerated with each Chinaready Landscape publish.
Quick answer: Google reCAPTCHA is Limited in mainland China. The default www.google.com/recaptcha/ endpoint is blocked, so forms and logins hang or never render. Google documents www.recaptcha.net as an alternate domain for regions where google.com is unreachable, and that domain usually resolves from the mainland — but it is not a guaranteed path, and any residual www.gstatic.com asset request can still stall the widget. For China-facing traffic that must work reliably, map to GeeTest and Alibaba Cloud CAPTCHA. Availability in China: Limited.
Availability in China:Limited
Also searched as: recaptcha.
Making CAPTCHA work for mainland China users
Why reCAPTCHA fails on the default domain
The standard reCAPTCHA integration loads its script, iframe, and verification calls from www.google.com/recaptcha/. That host is blocked in mainland China, so the widget never finishes loading. The visible symptom is not usually an error message — it is a form that appears to hang, a submit button that stays disabled, or a login page that takes tens of seconds before failing.
Option 1 — Switch to the recaptcha.net domain
Google's own reCAPTCHA FAQ states that you can use www.recaptcha.net in your frontend code when www.google.com is not accessible to your users. Replace every reference to www.google.com/recaptcha/ with www.recaptcha.net/recaptcha/, including the script tag, the API calls, and your Content-Security-Policy directives. Server-side verification should call https://www.recaptcha.net/recaptcha/api/siteverify.
Two caveats before you treat this as solved:
Not guaranteed. The alternate domain is generally reachable from the mainland, but reachability is measured, not promised. Test from real mainland networks on more than one carrier before shipping.
Watch residual Google hosts. Assets or fallbacks that still point at www.gstatic.com can stall the widget even after the main domain is swapped. Audit the full request waterfall from a mainland vantage point, not just the script URL.
This option suits products whose primary audience is outside China and that only need mainland visitors to get through a form occasionally.
Option 2 — Use a domestic CAPTCHA provider
If China is a core market — or if a blocked login screen is a revenue or support problem — serve a domestic provider to China-facing traffic instead of relying on an alternate Google domain. Domestic vendors run mainland nodes, so challenge latency is low, and their interaction patterns match what Chinese users already expect.
Approach
Mainland reliability
Best fit
reCAPTCHA on www.google.com
Blocked — the widget does not load
Nothing China-facing
reCAPTCHA on www.recaptcha.net
Usually loads; not guaranteed, and gstatic.com assets can still stall
Global products with occasional mainland visitors
GeeTest (极验)
Mainland nodes; built for China traffic
China-facing login, registration, and abuse control
Alibaba Cloud CAPTCHA (阿里云验证码)
Mainland nodes; built for China traffic
Stacks already on Alibaba Cloud edge and security services
Recommended pattern
Most teams do not pick one globally. Keep reCAPTCHA for the rest of the world and branch on visitor geography or locale so China-facing sessions get a domestic provider. That keeps your existing risk-scoring history intact outside China while removing the blocked dependency from the path that matters for mainland conversion.
The domestic options above appear on this alternatives page as orientation candidates for research. Validate pricing, data-handling terms, and accessibility requirements before production adoption.
Google's wider presence in mainland China
Google officially established its Chinese corporate entity in April 2006. Most core consumer services are blocked in mainland China due to strict local censorship regulations.
Blocked products
Google Search
YouTube
Gmail
Google Play
Google Maps
Google Drive
Google Docs
Google Photos
Google News
Blogger
Google maintains local offices focused exclusively on enterprise (B2B) services, developer support for global expansion, and hardware manufacturing.
China context: Started in CAPTCHA and now covers frictionless verification, identity anti-fraud, and device fingerprinting. Collects device and behavior signals, returns a real-time risk score, and supports silent protection plus custom block policies with a strong developer experience. Best for UX-sensitive apps — especially mobile — that want frictionless filtering of bot traffic and account attacks. Also a common Castle.io research option for mainland account-abuse and bot defense.
Only partially. The default www.google.com/recaptcha/ endpoint is blocked in mainland China, so the widget does not load and forms appear to hang. Google's reCAPTCHA FAQ documents www.recaptcha.net as an alternate domain for regions where google.com is not accessible, and that domain generally resolves from the mainland — but reachability is not guaranteed and residual www.gstatic.com asset requests can still stall the widget. Chinaready labels Google reCAPTCHA as Limited for mainland production use.
How do I fix reCAPTCHA not loading in China?
Replace every www.google.com/recaptcha/ reference with www.recaptcha.net/recaptcha/ — the script tag, the client API calls, your Content-Security-Policy directives, and the server-side siteverify endpoint. Then audit the full request waterfall from a real mainland network on more than one carrier, because assets still pointing at www.gstatic.com can stall the widget even after the main domain is swapped. If China is a core market, serve a domestic provider to China-facing traffic instead of depending on the alternate domain.
What are the best China alternatives to Google reCAPTCHA?
Chinaready Landscape currently maps Google reCAPTCHA to GeeTest, Alibaba Cloud CAPTCHA. These run mainland nodes, so challenge latency is low and the interaction patterns match Chinese user expectations. Replacement fit varies by product, so treat this as a research shortlist rather than a one-to-one endorsement.
Should I replace reCAPTCHA everywhere or only for China traffic?
Usually only for China traffic. Branch on visitor geography or locale so mainland sessions get a domestic CAPTCHA while the rest of the world keeps reCAPTCHA. That preserves your existing risk-scoring history outside China and removes the blocked dependency from the path that affects mainland conversion.
Where should teams go after shortlisting Google reCAPTCHA alternatives?
Compare the adjacent bot-protection pages for hCaptcha and Cloudflare Turnstile, since they share similar China failure modes, then use the Bot Protection & CAPTCHA section of the Chinaready Guide for where this sits in a China stack. If the path remains unclear, book a call with Chinaready.
