How to Secure Your Forms

As your static website grows, it becomes a target for automated spam bots. These bots crawl the web to submit fake entries through contact forms and newsletter sign-ups. To keep your data clean, Static.app offers two specialized security features in the Forms section:

  • Honeypot Field: A simple but effective "trap." It creates a hidden field that only bots can see. If the field is filled out, Static.app knows the submitter is a bot and rejects the entry.
  • reCAPTCHA v3: An advanced, invisible security layer from Google. It uses AI to score users based on their interactions, blocking high-risk traffic without requiring users to solve puzzles.

Configure the Honeypot Field

The Honeypot is your first line of defense. It is "invisible" to human users but irresistible to automated scripts.

  1. Log in to your Static.app dashboard and select your project.
  2. Navigate to Settings and then Forms.
  3. Locate the Honeypot Field Name (optional) field.
  4. Enter a generic name for this hidden field, such as middle_name   or phone_ext  .
  5. Click Save Changes.

Note: Using a common-sounding name is more effective at "tricking" bots.

The Honeypot Field
Configuring the Honeypot

Enable reCAPTCHA v3

For more robust protection, you can integrate Google’s industry-standard verification system.

  1. Visit Google reCAPTCHA site. Register your domain to receive two specific strings: a Site Key and a Secret Key.

    Google reCAPTCHA
    Google reCAPTCHA
  2. In your Static.app Forms settings, check the box labeled Enable reCAPTCHA v3.
  3. Paste your public Site Key into the reCAPTCHA v3 Site Key field. This key is used to identify your site to Google's service.
  4. Paste your private Secret Key into the reCAPTCHA v3 Secret Key field. This key allows Static.app’s server to securely communicate with Google to validate the submission.
  5. Click Save Changes.
Enable reCAPTCHA v3
Enable reCAPTCHA v3
Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.

Still need help? Contact Us Contact Us