Protect Public Forms with reCAPTCHA - Article
Summary
Public forms need to remain usable for legitimate visitors while reducing automated spam and abuse. The supported reCAPTCHA connection adds protection to selected form routes. Configure the correct site keys and domains, then verify the actual visitor journey rather than assuming that enabling one checkbox protects every form.
Use this article to:
- Prepare the supported provider registration and platform keys
- Choose which public form routes use protection
- Verify legitimate submission and investigate configuration failures
Choose the forms that need protection
A public training offer can attract legitimate prospects and automated submissions at the same time. Select protection around the forms your organization actually exposes, such as account signup, anonymous contact or Course On Demand enquiries.
The integration supports reCAPTCHA v3. It is a provider-backed risk-control mechanism, not a training assessment or an eligibility decision about which Course a person may attend. Keep the normal form validation and business process intact.
Register the intended domains
Ask Eurekos to confirm configuration access. Open Settings → Third party integrations → reCAPTCHA and follow the provider registration link where needed.
In the provider setup, register the intended site with reCAPTCHA v3 and list the actual domains on which the forms will be used. The domain entry excludes the https:// or http:// prefix. Review custom domains and environment differences with the platform owner instead of assuming a test domain covers production.
Obtain the Site key and Site secret for that registration. They have different roles; keep the secret private and use the matching pair from the intended provider configuration.
Configure the platform forms
Enter Site key and Site secret in the Eurekos integration form. Select the intended form options, then Save.
| Option | Protected route | What to verify |
|---|---|---|
| Enable on Sign up form | Account-registration form | A legitimate new-user submission can follow the intended registration journey |
| Enable on Contact form | An anonymous visitor uses the Contact form | An anonymous visitor can submit a valid enquiry |
| Enable on Course On Demand form | An anonymous visitor uses the Course On Demand form | A legitimate training enquiry reaches its normal follow-up process |
These are separate choices. Enabling the Sign up form does not establish that Contact or Course On Demand is also protected. The anonymous-form behavior should not be generalized to every authenticated form or every page of the platform.
Test the visitor journey in context
Use the actual intended domain and an ordinary visitor session. Check that the provider protection is present and that a legitimate complete form can be submitted through the normal process. Confirm the resulting account or enquiry evidence separately from the visible provider indicator.
Coordinate the test with the owner of registration and notification settings. A successful form submission can still be followed by the platform’s normal approval, email or enrollment requirements. Protection does not replace those steps.
If a form stops working after configuration, identify whether the failure comes from a domain/key mismatch, provider loading or the form’s own validation. Avoid repeatedly changing unrelated registration rules to resolve a provider setup problem.
Verify the configuration
| Scenario or check | Expected result or evidence |
|---|---|
| Provider registration | Supported v3 configuration and the correct intended domains |
| Matching keys | Site key and private Site secret belong to that registration |
| Each enabled public form | Protection is present and legitimate submission follows the normal workflow |
| An authenticated user context | Protection is tested on the specific enabled form and visitor state |
| A changed production/custom domain | Provider registration and working submission are rechecked |
Troubleshooting
| Problem | What to check |
|---|---|
| A protected form fails after setup | Matching v3 keys, registered domain and provider-loading evidence |
| One form is protected but another is not | Separate enable options for Sign up, Contact and Course On Demand |
| The test works only on the test domain | Register and verify the intended production/custom domain |
| A legitimate submission is not recorded | Separate provider validation from the form’s own required fields and downstream workflow |
| The secret appears in an instructional asset | Remove the exposure and coordinate replacement through the credential owner |
FAQ
-
Does enabling reCAPTCHA on Sign up protect every public form?
No. Sign up, Contact and Course On Demand have separate enable options in the integration form.
-
Which reCAPTCHA version does Eurekos support?
The integration supports reCAPTCHA v3. Use keys and a provider registration for that version and the intended domains.