By platform
Squarespace form not sending email: which form
The visitor fills in the form, sees a thank-you message, and nothing arrives in the inbox you read. Mimiq sends simulated visitors to the page and shows which form they used and what appeared after Submit.
Why is my Squarespace form not sending email?
A Squarespace form sends mail only if the form block the visitor used is set to send an email and points at an inbox you read. A page can hold several form blocks, and each one keeps its own settings, so the form a visitor used may not be the one you tested. A simulated visitor test shows which form a visitor filled in and what appeared after Submit, but it cannot tell you whether an email reached your inbox.
What this looks like in a report
“The main page had no form, so I used the box in the footer. A thank-you appeared, so I assumed the teacher had my question about the Saturday class.”
The fix. Open the footer form's settings in the editor, switch on the email setting and point it at the class inbox, then submit a test message from a private window and confirm it arrives in that inbox.
An illustration. Run a test to see your own.See a real sample report
The form a visitor fills in may not be the one that sends mail
A Squarespace page can include several form blocks: one in the body, one in the footer, and one in a section the visitor has to open. Each block keeps its own settings, so a block added later can be set up differently from the one you tested. A visitor fills in whichever form they reach first, which is often the one nearest the top or the footer, and sees a confirmation either way. The owner tests from the contact page, sees mail arrive, and concludes the form works. Both are telling the truth, about two different forms.
- Open the page in the editor and list every form block, including the footer and any pop-up. How many are there?
- For each one, open its settings and check whether it is set to send an email, and to which address.
- In a private window, submit the form nearest the top of the page. Does an email arrive?
- Submit the footer form once with a test message, then the one in any collapsed section.
- Use a subject line that names the form, such as footer or contact, so the inbox shows which one sent it.
A page can hold more than one form, and only one may send mail
Squarespace pages are assembled from blocks, and a form is one block among many. Owners often add a form to the contact page, then a second one to the footer that shows on every page, and sometimes a third inside a section the visitor has to open. Each form block carries its own settings, so the one you tested may be set up differently from the one a visitor used. That difference explains a form that works for the owner and sends nothing for visitors.
The check starts in the editor. List every form block on the page, including the footer and anything in a pop-up or a collapsed section. Open each form's settings and read whether it is set to send an email, and where that email goes. A thank-you message on screen does not say which forms send mail, so the confirmation alone cannot answer that.
Find the form the visitor actually used
A visitor uses the form they can see first, and the owner rarely sees the same screen. On a laptop, the form in the body may sit above the fold. On a phone, the footer form may be the only one within reach after a scroll. The screenshot of the visitor's step shows which form was filled in, so read it before anything else. If it shows the footer, the footer block is the one to check, whatever the contact page says.
The wrong approach is to test one form from the contact page and call the whole site fixed. The right approach is to submit each form once, from a private window, with a message you can find in your inbox. A subject line that names the form tells you which block sent each message, so the inbox answers the question the screenshot raised.
What a visitor test confirms, and what you still check yourself
Give Mimiq the page address and one task a visitor would have: send a question about the Saturday class through the form. Each simulated visitor picks the form it reaches first, so the run shows which form a visitor actually reaches. Each run shows which form was used, the fields filled in, the message after Submit, and any request that never returned, with a screenshot of the form at the press.
The test does not open your inbox, so it cannot confirm that a notification was sent or delivered. Each simulated visitor has a working email inbox, but that inbox belongs to the visitor, not to you. Use the screenshot to learn which form was used, then confirm delivery by sending one message from a personal address to each form after every change.
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 form, pop-up or footer block can add a silent second form
Rerun the same task after you add a form, a pop-up, a footer block or a copied section. A new form copied from another page can start with different email settings, while the contact page keeps working. The same task run once per form shows which ones send mail after each change.
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
Will the test show whether my email is sent?
No. The test shows which form the visitor used, what appeared after Submit, and where the step stopped. It does not open your inbox, and a confirmation on screen does not prove a notification was sent. After each fix, send one message through each form and check your inbox for it.
Why does the contact page work but the footer form does not?
They are separate blocks with separate settings. The contact page form may send an email, while the footer form was added later with that setting off. Open each one's settings in the editor and compare them side by side before you change anything.
Should I delete the extra forms?
Only after you have checked where each one sends. A form you have forgotten can still be the one a visitor finds in the footer. Remove a form when you have confirmed the page does not need it, and point the one you keep at the inbox you read.
Does the test cover a form in a pop-up?
A pop-up that opens from a button on the page is a fair test. A pop-up that waits for a delay or a return visit may not show in one run, so check that case by hand in a private window.
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.