Skip to content

What visitors see

  • A regular visitor usually sees nothing. They fill in and submit the form as before.
  • The service script is loaded only when the visitor starts using the form (clicks into a field). The verification token is created only on submit so that it is fresh.
  • Failed verification: the form is not processed, the visitor sees a message (you set the text in the module) and keeps the data they entered. They just need to reload the page and try again.
  • Google reCAPTCHA v3: never shows a task or window. The visitor sees only a badge in the corner of the page, which appears only after the first click into a protected form. If you hide the badge, a text with links to Google’s terms is shown under the forms.
  • Cloudflare Turnstile: a regular visitor sees nothing. For a suspicious attempt a short check appears in the middle of the page after clicking submit. Set the widget mode to Managed in Cloudflare, in other modes no challenge is shown.
  • hCaptcha: the visitor sees the required privacy text under the form. For a risky attempt an image task appears after submitting. You set the strictness in the hCaptcha dashboard.
  1. Setup status panel: shows whether the keys are filled in and accepted by the service.
  2. Overview for the last 30 days: after submitting a form, the number of allowed attempts for that form increases. This is the best proof that the whole chain works.
  3. Blocking (reCAPTCHA v3): set the Najnižšie hodnotenie to 0.9 and try the form from a private window or over a VPN. You will see the failed verification message. Afterwards set the score back to 0.5, otherwise you may block real customers.
  4. Visible challenge (Turnstile, hCaptcha): they show it only for a suspicious attempt, so you cannot normally trigger it on demand. Both services offer test keys that force a challenge (see their documentation, the Testing section). After testing, replace the test keys with real ones, otherwise the forms do not protect against bots.
Was this article helpful?