Google Workspace records at Cloudflare
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 | @ | 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 Content. 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 answers that the domain is already in use, Cloudflare notes that is a Google account matter, not a DNS one: the domain is still attached to another Google Workspace account. Other causes are in Google Workspace domain verification failed.
Pointing mail at Google
Google's current mail record is a single MX record: smtp.google.com at priority 1 (Google's MX guide). Cloudflare's own Google Workspace guide still lists Google's five older records that start with aspmx; Google says those older values are still supported, so a domain already using them with working mail needs no change. Either way, Google says to remove any other MX records, and Cloudflare's guide says to delete MX records that point at another mail provider. Make this change only when the new mailboxes exist.
Check for Cloudflare Email Routing before you start. Cloudflare's Google guide says Email Routing and Google Workspace MX records cannot coexist on the same domain, and has you turn Email Routing off before adding Google's. Turning it off removes every MX, SPF and DKIM record it added, even one you unlocked and edited to point somewhere else. If mail has to keep arriving during the switch, Cloudflare's Email Routing page gives a gentler order: unlock its records, add Google's alongside them as new records, check the new mailboxes work, then turn Email Routing off. Either way, check the record list again straight after.
SPF, DKIM and DMARC
For SPF, Google's value when Workspace is your only sender is v=spf1 include:_spf.google.com ~all (Google's SPF guide). Cloudflare's guide says your domain must have exactly one SPF record, so every other service that sends as you adds its include to that same record rather than a record of its own. 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; Cloudflare's guide picks the 2048-bit key length. Add it as a TXT record with google._domainkey in Name and the whole key in Content, and only then select Start authentication (Google's DKIM guide).
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). If a _dmarc record already exists, we edit it rather than add a second, so the domain keeps one.