Google Workspace + WordPress.com
Set up Google Workspace email on WordPress.com
The records Google Workspace needs, written with the field names WordPress.com uses (Name, Handled by, Text, Alias of (points to)), in the order to add them.
- 5 steps
- 5 DNS records
- Sources checked October 21, 2026
Before you start
- Have your Google Workspace account ready. Some values are unique to your account and come from the Google Admin console.
- Open DNS at WordPress.com: In your Hosting Dashboard, open Domains and select your domain. Under Settings, open DNS records, then select Add record (upper right).
- Keep both tabs open and add the records below one at a time.
Records to add
Copy each value with the button next to it. Rows marked “Copy from Google Admin console” are unique to your account.
| Record | Type | Name | Value | Priority | TTL | |||||
|---|---|---|---|---|---|---|---|---|---|---|
| Domain verification Proves you own the domain | Type | TXT | Name | @ | Value | Copy from Google Admin console Looks like: google-site-verification= followed by your unique code | Priority | n/a | TTL | 3600 seconds (when no other records share a TTL) |
| MX records Where incoming email goes | Type | MX | Name | @ | Value | smtp.google.com | Priority | 1 | TTL | 3600 seconds (when no other records share a TTL) |
| SPF record Which servers may send as you | Type | TXT | Name | @ | Value | v=spf1 include:_spf.google.com ~all | Priority | n/a | TTL | 3600 seconds (when no other records share a TTL) |
| DKIM A signature on every message | Type | TXT | Name | google._domainkey | Value | Copy from Google Admin console | Priority | n/a | TTL | 3600 seconds (when no other records share a TTL) |
| DMARC record What to do with fakes · recommended | Type | TXT | Name | _dmarc | Value | v=DMARC1; p=none; rua=mailto:dmarc@yourdomain.com | Priority | n/a | TTL | 3600 seconds (when no other records share a TTL) |
Step by step in WordPress.com
Verify your domain
Your email provider needs proof that you control this domain before it accepts email for it.
- Type
- TXT
- Name
-
@ - Text
- Copy it from Google Admin console (see below)
Where to find your value
In the Google Admin console go to Menu > Account > Domains > Manage domains, click Verify domain, then Get started. In the TXT record section, copy the Value, including google-site-verification=.
It looks like: google-site-verification= followed by your unique code
- Leave the host blank or enter @.
- Once Google has verified the domain, this TXT record can be safely removed. Removing it earlier makes verification fail.
- It can take up to 72 hours for a new TXT record to be recognized.
In WordPress.com
- Select Add record and choose TXT.
- Enter the Name (@ for your bare domain) and paste the value in Text.
- Save the record.
Point your MX records
MX records tell every other mail server where to deliver email for your domain. They must point to your provider and nowhere else.
- Type
- MX
- Name
-
@ - Priority
- 1
- Handled by
-
smtp.google.com
- Remove any other MX records. Email might not work correctly if old or incorrect MX records stay in place.
- Some domain hosts need a trailing period: smtp.google.com.
- Accounts that started before 2023 may use older values beginning with aspmx. Those are still supported, so there is no need to change working records.
- For TTL, use your domain host's default.
In WordPress.com
- Select Add record and choose MX.
- Enter @ in Name, the mail server in Handled by, and the Priority (pre-filled with 10).
- Save the record.
Add the SPF record
SPF is a TXT record that lists the services allowed to send email from your domain, so receivers can spot forgeries.
- Type
- TXT
- Name
-
@ - Text
-
v=spf1 include:_spf.google.com ~all
- This is the record for domains that send email only through Google Workspace.
- If other services also send email for your domain, list each one in the same record, for example: v=spf1 include:_spf.google.com include:amazonses.com ~all.
- Google recommends ~all at the end of the record.
In WordPress.com
- Select Add record and choose TXT.
- Enter the Name (@ for your bare domain) and paste the value in Text.
- Save the record.
Set up DKIM
DKIM publishes a public key so receivers can confirm your messages really came from you and were not changed on the way.
- Type
- TXT
- Name
-
google._domainkey - Text
- Copy it from Google Admin console (see below)
Where to find your value
In the Google Admin console go to Menu > Apps > Google Workspace > Gmail and click Authenticate email. Select your domain, generate a new record (2048-bit if your domain host supports it, otherwise 1024-bit) and copy the TXT record value.
- google is Google's default selector, so the host is google._domainkey.
- Wait 24 to 72 hours after turning on Gmail before generating the key.
- Some domain hosts limit TXT record length. If the 2048-bit key will not fit, generate a 1024-bit key instead.
- After the record is published, go back to Authenticate email and turn on authentication for the domain.
In WordPress.com
- Select Add record and choose TXT.
- Enter the Name (@ for your bare domain) and paste the value in Text.
- Save the record.
Add the DMARC record (recommended)
DMARC tells receivers what to do with mail that fails SPF and DKIM, and where to send reports about it.
- Type
- TXT
- Name
-
_dmarc - Text
-
v=DMARC1; p=none; rua=mailto:dmarc@yourdomain.com
- Start with p=none so nothing is blocked while you read the reports. Google suggests running it for about a week.
- Replace the report address with a mailbox or group you actually check. Google advises against a personal inbox.
- Then tighten gradually, for example v=DMARC1; p=quarantine; pct=5; rua=mailto:dmarc@{domain}, raising pct over time.
- Set up SPF and DKIM first. Google recommends 48 hours of authentication before turning on DMARC.
In WordPress.com
- Select Add record and choose TXT.
- Enter the Name (@ for your bare domain) and paste the value in Text.
- Save the record.
Check your setup
Once the records are saved, run a live check. We look up your domain in public DNS and tell you what is right, missing or wrong, with the fix in WordPress.com’s words.
Common mistakes with Google Workspace on WordPress.com
Leaving old MX records in place
Google says email might not work correctly if old or incorrect MX records stay. Remove every MX record except smtp.google.com.
Adding a second SPF record
A domain must have only one SPF record. If you already have one, add include:_spf.google.com to it instead of creating another.
Generating the DKIM key too soon
Google asks you to wait 24 to 72 hours after turning on Gmail before generating the DKIM key.
Publishing DKIM but not turning it on
Adding the TXT record is only half the job. Go back to Authenticate email in the Admin console and turn on authentication.
Deleting the verification record too early
Removing the google-site-verification record before Google confirms the domain makes verification fail.
Rather have someone do it for you?
Tell us your domain and we will add and verify every record for Google Workspace on WordPress.com, then send you the check results.
Google Workspace on WordPress.com: questions
Where do I add Google Workspace DNS records in WordPress.com?
In your Hosting Dashboard, open Domains and select your domain. Under Settings, open DNS records, then select Add record (upper right). Add each record there, one at a time.
What goes in the Name field at WordPress.com?
Enter @ for records on your bare domain, such as MX and SPF. For the others, enter only the part before your domain, for example google._domainkey. WordPress.com adds your domain automatically.
Do I need to delete my existing MX records at WordPress.com?
Remove any other MX records. Email might not work correctly if old or incorrect MX records stay in place.
Where do I get my Google Workspace DKIM record?
In the Google Admin console go to Menu > Apps > Google Workspace > Gmail and click Authenticate email. Select your domain, generate a new record (2048-bit if your domain host supports it, otherwise 1024-bit) and copy the TXT record value.
How long until Google Workspace email works on WordPress.com?
New MX records can take up to 72 hours to be recognized.
Sources
Every value and step on this page comes from these official pages. Dashboards change, so if something doesn’t match what you see, tell us.
- Add a DNS record to your WordPress.com domain (WordPress.com Support) Checked October 21, 2026
- Recommended DMARC rollout (Google Workspace Help) Checked October 21, 2026
- RFC 7208: Sender Policy Framework (IETF) Checked October 21, 2026
- Set up DKIM (Google Workspace Help) Checked October 21, 2026
- Set up DMARC (Google Workspace Help) Checked October 21, 2026
- Set up MX records for Google Workspace (Google Workspace Help) Checked October 21, 2026
- Set up SPF (Google Workspace Help) Checked October 21, 2026
- Verify your domain with a TXT record (Google Workspace Help) Checked October 21, 2026
Google Workspace on other hosts
- Google Workspace on Amazon Route 53
- Google Workspace on Bluehost
- Google Workspace on Cloudflare
- Google Workspace on DreamHost
- Google Workspace on GoDaddy
- Google Workspace on Hostinger
- Google Workspace on IONOS
- Google Workspace on Name.com
- Google Workspace on Namecheap
- Google Workspace on Network Solutions
- Google Workspace on OVHcloud
- Google Workspace on Porkbun
- Google Workspace on SiteGround
- Google Workspace on Squarespace Domains
- Google Workspace on Wix
Other email providers on WordPress.com
- Fastmail on WordPress.com
- Hostinger Email on WordPress.com
- iCloud+ Custom Email Domain on WordPress.com
- Microsoft 365 on WordPress.com
- Migadu on WordPress.com
- Namecheap Private Email on WordPress.com
- Proton Mail on WordPress.com
- Rackspace Email on WordPress.com
- Titan Email on WordPress.com
- Zoho Mail on WordPress.com