Google Workspace records at Squarespace
Google gives you each value in the Google Admin console. Add them in this order: verification first, the mail record once the new mailboxes are ready, then the three records that keep your mail out of spam.
| Record | Name | Value |
| Verify the domainTXT | @ | google-site-verification= followed by your code from the Admin console |
| Receive mailMX, priority 1, or the Google Workspace preset | @ | smtp.google.com |
| SPFTXT | @ | v=spf1 include:_spf.google.com ~all |
| DKIMTXT | google._domainkey | The key starting v=DKIM1; that the Admin console generates for you |
| DMARCTXT | _dmarc | v=DMARC1; p=none; rua=mailto: followed by an address you read |
Verifying the domain
In the Admin console, go to Account, Domains, Manage domains, and select Verify domain. Copy the whole value, including google-site-verification=, and add it as a TXT record with @ in Name and the value in Text. Leave it in place until Google confirms, which Google says can take up to 72 hours. This record proves you own the domain and does not change where your email goes, so it is safe to add while your current email keeps working. If Google still refuses, the usual causes are in Google Workspace domain verification failed.
Pointing mail at Google
Squarespace has a preset for this: on the domain's DNS page, select Add preset, confirm your password or two-step sign-in, choose Google Workspace and select Confirm (Squarespace's Google Workspace guide). It treats either Google's single smtp.google.com record or Google's five older aspmx records as correct. Adding smtp.google.com by hand at priority 1 does the same job. Either way, Google says to remove any other MX records, and Squarespace says leftover MX records stop mail being sent and received. Remove any email forwarding rules on the domain too; Squarespace lists them, beside old MX, SPF and DKIM records, as the cause of Google's Conflicting DNS record error. Make this change only when the new mailboxes exist.
One Squarespace warning before deleting anything: if you sign in to Squarespace with an address at this domain, change your Squarespace login address first. Otherwise the codes Squarespace sends you can stop arriving, and you can be locked out of the account that holds the records.
SPF, DKIM and DMARC
Squarespace gives a domain it registers, or connects by nameservers, three default anti-spam records, an SPF, a DKIM and a DMARC, and removes them automatically once you add records for an email provider. They cannot be added back by hand, so the domain has no protection of its own until you add Google's.
For SPF, Google's value when Workspace is your only sender is v=spf1 include:_spf.google.com ~all, and every other service that sends as you belongs in the same record (Google's SPF guide). Squarespace merges several SPF custom records into one, so delete the SPF entry of any service you are leaving rather than letting it merge in. Our free SPF checker shows the record the world actually sees.
For DKIM, wait 24 to 72 hours after Gmail is turned on. Then, in the Admin console, go to Apps, Google Workspace, Gmail, Authenticate email, and generate a new record. Add it as a TXT record with google._domainkey in Name, and only then select Start authentication (Google's DKIM guide). Squarespace takes SPF and DKIM values up to 2048 bits in one piece, so the key needs no splitting.
Add DMARC last. Google suggests waiting 48 hours after SPF and DKIM, then starting at p=none, which only reports and blocks nothing, and tightening it once the reports show your real mail passing (Google's DMARC guide). Squarespace allows one DMARC record per domain, and its Email Campaigns preset or an email forwarding rule may already have added one, so look for a _dmarc record and edit it rather than adding a second.