Is your contact form actually working? A 10-minute check
When a form breaks, nobody usually notices: the visitor writes a message, presses send and never hears back. Running this check monthly is a simple way to spot message delivery problems early.
Why forms break
Forms usually depend on a part that is separate from the rest of the site: a sending script on the server, a mailbox, or a third-party form service. A server move, a PHP update, a changed mailbox password or new email domain settings (SPF, DKIM) can quietly break it.
Because the page still loads, the problem stays invisible. The visitor either sees an error page or gets a “sent” message while nothing ever reaches you.
The 10-minute check
- Fill in the form with an email address outside your company and send it.
- Look at what appears after sending: a clear thank-you message, a blank page, or words such as “error” or “500”?
- Check whether the message reached the mailbox the form is connected to, including the spam folder.
- Repeat the test on a phone. Pop-ups, consent boxes or keyboard layouts can make a form unusable on mobile.
- Try sending with required fields empty. Is the error message clear, and is the visitor’s text kept?
- Does the form page open over HTTPS? A browser warning in the address bar can make visitors give up.
How to read the results
- Thank-you message shown and the message arrived: the form works. Repeat monthly anyway.
- Thank-you message shown but nothing arrived: delivery is unconfirmed; check for delays, spam filtering, sending errors and email configuration.
- Error page, blank page or “not found”: submission or response display may have failed; check whether the enquiry was recorded.
This is not a security or performance audit; it only shows whether an enquiry reaches you.
A lasting fix
Store enquiries before sending email notifications. Configure retries for temporary delivery failures and alerts for unresolved errors; successfully stored enquiries remain available if email delivery fails.
A workflow planned with Minimolo can receive, validate, store and notify, with retries for temporary failures, duplicate prevention and alerts for unresolved errors.