Google is testing a new human verification step on search results where a “Continue” button starts grayed out and only turns blue after a few seconds, once the request is verified. The test is part of a broader set of anti-scraping measures Google has been rolling out, adding a friction layer that does not require a sign-in.<\/p>\n
The experience is straightforward: a searcher reaches a results page and sees a Continue button that cannot be clicked right away. The button stays disabled for a few seconds, then becomes active once Google finishes its check. The delay is the verification itself, using a brief waiting period rather than a challenge or credential. A screenshot of the behavior circulated on X with a note that the button was gray before turning blue, a signal that the system was actively confirming the request rather than just loading.<\/p>\n
This Continue button is the latest in a string of Google experiments aimed at keeping bots away from search results. In early August, Google was testing a flow that required searchers to sign in to keep seeing results. That approach added a strong gate, but it also forced every human user through an account login. The Continue button test removes the account requirement and replaces it with a short automatic check, which is easier for real users to pass and harder for simple scrapers to mimic.<\/p>\n
Beyond sign-in and the new Continue prompt, Google has also been leaning on goto redirects and the long-standing CAPTCHA system. Each method attacks a different part of the scraping pipeline: redirects break naive URL harvesters, sign-in forces a persistent identity, CAPTCHAs test interactive behavior, and the timed Continue button tests whether a client behaves like a patient human versus a fast automated loop.<\/p>\n
The Continue button test has shown up in English search sessions and in other languages. One screenshot from a private browsing session in French captured the same gating pattern on a third page of Google results, with the caption suggesting Google is pushing its anti-scraping work into more markets and more parts of the results experience, not just the first page.<\/p>\n
For regular users, the effect is a short pause before the next click. The button being unavailable for a few seconds is the cost of the check, and once the verification window closes, the search continues normally. For automated tools, the timed gate is a new obstacle: a script that grabs a results page the instant it loads will either miss the active button or trigger the same verification path, reducing the value of any single request.<\/p>\n
Google has not announced a timeline for rolling the Continue button out broadly, and the test is limited in scope. Other parts of the anti-scraping stack, including the sign-in requirement and goto redirects, also remain in testing rather than general release. For anyone tracking how Google is hardening its search surface, the Continue button is the clearest signal yet that the company is willing to add small amounts of friction to keep human users in front of bots.<\/p>\n
It is a test that shows a grayed-out Continue button on the search results page. The button becomes clickable after a few seconds, once Google completes a human verification check on the request.<\/p>\n
No. The Continue button test does not require signing in. It replaces the sign-in step tested earlier with a short timed check that runs automatically.<\/p>\n
Google is testing several approaches at once, including a sign-in requirement to view results, goto redirects, and traditional CAPTCHAs, alongside the new Continue button prompt.<\/p>\n