Hide reCAPTCHA Badge in WordPress (2026)

If you’ve ever looked at the little reCAPTCHA badge stuck in your corner and thought, “This is messing with my design”… same.

But here’s the catch: you can’t just hide the reCAPTCHA badge and call it a day. Google allows hiding the badge only if you keep the reCAPTCHA branding visible in the user flow with a specific disclosure.^[1]

I’m Ben Marshall (full-stack dev + engineering manager). This guide shows you the safe way to hide the reCAPTCHA badge in WordPress, where to put the required disclosure, and what to review ahead of the April 2, 2026 terms update.

TL;DR: The safe way to hide the reCAPTCHA badge

• Yes, you can hide the badge — but only if you add the required disclosure text visibly in the user flow.^[1]
• Use Google’s recommended CSS: .grecaptcha-badge { visibility: hidden; }.^[1]
• Put the disclosure near the form (best) or in a global location that’s visible wherever reCAPTCHA runs.
• Before April 2, 2026, audit your site for reCAPTCHA privacy/terms references because they’re expected to change/vanish from the badge and Google is urging site owners to remove manual references.^[2]

What Google actually requires when you hide the badge

Google’s reCAPTCHA FAQ is clear: you’re allowed to hide the badge as long as you include the reCAPTCHA branding visibly in the user flow, using the provided text snippet.^[1]

Required disclosure text (current guidance)

Place this somewhere users will actually see it during the form flow (for example: right under your submit button):^[1]

Hide the badge with the recommended CSS

Google’s FAQ recommends hiding the badge with visibility: hidden (not “display: none”).^[1]

.grecaptcha-badge { visibility: hidden; }

Where to add CSS in WordPress: Appearance → Customize → Additional CSS (or your theme’s stylesheet if you prefer). (If your theme doesn’t have the Customizer, use your site editor’s global styles or a child theme.)

Where to place the disclosure in WordPress (so it’s actually compliant)

The disclosure has to be “visibly in the user flow.” In practice, that means: put it near the exact form(s) that use reCAPTCHA, not buried in a random page.

Best placement (recommended)

• Directly under the submit button on contact/lead/support forms
• Near the “Place order” button if you run it on checkout flows
• Near the login/register button if you protect wp-login or registration

Acceptable “global” placement (only if it’s truly visible)

If reCAPTCHA is used across many pages (multiple forms/plugins), a global disclosure can make sense — but only if it’s visible on the pages where reCAPTCHA runs. If a user can submit a form without ever seeing the disclosure, it’s not doing its job.

Common mistakes that create headaches

• Hiding the badge but forgetting the disclosure (easy to do, especially if a plugin hides it automatically)
• Multiple plugins injecting reCAPTCHA (you think you updated it once, but it appears elsewhere)
• Putting the disclosure only in the footer when your forms are embedded in ways that don’t reliably show the footer

Cookie note (quick heads-up)

Google’s FAQ notes reCAPTCHA sets a necessary cookie named _GRECAPTCHA when executed for risk analysis, and it also mentions using www.recaptcha.net instead of www.google.com if you prefer to avoid other potential Google cookies from that domain.^[1]

What changes on April 2, 2026 (and what you should review)

Google is shifting reCAPTCHA’s GDPR posture by moving from “data controller” behavior to “data processor” behavior, which changes responsibility and what terms apply.^[2]

Reporting on the change says the badge references to Google’s privacy policy and terms are expected to disappear starting April 2, 2026, and Google urges customers to remove manual references to Google’s privacy policy connected to reCAPTCHA to match the new legal situation.^[2]

Practical checklist for WordPress site owners

• Search your site for policies.google.com/privacy and policies.google.com/terms (theme, blocks, widgets, footers, form templates).
• Search for the disclosure phrase (“This site is protected by reCAPTCHA…”) and note every place it appears.
• Review your privacy policy language describing bot protection and who processes what (especially if you’re in a regulated context).^[2]
• Re-check Google’s latest guidance closer to April 2, 2026, because the exact “replacement” language may evolve.

If you’re already touching this, consider a better anti-spam stack

CAPTCHA tools are a useful layer, but they’re not a complete spam strategy. If the badge/disclosure/terms churn is already annoying you, it’s a good moment to shift toward layered defense that blocks repeat offenders quietly before a challenge is even needed.

Zero Spam for WordPress is built around layered protection and integrates with reputation sources (including Stop Forum Spam and Project Honey Pot) to block spam with minimal friction.^[3]

If your forms are business-critical (sales leads, support, quote forms), a Zero Spam API license adds deeper intelligence like confidence scoring and report history on higher tiers, which helps reduce spam and tune false positives without guessing.^[4]

Discount if you want it: use code ZEROSPAM20 for 20% off a Zero Spam License.^[5]

About Ben Marshall

Full-stack Developer & Engineering Manager

Ben Marshall is a full-stack developer and engineering manager who loves building solid software and helping teams do their best work. He’s equal parts builder and coach—focused on practical architecture, clean implementation, and making collaboration easier (and faster) for everyone.

• WordPress.org