SilentShield

Migration from Other Solutions

Step-by-step guide for migrating from reCAPTCHA, hCaptcha, or other CAPTCHA solutions to SilentShield.

From Google reCAPTCHA

  1. Create a SilentShield account and API key for your domain
  2. Remove the reCAPTCHA script tag (google.com/recaptcha/api.js)
  3. Remove any grecaptcha.render() or grecaptcha.execute() calls
  4. Add the SilentShield script tag and init call
  5. Replace your server-side reCAPTCHA verification with SilentShield nonce verification
  6. Test with ?silentshield-debug to verify the widget is working

SilentShield automatically detects forms — you don't need to add data-sitekey attributes or form callbacks.

From hCaptcha

  1. Remove the hCaptcha script tag (hcaptcha.com/1/api.js)
  2. Remove any h-captcha div elements and data-sitekey attributes
  3. Add the SilentShield script tag and init call
  4. Replace your server-side hCaptcha verification (hcaptcha.com/siteverify) with SilentShield nonce verification
  5. Test your forms to verify protection is active

From Cloudflare Turnstile

  1. Remove the Turnstile script tag (challenges.cloudflare.com/turnstile/v0/api.js)
  2. Remove any cf-turnstile div elements
  3. Add the SilentShield script tag and init call
  4. Replace your server-side Turnstile verification with SilentShield nonce verification
  5. Test your forms to verify protection is active

Migration Tips

  • Run both solutions in parallel during migration to ensure no downtime
  • Use SilentShield's debug mode (?silentshield-debug) to verify correct operation
  • Start with your development environment before deploying to production
  • Monitor your analytics dashboard after migration to ensure expected detection rates