Connect GoDaddy Domain to Google Workspace

Last reviewed: July 13, 2026 · Written by Email Solutions

Connecting a GoDaddy domain to Google Workspace is mostly DNS work: MX for delivery, a TXT record to prove you own the domain, then SPF, DKIM, and DMARC so messages authenticate.

If mail already "works" but lands in spam, skip to authentication — or use our related spam-fix landing. To see what your domain publishes today, open the free deliverability report.

Official references:

• Google Workspace MX record values
• Google email sender guidelines

Before you start

1. You can sign in to GoDaddy DNS Management for the domain.
2. You have Google Workspace Super Admin access for the organization.
3. Note any existing MX, TXT (especially v=spf1), and email forwarding at GoDaddy. Screenshot them.

Step 1 — Publish Google MX records

Inbound Workspace mail needs Google's MX hosts. Old GoDaddy Email / Workspace Email MX entries conflict and must go.

1. Open the domain in GoDaddy → DNS (DNS Management).
2. Delete MX records that do not point at Google.
3. Add these MX records (values from Google's documentation — confirm against Admin Console if Google shows custom values for your tenant):

4. Turn off GoDaddy email forwarding that still routes to a non-Google destination, unless you intentionally keep it.

Verify with:

dig +short MX example.com

You should see only the Google hosts above (possibly in a different order).

Step 2 — Verify domain ownership

Google Admin will ask for a TXT (or sometimes CNAME/HTML) verification record.

1. In Google Admin, start domain verification for the domain.
2. Copy the exact TXT name/value Google shows.
3. Add it in GoDaddy DNS (usually host @ or a Google-specified hostname).
4. Return to Admin and click verify after DNS propagates (often minutes; can take up to 48 hours).

Do not delete the verification TXT afterward unless Google says it is safe for your setup — many tenants leave it in place.

Step 3 — SPF (one record only)

Google Workspace senders need SPF authorization. On GoDaddy domains we frequently see two v=spf1 TXT records (legacy GoDaddy email + a new Google include). Receivers treat multiple SPF records as a permanent failure.

Workspace-only baseline:

v=spf1 include:_spf.google.com ~all

If you also send through Stripe, Shopify, or a marketing ESP, merge their includes into the same string. Example shape:

v=spf1 include:_spf.google.com include:example-vendor.com ~all

Rules that matter:

• Exactly one SPF TXT at @
• Prefer ~all while testing; move to -all after mail paths are confirmed
• Stay within SPF's 10 DNS-lookup limit (RFC 7208) or evaluation returns PermError — see Fix SPF PermError

dig +short TXT example.com

Step 4 — DKIM (2048-bit)

1. Google Admin → Apps → Google Workspace → Gmail → Authenticate email
2. Select the domain → Generate new record → 2048-bit key
3. In GoDaddy, add the TXT (host often google._domainkey) with the full v=DKIM1; k=rsa; p=... value
4. Click Start authentication in Admin after the TXT is live

dig +short TXT google._domainkey.example.com

Step 5 — DMARC (start with monitoring)

v=DMARC1; p=none; rua=mailto:dmarc@example.com; fo=1

Publish as TXT host _dmarc. p=none is the monitoring policy Google documents as acceptable for bulk-sender minimums; tighten to quarantine only after you review aggregate reports.

dig +short TXT _dmarc.example.com

Common GoDaddy mistakes we see

1. Left-over MX pointing at GoDaddy email after Workspace signup
2. Two SPF records after pasting Google's include without deleting the old TXT
3. DKIM TXT truncated in the GoDaddy UI (paste the entire p= block)
4. Skipping DMARC, then failing mailbox-provider bulk-sender checks later — see the bulk sender checklist

Verify and next steps

1. Run the free domain report
2. Send a test message from Workspace to a personal Gmail inbox and check headers for spf=pass, dkim=pass, dmarc=pass
3. If you want this done without DNS panels, use the 1-Click Fix flow or the GoDaddy spam-fix landing