Skip to content
Front User Submit
Menu

reCAPTCHA vs hCaptcha for WordPress Post Forms

By Aleksan Aharonyan · · Updated

For most WordPress sites that take posts from visitors, hCaptcha is the calmer choice: it does the same job as Google reCAPTCHA v2 without sending your visitors’ browsers to Google, and the setup takes the same amount of work. Pick reCAPTCHA v2 instead when the familiar Google checkbox is worth more to your contributors than that, or when your site already leans on Google services. Neither one is a complete spam plan, and the sites that stay clean are the ones that pair a captcha with a login requirement and a review step.

Key takeaways

  • Both reCAPTCHA v2 and hCaptcha put a checkbox on the form and can follow it with a short image or audio challenge, so the friction for a real visitor is similar.
  • The difference that matters is whose servers serve the challenge and see the visitor’s browser: Google’s for reCAPTCHA, hCaptcha’s own for hCaptcha.
  • Choose hCaptcha when keeping Google out of the page is the point; choose reCAPTCHA v2 when a checkbox people recognize is worth more to you.
  • A captcha filters bots, not bad posts, so hold new submissions in Pending and read them before they publish.

What reCAPTCHA v2 and hCaptcha ask of visitors

Both widgets ask the visitor to confirm they are not a robot with a checkbox, and both may follow that tick with a short image challenge before the form submits. After the visitor ticks the box, the provider decides whether to accept the answer silently or to show a grid of images, a puzzle, or an audio clip. There is nothing else to fill in and no account to create.

Google reCAPTCHA v2 is the “I’m not a robot” checkbox. Google also offers reCAPTCHA v3, which scores traffic invisibly with no checkbox at all, but the fields discussed here are the v2 checkbox, which is what a post submission form usually gets. hCaptcha is an independent service that presents the same kind of checkbox and the same kind of image challenge, run by a different company.

On a submission form, the widget sits between finishing the post and sending it. Put it last, directly above the submit button, so the visitor has already written the post before meeting the challenge and is not asked to solve a puzzle before they have decided to contribute.

Privacy and where the challenge data goes

A captcha is a third-party service: the page loads a script from the provider, and the visitor’s browser talks to that provider to fetch and answer the challenge, which means the provider sees the visitor’s IP address and browser details. With reCAPTCHA that provider is Google, and Google’s terms and privacy policy apply to that exchange. With hCaptcha the provider is hCaptcha, an independent company, and its own terms and privacy policy apply instead.

That difference matters most if you have deliberately kept Google scripts off the site, for example because you tell European visitors you do not send their data to Google. Adding reCAPTCHA undoes that position in one line of code; hCaptcha keeps your position, though it is still a third party and still needs a mention in your privacy policy. If you already load Google Maps, Google Analytics or Google Fonts, reCAPTCHA adds one more request to a company you already work with, and the privacy argument for hCaptcha is weaker.

Whichever you choose, name the provider on your privacy policy page and link to its documentation. Read Google’s reCAPTCHA documentation or the hCaptcha docs for what each service says it collects. Do not take a blog post, including this one, as legal advice on consent.

Accessibility and friction on a post submission form

Both widgets can lock out real people, especially when the image challenge appears, so test keyboard access, the audio alternative and the mobile layout before you launch. An image grid is unusable for a visitor who cannot see it, and both providers offer an audio option instead; open it with a screen reader and on a phone to make sure it works on your theme. Then tab through the form without a mouse and confirm the widget can be reached and completed from the keyboard.

Friction costs more on a post submission form than on a contact form, because the visitor has just spent time writing. A challenge that fails and clears the textarea loses that contributor for good. Two habits prevent this: keep the captcha field at the end of the form, and check what your form does when the challenge is not answered. The visitor should see a message, keep their content, and be able to try again.

You can also cut the friction in half by showing the captcha only where the bots are. Members who are logged in and have an account on your site are rarely the source of automated spam, so a form that requires login and skips the challenge for signed-in users is both friendlier and cheaper in effort.

How each one is set up in WordPress

Setup follows the same four steps for either provider: register the site, copy the keys, paste them into your form plugin, and test a real submission from a logged-out browser.

  1. Register the site with the provider. For reCAPTCHA, choose v2 with the “I’m not a robot” checkbox, not v3, and add your domain. For hCaptcha, create a site in the hCaptcha dashboard and add your domain there. Copy the site key and the secret key.
  2. Paste both keys into the settings of the plugin that renders the form. The keys are tied to the domain, so a staging copy of the site needs its own pair or the challenge will fail there.
  3. Add the captcha field to the form, directly above the submit button, and decide what happens when the challenge is missing or wrong. The visitor should get a clear message and keep the post they wrote.
  4. Test it logged out. Open a private window, fill in the form as a guest, submit once with the challenge answered and once without it. Confirm that the first submission is saved and the second is refused, then check that a real spam-looking post is caught.

If the form runs on Front User Submit, a free plugin for frontend post submission and guest posting forms, both providers are available as fields you add in the form builder, and both are in the free version: the reCAPTCHA v2 field page and the hCaptcha field page cover the keys and options. The same builder also has a Cloudflare Turnstile field, a third free option that does not show image puzzles, set up with the same pair of keys.

reCAPTCHA or hCaptcha? A decision checklist

Choose hCaptcha when keeping Google out of the visitor’s browser is the point, and reCAPTCHA v2 when the familiar Google checkbox is worth more to your contributors than that. The effort is the same for both: an account with the provider, two keys, one field in the form.

reCAPTCHA v2

Google’s checkbox widget. It wins when your audience is non-technical and has seen the Google checkbox on other sites or when the site already loads Google services. It costs you one more Google script on every page that holds the form, plus a line in your privacy policy.

hCaptcha

An independent captcha service, often chosen as a privacy-friendly alternative to reCAPTCHA. It wins when you have promised visitors that Google scripts stay off the site, when your audience is privacy-conscious, or when you simply prefer not to add another Google dependency. It costs you the recognition factor: some visitors will not have seen the widget before, and a few will hesitate.

If this sounds like your site Pick Why
You tell visitors that Google scripts stay off the site hCaptcha the challenge is served by hCaptcha, not Google
Most contributors are first-time guest authors on mobile reCAPTCHA v2 the Google checkbox is one most people have seen before
The site already loads Google Maps, Analytics or fonts reCAPTCHA v2 one more Google request fits what you already run
Spam arrives in bursts and real submissions are rare either, plus review a captcha thins the queue but does not empty it

Matching the choice to the site:

  • Guest-post blog with a small pool of writers. hCaptcha if you have made privacy part of how you talk about the site, reCAPTCHA v2 if not. Either way, require an account and keep posts Pending.
  • Local directory where businesses submit their own listings. Use a captcha on the public form, keep every listing Pending, and check the queue on a schedule instead of the moment each one arrives.
  • Club, school or news site with known contributors. Consider skipping the captcha and relying on accounts and Pending review. A challenge is friction for people you already trust.

Layering a captcha with login and Pending review

A captcha stops automated submissions; it does not stop a person from sending nonsense, links or copied text, so the layers that catch those are login, review and notifications. Use them together and spam that gets past the checkbox still lands in a queue you control instead of on your front page.

Login. Requiring an account removes most automated submissions before the captcha is even reached, because bots rarely register and confirm. WordPress roles already do part of this work: a Subscriber cannot publish anything, and a Contributor can write posts but cannot publish them. Never give untrusted contributors a role that can publish without review.

Pending review. The Pending post status holds a post until an editor publishes it. In Front User Submit, the Post Status setting on the form is what decides this: set it to Pending and every submitted post waits for you, while the post submit settings page explains the redirect, buttons and success message that go with it. Pair Pending with an admin email notification so you know when the queue has something in it.

A quick read before publishing. Most spam is obvious in the title and first line. A minute on each submission catches the rest, and it is the only layer that judges meaning rather than behavior.

FAQ

Does a captcha alone stop spam on a post submission form?

No. A captcha raises the cost of automated submission, which thins the volume, but determined bots and paid human solvers get through, and a captcha says nothing about whether a post is any good. Treat it as the first layer and keep Pending review behind it.

Will reCAPTCHA or hCaptcha block real contributors?

Sometimes, especially when the image challenge appears on a slow phone or the visitor uses a screen reader. Test the audio option and keyboard access before launch, and consider showing the captcha only to logged-out visitors, since signed-in members are rarely the source of automated spam.

Do I need a paid plugin to use either one?

It depends on the form plugin you use. In Front User Submit, reCAPTCHA v2, hCaptcha and Cloudflare Turnstile are all free fields, so a free site can layer a captcha with login restriction, the Pending post status and moderation. With other plugins, if a captcha is the deciding feature for you, check the plan before you commit.