reCAPTCHA Scores, Mobile IPs and Automation

reCAPTCHA is the most widely deployed bot check on the web, and it is also the least transparent. Google does not publish its signals, and the site owner, not Google, decides what to do with the result. For automation builders that creates confusion: the same flow passes on Monday and fails on Tuesday with no visible reason. This page lays out what is publicly understood about how reCAPTCHA evaluates a visitor, what a dedicated NeonProxies carrier line does and does not influence, and how to design both your automation and your own forms around it.

Three products that behave differently

reCAPTCHA v2 is the familiar checkbox, sometimes followed by an image grid, plus an invisible variant that only shows images when risk looks high. reCAPTCHA v3 never shows anything: it returns a score from 0.0 to 1.0 for each action, and the site's backend decides whether to allow, add friction or refuse. reCAPTCHA Enterprise extends the scoring with reason codes, account defender features and tuning options for larger sites. A form that fails with no visible challenge is most likely v3 or Enterprise returning a low score that the site rejected.

Google describes the inputs only broadly: interactions with the page, the browser environment, and signals it has about the visitor, which is widely understood to include cookies from Google properties and a signed-in Google account in that browser. A fresh profile with no history tends to score lower than a long-used one, independent of the network. That is also why a worker that wipes its profile on every run keeps meeting challenges that a person on the same connection never sees, and why the fix is usually in how the profile is stored rather than in the proxy.

The network's share of the verdict

Address reputation is part of the picture. Traffic from cloud ranges and from IPs that have generated abusive volume across Google's services scores worse. A NeonProxies line is an AT&T, T-Mobile or Verizon address shared through carrier-grade NAT with real handsets, and it is yours alone, so your score is not dragged down by another customer's behavior on the same IP. For a legitimate workflow that was failing only because it ran from a server, that can be the whole difference.

The limits are just as real. Carrier ranges also carry some abuse from the phones behind them, so a carrier IP is not an automatic high score. A new, empty browser profile, automation flags in the browser, or unnaturally fast form filling are all visible to the page-level signals, and the line does nothing about them.

How automation should handle reCAPTCHA

If a site puts reCAPTCHA on a form, the owner is telling you that automated submissions on that form are not wanted. A well-behaved job reads public pages and leaves protected forms to people. Where your workflow legitimately includes a form, such as submitting your own company's listing update, keep a human in the loop for the challenge step, and never feed challenges to paid solving services, which violate both Google's terms and ours.

For read-only automation, reCAPTCHA appearing on pages that were open before is a signal that your rate or pattern changed. Slow the job, check that the worker is still on its sticky line, and review whether the browser profile was reset. Those three causes explain most sudden changes.

Testing reCAPTCHA on your own site

Google provides dedicated test keys for development that always pass, which is the right tool for automated tests of your own forms in staging. For production tuning, a carrier line lets you see what scores genuine mobile visitors in your metros receive. Submit your own form from a phone-like profile through the line, record the v3 score or Enterprise reasons, and compare with a server run before you set the threshold that decides who gets turned away.

Setting up a Google reCAPTCHA proxy on NeonProxies

1. Order a line in a metro where your users or research targets are.
2. Use a long-lived browser profile per line rather than a fresh one each run.
3. Keep automated jobs on public pages and out of protected forms.
4. Route any challenge that does appear to a person.
5. For your own site, use Google's test keys in staging and a carrier line to sample real scores in production.
6. Log scores and outcomes so threshold changes are based on data.

Google reCAPTCHA proxy questions