Google Postmaster Tools is not telling you what you expected

Postmaster Tools reports one thing no external check can: how Gmail users treat your mail. It covers personal @gmail.com recipients only, updates roughly daily rather than live, and hides data entirely when your volume is low. It will not tell you why a message was filtered, or anything about Yahoo, Outlook or Workspace inboxes.

Most people arrive at this dashboard with one of three problems. Each has a cause worth understanding before you change anything.

“No data to display at present”

An empty dashboard is the normal state for most domains, and almost never a sign that something is broken. Four causes, in the order worth checking.

Your volume is below the threshold

Google withholds data deliberately. Its documentation says dashboards might not include all data on days when your outgoing email volume is low, and that this is to protect the privacy of Gmail users — with too few messages, a rate would identify individual recipients.

Google publishes no number for this. Not a daily minimum, not a per-dashboard one. Anyone quoting you a specific figure is repeating folklore. What is documented is that the bulk sender requirements apply from 5,000 messages a day to personal Gmail accounts — that is the compliance threshold, not the reporting one, and the two are frequently confused.

The practical consequence: if you send hundreds of messages a day to Gmail, expect sparse charts or none at all, permanently. That is not a misconfiguration to chase. Check that your setup is right, then stop looking at it daily.

You added the wrong domain

This is the one people miss. Google says to add either the DKIM d= domain or the SPF Return-Path domain — not your website, and not necessarily the domain in your From: header. If your ESP signs with mail.example.com or its own subdomain, that is the only entry that will ever show data. A verified domain that never sends is a verified domain that reports nothing forever.

Add every domain and subdomain you actually send from. Reporting is per domain, so a marketing subdomain and a transactional one are separate entries with separate reputations — which is exactly why splitting your streams is worth doing.

Verification never completed

Adding a domain at postmaster.google.com is not verifying it. Google gives you a TXT or CNAME record to publish at your DNS provider, and you have to come back and press Verify. Google says verification is usually immediate but the status can take up to 10 minutes to update. Until it is verified, no dashboard populates at all.

You are looking too early

Dashboard data is not real time. Google states that data is typically updated within 24 hours, but can take longer. A send from this morning is not missing; it has not been processed yet.

Do this: confirm the domain you added matches your DKIM d= or Return-Path — the SPF, DKIM and DMARC checker shows you both — re-check the verification record, then leave it a week before concluding anything.

Domain reputation is “Low” or “Bad”

Google defines four bands, and the wording matters more than the labels do. All four are descriptions of a history, not of today:

• High — history of very low spam rates, and complies with Gmail’s sender guidelines.
• Medium — history of sending legitimate email, but occasionally sends spam.
• Low — history of sending a significant volume of spam regularly.
• Bad — history of sending a high volume of spam regularly.

IP reputation uses the same four bands. If you send through a shared pool at an ESP your IP reputation is largely other people’s behaviour; your domain reputation is yours. When the two disagree, the domain figure is the one that reflects what you did.

Why one bad campaign stays visible for weeks

Because the band is a verdict on a run of days, not on the last one. A single send to a stale or bought list puts spam-marked days into the history, and a clean send the following week does not erase them — it only starts diluting them. The charts are per-day series, so those spikes stay on screen for as long as the date range covers them.

How long recovery takes is not published. Google gives no figure for how many clean days move a band, and any recovery timeline you have read elsewhere is an estimate. The one number Google does publish is adjacent: bulk senders become eligible for mitigation when their spam rate stays below 0.3% for seven consecutive days, and only if they also meet the rest of the sender requirements, one-click unsubscribe included. Treat seven clean days as the floor, not the finish.

Check the Delivery Errors dashboard alongside reputation — it reports the percent of authenticated mail that was rejected or temporarily failed, and a spike there usually arrives before or with a reputation drop. If it is filling with rate limits, that is 4.7.28, and it means Gmail is already throttling you.

Do this: find the send that started it, suppress everyone who complained or never engaged on it, and hold your volume steady rather than trying to mail your way back. Sending more into a Low reputation deepens it.

Spam rate above 0.3%

Google’s guidelines say to keep spam rates reported in Postmaster Tools below 0.3%, and to aim below 0.10% while never reaching 0.30%. At 0.3%, three complaints per thousand is enough — on a list of 50,000 that is 150 people pressing Report spam.

It is a Gmail-only, user-reported number

Two limits on what this figure means. First, Postmaster data applies only to messages sent to personal Gmail accounts — addresses ending in @gmail.com or @googlemail.com. Mail to Workspace recipients, Yahoo, Outlook or anyone else is not in it. Your real complaint rate across all your recipients is a different number that nobody publishes.

Second, it is not a filtering rate. Google defines it as the percent of your messages delivered to engaged recipients’ inboxes that were then marked as spam by the recipient. It counts humans pressing a button. It says nothing about how much of your mail Gmail filtered on its own — a dashboard reading 0.0% is compatible with most of your mail going to the spam folder unread.

That denominator has an awkward consequence. Because it counts mail that reached the inbox, worsening placement shrinks it, and the rate can climb while the raw number of complaints holds flat.

Nothing outside Google can see this

Of everything Gmail and Yahoo require from bulk senders, the complaint rate is the single requirement that cannot be checked from outside. It is measured inside Gmail and published nowhere: no DNS lookup reveals it, no header carries it. Any tool claiming to check your spam rate is estimating from something else. The compliance checker on this site reports it as uncheckable and sends you here, because that is the honest answer.

What to do first

Start with the Authentication dashboard, because it settles the question of whether this is a technical problem at all. It shows the percent of your mail passing SPF, DKIM and DMARC across everything sending as you — including the system nobody remembered. If it reads 100%, your DNS is not the cause and no further authentication work will move the spam rate. If it reads 94%, find the sender behind the gap first; unauthenticated bulk mail gets rejected outright anyway.

Once authentication passes, the rate moves on list hygiene and nothing else:

• Make unsubscribing trivial. Someone who cannot find the unsubscribe presses the spam button instead. That is the direct link to one-click unsubscribe — and if those headers are not DKIM-signed, receivers ignore them and your recipients never see the button you believe you provided.
• Stop mailing people who never open. An unengaged list raises the rate from both ends: more complaints, and worse placement shrinking the denominator.
• Clean the list properly. Suppress every complaint immediately, and suppress on the right bounces — the hard/soft split is not the rule people think it is.
• Separate your streams. Transactional mail sharing a domain with marketing inherits marketing’s complaint rate. Receipts and password resets are the mail you least want filtered.

Do this: identify the campaign the spike belongs to, suppress its complainers and its non-openers, and send nothing to that segment again. Then hold below 0.3% for at least seven consecutive days before you judge whether it worked.

Yahoo and the others

Yahoo publishes no equivalent dashboard. What it offers is a Complaint Feedback Loop: register, and Yahoo forwards you a copy of each message a recipient marks as spam. That is per-complaint rather than a rate, and it is more actionable — you get the actual message and the actual address, which you should suppress the same day. Microsoft runs a comparable programme through Smart Network Data Services, keyed to sending IPs rather than domains, so it is useful mainly if you send from your own infrastructure.

Between them, these cover the half of the picture a domain check cannot reach. For the other half — the records, the policy and the headers — run the compliance checker and fix what it reports before you spend another week reading graphs.