A WordPress contact form not sending email can fail without announcing itself. The form still loads. A visitor fills it in, clicks submit and sees a thank-you screen. Nothing on the page looks wrong. Our verdict: that screen shows the website accepted the entry, and it doesn’t show that an email reached anyone. Before you change a setting, submit the live form twice — once with an address at a mailbox provider, once with an address on your own business domain — and read where each message lands.
A visitor who fills in the form sees a confirmation and waits to hear from you. If the notification doesn’t reach an inbox, that person’s request goes unanswered, and nothing in your inbox shows it happened.
So the first move isn’t a repair. It’s a test you can run yourself, and the result tells you whether to act with urgency, schedule it or carry on.
A Thank-You Screen Proves Less Than It Seems
The confirmation screen is the website talking about itself. It tells you the page took what the visitor typed and moved to the next step. It doesn’t tell you an email landed anywhere.
That distinction isn’t ours to make. WordPress’s own developer documentation says a successful result from the site’s mail function “does not automatically mean that the user received the email successfully” — it means the method could process the request without errors.
In our reading, a notification has four handoffs to clear. The form accepts the entry. The site sends a message. The receiving provider accepts it. The message reaches the inbox instead of the spam folder, where a provider puts mail it doesn’t trust. The thank-you screen alone can’t confirm the other three.
A form that looks healthy can be failing at the second, third or fourth. The thank-you screen won’t mention it.
Run a Two-Address Test Before You Change Anything
This test is ours, not a rule from any documentation. It needs no access to settings, code or hosting.
- Open the live form on your phone using mobile data, or in a private browser window, so you’re seeing what a visitor sees rather than a logged-in version of your own site.
- Submit it once as a visitor, using an address at a mailbox provider. Put a distinctive phrase in the message along with “TEST, please ignore” so you can find it later and nobody answers it as a real request.
- Submit it again, this time with an address on your own business domain.
- Check the inbox that’s supposed to receive form notifications, and check its spam or junk folder too. For each test, note whether it arrived, where it landed and what the sender line shows — that’s the From: address a message appears to come from.
- Write down when you submitted each one, so whoever looks into it can trace the messages.
Why two addresses? Google’s email sender guidelines, which cover mail sent to Gmail accounts, give senders a plain instruction: “Don’t impersonate Gmail From: headers.” In our reading, a form that puts the visitor’s own address on the sender line can end up looking like that to a receiving provider, which makes a test address at the provider those guidelines cover a useful probe. The second test, from an address on your own domain, gives you something to compare against.
Nothing Arrives, Even in Spam
You ran both tests. The inbox that should receive form notifications is empty. Its junk folder is empty too, and your distinctive phrase turns up nothing.
What it can mean: the site can be failing to send at all, the notification address inside the form’s settings can be wrong or belong to someone who has left, or something between the site and the inbox can be refusing the message. From the inbox alone, you can’t tell which.
Waiting is the real risk. If your own tests don’t arrive, live submissions can be failing the same way, and from the visitor’s side the two look identical — thank-you screen, then silence.
Do this first. If the form keeps a record of entries inside the site, compare that record against your inbox, confirm which address is meant to receive notifications, then hand your submission times to whoever manages the site.
It Lands in Spam or Junk
The message arrived. It’s in the junk folder, not the inbox. Treat that as delivery you can’t count on.
A receiving provider needs some way to check that a message claiming to come from your domain was sent by something the domain’s owner allows. Email authentication is that check — records published for your domain, two of which are called SPF and DKIM. Google’s sender guidelines ask senders to set up SPF or DKIM authentication for their sending domains, and say messages that aren’t authenticated with these methods might be marked as spam or rejected. Those guidelines cover mail sent to Gmail accounts; other providers set their own rules.
The risk of waiting is quiet. A real lead’s message can sit in a folder nobody opens, or be rejected before it reaches a folder at all.
Do this first. Resist marking one message “not spam” and moving on, which can train a single mailbox without changing anything on the sending side. Ask whoever manages your domain whether authentication is set up for whatever sends the form’s email, and if a separate service does the sending, whether that service authenticates your domain’s email.
Only One of the Two Tests Arrives
One test landed. The other didn’t. In our reading, that’s a narrower problem than total silence.
If the mailbox-provider test failed and the business-domain test arrived, in our reading the sender line is the first thing to look at, given what Google’s guidelines say about Gmail From: headers. If it went the other way, the split still points somewhere useful.
We can’t name the cause from here, and we wouldn’t try. Whichever test failed, tell whoever fixes it which address you used and when you submitted it. That detail saves a round of guessing.
It Worked Until Something Changed
A form that has been delivering can stop without anyone touching the form. A plugin update, a theme change, a move to different hosting, a domain change, a switch of email provider — any of those can change how the form’s email travels. As a general rule, the path matters as much as the form.
The risk of waiting is that the failure stays silent. Visitors keep submitting, the thank-you screen keeps appearing, and the gap can come to light when someone mentions they filled in your form and heard nothing back.
Do this first. Write down what changed on the site and when — updates, a new theme, a hosting move, a domain or email change. Whoever fixes it can use that list.
Spilt Media’s WordPress support plans list plugin updates and troubleshooting among what they handle.
In our reading, having a named owner for the site makes a failed test easier to act on.
And if every test passes while the leads still seem to have dried up, it’s worth ruling out the other reasons a website stops generating leads before you keep testing the form.
Sort Your Result Into Urgent, Soon or Fine
- Urgent if neither test reached the inbox, whether they went to spam or never arrived. Live submissions can be failing the same way, and each one is a person who believes you have their message.
- Soon if only one of the two tests reached the inbox, or both did but the sender line or reply address looks wrong — the reply address being where your answer goes when you hit Reply. In our reading, delivery is partly working, so the search is narrower and a scheduled fix is reasonable.
- Fine if both tests landed in the inbox and the sender line and reply address look right. That’s a pass for the moment you ran it, and nothing more. Put the next test on a routine you’ll keep.
Once both tests reach your inbox, the next question is where your leads are actually coming from, because a working form doesn’t by itself tell you which channel sent the person to it.
What to Ask Whoever Manages Your Site
- Which address do the form’s notification emails come from, and where does Reply go? WordPress has a default sender address, and using a different one takes a setting made by the form or the site.
- Is whatever sends the form’s email set up with SPF or DKIM for our domain, and if a separate service sends it, does that service authenticate our domain’s email?
- Does the form keep a record of every entry inside the site, so a lost email isn’t a lost lead?
- Who gets told when sending fails, and how do they find out?
- When was the last full test of the form, and what has changed on the site since then?
These questions work the same whether a developer, your host or an agency looks after the site. The answers tell you who owns the next step.
Frequently Asked Questions About Contact Form Emails
Why does my WordPress form say sent when no email arrives?
The message you see is the site reporting on its own work. It tells you the site accepted the entry. WordPress’s documentation is blunt about what a successful send result means: the method processed the request without errors, not that anyone received anything. Everything after that sits outside the result, and those later steps are the ones an inbox can show you.
Why do contact form emails land in spam?
For mail sent to Gmail accounts, Google’s guidelines are specific on two points. Messages that aren’t authenticated with SPF or DKIM might be marked as spam or rejected, and senders are told not to impersonate Gmail From: headers. In our reading, that makes the sender line one of the first things worth checking when a form’s email keeps landing in junk. Other providers filter on their own rules, so one mailbox’s verdict isn’t the whole picture.
Can I send form notifications to a second address?
Ask whoever manages the form, because how yours is set up isn’t something we’d assume. Be clear about what a second recipient does, though. It’s a backup route, not a repair. If something stopped the first notification from getting through, a second address can meet the same obstacle. Add one for redundancy if you like, then fix the original path.
How often should I test my contact form?
Our suggestion, and it is a suggestion rather than a rule: after any change to the site, its plugins, the hosting, the domain or the email provider, and then on a routine you’ll keep, such as once a month. A short test you run on schedule beats a thorough one you keep postponing.
Not Sure Who Is Responsible for Your Form Emails?
If you’ve run the test and you’re not sure who should act on the result, that’s a conversation worth having. Bring what you wrote down: which test failed, where it landed, what changed before it started. You can book a consultation with Spilt Media and talk it through.