You set up a contact form on your Squarespace site, made it look pretty, tested it once — it worked. Three weeks later, a friend mentions they submitted the form and never heard back. You check your inbox: nothing. You check spam: nothing. The submission is sitting in Squarespace’s dashboard, but the email notification never arrived.
Where does Squarespace form mail actually go? And why does it disappear?
How Squarespace handles form email
When someone fills out your Squarespace form, the system does two things:
- Stores the submission in Squarespace’s database (visible under Analytics → Form & Newsletter Submissions)
- Sends a notification email to whatever address you configured under the form’s “Storage” tab
Squarespace sends that notification email through their own shared SMTP infrastructure. It comes from a Squarespace-controlled address (typicallynoreply@squarespace.com) on your behalf, with a reply-to set to the form submitter’s email.
This is convenient. It’s also fragile. Three things commonly go wrong:
1. Gmail / Outlook spam-filter the Squarespace sender
Squarespace shares sending IPs across millions of sites. If a few of those sites send spam (or just trigger user spam reports), the whole shared IP pool can land on a blocklist for weeks. Your perfectly legitimate contact form notification gets quietly junked because of someone else’s behavior.
2. The reply-to trick fails DMARC
Squarespace tries to set “Reply-To” to the form submitter’s address. Some recipient mail servers see this as suspicious — a message claiming to be from squarespace.com but asking replies to go to a random gmail.com address — and silently drop it.
3. Storage settings get reset
If you migrated themes, switched templates, or had a teammate edit the form, the Storage destination email can get reset or disabled. The form keeps accepting submissions, but the notification target gets emptied.
Squarespace doesn't tell you when delivery fails
Diagnose your Squarespace delivery problem
Run this five-minute checklist:
1. Submit your own form
Go to your live site, fill out the form with your personal email. Wait 5 minutes. Check inbox and spam folder of the notification address.
2. Check Form Submissions in Squarespace
Squarespace Editor → Analytics → Form & Newsletter Submissions. If your test submission is there but you didn’t get the email, the form is collecting fine — the email step is broken.
3. Verify Storage settings
Edit the form → Storage tab → confirm “Email” is enabled and the destination address is correct. Tip: avoid using a Gmail address that has aggressive spam filtering enabled.
4. Check spam filter rules at the destination
Some corporate Gmail / Outlook accounts auto-archive messages fromnoreply@ senders. Check spam, then check the Trash, then look at your Gmail / Outlook filter rules to make sure nothing’s catching it.
5. Send a manual test from the Squarespace dashboard
Form Submissions → Send Test Email. If this lands but live form submissions don’t, the issue is downstream of Squarespace’s SMTP — possibly the receiving mail server’s filtering.
How to fix Squarespace email delivery
Option A: Use Squarespace’s Zapier integration (workaround)
Squarespace forms have a Zapier integration. You can set up a Zap that watches for new form submissions and sends an email through Gmail / Outlook / a dedicated mail service.
Pros: works for low-volume forms.
Cons: Zapier free tier is 100 tasks/month and runs Zaps every 15 minutes (so notifications are delayed by up to 15 minutes). Above the free tier, $20+/month. And you’re still sending through Gmail, which has its own deliverability constraints.
Option B: Switch to webhook delivery (recommended)
Squarespace Forms (Business and Commerce plans only) support direct webhook integration. You configure the form to POST submissions to an external endpoint, then have that endpoint send the email through reliable infrastructure.
This is the “real” fix because it bypasses Squarespace’s shared SMTP entirely. Submissions go from your form → SecureSMTP → your inbox, with full SPF + DKIM + DMARC alignment and a delivery dashboard.
Setup:
- Sign up at securessmtp.com/signup — free tier handles 100 submissions/month.
- Dashboard → API keys → Create. Copy the key.
- Squarespace Editor → edit your form → Storage tab → enable Webhook.
- Webhook URL:
https://api.securessmtp.com/v1/forms/submit - Add header:
Authorization: Bearer <your-api-key> - Save. Test by submitting the form.
Within seconds, you’ll see the submission in your SecureSMTP dashboard, the notification email lands in your inbox, and SecureSMTP’s AI classifier automatically flags any suspected spam before it ever hits your inbox.
Native Squarespace vs webhook delivery
| Feature | Squarespace native | Webhook (SecureSMTP) |
|---|---|---|
| Delivery reliability | Shared IP, blocklist risk | Dedicated infra, 99.9% inbox |
| Spam protection | Honeypot only | AI classifier + Turnstile |
| Delivery confirmation | None | Per-message status |
| Custom reply-to | Limited | Full control |
| Bounce handling | Silent | Real-time webhook events |
| Submitter auto-reply | No | Yes |
| Cost | Included with paid plan | Free up to 100/mo |
Frequently asked questions
Does this work on Squarespace's free plan?+
Webhook delivery requires Squarespace Business or Commerce plan. If you're on the Personal plan, you'll need to either upgrade Squarespace OR use the Zapier workaround. The Personal plan doesn't expose webhook configuration in form Storage settings, so there's no way to route submissions through a third party without Zapier as a bridge.
Will I lose my form submissions if I switch to a webhook?+
No. Squarespace still stores every submission in the Form Submissions dashboard regardless of where the notification email goes. You're adding a reliable email layer on top — not replacing data storage.
What if SecureSMTP is down?+
SecureSMTP queues messages and retries automatically for up to 72 hours. Squarespace also keeps a copy of the submission in its own dashboard. Even in a worst-case provider outage, you can still see every form submission and the email goes out as soon as service returns.
Can I send a confirmation email to the form submitter too?+
Yes. SecureSMTP can fire two emails per submission: one notification to your inbox, and one auto-reply confirmation to the form submitter. Configure both in your dashboard — same payload, two destinations. Useful for "Thanks for reaching out, we'll be in touch" auto-responses.
How long does setup take?+
About 5 minutes if you have admin access to your Squarespace site. The webhook URL paste-in is the main step. You won't need to touch any DNS records for basic webhook setup — only if you want the notification to come from your custom domain (which we recommend for the most professional look).
Will the form submitter notice anything different?+
No. From their perspective, nothing changes. They submit the form, see the Squarespace success message, and (if you set up auto-reply) get a confirmation email from your domain. The only thing they could possibly notice is that your reply lands in their inbox instead of spam — which is the whole point.
What about Squarespace's built-in spam protection?+
Squarespace's anti-spam is rudimentary — basically a honeypot field. SecureSMTP layers AI spam classification, Cloudflare Turnstile, IP rate limiting, and per-form abuse detection on top. You'll see fewer bot submissions in your inbox and your sender reputation stays clean even when bots try to abuse your forms.
Ready to fix it?