WordPress

Why Is My WordPress Contact Form Not Working? Causes and Fixes

WordPress November 5, 2026 16 min read
Why Is My WordPress Contact Form Not Working? Causes and Fixes

A visitor fills in your contact form, clicks Send, and sees a thank-you message. Then nothing arrives in your inbox.

Or the form will not submit at all. The button spins, an error message appears, or the page reloads with an empty form. Either way, you may be losing leads without knowing it, because a broken form does not warn you.

The good news is that contact form problems follow a small number of patterns. Most are caused by email delivery, spam protection, a plugin or script conflict, or a caching setting. You can find the cause by testing one stage at a time.

Advertisement

In this guide, we’ll explain how a WordPress form works, how to tell which stage is failing, and how to fix each common cause. We’ll also show how to test your forms so that you find the next problem before your visitors do.

How a WordPress Contact Form Works

When a visitor sends a form, several things happen in order.

  1. The page loads the form, with its styles and scripts.
  2. The visitor fills in the fields, and the browser checks them.
  3. The browser sends the data to your site, usually through a background request.
  4. The form plugin checks the data, and applies spam rules.
  5. The plugin saves the entry, if it is set to store entries.
  6. The plugin creates an email, and WordPress sends it.
  7. The mail server delivers the message, or rejects it.
  8. The visitor sees a confirmation message.

A problem at any step looks like “the form does not work”. Your job is to find the step that fails.

Find the Failing Stage

What you seeStage that likely failsWhere to look first
The form does not show, or looks brokenPage loadStyles, scripts, caching
The button does nothing, or spins foreverBrowser or background requestBrowser console, plugin conflicts
An error message appears on submitPlugin checks, or server errorPlugin settings, error log
Success message appears, but no email arrivesEmail sending or deliverySMTP, spam folder, From address
Entry is saved, but no emailEmail stageNotification settings, SMTP
No entry and no emailRequest or plugin stageConsole, security rules, spam rules
Email arrives, but in spamDelivery reputationSPF, DKIM, DMARC, From address

If your plugin saves entries, this is a very useful test. An entry in the dashboard with no email proves that the form works and that email is the problem.

Before You Start

  • Take a full backup of your site.
  • Test in a private browser window, so that cached files and logged-in features do not hide the problem.
  • Submit the form with a real address that you can check, and look in the spam folder too.
  • Note the exact time of each test, so that you can find it in logs.
  • Write down the error message, or take a screenshot.

Cause 1: Email Is Not Being Sent or Delivered

This is the most common reason why a contact form seems broken. The form itself works, but the email never arrives.

Why it happens

  • By default, WordPress sends email using the server’s PHP mail function, which many hosts block or limit. The official wp_mail reference describes how WordPress sends email.
  • Receiving servers do not trust unauthenticated mail, so they drop it or put it in spam.
  • The From address does not match your domain.
  • Your domain has no SPF, DKIM, or DMARC records.

How to fix it

  1. Install an SMTP or email API plugin, and connect it to a mail service. Our review of WP Mail SMTP shows how to set it up.
  2. Set a From address on your own domain.
  3. Add the SPF, DKIM, and DMARC records that your mail service gives you.
  4. Send a test email from the plugin, and check the result.
  5. Test the form again.

Our full guide on how to fix WordPress emails that are not sending covers ports, records, and logs in detail.

Cause 2: The From Address Is Wrong

Many forms use the visitor’s email address as the From address. This looks logical, but it causes trouble. Your server is not allowed to send mail on behalf of the visitor’s domain, so the message fails authentication.

How to fix it

  • Set the From address to an address on your own domain.
  • Set the From name to your site name, or to the form name.
  • Put the visitor’s address in the Reply-To field, so that you can answer by pressing reply.
  • Check that no other plugin overrides the From address.

Cause 3: The Notification Is Turned Off or Sent to the Wrong Place

Sometimes the cause is a small setting.

  • Check that the notification for the form is turned on.
  • Check the recipient address for typing mistakes.
  • Check whether the form uses a shortcode that points to a different form, or an old copy.
  • Check that the address is not a mailbox that is full, closed, or forwarding to a broken address.
  • Check the admin email in Settings, then General, since some forms use it as the default.

Cause 4: Spam Protection Blocks Real Messages

Honeypot fields, captchas, and anti-spam rules can block real visitors if they are set up wrongly.

  • If the form has a captcha, check that the site key and secret key are correct, and that the captcha shows on the page.
  • If your caching plugin delays or removes scripts, the captcha may not load.
  • Some anti-spam rules block messages that contain certain words or links.
  • Some security tools block form requests from certain countries or networks.

How to test

  1. Turn off the captcha for a short test, and submit the form.
  2. If it works, turn the captcha back on, and fix the keys or the script loading.
  3. Check the plugin’s spam log, if there is one, for blocked messages.
  4. Test from a phone on a different network.

Cause 5: A Plugin or Theme Conflict

A script from another plugin can stop the form from submitting. Typical signs are a button that does nothing, or a form that works for a moment and then fails.

How to find it

  1. Open the form page, then open your browser’s developer tools and click the Console tab.
  2. Reload, and look for red errors. A file path with /wp-content/plugins/ names the plugin.
  3. Use a troubleshooting mode or turn off other plugins one at a time, and test the form after each.
  4. Switch to a default theme for a test.

Our guide on how to find which plugin is breaking your site shows each method, including the safest way to test on a live site.

Cause 6: Caching and Script Optimization

Caching and optimization tools can break forms.

  • A cached page may hold an old security token, so the form fails when it is sent.
  • Minify, combine, and delay options can break the form’s script.
  • A CDN may cache the form’s request.

How to fix it

  1. Clear all caches: plugin, host, CDN, and browser.
  2. Turn off minify, combine, and delay for scripts, and test the form.
  3. Exclude the form page from caching, if the problem remains.
  4. Turn the options back on one at a time, and test after each.

Cause 7: Blocked Requests

Most modern forms send data in the background through the REST API or a file named admin-ajax.php. If a firewall or security rule blocks these requests, the form fails with an error.

How to check

  1. Open the form page, and open the Network tab in your browser’s developer tools.
  2. Submit the form.
  3. Look for a red request. A code of 403 means blocked, 404 means not found, and 500 means a server error.
  4. Click the request, and read the response.

Common fixes

  • Add an exception in your firewall or security plugin for the blocked request.
  • Save your permalinks in Settings, then Permalinks, to refresh rewrite rules.
  • Ask your host if a server rule blocks the request.
  • Check for a redirect loop, which can come from a mix of HTTP and HTTPS.

Cause 8: Server Errors and Limits

A server error can stop the form from processing.

  • A low PHP memory limit can stop the plugin from sending.
  • A short execution time can stop a slow request, such as an upload.
  • A damaged .htaccess file can break routes.
  • A PHP error from an update can stop the plugin.

Turn on the debug log, as described in the official WordPress debugging guide, submit the form, and read the newest lines in the log. They often name the file and line that failed.

Cause 9: Form Settings That Cause Silent Failure

Check these settings in your form plugin.

SettingWhat can go wrong
Required fieldsA field that cannot be completed on some devices
Field validationA rule that rejects valid input, such as a phone number format
Confirmation typeA redirect to a page that does not exist
Entry limitsA form that closes after a set number of entries
ScheduleA form that is turned off outside certain dates
Login requirementA form that works only for logged-in users
File uploadAn upload field that fails because of a size limit

Open the form as a visitor, and fill in every field with normal data. A field that rejects valid input is a quiet cause of lost leads.

Cause 10: Old Plugin Versions and PHP Problems

An old form plugin on a new PHP version can fail. A new plugin version on an old WordPress can also fail.

  • Update the form plugin, WordPress, and your theme, after a backup.
  • Check that your PHP version is supported by the plugin.
  • Read the plugin’s change log for known issues.
  • If the problem began after an update, roll back the plugin and test.

How to Test Your Contact Form Properly

A proper test covers each stage.

  1. Open the form in a private window.
  2. Submit it with valid data, using an address that you can check.
  3. Check that the confirmation message appears.
  4. Check that the entry is saved, if your plugin stores entries.
  5. Check the inbox, then the spam folder.
  6. Check that the email shows the right From name, Reply-To, and content.
  7. Submit again with an invalid field, and check the error message.
  8. Test on a phone, on mobile data.
  9. Test with a different email provider as the recipient.
  10. Repeat after any plugin or hosting change.

A Step-by-Step Troubleshooting Order

If you are not sure where to begin, follow this order. It checks the most likely causes first, with the least risk.

  1. Back up your site.
  2. Submit the form in a private window, and note what happens.
  3. Check the spam folder, and the notification address.
  4. Check that the entry was saved, if your plugin stores entries.
  5. Send a test email from your SMTP plugin, or install one if you have none.
  6. Set the From address to your own domain, and the Reply-To to the visitor.
  7. Check the browser console and the Network tab for errors and blocked requests.
  8. Clear all caches, and turn off script optimization for a test.
  9. Turn off the captcha for a test.
  10. Test with other plugins off, and with a default theme.
  11. Check the debug log for PHP errors.
  12. Ask your host to check the server log if the problem remains.

Change one thing at a time, and test after each change. If you change five things at once, you will not know which one worked.

Using the Browser Console and Network Tab

You do not need to be a developer to read these tools. They show what happens when the form is sent.

The Console tab

Open it, reload the page, and submit the form. Red lines are errors. Read the first one, since the others may follow from it. A message with a file name tells you which plugin or theme file failed.

The Network tab

Open it before you submit the form, then submit and look at the new rows. The row for the form request shows a status code.

CodeMeaningWhat to do
200The request workedLook at the response, and check email settings
301 or 302The request was redirectedCheck HTTP and HTTPS settings, and redirects
400Bad requestCheck the form data, and the plugin version
403BlockedCheck firewall and security rules
404Not foundSave permalinks, and check the form’s address
500Server errorCheck the error log, and memory limits
503Server busy or in maintenanceCheck the host, and a stuck maintenance file

Click the row, and read the response. Many plugins send a message that explains the failure.

What to Do If the Form Worked Before and Stopped

A form that stops working is usually the result of a change. Think about what changed just before it stopped.

Advertisement
  • A plugin, theme, or WordPress update.
  • A change of host, PHP version, or server settings.
  • A new security, caching, or optimization plugin.
  • A change to your domain, DNS, or email provider.
  • An expired captcha key, license, or API key.
  • A mailbox that changed or was closed.
  • A new firewall rule.

Work backward. Undo the latest change in a test, and see whether the form works. If an update caused the problem, roll back that plugin and test again. Our guide on what to do when your WordPress website breaks after an update covers rollbacks in more detail.

Using an Email Log to See the Truth

An email log answers the question “did WordPress even try to send it?”.

  • If the log shows no entry for your test, the form never created the email. Look at the form’s notification settings and the plugin.
  • If the log shows a failed entry, read the error message. It usually names the cause, such as a wrong password, a blocked port, or an unverified sender.
  • If the log shows a sent entry, the message left your site. Check the spam folder, then your mail service’s dashboard for bounces.

Many SMTP plugins include a log, and some form plugins keep their own. Turn one on, and keep it on. Delete old entries after a few weeks, because logs hold personal data.

Forms That Use Third-Party Services

Some forms send data to other tools, such as a CRM, a spreadsheet, or an email list. These connections can fail on their own, even when the email works.

  • Check that the connection is still authorized. Tokens can expire or be revoked.
  • Check that the service has not changed its fields or its limits.
  • Check the plugin’s integration log, if there is one.
  • Check that the service’s plan still allows new entries.
  • Test the connection with a simple form.

If entries reach your dashboard but not the other tool, the form is fine, and the connection is the problem.

Forms Inside Page Builders and Popups

Forms placed in a page builder or a popup have extra points of failure.

  • A popup may load the form late, so the script runs before the form exists.
  • A page builder may rewrite the form’s markup or load its own scripts, which can clash.
  • A form in a hidden tab or accordion may not load on some devices.
  • Some builders have their own form widgets, with their own settings for email.

Test the form on a normal page first. If it works there but not in the popup or builder, the problem is in the way that the builder loads it. Check the builder’s documentation, and test with optimization options turned off.

Hosting and Server Reasons

Sometimes the cause lies outside WordPress.

Server issueWhat it doesWhat to do
Outgoing mail is blockedPHP mail never leaves the serverUse SMTP or an email API
SMTP ports are blockedSMTP connection failsUse another port, or an HTTPS API
Email limits per hourExtra messages are dropped or delayedReduce volume, or use an external service
Low memory or time limitsForm requests failAsk your host to raise limits
Server firewall rulesRequests are blockedAsk your host to review the rules
An outage at the mail serviceMessages are delayedCheck the service’s status page

If you have tried the fixes in this guide and the problem remains, contact your host with the time of your test, the page address, and the error you see. They can read logs that you cannot.

Security Points for Contact Forms

A form is a doorway into your site, so keep it safe.

  • Keep your form plugin updated, because old versions can have known weaknesses.
  • Do not allow file uploads unless you need them, and restrict file types and sizes.
  • Use spam protection, and limit how fast one visitor can submit.
  • Do not store sensitive data in entries unless you need to.
  • Limit who can view entries in the dashboard.
  • Use HTTPS on the page with the form.
  • Do not show error messages that reveal server details to visitors.

Prevent Contact Form Problems in the Future

  • Use SMTP or an email API from the start.
  • Choose a form plugin that stores entries, so that email failures do not lose leads.
  • Set up SPF, DKIM, and DMARC for your domain.
  • Test every form each month.
  • Test after each plugin, theme, or hosting change.
  • Keep a short note of form settings, so that you can restore them.
  • Set up an alert for failed emails, if your SMTP plugin offers one.
  • Back up your site before every update.
  • Ask a few people to send a test message from different providers once or twice a year.

A Quick Troubleshooting Summary

SymptomFirst thing to try
No email, but success messageSet up SMTP, check spam
Email in spamAdd SPF, DKIM, DMARC, and fix From address
Button does nothingCheck the console, and test plugins
Error message on submitCheck the Network tab, and security rules
Form looks brokenClear caches, and turn off optimization
Captcha missingCheck keys, and script loading
Form works for you, not othersTest in a private window and on other networks
Problem began after updateRoll back the plugin, and test

When to Ask for Help

Ask for help when you have worked through the checks above and the form still fails, or when the form handles leads or payments that you cannot afford to lose. Prepare these items first, so that the helper can start at once.

  • The address of the page with the form.
  • The name and version of the form plugin, and of your SMTP or email plugin.
  • Your WordPress and PHP versions.
  • The exact error message, copied or in a screenshot.
  • The time of your last test, and the address that you used.
  • A list of changes made in the days before the problem began.
  • Any errors from the browser console or the debug log.

With these details, a simple cause can often be found in minutes, whether you ask your host, the plugin’s support team, or a WordPress professional.

Frequently Asked Questions (FAQs)

Why does my form say it was sent, but I get no email?

The form worked, but the email failed at the sending or delivery stage. Set up SMTP, check your spam folder, and use a From address on your own domain.

Why does my form button do nothing?

Usually a script error or a conflict with another plugin. Check the browser console, and test with other plugins turned off.

Why do my form emails go to spam?

The messages are not authenticated. Add SPF, DKIM, and DMARC records, send through a mail service, and use your own domain in the From address.

Can caching break my contact form?

Yes. Cached pages can hold old tokens, and script optimization can break the form’s code. Clear caches, and exclude the form page if needed.

How do I know if my form is blocked by a firewall?

Open the Network tab, submit the form, and look for a request with a 403 code. Add an exception in your firewall, or ask your host.

Should I use the visitor’s email as the From address?

No. Use your own domain as the From address, and set the visitor’s address as Reply-To.

How often should I test my forms?

Test each form once a month, and after any update or change in hosting or email settings.

Does my form plugin save entries?

Some plugins save entries in the dashboard, and some only send email in the free version. Check your plugin’s settings. Saved entries give you a backup if email fails.

Can someone fix my contact form for me?

Yes. If you prefer an experienced person to find the cause and fix it, you can get WordPress management help through this Fiverr gig.

Final Thoughts

A contact form that does not work usually fails at one clear stage: the email, the spam check, a script conflict, a cache, or a blocked request. Test one stage at a time, and the cause shows itself.

Fix email delivery first, because it is the most common cause. Then check spam settings, plugin conflicts, and caching. After the fix, make a habit of testing your forms each month, so that a failure never costs you a lead without your knowing.

Advertisement
Mindful reading

Better ideas, delivered thoughtfully.

Receive useful articles, thoughtful perspectives and practical knowledge from Mindful Tomorrow without unnecessary noise.

Scroll to Top