Provider repair guideReviewed 2026-08-07By HostWithShery technical editorial

Fix Google Workspace email on Squarespace DNS

Restore Google Workspace MX and email-authentication records without changing the Squarespace website records.

Start with evidence from your own domain before changing DNS, SSL or mail settings.
Check your own configuration

Email Health Check

This page is preconfigured with the Email Health Check that best matches this problem.

No accountPublic evidence only
Live public check

Checks MX routing plus SPF, DKIM discovery, DMARC, BIMI, MTA-STS and TLS-RPT public signals.

No account · Public configuration only
On this page

Fix Google Workspace email on Squarespace DNS: when this repair path applies

Restore Google Workspace MX and email-authentication records without changing the Squarespace website records. Use these steps when website connection works but Google MX is incomplete, but first run the embedded diagnostic so the business-email DNS and mail authentication evidence supports this provider-specific path rather than a neighboring DNS, TLS, application or mail cause.

Find the authoritative setting before editing

Squarespace Domains/DNS settings or the external registrar/DNS provider shown by the active nameservers. For Fix Google Workspace email on Squarespace DNS, confirm the active nameservers and exact service owner before changing keep website records intact. A DNS-looking screen at squarespace has no public effect when another provider is authoritative for the zone.

Evidence to save for Fix Google Workspace email on Squarespace DNS

Record the current public state for keep website records intact, restore Google MX, verify SPF/DKIM/DMARC. This gives the repair a before/after comparison and prevents a cached answer or a separate working service from being confused with the configuration that produced the symptom.

  • Keep website records intactVerify keep website records intact from the public Internet and compare it with the value the responsible provider says should be live.
  • Restore Google MXRead the public MX priorities and targets, then verify that each target itself resolves. A visible MX record is not enough if its mail hostname is broken.
  • Verify SPF/DKIM/DMARCInspect the single public v=spf1 policy, validate its terms and count DNS-query-causing mechanisms; duplicate policies or excessive lookups can invalidate SPF.
  • Retest mail DNSVerify retest mail DNS from the public Internet and compare it with the value the responsible provider says should be live.

Repair steps in squarespace

Restore Google Workspace MX and email-authentication records without changing the Squarespace website records.

  • 1. Keep website records intact. After this step, check the public value tied to keep website records intact before changing another unrelated setting.
  • 2. Restore Google MX. After this step, check the public value tied to restore google mx before changing another unrelated setting.
  • 3. Verify SPF/DKIM/DMARC. After this step, check the public value tied to verify spf/dkim/dmarc before changing another unrelated setting.
  • 4. Retest mail DNS. After this step, check the public value tied to retest mail dns before changing another unrelated setting.

Why this order matters for squarespace

The sequence begins with the provider/authority decision, then moves through keep website records intact, restore Google MX, verify SPF/DKIM/DMARC. That keeps the change scoped to the failed business-email DNS and mail authentication path and avoids replacing nameservers, mail authentication or another healthy service just to make a provider dashboard indicator change.

Verify Fix Google Workspace email on Squarespace DNS

The public MX/authentication records should match the intended mail provider, required hostnames should resolve, and the relevant SPF/DKIM/DMARC check should no longer show the original failure. Compare the same keep website records intact and restore Google MX evidence used before the change; a repair is complete when the public result agrees, not merely when the squarespace interface reports that a save succeeded.

If squarespace and the public result disagree

Check whether the edited zone is authoritative, whether the exact root/www/subdomain was changed, whether a proxy state alters the visible endpoint, and whether a prior TTL can still exist in recursive caches. Do not add a second conflicting keep website records intact value to force validation.

Mistakes to avoid for this repair

Do not copy tenant-specific or region-specific values from another account, delete working email records during a website repair, change nameservers as a shortcut, or alter SSL/proxy modes without evidence from the origin. Fix Google Workspace email on Squarespace DNS should change only the settings required by this diagnosis.

Technical references

These primary standards and provider documents are used to verify the behavior described on this page. Provider dashboards can change, so use the current official value for tenant-specific DNS records rather than copying an example from another account.