Why Is My WordPress Contact Form Not Sending Emails?
Trace a WordPress form email problem from submission to inbox, using harmless test data and provider evidence rather than assuming a success message proves delivery.
Part of our guide: What WordPress Maintenance Does a Small Business Website Need?
A WordPress contact form can appear to submit successfully without its notification reaching your inbox. Separate the stages: the browser submits, the website processes the request, a mail service accepts the message and the recipient system decides how to handle it.
WordPress’s wp_mail documentation explicitly notes that a successful return value does not prove the recipient received the email. A confirmation message is therefore only one part of an end-to-end test.
Make a harmless test first
Use an address you control and a recognisable test reference. Do not include passwords, financial details or genuine customer information.
Record the form URL, time, device, confirmation shown and expected recipient. Check whether the form system stores a submission record, if that feature is enabled and appropriate.
If no submission is recorded, investigate the form request and validation before changing mailbox settings. If the submission exists, move on to notification and delivery evidence.
Check the notification configuration
Confirm that notifications are enabled, the recipient address is correct and any conditional rules match the test.
Ask the maintainer whether the sender address is authorised for the configured mail service. A visitor’s email address may belong in a reply-to field rather than being impersonated as the sender; follow the provider’s exact setup instructions.
Do not paste arbitrary SMTP settings from a different host into the website. Credentials and supported sending methods are provider-specific.
Trace the message beyond WordPress
Check spam and quarantine folders, mailbox rules and the mail provider’s available delivery logs. Look for rejection, deferral or suppression evidence at the recorded time.
A service accepting a message is different from inbox placement. Ask support to explain which stage their “sent” status confirms.
If a recent DNS or hosting change coincides with the failure, use the domain and email protection checklist. The email during a website rebuild guide explains why website delivery and ordinary mailbox operation need separate tests.
Use an end-to-end test record
| Stage | Evidence to record |
|---|---|
| Browser | Test reference and visible result |
| Form system | Submission present or absent |
| Notification | Correct recipient and applicable rule |
| Sending service | Message identifier or failure reason |
| Recipient system | Received, quarantined or rejected |
| Follow-up | Person who confirmed the final result |
Keep sensitive logs restricted and redact customer information before sharing with suppliers. Our form-data handling guide covers the wider responsibilities.
Change the smallest relevant part
If the cause is a mistyped recipient, correct it and repeat the same test. If the mail service rejects the sender, resolve that configuration with the provider.
Do not install several mail plugins simultaneously. Overlapping sending routes can make the result harder to explain.
If the problem started after an extension change, the plugin-conflict guide provides a controlled investigation. Preserve existing evidence before replacing the form.
Verify the customer-facing response
The form should communicate success or failure accurately enough for a visitor to know what to do next. A silent loss behind a cheerful confirmation is a business problem even if the layout looks perfect.
Provide a clear alternative contact route where appropriate. Avoid asking customers to resubmit sensitive information repeatedly while the team experiments.
Use the contact-form questions guide to check whether every field is necessary. Delivery reliability does not justify collecting more information than the enquiry requires.
Add a maintenance check
After resolving the fault, record the cause, correction and test result. Test again after relevant changes to hosting, mail delivery, forms or security configuration.
The WordPress maintenance checklist helps give this responsibility an owner. A simple received test enquiry can reveal a failure that an uptime monitor never sees.
Confirm that a test enquiry reaches the intended person, and that the mail setup is supported and can be maintained.
Thinking about your own rebuild?
Tell us about your business, your current website and what you would like to improve. We will help you work out the next step.
