FREEFirst project with us? Your landing page design is on the house.See the offer

Webflow

How to stop form spam in Webflow, in the right order

Webflow has bot blocking, spam filtering and reCAPTCHA built in. What each one stops, when to add a honeypot, and the server checks for forms you host yourself.

By Abdul QuadirUpdated 2026-11-036 min read
TL;DR
  • Start with Webflow's own bot blocking and spam filtering. Both live in Site settings and apply to every form on the site.
  • Add a honeypot field if spam still gets through. Webflow's help pages describe it as a hidden field plus custom code.
  • Use reCAPTCHA last. It works, but it asks real people to prove they are human, and once it is on, every form needs the reCAPTCHA element.
  • If a form posts to your own endpoint, the checks must happen on the server. A widget in the browser alone does not protect the form.
  • Test every form after each change, on desktop and phone, and check the leads still reach your inbox and CRM.

The short answer

To stop form spam in Webflow, start with the two built-in switches. In Site settings, open Apps and Integrations, find Cloudflare Turnstile spam protection, and turn on bot blocking and spam filtering. Publish the site. If spam still gets through, add a honeypot field. Add reCAPTCHA only if you still need it, because it adds a step for real people. If your form sends data to your own endpoint instead of Webflow, check every submission on the server as well.

That order keeps the site easy to use while closing the gaps one at a time.

What Webflow offers out of the box

Webflow's help page on form spam lists four methods. Three are settings or elements you can use without code, and one needs a little custom code:

  • Bot blocking. A site-level setting that uses Cloudflare Turnstile. Webflow says it looks at signals such as mouse movement and input to tell bots from people, and blocks submissions from bots.
  • Spam filtering. A site-level setting that checks the data sent through your forms and filters out spam.
  • reCAPTCHA. A form element that asks visitors to confirm they are human before they submit.
  • Honeypot. A hidden field that people never see but bots often fill in. Webflow's help describes it as a hidden field plus custom code that blocks the submission.

Bot blocking and spam filtering apply to every form on the site once they are on. You can use them together with reCAPTCHA.

Step 1: turn on bot blocking and spam filtering

  1. Open Site settings, then Apps and Integrations.
  2. Find Cloudflare Turnstile spam protection.
  3. Turn on bot blocking and turn on spam filtering.
  4. Publish the site. Settings like this only reach the live site after a publish.

One detail catches people out. With bot blocking on, Webflow disables the submit button while the bot check loads. Style the button's disabled state in the Style panel so it looks like it is loading, not broken. Webflow's help page also shows how to target the loading state with a little custom CSS or JavaScript if you want a "Loading" label on the button.

Step 2: add a honeypot if spam continues

A honeypot is a field that real visitors never see. Simple bots fill in every field they find, so a value in the hidden field marks the submission as spam.

  • Add a text field with a plain, believable name, such as "website" or "company_url".
  • Hide it with a class that moves it off screen, and add tabindex="-1" and autocomplete="off" as custom attributes so keyboard users and browsers skip it.
  • Add custom code that stops the submission when the field has a value.

Know the limit. A check that runs in the browser only stops bots that run your page's scripts. Bots that post straight to the form endpoint skip it. That is why the built-in checks, which Webflow runs on its side, come first.

Step 3: reCAPTCHA, when it is worth the friction

reCAPTCHA puts an "I'm not a robot" step in front of your visitors. It blocks a lot of automated spam, but Webflow's own help page notes it can hurt the visitor experience and that advanced bots can get past it. Use it on forms that still attract spam after steps 1 and 2.

Two things to know before you switch it on, from Webflow's guide to reCAPTCHA:

  • The native setup uses the reCAPTCHA v2 checkbox. Keys made for another version will not work.
  • Once it is on for the site, every form needs a reCAPTCHA element, or submissions from that form fail. The newsletter form in your footer counts.

Forms you host yourself need server checks

Some forms do not use Webflow's form handler. They post to a webhook, a serverless function or your own API, often to send leads straight to a CRM. Webflow's site settings do not protect those. You need checks on the server that receives the data.

If you add Cloudflare Turnstile with custom code, Cloudflare's server-side validation docs are clear: the widget alone does not protect your form, and your server must call the Siteverify API for each token. Cloudflare also says each token can be checked only once and expires after a few minutes.

Other server checks that cost nothing to visitors:

  • Accept only what you expect. Known fields, sensible length caps, a valid email format.
  • Check where the request came from. Refuse posts from other sites.
  • Rate limit. Cap how many submissions one address can send in a short window.
  • Escape values for spreadsheets. If leads land in a sheet, a value that starts with "=" should not run as a formula.

Our own site's lead route checks the origin, caps field lengths, rate limits and escapes spreadsheet values. It is a small amount of code and it removes a whole class of junk.

Which method to use: a quick table

MethodStopsCost to real visitorsWhere
Bot blockingAutomated submissionsSubmit button waits a momentSite settings
Spam filteringSpammy content in the dataNoneSite settings
HoneypotSimple bots that fill every fieldNoneHidden field and custom code
reCAPTCHA v2Most automated spamA checkbox, sometimes a puzzleSite settings and a form element
Server checksDirect posts to your own endpointNoneYour server or function

When the spam is from people

Some spam is typed by hand: sales pitches, link offers, "SEO packages". No bot check stops a real person. Handle it after the form instead:

  • Add a required question only a real buyer can answer, such as a budget range or a project type.
  • Filter in your CRM or inbox before anything triggers an automation.
  • Keep spam out of your analytics. If a lead event fires on every submit, junk inflates your numbers. Our guide to tracking form submits in GA4 shows where to fire the event.

Test after every change

  1. Submit every form on the live site, including footer and popup forms.
  2. Check the submission appears in Webflow and the notification email arrives.
  3. Check it reaches your CRM or sheet, if you connected one.
  4. Try it on a phone, where slow connections make the loading state easy to see.
  5. Look at the button while the bot check loads. It should look like it is waiting, not dead.

What to do next

Turn on bot blocking and spam filtering today, publish, and watch a week of submissions. Add the honeypot only if you need it, then reCAPTCHA. If your forms feed a CRM through your own code, add the server checks above. Spam settings are one of many small jobs after launch; our post on what breaks after launch covers the rest.

Want us to set it up or check it? See Webflow development or our care plan, or send us your site.

Abdul Quadir
Abdul QuadirFounder of Kookies. Builds Webflow and Astro sites for startups and growing teams.

Terms used: Webflow, Core Web Vitals

FAQs

Questions
people ask.

Abdul Quadir
Still have a question?Ask us directly. We reply within a day.
Book a callPick a timehello@kookies.io

Turn on bot blocking and spam filtering in Site settings under Cloudflare Turnstile spam protection, then publish. Add a honeypot field if spam continues, and reCAPTCHA as a last step.

Yes. Webflow's bot blocking setting uses Cloudflare Turnstile. You turn it on under Site settings, Apps and Integrations, and it applies to every form on the site.

With bot blocking on, Webflow disables the submit button while the bot check loads. Style the disabled state so it looks like it is loading.

Webflow's native setup uses the reCAPTCHA v2 checkbox. Once enabled, every form on the site needs a reCAPTCHA element, or its submissions fail.

No. It stops simple bots that fill in every field. A check in the browser does not stop bots that post straight to the form endpoint.

No. Those forms skip Webflow's form handler, so the checks must run on your server, including Turnstile token validation if you use it.

Your turn

Let's kook
what you krave.

Hi Kookies, I need a built on . I'd love to launch . Reach me at
or book a callSent. We reply within one working day.