Should your website keep its CAPTCHA?
October 26, 2026
You know the test. Click every traffic light. Pick the crosswalks. Prove you are human before the website will let you send a message, book an appointment, or ask for a quote. That test is a CAPTCHA, and if your website has forms, there is a fair chance one is standing guard over them.
It was put there for a good reason. The question worth asking now is whether it is still earning its keep, because the cost side of the ledger has quietly changed.
What a CAPTCHA actually does
A CAPTCHA separates people from software. Bots submit contact forms by the thousand, stuff login pages with stolen passwords, create fake accounts, and test stolen credit cards against store checkouts. A working CAPTCHA blocks a large share of that abuse before it reaches you. If your site takes payments, has customer logins, or gets real spam today, that protection is not decoration. It is doing a job.
The case for keeping it
- Online stores and checkout pages. Card testing, where criminals run thousands of small charges to check stolen card numbers, is a real and expensive attack. Bot protection here could save you from fees and a shut-down payment account.
- Logins, portals, and signups. Member areas, account creation, and free-trial forms are magnets for automated abuse. A challenge at the door is reasonable.
- Forms that already get spammed. If junk submissions land in your inbox every week, removing protection without a replacement may trade a small friction problem for a daily cleanup problem.
The case against, especially for service businesses
Most local businesses are not running stores or portals. A law firm, an accounting practice, a dental office, a plumbing or HVAC company: the website is information plus a contact form, and that form is where the leads live. On that kind of site, a puzzle-style CAPTCHA can cost more than it protects against.
- People give up. Every extra step between a visitor and a sent message loses some of them, and puzzles on a phone screen lose more. A potential client who cannot be bothered to click buses three times may simply call the next firm on the list.
- Some customers cannot pass them. Image challenges are hard for people with vision or motor difficulties, and a customer who physically cannot complete your form is a customer turned away at the door.
- AI assistants get stopped too. More customers now send an AI agent to research options, gather quotes, or start a booking on their behalf. A hard bot wall treats that assistant exactly like the spam it was built to stop. The assistant usually does not report back that your form rejected it. It moves on, and you never learn the inquiry existed.
The middle path most businesses should take
This is rarely an all-or-nothing choice. Modern bot protection can run invisibly, scoring each visit and only challenging the ones that look suspicious. Tools like Cloudflare Turnstile and the score-based version of reCAPTCHA exist for exactly this. A few practical rules cover most cases:
- Protect the form, not the whole site. Reading your pages should never require proving anything.
- Challenge suspicious visits, not every visitor. Risk-based settings reserve the puzzles for traffic that looks automated.
- Guard the valuable doors hardest. Logins and checkouts deserve strong protection. A request-a-callback form deserves a lighter touch.
- Count both sides. If spam is rare and inquiries matter, the balance potentially tips toward less friction. If abuse is constant, it tips the other way.
A simple way to decide
Ask two questions. First, what is this CAPTCHA actually stopping? If you cannot point to real spam, fake accounts, or abuse it has blocked, it may be a default nobody ever reviewed rather than a decision somebody made. Second, what might it be turning away? On a services business, one lost client can outweigh a year of deleted spam.
Protection chosen on purpose is good practice. Protection left on by accident is just friction. Our free scan checks, among other things, whether an automated reader can reach your business at all, which is a reasonable place to start the review.