Before changing anything, trigger one real email from the live site, not just from the dashboard. Use a private browser window, submit the real form with a unique phrase you can search for later, and wait a few minutes. If nothing lands in your inbox or spam folder, work through the checks below in order. You can also paste your form URL into our free form checker first to see how the form is structured before you start digging.
First, run a real WordPress email test
Start with a test you can search for later. Use a private browser window and trigger a real email from the live site, not only from the dashboard.
Use a unique phrase such as WordPress email test July 2026 in the form message, password reset request, or test order note. After submitting, search your inbox, spam folder, all mail, and quarantine for that exact phrase. That tells you whether the message was ever accepted and where it ended up.
Check the WordPress admin email address
Go to Dashboard > Settings > General and check the Administration Email Address field. This address receives important site notifications, including updates, recovery mode, user registrations, and some plugin or theme warnings.
Make sure it is an inbox your business can access. If you change it, WordPress sends a confirmation email to the new address. The new address usually does not become active until that link is clicked.
Check whether WordPress can send through SMTP
Many WordPress email problems happen because the site is relying on the default server mail function. An SMTP plugin connects WordPress to a real mailer, such as your email provider, host SMTP account, or transactional email service.
Send a test email from the SMTP plugin
If you already use an SMTP plugin, test it first. In WP Mail SMTP, go to WP Mail SMTP > Tools > Email Test and send a message to an inbox you control.
A successful SMTP test means WordPress can hand a message to the configured mailer. It does not prove every form notification is correct, but it confirms the sending path is working.
If the test fails, save the error first
A failed test points to the mailer setup, login, API key, host, port, encryption, blocked outbound mail, or domain authentication. Save the error message before changing settings.
Check the From Email and sender domain
Open the SMTP settings and check the From Email and From Name fields. When possible, use an address on your website domain, such as [email protected], instead of a free Gmail or Outlook address.
The From Email should match what the mailer is allowed to send. If the SMTP account is [email protected] but a plugin sends from [email protected], the message may be rejected, filtered, or treated as suspicious.
If your SMTP plugin has a Force From Email option, enable it after confirming the correct sender address. This helps keep all site emails on the same authenticated sender.
Check the notification that should have sent
If the SMTP test works but contact form emails are not sending, check the form notification itself. A working SMTP test will not fix a disabled notification, wrong recipient, or broken condition.
Open the form plugin and find its email or notification settings. Check Send To Email, From Email, Reply-To, Subject, Message, and whether the notification is enabled.
The recipient should be the business inbox. The From Email should usually be your authenticated sender address. Reply-To should use the visitor email field, so replies go to the lead.
Check whether the submission was saved or logged
This step separates form submission problems from email notification problems.
If your form plugin saves entries, open the entries or submissions screen and search for your test phrase. If the entry exists, the form accepted the submission and the issue is likely email delivery, spam filtering, routing, or notification settings.
If there is no entry, the form may not be submitting. Check required fields, JavaScript errors, reCAPTCHA, anti-spam settings, caching, firewall rules, and plugin conflicts. Some free form plugins do not store entries unless that feature is enabled or included in the plan.
Check spam, filters, forwarding, and inbox rules
If WordPress is sending but the message is hidden after delivery, the problem is in the mailbox path. Search for your exact test phrase in spam, junk, promotions, deleted items, all mail, and quarantine.
Also check forwarding rules and inbox filters. A rule may be archiving form notifications, moving them to a folder, or forwarding them to a person who no longer handles leads.
If messages land in spam, review the sender address, subject, message content, and links. Mismatched From addresses and weak sender authentication often make a delivery problem look like a site problem when it is really filtering. These authentication issues are covered in more depth in 10 reasons your contact form is silently broken.
Check SPF, DKIM, DMARC, and mailer warnings
If your SMTP plugin or mailer shows DNS warnings, fix those next. SPF, DKIM, and DMARC help inbox providers decide whether your domain is allowed to send the email.
Open your mailer's setup instructions, copy the required DNS records exactly, and add them where your domain DNS is managed. Avoid duplicate SPF records. Then run another test after DNS has had time to update.
Check conflicts, caching, and anti-spam tools
If only one form is broken, look for a local conflict. Recent plugin updates, theme changes, caching changes, security rules, reCAPTCHA, honeypots, and page builders can break a form without changing its front-end design.
Test in a private window. If you have staging, disable non-essential plugins there and test again. Change one thing at a time, then repeat the same test phrase.
Run one final end-to-end test
Before calling the issue fixed, test the full live path. Submit the real form as a visitor, confirm the success message, check the entry or log if available, and confirm the notification arrives in the correct inbox.
Open the email and make sure it includes the lead's name, email, phone, message, and page source if you need it. Then click reply. The reply should go to the visitor, not your own sender address.
How to catch this next time before leads go missing
Once the form is fixed, the next problem is knowing when it breaks again. Plugin updates, SMTP password changes, DNS changes, spam rules, and email provider changes can break delivery later without changing how the form looks on the page.
That is the gap Website Form Checker is built to watch. It sends real test submissions through your form on a schedule and alerts you if they stop arriving, so you catch the issue before a real customer gets ignored.
Use it after the fix, not instead of the fix. First make WordPress, SMTP, notifications, entries, and the inbox work. Then monitor the live form so a silent failure does not sit unnoticed.
Quick checklist
- A real test was submitted from the live site.
- The exact test phrase was searched in inbox, spam, and quarantine.
- The WordPress Administration Email Address is correct.
- SMTP is connected and a test email works.
- The From Email uses an authenticated sender address.
- The form notification is enabled and the recipient is correct.
- Reply-To uses the visitor email field.
- Entries or submissions were checked if available.
- Forwarding rules, filters, and spam folders were checked.
- SPF, DKIM, and DMARC warnings were reviewed.
- Caching, anti-spam, reCAPTCHA, and plugin conflicts were tested if needed.
- A final live test reached the correct inbox with full lead details.
Test your form right now, free
Paste your contact form URL. We'll open it in a real browser, find the form, detect spam protection, and tell you whether it's structured to actually deliver submissions. Takes about 20 seconds.
Run a free audit →