Google Postmaster Tools: Read Each Dashboard and Fix Gmail Warnings

Google Postmaster Tools shows whether Gmail trusts your sending domain, and the number to protect is user-reported spam: keep it under 0.1% and never let it reach 0.3%. Ignore the dashboards and you will diagnose Gmail placement too late. This guide shows what each dashboard means, which warnings matter first, and what to fix next.

Use it beside your own Gmail tests, not instead of them. If your issue is already visible in Gmail, start with the Gmail spam troubleshooting checklist. If you are starting a sender from zero, follow a controlled Gmail warm-up plan before you scale.

Google’s own references are the source of truth for the interface and sender rules: the Postmaster Tools help pages, the email sender guidelines, and Google’s Feedback Loop documentation. Keep those open when you change DNS or compliance settings.

How do you set up Google Postmaster Tools?

Go to postmaster.google.com, sign in with a Google account, and add your sending domain. Google gives you a DNS TXT record. Add that record at your DNS host, then return to Postmaster Tools and verify the domain.

Start with the organisational domain, such as example.com. If you send from a subdomain, such as mail.example.com, add that too when you need separate visibility.

Postmaster Tools is domain-based. It does not require access to every mailbox. It reports Google’s view of mail received by Gmail users from your authenticated domain.

Empty dashboards are common at first. They usually mean Google does not have enough recent mail from your domain to Gmail users. They can also mean authentication is not passing. Do not treat a blank chart as proof that Gmail sees no problem.

Verify the sending domain

Add the TXT record exactly as Google gives it. DNS changes often appear within minutes, but timing depends on your DNS host and TTL.

After verification, leave the record in place. Removing it can break future access or make ownership harder to prove later.

Add every real sender

Add domains that appear in your visible From address. If sales sends from sales.example.com, newsletters send from news.example.com, and app mail sends from notify.example.com, track those streams separately.

This stops one stream hiding another. A clean product notification stream can mask a poor cold outreach stream when everything is grouped too broadly.

Wait for enough traffic

Postmaster Tools is not a live inbox test. It is an aggregate view of Gmail’s signals. Check it daily during ramp-up, but do not refresh it hourly and make decisions from one point.

For new domains, pair Postmaster Tools with a 28-day warm-up schedule and DNS checks. You need both trend data and technical correctness.

Which dashboards matter first?

Start with dashboards that have clear thresholds or pass/fail signals. Spam rate, authentication, encryption, and delivery errors are usually more actionable than reputation labels.

Use this table as your daily triage view.

The spam thresholds are the most explicit. Google tells senders to keep spam rates below 0.10% and avoid 0.30% or higher. Treat 0.3% as a ceiling, not a target.

Authentication is also non-negotiable. Bulk senders to Gmail need SPF or DKIM, DMARC, valid forward and reverse DNS, and aligned sending practices. Promotional mail also needs easy unsubscribe handling under Google’s current sender rules.

If you want a quick technical baseline before reading the charts, check SPF, DKIM, and DMARC with the free SPF checker, DKIM checker, and DMARC checker.

What does spam rate mean?

The Spam Rate dashboard shows the percentage of your authenticated mail that Gmail users reported as spam. It reflects recipient behaviour, not only DNS setup.

Do not confuse this with spam-folder placement. A message can land in spam without a user reporting it. A message can also reach the inbox and later be marked as spam. Postmaster’s spam rate focuses on user reports.

A low spam rate does not guarantee inbox placement. It means Gmail users are not frequently pressing the spam button on the measured mail.

Below 0.1%

If the spam rate stays below 0.1%, keep your current volume steady. This is not a reason to double sending overnight.

Review the campaigns that generated the clean days. Look at list source, subject lines, offer, sending time, and unsubscribe handling. Repeat the pattern before you increase volume.

Rising toward 0.3%

If spam rate rises toward 0.3%, slow down. Reduce new prospect volume, remove weak segments, and stop any campaign that uses old, scraped, or poorly qualified lists.

Check whether a specific mailbox, subdomain, or offer changed. Most spam-rate jumps have a cause. Common causes include a new list source, misleading subject, sudden volume increase, or poor unsubscribe handling.

At 0.3% or higher

At 0.3% or higher, stop scaling. Pause the campaign that caused the spike, send only to recently engaged recipients, and wait for the trend to stabilise.

Do not try to “send through” a complaint spike. More mail creates more chances for complaints. That can push domain reputation down and make recovery slower.

If you use BobWork Email Warm-up for Gmail or Google Workspace, the shared warm-up network sends low-volume warm-up mail and measures spam landings directly in receiving mailboxes. It should sit below your real outreach volume, not hide bad campaigns.

What do reputation colours mean?

Domain Reputation and IP Reputation use Google’s labels: High, Medium, Low, and Bad. Read them as trend indicators. They do not tell you one exact cause, and they do not replace campaign-level analysis.

Domain reputation follows the sending domain. IP reputation follows the infrastructure sending the mail. With Google Workspace, you usually pay more attention to domain reputation. With SMTP platforms, both domain and IP reputation can matter.

Reputation usually lags your actions. If you fixed a bad campaign today, the chart may not recover tomorrow. Look for direction over several sending days.

High

High is the state to protect. Keep daily sending predictable. Do not add a new cold list, a new sending platform, and a higher daily limit in the same week.

Use High reputation to build a baseline. Record normal spam rate, bounce behaviour, delivery errors, and send volume. That gives you a comparison when something changes.

Medium

Medium is not failure. Many senders sit there during ramp-up or after a campaign change. It does mean you should avoid aggressive scaling.

Find what changed before the drop. Check new mailboxes, new domains, new templates, new links, and new data sources. If only one stream changed, isolate it.

Low

Low means Gmail trust is weak. Reduce cold volume and focus on mail recipients expect. Remove unengaged contacts from campaigns until the trend improves.

Check your DNS records. SPF should authorise the sender. DKIM should pass and align with the domain. DMARC should exist. For bulk sending, DMARC can start at p=none, but it must be present.

Bad

Bad means you need restraint. Stop risky outbound. Keep necessary transactional mail clean, authenticated, and expected. Do not rotate domains to dodge the problem; that usually spreads poor practices.

If the bad rating followed a new tool or SMTP route, move back to the last known-good configuration. Then reintroduce changes one at a time.

For more context on what warm-up can and cannot change, read Does email warm-up work?. Reputation recovery still depends on wanted mail.

Are authentication and TLS passing?

The Authentication dashboard shows whether Gmail sees your mail passing SPF, DKIM, and DMARC. This is the technical floor. Fix it before you analyse copy, timing, or warm-up.

SPF says which servers can send for your domain. DKIM signs the message. DMARC tells receivers what to do when authentication fails and gives you alignment rules.

For Gmail, DKIM matters because Postmaster reporting and sender trust depend on authenticated mail. If DKIM fails for one stream, that stream can pollute your diagnosis.

SPF

Your SPF record lives as a TXT record on the sending domain. It often starts with v=spf1 and includes the services allowed to send.

Common failures include missing include mechanisms, too many DNS lookups, sending from a platform you forgot to add, or having more than one SPF record. There should be one SPF TXT record per hostname.

DKIM

Your DKIM record lives under a selector, such as google._domainkey.example.com for Google Workspace. Other providers use different selectors.

If you changed DNS recently, send a fresh message to a Gmail inbox and inspect the headers. Look for dkim=pass. Then confirm the Postmaster chart returns to normal after Google has enough data.

DMARC

DMARC usually starts at _dmarc.example.com with a TXT record such as v=DMARC1; p=none; rua=mailto:dmarc@example.com. Use a reporting mailbox you actually monitor.

For Gmail bulk sending, a DMARC record is required. Starting at p=none is common while you verify legitimate streams. Move toward a stricter policy only after reports show your real senders pass.

TLS encryption

The Encryption dashboard shows how much mail between your domain and Gmail uses TLS. For modern providers, this should typically be near 100%.

If it is not, identify the sending route. Older SMTP relays, misconfigured servers, or niche tools can still send without proper TLS. For sensitive or customer-facing mail, fix this quickly.

Which delivery errors need action?

The Delivery Errors dashboard shows why Gmail deferred or rejected mail. This chart is where technical and reputation problems become visible.

Errors may relate to rate limits, authentication, policy, spam suspicion, bad DNS, or temporary server issues. Read the exact error text where available. Then match the timing to your sending logs.

Do not treat all errors equally. A short temporary deferral during a volume increase is different from repeated authentication failures across every campaign.

Rate or volume errors

If errors appear after a volume jump, reduce daily sends. Hold the lower volume for several days. Then increase slowly only if spam rate and reputation remain stable.

For cold outreach, a typical safe practice is to keep real outreach around 30–50 emails per mailbox per day. Add mailboxes rather than pushing one mailbox harder.

Authentication errors

If Gmail rejects or defers mail for authentication, stop the affected stream until SPF, DKIM, and DMARC pass. Sending more unauthenticated mail will not build trust.

Check whether the error affects one platform. For example, Google Workspace mail may pass while a CRM or SMTP service fails because it was never added to SPF or DKIM.

Policy errors

Policy errors often point to content, list quality, user complaints, or missing sender requirements. Review Google’s sender guidelines before changing random settings.

For promotional mail, make unsubscribe simple. Do not hide opt-out language. If recipients cannot unsubscribe, they use the spam button.

Feedback Loop patterns

Google’s Feedback Loop is mainly for high-volume senders and email service providers. It works through identifiers in headers, not by showing individual complainers.

If you have it configured, use it to compare campaign streams. A specific identifier may show higher complaint patterns than the rest of your mail. That tells you where to cut first.

Feedback Loop data is not a contact-level suppression file. You do not get a list of Gmail users who complained. Use it for campaign diagnosis, not personal tracking.

If you do not see Feedback Loop data, that is common for smaller senders. Focus on spam rate, reputation, authentication, and delivery errors first.

What should you fix this week?

Do not change ten things at once. Pick the dashboard with the clearest failure, fix that, and wait long enough to see a trend.

Use this checklist during the next sending week.

If a new domain is already struggling, use the new-domain spam guide before you increase volume. New domains need slower ramps, cleaner lists, and fewer simultaneous changes.

When the charts are stable, keep a simple operating rhythm. Check Postmaster Tools daily during ramp-up, twice weekly during normal sending, and immediately after any campaign or infrastructure change.

For warm-up, keep the volume modest during active campaigns. A typical practice is 10–15 warm-up emails per day while real outreach runs. Real outreach should stay controlled, usually around 30–50 per mailbox per day.

BobWork Email Warm-up can keep that background pattern running for Gmail and Google Workspace. It is free for up to 10 mailboxes, starts at 3 emails per day, ramps by 2 per day, and uses a shared warm-up network by default, with a private pool per account if you prefer. Start with the free warm-up tool only after authentication is correct.

What else do senders ask?

How long does Google Postmaster Tools take to show data?

It can show data after Google sees enough authenticated mail from your domain to Gmail users. Low-volume domains may see empty charts. Check again after several sending days, and make sure DKIM is passing.

Is Google Postmaster Tools only for bulk senders?

It is most useful for bulk senders, but smaller senders can still verify a domain. Some dashboards may stay blank if your Gmail volume is too low for Google to report.

What spam rate is safe in Gmail?

Aim to keep user-reported spam below 0.1%. Google says senders should avoid reaching 0.3% or higher. Treat any rise as a reason to reduce volume and fix list quality.

Why is my domain reputation blank?

Blank usually means Google does not have enough recent data to display a reputation level. It can also happen if mail is not authenticated correctly. Check DKIM, SPF, and DMARC first.

Does Postmaster Tools show inbox placement?

No. It shows sender signals, including spam rate, reputation, authentication, encryption, and delivery errors. It does not tell you exactly how many messages reached the inbox, spam folder, or Promotions tab.

Can warm-up fix a bad Postmaster reputation?

Warm-up can help rebuild normal engagement patterns, but it cannot override spam complaints, bad lists, or failed authentication. Fix those causes first, then use a controlled sending ramp.

Do I need separate Postmaster domains for subdomains?

If you send from subdomains, add and verify the domain setup that matches your sending pattern. Google’s reporting can vary by domain and subdomain, so check the current Postmaster documentation for your case.

Frequently asked questions