If you're using Google Workspace and haven’t set up your SPF record yet, you’re leaving your domain wide open to spoofing, which means anyone could fake emails using your domain.
That’s a serious risk for your brand reputation and your customers.
The fix? Add an SPF record that tells inboxes which servers are allowed to send your emails.
In this guide, I’ll walk you through how to set up your SPF record for Google Workspace — step-by-step, without needing to be technical.
In this guide, I’ll show you exactly how to:
No fluff. Just a clear setup guide to help you send emails without worrying about spam filters.
Let’s get started.
An SPF record is a small rule you add to your domain. It tells email services, like Gmail, Outlook, or Yahoo, that Google Workspace is allowed to send emails for you.
If you don’t have this rule, your emails might look suspicious.
Even if they’re real, they can end up in spam or not get delivered at all.
Here’s why it matters:
For anyone using Google Workspace, adding the Google Workspace SPF record is a must.
It’s one of the first things you should do to avoid email problems.
And don’t worry — it’s not hard.
In the next part, I’ll walk you through how to set it up, step by step.
If you’re using Google Workspace for email, here’s the SPF record you need to add to your domain:
v=spf1 include:_spf.google.com ~all
This is the standard setup Google recommends. Let’s break it down so it’s easy to understand:
So, this one line basically tells email providers:
“Yes, I send emails using Google Workspace. Please allow them.”
📝 Note: This SPF record only covers Google services like Gmail.
If you also send emails through tools like Mailchimp, SendGrid, or another CRM, you’ll need to add them to the same SPF record (not create a second one).
Having multiple SPF records can cause failures, so it’s important to combine them correctly.
We’ll talk more about that later in the guide.
For now, let’s add this SPF TXT record to your domain so Google Workspace is properly authorized.
Adding an SPF record to your domain might sound like a “techie” task, but don’t worry. You don’t need to code or be an expert.
If you’re using Google Workspace to send emails from your domain (like you@yourcompany.com), this step makes sure email providers know those emails are real, and not spam.
Let me walk you through it in plain, simple steps.
Go to the website where you bought your domain — this could be:
Log in to your account and go to the settings for the domain you're using with Google Workspace.
Find the section that says something like:
This is where you control things like TXT records, which is where SPF lives.
Now you’ll create the SPF record.
Here’s what to enter (don’t worry, it’s just a copy-paste job):
Value:
v=spf1 include:_spf.google.com ~all
💡 This tells email services that Google is allowed to send emails using your domain.
Once you’ve added everything, click Save or Update.
Now your changes need to spread across the internet, which can take anywhere from a few minutes to 48 hours.
That’s it. You’ve set up your Google Workspace SPF record.
By doing this, you’ve:
If you also use tools like Mailchimp, SendGrid, or CRMs to send email, don’t worry, I’ll explain how to add them later without breaking your SPF setup.
Not sure what your SPF record should look like?
You can generate it for free using a simple tool:
👉 Free SPF Record Generator by Salesforge
Just choose Google Workspace (and any other tools you send emails from), and it will build the correct SPF record for you.
Copy that, you’ll need it in the next step.
Up next: let’s check if your SPF record is working.
After you’ve added the Google Workspace SPF record to your domain, it’s important to test if it’s working properly.
If your SPF record isn’t set up correctly, email services might still treat your messages as suspicious, even if you’ve done everything else right.
Luckily, there are free tools that let you check your SPF record in seconds.
Here are three simple tools you can use, even if you're not technical.
Salesforge SPF checker is one of the easiest tools to use. If you’re just starting out or want something quick and simple, this is the best place to begin.
How to use it:
What it shows:
If your SPF is good, it will say something like “SPF is valid” or “SPF record found”.
If something’s wrong, it’ll show a clear message — like "No SPF found" or "Syntax error."
You can then go back and fix your record.
✅ Why use this tool: It's super clean, fast, and doesn't overload you with technical stuff.
Pricing: Free:- Which includes creating and validating SPF records, identifying syntax errors, and optimizing email deliverability.
MXToolbox SPF Tool is a bit more detailed. If you want to go deeper and really understand what’s going on with your SPF setup, MXToolbox is a great option.
How to use it:
What it shows:
✅ Why use this tool: It helps you catch deeper issues. Great if you're sending emails from more than just Google (like Mailchimp, SendGrid, etc.).
Pricing:
Google Admin Toolbox is made by Google, so it’s perfect if you're using Google Workspace.
How to use it:
What it shows:
✅ Why use this tool: It's directly from Google and checks your full email authentication setup, not just SPF.
It helps you spot issues that affect how Gmail and other services treat your domain.
Pricing: Free:- Includes check MX, SPF, DKIM, and DMARC records; ideal for Google Workspace users.
No matter which tool you use, here’s what you want to see:
Here’s a simple table of the most common issues people run into while setting up their Google Workspace SPF record, along with clear explanations and fixes:
If you're managing multiple domains or email inboxes, doing this over and over can become a headache.
That’s where Primeforge.ai can help.
If you’re handling multiple domains, inboxes, or running outbound email at scale, Primeforge makes things easier.
It automates the entire email infrastructure setup — including SPF, DKIM, DMARC, and inbox warmup — so you don’t have to do it manually every time.
Whether you're scaling outreach across Gmail or Outlook, Primeforge works on both.
💡 No need to touch DNS settings or worry about what goes wrong — Primeforge handles it all in the background.
Perfect for teams, agencies, or founders who just want their emails to land in inboxes without managing the setup manually.
Pricing: Starts at $45 per mailbox per month; pricing may vary based on usage and features.
Once you’ve set up your Google Workspace SPF record, it’s easy to forget about it.
But email systems keep evolving — and so do the tools you use to send emails.
That’s why it’s good to follow a few best practices to keep your setup clean and reliable.
Here’s what you should always keep in mind:
You should never have two separate SPF records in your DNS.
If you do, email services will ignore both, and your emails could get flagged or blocked.
Do this instead:
Always combine all senders into one single SPF record.
If you send emails through services like Mailchimp, SendGrid, Postmark, or any CRM, you’ll need to include them in your existing SPF record.
Example:
makefile
CopyEdit
v=spf1 include:_spf.google.com include:sendgrid.net include:mailchimp.com ~all
Tip: Use the Salesforge SPF Generator to safely combine services without mistakes.
At the end of every SPF record, you’ll see something like ~all or -all.
If you’re not sure, stick with ~all for safety.
Every few months, check your SPF record to make sure:
Use tools like MXToolbox or Google Admin Toolbox to review your current setup.
Following these best practices will help keep your domain trusted, your emails deliverable, and your Google Workspace setup running smoothly.
Before you move on, here’s a quick checklist to make sure your Google Workspace SPF record is set up correctly.
You can use this as a final review to avoid small mistakes that lead to big email problems.
If you’ve checked everything on this list, your SPF setup for Google Workspace is solid, and your emails should land in inboxes, not spam.
Setting up your Google Workspace SPF record is a small but powerful step.
It helps email providers trust your domain, keeps your emails out of spam, and protects you from spoofing.
In this guide, you’ve seen how to:
It’s a one-time setup that pays off every time you hit send.
💡 If you're managing multiple domains or want to skip manual setup, tools like Primeforge can help you automate everything — from SPF to warmup — without the hassle.
Yes. Even if you’re only using Gmail through Google Workspace, you still need to add an SPF record to your domain’s DNS settings.
It helps inboxes trust your emails and reduces spam risk.
Use this exact record:
v=spf1 include:_spf.google.com ~all
It tells other email services that Google is allowed to send emails for your domain.
If you're not sure how to create or modify this, the Salesforge SPF Generator can help you build one quickly, even if you’re new to DNS setup.
Changes can take anywhere from a few minutes to 48 hours to fully propagate, depending on your domain provider.
No. Only one SPF record is allowed per domain. If you're using multiple services (like Google, Mailchimp, or CRMs), you’ll need to combine them into a single SPF line.
Doing this manually for each one can get messy.
If you’re managing a large email setup or running cold outreach, a tool like Primeforge can handle SPF, DKIM, DMARC, and inbox warmup automatically, so you don’t have to do it one domain at a time.