Migrate your Google reCAPTCHA keys to a Google Cloud Project by end of Dec 2025

Google is introducing new features to support the users of Google reCAPTCHA to consolidate all billing, pricing structure and terms of agreement. If like me you have received an email in your inbox as such “[Action Advised] Migrate Google reCAPTCHA key to a Google Cloud Project by the end of 2025” then you are advised to take some form of action be that talking to your digital management team or partner to see what needs to be done or taking the action suggested in the email yourself. If you haven’t received this email but do know your site is utilising reCAPTCHA, then read on and highlight again to your digital team, or get in touch with me and we can discuss the strategy for getting you upgraded.

How does this change affect me and my site?

Now if you have a website or online form anywhere you more than likely are using Google’s reCAPTCHA tool be that v2 (with the challenge “pick these pictures”) or the more discrete v3 version that uses tokens behind the scenes to determine a “real” person.

Google will throughout the year be migrating accounts over to GCP creating a project  upgrading your keys and associating them to that project. You will then basically be running the free version of the feature giving you up to 10,000 assessments a month and that’s it. The reCAPTCHA code that is sitting on your site will still continue to work but at a legacy level meaning that even though your keys are upgraded you will not have access to some of the advanced features.

What you need to do

So although Google will be moving your keys for you eventually it’s a good idea to get ahead of the flow and get your GCP account configured how you want it.

Setup Google Console and Project

Go to Google Cloud Project Selector and login to your company’s main Google account, if you are already using Google Maps API on your site the chances are you already have an account and project with billing setup. It is recommended to have a Google Cloud Project per site that you are using API’s for this will allow you to enable and disable keys on a site per site basis and also manage who has access to those resources. e.g. example.com will have its own project and reCAPTCHA enterprise API, and example2.com will have its own project and another set of keys.

Enable reCAPTCHA Enterprise API

Ensure that you have the correct Google Cloud Project selected and go to the enable reCAPTCHA API.

Upgrade keys

Navigating to reCAPTHCA under security at the bottom of the page you should see all of the Classic Keys that are associated with your account. Select the key that you would like to attach to the current project that you are in and hit upgrade. Your key should now be showing under reCAPTCHA Keys and that means you have now migrated your key congratulations.

What happens next

Your site keys will continue to work with your current site integration code but it will be using the legacy implementation, in an ideal world you will talk to your digital team and have them update the code implementation to the newest enterprise version.