Logo of «2Captcha»To home page
Captcha bypass tutorials

How to Scrape Google SERPs Without Getting Stopped by reCAPTCHA

This article is an update to our previous guides:

Google Search reCAPTCHA: How to Bypass the Protection

Changes in Google reCAPTCHA: New Requirements

Alright, let’s get into it. If you’re here, Google’s CAPTCHA is driving you nuts again, and you need a reliable way around it. We’ve got a method that still works, but there are some key details—let’s break it all down.

🔥 What’s New in 2025?

Google’s gotten stricter, but not smarter. The CAPTCHA is still solvable—you just have to nail the parameters now. Cutting corners won’t cut it anymore; you’ve got to follow the steps precisely.

Heads up: Code examples are in Python + Selenium. Full code is available for clients upon request.

🎯 The Keys to Success:

✔ Proxies – Without them, Google won’t even let you in.

✔ Cookies – Missing these? Your token might fail.

✔ Exact User-Agent – Must match a real browser.

✔ Correct data-s – No data-s? The CAPTCHA won’t even start.

📌 How It Works in Code

1. Extract the data-s Value

When Google throws a reCAPTCHA at you, the first step is grabbing the data-s parameter. It’s unique for each CAPTCHA instance, so you need to fetch it fresh every time.

Find the CAPTCHA element and pull its data-s attribute:

data_s = driver.get_attribute('div[id="recaptcha"]', 'data-s')

No data-s? The CAPTCHA won’t even process your request.

2. Send the Request to 2Captcha

Here’s the exact parameter set you’ll need in 2025:

result = solver.recaptcha(

    sitekey="6LfwuyUTAAAAAOAmoS0fdqijC2PbbdH4kjq62Y1b", # Same for all Google CAPTCHAs

    url="https://www.google.com/search", # Always this URL

    datas=data_s, # The dynamic key from earlier

    userAgent="Mozilla/5.0 (Windows NT 10.0...)", # Must match a real browser

    proxy={'type': 'HTTPS', 'uri': 'login:pass@123.123.123.123:3128'}, # HTTPS/SOCKS

    cookies="NID=123...; ANID=456..." # Cookies from google.com

)

Why does this matter?

  • Core params (`url`, `sitekey`, `datas`) – Without these, nothing happens.

  • No cookies? – Success rates drop hard.

  • No proxies? – Google will flag automation fast.

3. Insert the Token & Confirm

Once you get the token from 2Captcha, apply it properly:

# Inject into hidden field

driver.execute_script(

    'document.querySelector("[name=\'g-recaptcha-response\']").value = "' + token + '";'

)

# Trigger the callback (Google won’t accept it otherwise)

driver.execute_script("submitCallback('" + token + "');")

# Wait 5-10 sec—skip this, and the redirect might fail

time.sleep(10)

❗ Critical notes:

  • Just injecting the token isn’t enough—you must call submitCallback.

  • No delay? Google might not process the response in time.

💸 What If the Token Fails?

🚫 Don’t retry on the same page!

👉 Go back to search and get a fresh CAPTCHA—otherwise, Google may IP-ban you.

If the token gets rejected:

  1. File a complaint via API – You’ll get refunds for failed solves.

  2. Contact support – They’ll help troubleshoot.

Check:

✔ Cookies – Are they from google.com?

✔ Proxy – Is the IP blocked?

✔ User-Agent – Does it match a real browser?

If you’re not getting a token at all:

✔ Check the error response.

✔ Verify your proxies are live.

🎯 Bottom Line: What’s Changed?

Back in the day, you could skip cookies and still solve CAPTCHAs. Now? Google’s picky about every little thing. But if you follow the steps exactly, the token will work first try.

Key takeaways:

🔹 Precise params (url, data-s especially)

🔹 Cookies + proxies – Skip these, and failure rates spike.

🔹 Proper token insertion – Must call submitCallback.

🔹 Report failures – Get refunds if Google rejects your token.

Stuck? Hit up support—they’ll help sort it out. Good luck battling CAPTCHAs! 🚀