Table of contents
A WordPress contact form fails in three places: emails don't arrive (because WordPress sends them with a PHP function without authentication, so they land in spam or get rejected), spam floods the inbox (because the only protection is a CAPTCHA that bots get around) and data is processed without a legal basis (because someone added a consent checkbox that isn't needed here and skipped the privacy notice that is). A correct setup: sending via SMTP with SPF/DKIM/DMARC, layered spam protection, a copy of submissions in the database and a privacy notice below the button.
Thesis: one in ten business websites we audit has a form that doesn't deliver emails
Symptom: "fewer inquiries lately." Diagnosis: we send a test submission — it doesn't arrive. Since when? Since the hosting migration six months ago. How many inquiries were lost? Nobody knows, because the plugin doesn't store submissions. This isn't a rare case — it's the norm on sites nobody tests. That's exactly why a form test is part of our procedure after every update.
9 mistakes and fixes
1. Sending via wp_mail() without SMTP
By default, WordPress sends emails using the server's PHP function — without authentication, from an address the server has no right to use. Gmail, Outlook and Polish mailboxes increasingly reject such messages without a trace.
Fix: an SMTP plugin + a mailbox on your domain (or a transactional email service). The email goes out from an authenticated server, from a real address kontakt@twojadomena.pl.
2. No SPF, DKIM or DMARC in the domain's DNS
Even over SMTP, an email without these records looks suspicious. Since 2024, major email providers have required them for accepting bulk messages; for individual emails, they strongly affect the spam filter.
Fix: three DNS records:
| Record | What it does | Where to get it |
|---|---|---|
| SPF | A list of servers authorized to send from your domain | Your email/SMTP provider supplies a ready-made entry |
| DKIM | Cryptographic message signature | Key generated by your email provider |
| DMARC | Policy: what to do with emails that fail SPF/DKIM | You start with p=none with reporting, then quarantine |
Test: send an email from the form to a test mailbox and check the headers — spf=pass, dkim=pass, dmarc=pass.
3. Sender address = customer's address
The form sets "From: address@client.com" so that you can reply. The result: you send email from a domain you don't control — SPF fails and the email lands in spam.
Fix: "From: formularz@twojadomena.pl", with the customer's address in the Reply-To field.
4. CAPTCHA as the only protection
Bots solve classic CAPTCHA, while people abandon it — especially on mobile. reCAPTCHA v3 alone lets through manual spam and some bots.
Fix — layers: – Honeypot — a hidden field that only bots fill in (zero impact on users), – Completion time — a submission in 2 seconds is a bot, – Turnstile or reCAPTCHA v3 — invisible, as a third layer, – Content filter — blocking links in the message field, word lists, – Submission limit per IP.
A visible image CAPTCHA — only as a last resort, once you've determined that the layers aren't enough.
5. No copy of submissions in the database
Email didn't arrive = submission lost. Without a trace.
Fix: a plugin that saves every submission in the WordPress dashboard (most have this option or an add-on). Once a week: compare the number of submissions in the dashboard with the number of emails.
6. A "consent to data processing" checkbox — unnecessary; a missing clause — a mistake
A common misconception: a contact form doesn't require consent to processing, because the legal basis is taking steps at the person's request (answering their question) — Art. 6(1)(b) GDPR — or legitimate interest. What is required, however, is the information obligation: who processes the data, why, for how long and what rights apply.
Fix: remove the consent checkbox (unless you're asking about a newsletter — that's a separate, voluntary consent) and add a short notice below the button with a link to your privacy policy. Details in our GDPR guide for websites.
7. Too many fields
First name, last name, company, tax ID, phone, email, subject, budget, deadline, message, attachment. Every field means fewer submitted forms.
Fix: 3–4 fields: name, email or phone (one required), message. You'll sort out the rest in your reply. More context in the article on copywriting for a business website — a form is text too.
8. A "thank you" message with no information on what happens next
The client has submitted the form and doesn't know whether anyone will reply, when, or about what.
Fix: "Thank you — we reply within 24 business hours. Urgent? Call: …". Plus an autoresponder with the same information and a copy of the submission (the customer sees it got through).
9. No testing after every change
A plugin update, a hosting change, a DNS change, a new security plugin — any of these can break email delivery.
Fix: a test submission after every change and once a month regardless of changes. 30 seconds.
Implementation procedure — order of steps
- Email account on your domain (or a transactional service) → SMTP plugin → delivery test.
- SPF, DKIM, DMARC in DNS → header test.
- Sender from your own domain, customer's Reply-To.
- Honeypot + form completion time + Turnstile/reCAPTCHA v3.
- Submissions saved in the database + notification to a second address (e.g., phone).
- Privacy notice, removal of the unnecessary checkbox.
- Post-submission message + autoresponder.
- Calendar entry: form test on the 1st day of the month.
Forms and AI
Form submissions make a good automation trigger: classification, a draft reply, a CRM entry — we described this in the article on automation with n8n and Make. The condition: the form has to deliver first.
From our experience
When we take over websites, we test the form first — before the SEO audit. Too often it turns out that "the website brings no customers" means "the website delivers no inquiries."
We set up SMTP, DNS records and spam protection as part of website maintenance — with a monthly deliverability test.
FAQ — contact form
Most often because WordPress sends them using a PHP function without authentication, and mail servers reject such messages or route them to spam. The solution is to send through SMTP from an account on your own domain, with SPF, DKIM and DMARC records in DNS.
No — the legal basis for processing is responding to the person's request, not consent. What's required is an information clause (who, why, how long, rights) with a link to the privacy policy. A consent checkbox is only needed for additional purposes, such as a newsletter.
In layers: a honeypot (hidden field), form completion time measurement, invisible verification (Turnstile, reCAPTCHA v3), a link filter in the message body, and a limit on submissions from a single address. A visible image CAPTCHA reduces the number of submissions from real people and is a last resort.
Author: Adrian Kamiński — Websky Studio, Poznań. WordPress website maintenance — we test the form after every change and once a month, because a lack of inquiries looks like a lack of customers.
Your feedback
Was this article helpful?
One click — it helps me choose future topics.

