Squarespace is the "design-first" builder. The visual defaults are great, the templates ship clean, and the form builder covers 90% of what a service business needs. What Squarespace is conspicuously silent about is where form-notification emails come from, and why they sometimes never arrive at your team's inbox.
The short version: form notification mail from Squarespace is sent through Squarespace's mail relay. You don't choose the envelope, you don't sign DKIM, you don't set DMARC. For a lot of sites this is fine. For sites where leads are the product, it needs to be tested and usually rerouted.
Step 1: seed the current Squarespace notification to real inboxes and record the placement. Step 2: if placement is bad, route the form via Zapier (or Make) to an external ESP authenticated on your domain. Step 3: re-test.
How Squarespace sends form notifications
The typical Squarespace form notification has these properties:
- Envelope sender on a
squarespace.comsubdomain. - From header set to your site email, but signed by Squarespace.
- Shared reputation pool with every other Squarespace site.
- No admin-exposed DKIM selector. No bounce re-routing. No custom Return-Path.
Mailbox providers that enforce DMARC alignment strictly (Gmail, Outlook, Yahoo) will sometimes downgrade Squarespace-sent mail claiming to be from your domain — especially if your domain runs a p=quarantine or p=reject DMARC policy. That is the single biggest silent-failure mode.
What Squarespace does not let you change
- The SMTP server (it is Squarespace's).
- The DKIM selector or key rotation.
- The bounce / feedback loop address.
- Per-mail custom headers for threading or tracking on your side.
What you can do is change the recipient list, the Reply-To, and on paid plans, add a storefront email with branded sending — which solves the marketing stream but not the form-notification stream.
Squarespace has Customer Notifications (order confirmation, abandoned cart) on the Commerce side, and Form Submissions on the content side. They travel through different pipes. Test both separately — a fix for one may not fix the other.
Measure placement with a seed test
Add real seed addresses across providers and submit the form. The Squarespace form editor lets you add multiple notification recipients:
- Open the form block → Storage → Email.
- Paste 20+ seed addresses (Gmail, Workspace, Outlook.com, M365, Yahoo, Mail.ru, Yandex, GMX, Proton, Fastmail).
- Submit three plausible test leads.
- Record per-provider placement: Inbox / Promotions / Junk / missing.
- Repeat tomorrow.
Zapier → external ESP workaround
When placement is bad, the clean fix is to stop using Squarespace's built-in notification and route the form via Zapier (or Make) to your own ESP.
Trigger: Squarespace: New Form Submission
Action: Resend / Postmark / SendGrid: Send Email
from: leads@yourdomain.com
to: sales@yourdomain.com
reply-to:{{ submitter_email }}
subject: New lead: {{ name }}
body: {{ all form fields, formatted }}Because the outbound email now goes through an ESP that you authenticate (your SPF, your DKIM, your DMARC alignment), placement becomes a function of your own domain reputation rather than Squarespace's shared pool.
Disable the native notification once the Zap is live
Keep the native Squarespace notification on while you validate the Zap — you want to catch the case where Zapier trial hits a rate limit or the ESP rejects. Once you have 48h of clean operation, turn the native notification off to avoid duplicates.
Decide: stay, proxy, or switch
- Placement looks good in the seed test: keep the native flow. Retest monthly.
- Placement is mixed: proxy via Zapier to an ESP. 20 minutes of setup.
- You need richer lead routing anyway: route directly to your CRM or to Slack, and use email only as secondary confirmation.