The quietest way to go out of business

Fixing Broken Website Forms: How to Test Yours Today and Stop Losing Leads

A website form can tell a customer "thanks, we'll be in touch" and then throw the message away. The customer thinks you ignored them. You think business is slow. Nobody ever sends you an error. Here is a four-minute test, what each result means, and who fixes it when it is beyond you.

November 16, 2026 · 9 min read

acmefence.com · one form message, end to end
Where the message went
The customer saw a thank-you. The mail never landed
  1. 09:14 form submitted from contact page
  2. 09:14 confirmation shown: Thanks, we'll be in touch
  3. 09:14 server sends mail as info@acmefence.com
  4. 09:14 no SPF or DKIM for sending server
  5. 09:14 message rejected by recipient mail system
  6. 09:14 no copy stored on the site
Illustrative: a sample trace for a fictional fence company

The short answer

Test a website form by submitting it yourself from a phone with a personal email address, then confirming the message reached the inbox you read. If it does not arrive, check the destination address, the spam folder, the form's own stored entries, and whether your site's mail is authenticated with SPF or DKIM. Repeat the test monthly.

On this page
  1. A thank-you message proves only that a thank-you message works
  2. The four-minute test, done the way a stranger would do it
  3. What the result is telling you
  4. Your website has been forging your signature, and Gmail noticed
  5. Spam filters that are better at stopping customers than robots
  6. Getting back the leads you already lost
  7. Who should fix it, and what that costs you

A thank-you message proves only that a thank-you message works

When a visitor presses Send, the form does two separate things. It shows them a pleasant confirmation. And it tries to deliver the message to you, through a series of steps it does not report on. The first can succeed while the second fails entirely, for months. The whole design is cheerful in a way that should worry you, like a mail carrier who waves at you while dropping your letters in a creek.

Forms usually break after something ordinary. A plugin update. A hosting move. A staff change, so the form now mails a person who left. A rule change at the email provider. Nothing on the site looks different after any of those, which is why owners tend to find out late, if ever, and usually from a customer who says "I tried to reach you." A broken form is one of the first things to rule out when a website stops producing leads.

The four-minute test, done the way a stranger would do it

Your desktop browser may have saved logins and form data, so it is a poor stand-in. Use your phone, with Wi-Fi off. You will want to do this on every form on the site, including the quote form buried on the page nobody visits, because people who reach that page tend to be serious.

  1. 1

    Use an address the site has never seen

    A personal Gmail is a good choice. A customer from Gmail is common, and your own company address may be treated differently, since it is mailing itself.

  2. 2

    Put a dated word in the message

    "Form test November, ignore." Searching for that word later finds it in every folder at once.

  3. 3

    Press Send and write down the time

    Note exactly what happens on screen: a confirmation, a red error, or a button that does nothing at all.

  4. 4

    Check every inbox it might reach

    The one you read, spam and junk folders, then whichever inbox belonged to the person who used to do this.

  5. 5

    Reply to the message

    Does the reply go to the customer's address, or to your own website? A form that makes you unable to reply has only half worked.

  6. 6

    Do the same with the booking link and the phone link

    Press the tap-to-call number. Book a slot, then cancel it. These break too, and you might as well check while you are here.

Layered colored-paper scene of a tiny shop with a paper envelope falling through a gap in a pipe toward a dark hole below, soft shadows, no words
The customer sees the first half of the trip, and you see only what makes it to the end.

What the result is telling you

Reading the test: what happened, what it probably means and what to do
Likely causeFirst fix
The button does nothingA script conflict, often after an update or a speed pluginUndo the last change. On WordPress, this is the $199 conflict fix
A red error appearsThe form plugin, a spam check or the serverScreenshot the wording. On WordPress, a single error is the $149 fix
Confirmation appears, no email anywhereThe server's mail never left or was refusedCheck the form's stored entries, then set up authenticated sending, below
It lands in spamYour mail is not authenticated, or the content looks like spamAuthenticate the domain, and mark it as not spam
It reaches the wrong personAn old address in the form's settingsChange it, and use a shared address that survives staff changes
It arrives, but hours lateA delayed queue, or a provider slowing your mailMove to an email sending service, and retest

On a hosted builder, the notification settings come first, since a form there often saves entries in a dashboard and emails only if told to. Squarespace forms not sending is a good model of that. On a store, it is a neighboring problem, covered in WooCommerce order emails not sending.

Your website has been forging your signature, and Gmail noticed

Here is why a form that worked for years can stop without anyone touching it. Most forms send mail from your web server, labeled as coming from your domain. To the receiving mail system, that looks like what a scammer does: a machine claiming to be you, without proof. SPF and DKIM are the proof. They are records you publish in your DNS that say which servers may send as you, and that sign what they send.

Google's sender guidelines, as read in November 2026, require all senders to Gmail accounts to set up SPF or DKIM, starting February 1, 2024. Those sending 5,000 or more messages a day must do more, and that is not you. So if your form sends from an unauthenticated server, Gmail may refuse it or send it to spam, and any customer or owner on Gmail can be affected.

  1. 1.Stop sending from the web server. Route form mail through a real email service, using a sending account for your domain. On WordPress, an SMTP plugin connects the two.
  2. 2.Publish SPF and DKIM. Your email provider gives you the DNS records. Add them where your DNS lives, and keep the rest of the records untouched.
  3. 3.Make the sender your own domain, and set reply-to as the customer. Pretending the mail came from the customer's Gmail address is a common setting that invites rejection.
  4. 4.Store every submission on the site as well. Then a mail failure loses you a notification, not the lead itself.
  5. 5.Recheck after any hosting move. Moves change where mail comes from. If your regular email is affected too, see this page on lost email after a move.
A lead that was stored and not delivered can be recovered. A lead that was never stored has no name to call.

Spam filters that are better at stopping customers than robots

Then there is the opposite failure. An owner gets forty messages about crypto and SEO in a week and turns on every defense available. Now a customer with a flooded basement is asked to identify traffic lights three times on a phone. Some of them will go call someone else, and you will not hear about it, for the same reason you did not hear about the mail problem.

Try these first

  • A hidden field that only robots fill in
  • A check on how quickly the form was submitted
  • A filter that holds suspected spam for review rather than deleting it
  • Fewer fields, since it helps customers and hurts nothing

Go easy on these

  • A visible puzzle before the customer can send
  • Blocking whole countries or free email domains
  • Filters that silently delete anything they doubt
  • Stacking three security plugins on a single form

We wrote more on this in why WordPress forms get spammed. The test for any filter is simple: send yourself a real-looking message after you turn it on, and check the holding folder once a week. Spam is annoying. A silently deleted customer is expensive.

Getting back the leads you already lost

Sometimes some of them can be recovered. Many form plugins keep entries on the site, even when the email failed. Look in the plugin's entries or submissions screen, and in any spam-holding folder. Check your host's mail logs if you know how, and the old inbox. Search your own mail for your form's subject line. If your form connects to a service such as a CRM or booking tool, look there too. Then call them. Yes, even at six weeks.

Then find out how long the gap was, so you know how to read last quarter. Tracking can help: conversion tracking for a small shop shows when submissions drop to zero, as long as the tag sits on the real success step. If your ad reports suddenly look strange, your conversion tracking setup may have broken at the same moment as the form, which also means your ads have been optimizing toward nothing.

Who should fix it, and what that costs you

Do it yourself: $0

Correcting the address, fixing a builder's notification settings and removing a filter are all free. If you can get to your DNS, adding the records your email provider gives you takes minutes. Screenshot everything first.

WordPress repair: $149 or $199

A single error is $149, and a theme or plugin conflict is $199, at fixed prices with a refund if we cannot fix it. We start within one business day of payment.

Anything else: quoted

On a custom site or an unusual setup, our form and script repair follows a real message end to end and finds where it stops. We quote after looking.

Staying fixed: from $55 a month

Hosting and maintenance puts someone on the job of watching. Or put a monthly form test on your calendar for free. That works too, if you actually do it.

Every new site we build includes lead form capture and online booking, on Athena CMS, in packages starting at $1,500. If your form is one of several things wrong, weigh repair against replacement first, or see the general triage guide. The free website health check can flag more problems, and the maintenance section covers what else tends to break unattended. All of it sits in our guide for very small businesses.

Questions owner-operators ask

Something usually did change, just not by you. A plugin may have updated itself. Your host may have changed its mail settings. Email providers tighten their rules, as Google did for all senders to Gmail starting February 1, 2024. An employee's address may have been shut off. Test the form first, then check what updated lately, and then look at how the site sends its mail.

Test from a personal address too, since your own domain can behave oddly when it mails itself. A message to your own address may be filtered as suspicious or may slip through more easily than a customer's would. Using a Gmail account and one other provider gives you a better picture. Send from a phone so you see what a customer sees.

A difficult one can, and you will not see it happen, since a person who gives up leaves no record. We cannot give you a percentage that would apply to your site. Try invisible methods first, such as a hidden field and a timing check, and hold suspected spam for review. If spam still floods in, add a visible check, and then test it yourself on a phone.

Once a month, and again after any update, hosting move, staff change or email change. Put it on your calendar next to something you already do, like paying a bill. It takes a few minutes. If someone else maintains your site, ask them when they last tested it and how. A vague answer is itself a useful test result.

You can, and for some one-person businesses it is fine. But you are on a job half the day, and some people would rather type at 9 p.m. than call. A form also captures someone you cannot answer right away. If you keep one, keep it short: name, contact, job and town. If you remove it, make sure the voicemail is working and is actually checked.

Almost always. A form is a small part of a site, and the usual causes are settings, a conflict or mail authentication. On WordPress, that is typically our $149 or $199 fixed-price repair. A rebuild only becomes a real question if the site has many other problems, in which case it is worth comparing the costs before paying for anything.

Keep reading

Free · No obligation

Failed the test? Tell us where the message stopped

Tell us what happened when you pressed Send, and what your site runs on. A person at DataCram replies with the likely cause, and says if it is a fix you can make yourself.

Which of these sounds like you? (pick any)

Rather talk now? Call (210) 346-0848.

CallGet a quote