Recommended Free Tools
You can keep your WordPress website online while moving email to Google Workspace. The key is editing DNS at the service that controls your domain’s authoritative nameservers: leave the website’s A and CNAME records in place, add Google’s ownership TXT record, replace competing MX records with the current Google value, then activate Gmail. Finish by publishing SPF, DKIM and DMARC so messages from Gmail and your WordPress-related senders authenticate correctly.
Antihost offers managed WordPress hosting with free migration, one-click staging and a 14-day free trial.
For new Google Workspace configurations, the MX destination is smtp.google.com with priority 1. Google says DNS recognition can take up to 72 hours, so a record that is correct but not yet visible is usually a propagation delay rather than a WordPress failure.
As an Amazon Associate I earn from qualifying purchases.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →What changes when WordPress hosts the site and Google hosts email?
WordPress is your website platform; it is not automatically the place where every DNS record is managed. DNS records tell the internet where different parts of your domain should go. A and CNAME records direct web browsers to your site. MX records direct incoming email to a mail service. TXT records prove domain ownership and publish email-authentication policies. Changing MX or TXT records does not remove or redirect the web records that keep your WordPress site reachable.
When somebody sends mail to [email protected], the sender’s computer looks up the MX records for example.com and delivers the message to the listed mail server. Therefore, a WordPress dashboard can remain unchanged while your domain’s MX records point to Google Workspace.
#1 Best Overall
The control point is the authoritative DNS host
Edit records wherever the domain’s authoritative nameservers are managed. Depending on how the domain was connected, that may be your registrar, a separate DNS provider, a hosting company, WordPress.com, or another service. The WordPress page editor and WordPress admin area are not reliable indicators of DNS control.
WordPress.com and self-hosted WordPress follow the same DNS logic
| Website arrangement | Where to edit Google records | What happens to the website records |
|---|---|---|
| WordPress.com nameservers are authoritative | The DNS panel provided by WordPress.com | Keep the existing A and CNAME records unless you are deliberately changing web hosting. |
| A domain is connected to WordPress.com with A records while another service supplies nameservers | The external DNS provider that supplies those nameservers | A records continue sending web traffic to WordPress.com; MX records can send mail to Google. |
| Self-hosted WordPress | Normally the registrar, hosting company or separate DNS service that is authoritative for the domain | Leave the web host’s A/CNAME records alone and change only mail and authentication records. |
Look at the nameservers shown for the domain, then sign in to the service named there. If you add a record in a non-authoritative panel, Google will not see it even though the panel reports it as saved.
Prepare before changing DNS
- Have a Google Workspace administrator account and the domain name you intend to use for mail.
- Know which service is authoritative for DNS and have permission to create TXT and MX records.
- List every system that sends mail as your domain: Gmail users, WordPress contact forms, transactional plugins, a CRM, an SMTP relay, and marketing or support services.
- Record the current DNS values or export a zone file if your provider offers that option. This gives you a rollback reference without changing anything yet.
- Plan a testing window. DNS updates are not instantaneous, and some recipients may continue using cached records temporarily.
Do not delete website A or CNAME records as part of an email migration. The records you will normally touch are the root TXT record for verification, the root MX records for delivery, the SPF TXT record, the DKIM TXT record at Google’s selector, and the DMARC TXT record at _dmarc.
Step 1: Find the authoritative DNS provider
- Open the domain-management account where the nameservers are displayed.
- Compare the listed nameservers with the services you use. The service whose nameservers are delegated at the registry is the authoritative DNS host.
- Open that service’s DNS or zone editor. Look for controls labelled DNS records, Manage DNS, Zone file, or Advanced DNS.
- Confirm that existing A, CNAME, MX and TXT records are visible there. If the panel has no such records, you are probably in the wrong account or at a non-authoritative provider.
For a domain using external nameservers, changing a DNS screen inside WordPress will not alter public DNS. Conversely, if WordPress.com nameservers are authoritative, adding records at the registrar will not work. Establish this distinction before copying any Google value.
Step 2: Verify that you own the domain
Google Workspace supplies a unique TXT value beginning with google-site-verification=. Verification proves control of the domain; it does not change your website or mail routing.
- In Google Workspace Admin or the Workspace Setup tool, copy the complete verification value exactly as shown.
- In the authoritative DNS editor, create a record with type
TXT. - Set the name or host to the domain root. Providers represent the root as a blank field,
@, or the full domain; use the format required by that provider and do not append the domain twice. - Paste the entire
google-site-verification=...value into the TXT value field, save it, and leave any unrelated TXT records intact. - Return to Google’s setup screen and choose the verification action. If recognition is not immediate, wait for DNS propagation rather than repeatedly creating different TXT records.
Google’s current guidance allows up to 72 hours for TXT and MX changes to be recognized. A pending status during that period does not by itself indicate an incorrect value. If it remains pending after propagation, check the host/name field, quotation handling, and whether you edited the authoritative DNS provider.
Step 3: Route incoming mail with the current Google MX record
After ownership is verified, configure the MX record at the same DNS host. Google’s current instruction is: “The Google Workspace MX record value is smtp.google.com.” For a new setup, use the following record.
| Field | Value | Why it matters |
|---|---|---|
| Type | MX |
Identifies the record as a mail exchanger. |
| Name/host | Blank or @, according to the DNS provider |
Applies the mail route to the root domain. |
| Priority | 1 |
Sets the preference for this exchanger; lower numbers are preferred. |
| Destination | smtp.google.com |
Routes incoming domain mail to Google Workspace. |
Remove competing MX records
Delete old or unrelated MX records that point to a previous mailbox provider. If multiple providers remain, different senders can choose different destinations, producing the classic symptom of being able to send mail but not receive it consistently. Do not remove TXT, A, or CNAME records merely because they are near the MX records; they serve different purposes.
Understand legacy Google records
Accounts started before 2023 may still display legacy destinations beginning with aspmx. A working legacy configuration does not need to be changed solely because its values look different from smtp.google.com. For a new account, use the current value above; for an existing account, follow the MX value shown in its Admin setup instructions and avoid an unnecessary cutover.
Save without altering web traffic
Save the MX change while preserving every A and CNAME record used by WordPress. The result should be a domain whose web lookups still return the WordPress host while mail lookups return Google’s exchanger.
Step 4: Activate Gmail in Google Workspace
- Sign in to the Google Admin console with an administrator account that has the required domain-settings privilege.
- Open Account > Domains > Manage domains.
- Select the domain you just configured.
- Choose Activate Gmail and complete the confirmation.
Google may not recognize the MX record immediately. If the activation screen reports that records are missing just after you saved them, allow propagation and retry. Activation does not rewrite your WordPress configuration; it tells Workspace to accept mail for the verified domain.
Step 5: Publish SPF for every legitimate sender
SPF lists the servers authorized to send mail for your domain. Google gives this example when Google Workspace is the only sender: v=spf1 include:_spf.google.com ~all. SPF helps receiving servers avoid treating legitimate outgoing messages as spam.
Inventory before writing the record
WordPress forms and transactional plugins often send independently of Gmail. A CRM, SMTP relay, help-desk system, or marketing service may also send with your domain in the From address. Changing MX controls incoming mail; it does not reconfigure any of these outbound systems.
- Identify each service that sends as your domain.
- Obtain that service’s official SPF authorization mechanism.
- Combine Google’s mechanism and the other legitimate mechanisms in one SPF TXT record at the root.
- Remove obsolete mechanisms and make sure there is only one SPF record for the domain. Multiple SPF records are not combined by receiving servers and can cause an SPF failure.
- Save the record and allow time for authentication results to appear.
Google says SPF authentication can take up to 48 hours to start working. During that interval, compare test-message headers from more than one recipient before changing the record again.
Step 6: Configure DKIM signing
DKIM adds a cryptographic signature to messages sent by Google Workspace. The receiving server checks the public key in DNS and uses it to verify that the message was signed by an authorized system and was not altered in transit.
Rank #4
- In the Admin console, open the Gmail authentication area and choose the option to generate a new DKIM key.
- Copy the selector and public-key value Google provides. The selector is commonly represented by a host such as
google._domainkey, but use the exact selector displayed for your domain. - At the authoritative DNS provider, create a TXT record using that selector as the host/name and paste the complete public key as the value.
- Save the DNS record, return to the Gmail authentication page, and start authentication for the domain.
- Send a test message and inspect the recipient’s message headers after DNS has propagated.
Google states that DKIM can take up to 48 hours after the DNS key is added before authentication works reliably. Do not publish a shortened key, alter line breaks supplied by the DNS editor, or create the record at a secondary DNS service.
Step 7: Add DMARC after SPF and DKIM are understood
DMARC tells receiving servers how to handle messages that fail authentication and provides reporting options. Add the policy at the host _dmarc only after you have confirmed which systems send mail and checked SPF and DKIM alignment for those systems.
- Review legitimate senders and verify that each can authenticate with SPF, DKIM, or both.
- Create the DMARC TXT record at
_dmarcusing the policy and reporting settings selected in your organization’s mail plan. - Begin with a monitoring approach while you examine reports and correct legitimate sources that are failing alignment.
- Strengthen enforcement only after normal WordPress form mail, Gmail mailboxes, and third-party services pass consistently.
For senders delivering more than 5,000 messages per day to Gmail accounts, Google’s guidance effective February 1, 2024 requires SPF, DKIM and DMARC, along with additional sender requirements. Even domains below that volume benefit from publishing all three controls because WordPress and third-party applications frequently send mail as the same domain.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallOutdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchHow the main setup paths compare
| Decision point | WordPress.com nameservers | External nameservers with WordPress.com A records | Self-hosted WordPress |
|---|---|---|---|
| Authoritative DNS | WordPress.com DNS panel | The external DNS provider | Registrar, hosting company or separate DNS service |
| Website records | Remain in the same zone | A records continue pointing to WordPress.com | Keep the host’s A/CNAME records |
| Mail records | Add verification TXT and Google MX there | Add them at the external provider, not in the WordPress editor | Add them wherever the domain’s nameservers are managed |
| MX syntax for a new Workspace setup | smtp.google.com, priority 1 |
smtp.google.com, priority 1 |
smtp.google.com, priority 1 |
| Main risk | Editing the registrar instead of WordPress.com | Editing WordPress.com while external nameservers remain authoritative | Deleting web records while trying to change mail |
Testing after activation
Test incoming mail
Send messages from two unrelated external accounts to a Workspace mailbox. Confirm that both arrive in Gmail and that replies return to the original senders. If one arrives and another does not, inspect whether different senders are still seeing cached or conflicting MX data.
Test outgoing mail and authentication
Send from Gmail to external recipients and inspect the authentication results in the received headers. You want the recipient to report the expected SPF and DKIM results and a DMARC result consistent with your policy. A successful send alone does not prove that your domain’s SPF, DKIM and DMARC records are correct.
Best Value
Test WordPress forms separately
Submit every important contact or transaction form. Confirm both delivery and the visible From or Reply-To behavior. If forms still use an old SMTP server, update the plugin’s SMTP or API settings and include that sender in your SPF and DKIM plan. MX changes affect incoming delivery; they do not change a plugin’s outbound connection.
Troubleshooting common failures
You can send mail but cannot receive it
- Query the domain’s public MX records and check that the current Google destination is visible.
- Remove stale MX records for the former provider or any unrelated service.
- Verify that the record was added at the authoritative DNS host, not just at the registrar or WordPress dashboard.
- Check the record name. A root record entered as a full domain at a provider that automatically appends the domain can create a doubled hostname.
- Allow the propagation window before making another change.
Domain verification remains pending
- Confirm the TXT value begins with the exact
google-site-verification=string supplied by Google. - Check that the host is the root (
@, blank, or the provider’s equivalent), notwwwor a mail subdomain. - Ensure quotation marks added by the DNS interface are formatting, not characters you pasted into the value.
- Wait up to 72 hours for recognition, then recheck the authoritative zone and retry verification.
Messages land in spam
- Publish SPF and include every legitimate sender, including WordPress and third-party services.
- Generate and enable DKIM for Google Workspace, then allow up to 48 hours for authentication to become visible.
- Add DMARC after reviewing alignment and correct any sender that fails it.
- Inspect headers from a delivered message rather than relying only on the Gmail send status.
WordPress forms still use the old mail system
Find the form plugin’s SMTP, API, or mailer setting. Replace the former provider’s connection only when you know which service should send the form messages. Then authorize that service in SPF and, where supported, enable its DKIM signing. Changing the domain MX record alone never rewrites a plugin’s outbound SMTP configuration.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →A DNS proxy or orange-cloud style control is confusing the setup
MX and TXT records are DNS data, not website proxy traffic. Use the provider’s standard DNS-only controls for these records. Proxying a web A record and routing mail are separate operations; do not try to proxy an MX record as if it were a website request.
Gmail activation still reports missing records
Check that there is no typo in smtp.google.com, that the priority is 1, and that old MX records have been removed. If the public record is correct but the Admin console is still waiting, the remaining issue is usually propagation. Recheck after the stated window rather than adding multiple Google MX records with different spellings.
Quick Recap
DNS safety checklist
- Identify authoritative nameservers before editing anything.
- Keep WordPress A and CNAME records.
- Place Google’s verification TXT value at the root.
- Use
smtp.google.comwith priority1for a new Workspace setup. - Remove conflicting MX records, while leaving unrelated TXT records intact.
- Activate Gmail from Account > Domains > Manage domains after the MX record is visible.
- Publish one SPF record containing Google and every legitimate non-Google sender.
- Generate DKIM in the Admin console and publish the exact selector and public key.
- Add DMARC at
_dmarcafter checking SPF/DKIM alignment. - Allow up to 72 hours for MX/TXT recognition and up to 48 hours for SPF or DKIM authentication to appear.
- Test inbound mail, outbound authentication, and each WordPress form independently.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
