By platform
Squarespace contact form not working: trace it
A visitor fills in the form and presses send, then sees nothing happen, or a thank you for a message that never reaches you. Mimiq sends simulated visitors through the same form and shows what each one saw after pressing send.
Why is my Squarespace contact form not working?
Three things stop a contact form on a Squarespace site: the page blocks the send, the message goes to an address you no longer read, or it lands in a spam folder. Each one leaves a different trace, so start with what the visitor saw right after pressing send. A simulated test records that part, since it fills in the form and reports what appeared on the screen.
What this looks like in a report
“I typed my date and budget into the message box and pressed Send. The button flashed, then nothing else happened, so I could not tell if it went. I gave up and emailed the studio myself.”
The fix. Open the form's settings and confirm the notification address is one you read today, then send a test from a phone and check that address's spam folder. If the Send button does nothing on a phone, look for a cookie banner or other overlay that covers the button.
An illustration. Run a test to see your own.See a real sample report
A thank you can show before the message reaches your inbox
A contact form works in two steps that look like one. The page checks the fields and passes the message on, then shows a confirmation. The email to you is a second step, and it depends on the address set for notifications, whether that address accepts mail from the site, and whether the mail provider filters it. A visitor who saw the confirmation has finished their part. If you never get the email, the message was accepted and died after that point. A missing confirmation is a different fault, and it sits on the page itself.
- Fill every field, press send, and write down exactly what appears on the screen.
- Open the form's settings. Is the address that receives notifications one you read?
- Check the spam folder of that address for the last test message you sent.
- Send a test from an address on a different mail provider. Does it arrive?
- Look for a required field the visitor cannot see or change, such as a hidden checkbox.
What the visitor sees, and what it means
The visitor's screen is the one part you can reproduce exactly, so start there. Press send with every field filled in, then press it again with one field left empty. A message that stays on the page with a red line under a field means the form caught the mistake and sent nothing. A message that disappears and shows a thank you means the form accepted it. Nothing at all on the screen means the button is not reaching the form, which usually points at something covering the button, a required field hidden from the visitor, or a script that did not load on that page.
Three places a message can die after it is sent
The first is the notification address. The form sends to the address set in its settings, and if that address was typed wrong, belongs to someone who has left, or points at an inbox nobody checks, the message is delivered and never read. The second is the spam folder. Mail sent from a form on your domain can be filtered as bulk or suspicious, and the copy in the spam folder is the only trace of it. The third is the reply the visitor never gets, which matters if the thank you text promised one.
Test each place on its own. Send one message to an address on a different mail provider, and one to the address you read most. If the first arrives and the second does not, the notification address is wrong or being filtered. If neither arrives, the message never left the form, so go back to what the visitor saw on the screen.
Telling a sending fault from a delivery fault
A sending fault happens on the page. The visitor presses send, the form does not accept the message, and the visitor sees an error or nothing. A delivery fault happens after acceptance. The visitor sees the thank you, and the message is missing from your inbox. Keep the two apart before you change anything, because the fixes sit in different places: the page's own blocks for the first, and the form's notification settings for the second.
Mimiq is independent and not affiliated with the platforms it names. Names belong to their owners.
What you get with Mimiq
- 01
Run it by hand, or on every pull request
Paste a link and a task in the app and watch the visitors work. Or run them on every preview deploy: the GitHub Action comments on the pull request, any other CI can call the MCP endpoint, and your coding agent can run it too.
- 02
Bugs and usability problems in one report
The browser records errors and failed or slow requests on the step they happened. The visitors say where the wording or the steps confused them, and where they left.
- 03
Visitors that behave like your audience
Each visitor is a different profile with a reason to be there, matched to who the page is for, described by you, or built from your own customers.
- 04
A prompt to fix each problem
Every problem comes with a fix to paste into Cursor, Claude Code, Lovable or any coding agent, and one prompt hands over the top problems at once. Then send the same visitors through again.
- 05
Follow every visitor
See each visitor's whole path, step by step with screenshots, and what it was thinking at every step. Ask any visitor a question.
The browser records relevant JavaScript errors and failed or slow app requests encountered during the run, attached to the step where they occurred. The visitors are simulated: they find problems, they do not predict how many real people will convert.
A new notification address or spam rule can stop the form again
Changing the notification address, the sending domain or a page layout can break the form without touching the form itself. Rerun the same simulated visitors through the same page after each change, and check the spam folder of the address that receives the message. Each simulated visitor also gets a working inbox, so a reply the form sends to the visitor can be checked too.
Starter
Try it on one launch
About 4 tests of 5 visitors
- Visitors on your landing page, signup and checkout
- Where they left and why, with a fix to copy for each problem
- Run it in the app or on every pull request
- Ask any visitor a question, included
- Test accounts and protected previews
Builder
Test every build
About 20 tests of 5 visitors
- Everything in Starter
- Credits refill each month, and what is left rolls over once
- Cancel anytime
Pro
Test every release, as a team
About 60 tests of 5 visitors
- Everything in Starter
- Credits refill each month, and what is left rolls over once
- Cancel anytime
Scale
Test at scale, every day
About 240 tests of 5 visitors
- Everything in Starter
- Credits refill each month, and what is left rolls over once
- Priority support
- Cancel anytime
Questions
Why does my Squarespace form say thank you but no email arrives?
The form accepted the message, so the fault sits after that point: the notification address, the spam folder, or a mail provider filtering it. Send a test to a second address on a different provider. If only the first address misses it, check its spam folder first, then the spelling of the address in the form's settings.
Why does the Send button do nothing on my form?
Either the form rejects a field without showing the reason, something on the page covers the button, or a script on the page has stopped. Fill every field, press send, and watch what appears. A cookie banner or chat widget sitting over the button can look exactly like a dead button.
Does a simulated visitor check my inbox?
No. A simulated visitor fills in the form, presses send and reports what it saw on the screen. It can receive a reply the form sends to its own address, but it cannot read your inbox or your spam folder, so check those yourself.
Will a simulated test show how many people will send a message?
No. The test shows whether a simulated visitor could get the form to send, and what the screen showed them afterward. It does not predict how many real visitors would write in, so use your analytics or a live experiment for that number.
Keep reading
Send visitors and see what breaks first.
Your first test is free: sign in with Google and it starts right away. Last checked 2026-11-02.