How to test the request form on your website

By Dylan SaatdjianFounder, Fieldline Web Co.Published September 17, 2026

Why a form can stop working and nobody notices

A request form is the quiet half of your website. When the phone breaks, you hear about it fast. When a form breaks, it keeps looking normal. A customer fills it out, presses Send, maybe even sees a thank you message, and the request goes nowhere you will ever read.

This happens for ordinary reasons. The form was set up to email someone who no longer works with you. A spam filter started sorting the notices into a folder nobody opens. A plugin update changed how the site sends mail. None of these show up as an error on the page, which is why the only real check is to send a request yourself and follow it all the way to the person who answers it.

The ten minute test

Do this on your phone, on mobile data, because that is how most people will fill it out.

1. Open your website and find the form the way a new customer would, starting from the home page.
2. Fill it out with your own details, and put the word TEST in the name field so nobody mistakes it for a real request.
3. In the message box, write the date, the time and the page you used, for example: TEST from the home page, Tuesday 7:15 PM.
4. Press Send and note exactly what the screen shows next.
5. Wait ten minutes, then go looking for the request in the three places listed below.

If you have more than one form, such as a contact form, a quote request and a booking form, test each one. They are often wired up separately, and one working tells you nothing about the others.

Three receipts that prove it worked

A form only works when all three of these are true:

• The screen confirms it. After you press Send, a clear message or a thank you page appears. If the page just reloads with the boxes empty, or nothing happens at all, the customer has no idea whether it went through.
• The notice reaches an inbox you actually read. Not an old address, not a shared box nobody checks, and not a folder you never open. Check the time on the notice against the time you wrote in the message.
• A copy is saved somewhere besides email. Most website builders keep a record of every submission in the site dashboard. That saved copy is your backup when an email goes missing.

Where the saved copy lives

• Squarespace: Squarespace’s help center says every form needs at least one storage option, and that the default is the account email of whoever added the form. So if a past employee or an old web designer built your form, check that it still points at you. It also says you can pick more than one storage option as a backup, such as email plus Google Drive, and that the mailing list and Contacts panel options are the ones that keep submissions inside Squarespace.
• Wix: Wix’s help center says submissions are stored automatically and can all be seen under Forms & Submissions in your site dashboard. By default the notice goes to the site owner, and you can change who gets it in the form’s automation.
• WordPress: it depends on the form plugin. Open the plugin’s settings and look for an entries or submissions screen, and for the address in its notification settings. Some plugins only send an email and keep no copy at all, which is worth knowing before the day an email goes missing.

If the test never shows up

Work through these in order. The first two explain most missing requests.

1. Look in spam or junk. In Gmail, Google’s help page says to search with the Mail & Spam & Trash option so those folders are included, and that messages in Spam and Trash are deleted after 30 days. In Outlook, Microsoft says junk email is kept for 30 days and then deleted for good. If you find your test there, mark it as not spam and add the sender to your contacts or safe senders list. Microsoft says messages from safe senders will not be moved to Junk.
2. Check who sent it. Builder notices often come from the builder, not from your customer. Squarespace lists form-submission@squarespace.info as the sender, and Wix lists notifications@wix-forms.com. Search your whole mailbox for those addresses, not just for the customer’s name.
3. Read the notification address letter by letter. The WPForms documentation names misspelled addresses and missing commas as a cause of notices that never arrive. One wrong letter sends every request to a stranger or to nobody.
4. Check rules and forwarding. A mail rule that moves or deletes messages, or forwarding that does not keep a copy, can hide a notice that did arrive. Google’s help page on missing messages walks through both for Gmail.
5. On WordPress, look at how the site sends mail. WPForms recommends sending through a proper mail service (SMTP) and warns that a From address on a different domain, such as a gmail.com address on your business site, can get the notice flagged or blocked. This one usually needs whoever manages your site.

Test the parts around the form too

While you have the form open, try it the way a rushed customer would. Leave a required box empty and press Send: you should see a plain message saying what is missing, and whatever you already typed should still be there. Tap into the phone field and check that the number keypad opens. If the form asks for a file or a photo, attach one from your phone. And if the form sends the customer an automatic reply, make sure it arrived and that it says who you are and when you will get back to them.

For insurance agencies and mortgage offices

Quote request and prequalification forms often ask for more personal details than a plumber needs. Never type a real Social Security number, date of birth or account number into a test. Use obviously fake details that the form will still accept, and keep TEST in the name.

Tell whoever works your leads before you test, so the request is not called, logged as a prospect or added to a mailing list. And if your form feeds a CRM or a quoting tool instead of an inbox, follow the test into that system and confirm it landed with every field filled in, not just the name.

Make it a monthly habit

Forms break quietly after ordinary changes: a new staff email, a password reset, a plugin update, a new page with a copy of the form. Put a reminder on the first of each month and send one labeled test through every form. Do the same after any change to the site or your email. It takes ten minutes and it protects the moment a customer has already decided to ask you for help.

If you have not checked your phone number yet, the two minute tap to call test is the other half of this check. And our guide on why a site gets visits but no calls covers the usual causes beyond the form, for any kind of local business.

Where Fieldline fits

Fieldline’s optional Web Care includes a labeled test request through your form every month, confirmed in your inbox with the time it arrived, so a broken form gets found within the month instead of never. It is $99 a month after a Fieldline build and $149 a month on a site you already have. Mortgage and insurance offices can see our search work for those businesses.

Being straight about the limits: a working form removes a reason a request gets lost, and it cannot promise that anyone fills it out. If you would rather have someone check your current site and write down what they find, the free written website audit does that with no payment and no sales call.