Table of contents
Get insights delivered straight into your inbox every week!

How to Set Up DKIM in Google Workspace

Your emails are landing in spam. Or worse, they’re not even getting delivered.

That’s not just annoying, it kills your outreach before it even starts.

I’ve seen it happen. 

You set up Google Workspace, start sending emails, and suddenly nothing’s hitting the inbox.

In most cases? It’s because DKIM was never set up.

That’s why I wrote this.

In this blog, you’ll get:

  • A simple explanation of what DKIM is
  • A step-by-step guide to setting it up in Google Workspace
  • What to do before and after setup
  • How to check if it’s working
  • And how to fix it fast if it’s not

If you’re sending emails for cold outreach, newsletters, or client work, and you want better deliverability, this guide helps you do it right.

Let’s set it up.

What Is DKIM in Google Workspace?

DKIM stands for DomainKeys Identified Mail. It’s a way to prove that an email really came from your domain and wasn’t changed along the way.

When DKIM is turned on in Google Workspace, it adds a special digital signature to every email you send. 

This signature tells inbox providers like Gmail, Outlook, or Yahoo:

“This message is safe. It was sent by the right person and hasn’t been tampered with.”

How DKIM works
This image shows how DKIM works

Without DKIM, your emails look less trustworthy. 

Even if you’re sending legit emails, they can get flagged or land in spam, especially if you're doing cold outreach or marketing to new contacts.

Setting up DKIM in Google Workspace is one of the easiest ways to improve deliverability and protect your domain from email spoofing (when someone tries to send emails pretending to be you).

If you want your emails to land in the inbox, not spam, DKIM is a must. 

Why You Should Set Up DKIM in Google Workspace

Now that you know what DKIM is, let’s talk about why setting it up matters.

If you don’t have DKIM enabled, your emails may look suspicious, even if you’re sending real, valuable messages. 

Inbox providers don’t just look at what you say, they look at how the email is sent and whether it’s properly verified.

That’s where DKIM makes a big difference.

Why emails land in spam without DKIM
This image shows why emails land in spam without DKIM

Here’s what changes when you don’t set it up vs when you do:

Without DKIM With DKIM
Emails may land in spam Emails are more likely to reach inbox
“via yourdomain.com” warning shows No warning, looks clean and professional
Harder to build trust with contacts Helps build trust and domain reputation
Cold outreach often gets ignored Cold emails are more likely to be opened

If you're doing any kind of cold emailing, newsletters, or email marketing, DKIM is essential.

It’s a small setup step that makes a big difference in how your emails are seen, and whether they get seen at all.

Let’s look at what you need before you start.b

Requirements Before Setting Up DKIM in Google Workspace

Before you set up DKIM, there are a few things you’ll need.

This setup only works if your domain and Google Workspace account are already properly connected.

Here’s what you should have ready:

  • Access to the Google Admin Console: 

    • You need to be signed in as a super admin for your Google Workspace account.
       
    • That’s the only way you’ll be able to generate the DKIM record and turn on email authentication.

  • Login to your domain registrar: 

    • This is where your domain is hosted, like GoDaddy, Namecheap, Cloudflare, or any other provider. 
    • You’ll be adding a TXT record to your domain’s DNS settings, so you need to be able to log in and make changes.

  • A verified domain in Google Workspace: 

    • DKIM only works if Google Workspace already recognizes your domain. 
    • If your domain isn’t verified yet, you’ll need to do that first in the Admin Console under Domains > Manage domains.

Once you have these three things ready, you can move on to the actual setup.

It only takes a few minutes if you follow the steps correctly, let’s walk through them next.

How To Set Up DKIM in Google Workspace (Step-by-Step)

Setting up DKIM in Google Workspace only takes a few steps, but it’s important to follow them carefully. 

Once it’s done, your emails will be signed properly, helping them reach the inbox instead of spam.

Here’s how to do it:

Quick overview of DKIM setup steps in Google Workspace
This image shows the Quick overview of DKIM setup steps in Google Workspace

a. Generate the DKIM Record in Google Admin Console

  1. Log in to your Google Admin Console at admin.google.com.

    Make sure you’re signed in as a super admin.

  2. In the menu, go to: Apps > Google Workspace > Gmail > Authenticate Email

  3. Choose the domain you want to set up DKIM for (from the dropdown list).

  4. Click on "Generate New Record".

  5. Set the key length to 2048-bit (this is the recommended option for better security).

  6. Leave the selector prefix as “google”, unless you have a reason to change it.

  7. Click "Generate" to create your DKIM TXT record.

b. Add the DKIM Record to Your Domain’s DNS

  1. Open a new tab and log in to your domain registrar (like GoDaddy, Namecheap, Cloudflare, etc.).

  2. Go to the DNS settings or DNS management section for your domain.
GoDaddy’s DNS Management screen where you can add a new TXT record.
This image shows the GoDaddy’s DNS Management screen where you can add a new TXT record.
  1. Add a new TXT record using the following:

    • Host/Name: google._domainkey (or use the selector prefix you chose earlier)

    • Type: TXT

    • Value: Paste the DKIM key you copied from the Admin Console

  2. Save the DNS record.
Example of a correctly added DKIM TXT record (google._domainkey) in GoDaddy.
This image shows the Example of a correctly added DKIM TXT record (google._domainkey) in GoDaddy.

Note: It may take up to 48 hours for DNS changes to fully update.

c. Turn On DKIM Signing in Google Workspace

  1. Go back to the Google Admin Console.

  2. Return to Gmail > Authenticate Email.

  3. Select your domain again and click "Start Authentication".

  4. The status should change to “Authenticating email with DKIM” once it’s active.

That’s it! Your emails from Google Workspace will now include a DKIM signature, making them more secure and less likely to be flagged as spam.

Next, I’ll show you how to test if DKIM is working properly.

How To Check If DKIM Is Working in Google Workspace: Verifying DKIM Setup

Once you’ve set up DKIM, it’s important to confirm that it’s working properly. 

If the setup is incomplete or something’s wrong with the DNS record, your emails might still land in spam, even if DKIM looks “enabled.”

Here are three easy ways to check if DKIM is active and signing your emails:

Step What To Do What To Look For
1. Send a Test Email Send an email from your Google Workspace account to an external email (e.g., Gmail) Make sure the email is delivered
2. Check Email Headers In Gmail, open the test email → click ⋮ → Show original Look for dkim=pass under Authentication-Results
3. Use Online Tools Use MXToolbox DKIM Lookup or Google Admin Toolbox Enter your full DKIM record (e.g., google._domainkey.yourdomain.com) to check validity

If you see dkim=pass, you're all set.

If not, don’t worry, in the next section, I’ll walk you through how to fix common DKIM issues.

Fixing Common DKIM Errors in Google Workspace

Sometimes, even after setting up DKIM, it doesn’t work right away.

Don’t worry, most issues are common and easy to fix once you know what to look for.

Here are some common problems and how to solve them:

❌ Problem 💡 What It Means ✅ How To Fix It
DKIM not verifying You clicked "Start Authentication," but DKIM still shows as inactive Double-check that the TXT record is added correctly in your domain’s DNS. Ensure the value isn’t cut off or missing.
Selector not found The DNS lookup tool can’t find your DKIM record Verify the Host/Name is exactly google._domainkey (or your selector) and it's under the correct domain.
Multiple TXT records More than one DKIM record exists for the same selector Remove extra or incorrect records. Only one valid DKIM TXT record should exist per selector.
DNS changes not showing up You added the record, but lookup tools still show nothing Wait up to 48 hours. DNS updates can be delayed by caching depending on your provider.

Once the issue is fixed, test again using your email headers or MXToolbox DKIM Lookup to confirm everything is working.

Next, I’ll explain how DKIM works together with SPF and DMARC.

DKIM vs SPF vs DMARC: What’s the Difference?

DKIM, SPF, and DMARC are all email authentication methods. 

They work together to protect your domain and improve your email deliverability, but each one does something slightly different.

Here’s a quick breakdown:

Feature DKIM SPF DMARC
Purpose Signs your emails with a digital signature Approves which IPs can send email for your domain Combines DKIM and SPF to tell inboxes what to do if checks fail
Setup DNS TXT record DNS TXT record DNS TXT record
Role Proves the email hasn’t been changed and came from your domain Verifies the sender is allowed to send on your behalf Sets rules (like reject or quarantine) if DKIM or SPF fail

You can copy this table into your internal doc or Notion board, and check things off as you go.

Once all these steps are done, your DKIM setup is complete and your emails are more secure and inbox-ready.

Conclusion: Is DKIM Worth Setting Up in Google Workspace?

If you’ve made it this far, you already know the answer: yes — DKIM is absolutely worth setting up.

It’s a small step that makes a big difference. When DKIM is active:

  • Your emails look trusted and professional
  • You avoid spam folders and "via" warnings
  • Your domain is protected from spoofing
  • And your deliverability improves across the board

If you're only managing one or two inboxes, setting DKIM up manually works fine.

But if you're running outreach across multiple domains or inboxes, it becomes a lot to handle.

That’s where PrimeForge helps.

It handles the inbox creation, DNS setup, and DKIM/SPF/DMARC configuration for you  automatically.

So you can focus on sending emails, not fixing them.

Ready to scale outreach without the technical mess?

Check out PrimeForge and get your entire email infrastructure set up in minutes, not hours.

Frequently Asked Questions

Q1. Do I need DKIM if I already have SPF?

Yes. SPF and DKIM do different things. SPF checks if the sender's IP is allowed to send on behalf of your domain.

DKIM adds a digital signature to prove the email wasn’t changed and really came from you.

Using both gives better protection and improves deliverability.

Q2. How long does it take for DKIM to start working?

Once you add the TXT record and turn on authentication in Google Admin, it can take anywhere from a few minutes to 48 hours for DNS changes to fully update.

If it’s not working right away, give it some time and check again later.

Q3. Does Google Workspace enable DKIM by default?

No. You have to manually generate the DKIM record in the Admin Console and add it to your domain's DNS.

Then you need to go back and click “Start Authentication.” Until then, DKIM won’t be active.

Q4. What’s the best way to scale the DKIM setup for multiple inboxes?

If you're managing lots of inboxes or domains, doing it manually isn't practical.

The best option is to use a tool like PrimeForge.

It automatically sets up DKIM, SPF, and DMARC, creates inboxes, and tracks everything in one dashboard — no technical work needed.