Squarespace forms silent
Squarespace looks after itself. Your form notifications, less so.
The reassuring polish of Squarespace hides its classic quiet failure: forms submitting successfully — even storing successfully — while the notification emails that were supposed to reach you vanish. Weeks of inquiries, discovered late, in a dashboard nobody was checking.
Same-day diagnosis. Flat quote before any fix.
What’s actually happening
Squarespace forms have two destinations: storage (the submissions panel inside your dashboard, which almost never fails) and notification (the email alerting you, which fails in all the usual email ways). The gap between them is the trap — the platform truthfully reports submissions received while your inbox truthfully receives nothing, and no error appears anywhere you'd look.
Notification failures cluster: the connected email address is stale (an ex-employee, an old domain), the alerts are dying in spam at your inbox, or the storage-connected integrations (Google Drive, Mailchimp) silently disconnected during a platform update or password change. Walled garden means fewer knobs — but the knobs that exist still get left in the wrong position.
The usual causes, ranked
After twenty-seven years of these calls, the odds are well mapped. Start at the top.
Alerts dying in your spam
Squarespace's notification emails filtered at your inbox — especially strict corporate mail. The submissions exist; the alerts are in quarantine.
A stale notification address
Forms faithfully alerting an address nobody reads anymore. Configuration archaeology, two-minute fix, weeks of backlog.
Disconnected integrations
The Google or Mailchimp connection that expired with a password change — storage flowing, downstream silent.
Customer confirmation emails absent
The other direction: submitters expecting a confirmation that Squarespace's form blocks don't send by default — reading your silence as rejection.
What you can safely try first
Nothing below can make things worse — that’s the selection criterion. Anything riskier belongs in professional hands, on a backup.
- 1
Check the submissions storage first
Your Squarespace dashboard's form storage holds every submission regardless of notification health. If entries exist that you never heard about — there's your diagnosis, and your recovery list.
- 2
Submit a test and watch both ends
Fill your own form; check the dashboard (should appear instantly) and your notification inbox including spam (should arrive in minutes). The end that fails names the fix.
- 3
Verify the notification address
Form settings list where alerts go. Stale addresses hide in plain sight — especially post-turnover.
Stop and call when…
- Alerts consistently land in spam — the receiving side needs filter rules and possibly a forwarding redesign
- The backlog holds real inquiries needing careful, prompt replies
- You need form data flowing into email marketing or a CRM reliably — integration work, done once, properly
From there it’s our job: same-day look, flat quote, and the $389 flat repair covers most cases of exactly this.
Form & Email Rescue — buy it now, skip the hunt.
Contact forms delivering again, order and notification emails reaching inboxes.
Covers form and site-email failure on one site: broken submissions, vanishing notifications, spam-folder exile. Includes deliverability setup (SPF/DKIM) where the fix needs it.
Questions we hear a lot.
Are my old submissions recoverable?
Almost certainly — Squarespace stores submissions independently of notifications, so the dashboard holds everything the emails failed to announce. Bittersweet reading, but it's your recovery list: a late, gracious reply beats permanent silence, and often still wins the job.
Why doesn't Squarespace warn me notifications are failing?
From the platform's view, nothing failed — the form submitted, the email was handed off. Delivery into your specific inbox is beyond its sight. That blind spot is exactly why the periodic test submission (or a monthly dashboard glance) is cheap insurance for any Squarespace site.
What does the $389 fix cover?
Both directions: notifications repaired and verified to a monitored inbox, spam-filter rules set on the receiving side, integrations reconnected, and customer-facing confirmations added where the form warrants it — plus the walkthrough of your recovered backlog.
Related symptoms & help
Errors travel in packs. If this one visited, check its friends.
Hear every inquiry — including the ones waiting.
Send the symptom, get a same-day look and a flat quote from the developer who's fixed this exact thing more times than either of us can count.