Google Just Made Postmaster Tools Readable (Here's What the New Verdicts Mean)

I had a piece half-drafted about building a translator for Google Postmaster Tools – something to turn "spam rate: 0.18%" and a compliance grid into a plain sentence a non-technical stakeholder could actually understand. Then I went looking for a screenshot to use as an example and found out Google had already shipped exactly that back in June, without much announcement.

So this post exists instead. If you haven't logged into Postmaster Tools in a few months, the page looks different, and it's worth understanding why before you next pull it up for a client call.

What actually changed

Postmaster Tools has spent the last year in the middle of a real overhaul, not just a coat of paint. Google retired the original interface – the one built around High/Medium/Low domain and IP reputation scores – at the end of 2025. The replacement, Postmaster Tools v2, went generally available in February 2026 with a compliance-focused view: authentication, alignment, unsubscribe handling, spam rate.

Then in early June 2026, Google added something new on top of that: a Deliverability analysis section on the Compliance Status page. Instead of leaving you to read a spam-rate graph and infer what it means for placement, it states a verdict in a single plain-English sentence, adds a short description, and gives a recommended action.

Here's the part worth sitting with for a second: you can pass every SPF, DKIM, and DMARC check and still get a verdict that reads, in effect, "users don't want your email."

That's not a bug in how I'm describing it – it's the actual design. Google split the question in two.

Two separate questions, graded separately

Compliance Status answers "is this configured correctly." Deliverability analysis answers "do people actually want this." Those used to blur together in the old High/Medium/Low score. Now they're graded independently, and – this is the useful part – they don't always agree. A domain can be fully compliant on authentication and still carry a negative deliverability verdict, because recipients are ignoring or complaining about the mail even though it's technically well-formed.

The seven verdicts, in the language Google actually uses

The verdict system is built on a DeliverabilityStatusVerdict enum with seven real states plus a technical REASON_UNSPECIFIED fallback for when Google doesn't have enough signal to say anything at all. Broadly, they sort into three buckets: users want your mail, Google sees no clear signal either way, or users are signaling they don't want it.

Here's what's confirmed and documented so far:

Three more states round out the seven, covering compliance failures, high spam rate, and high delivery errors specifically as deliverability-flavored verdicts rather than just raw metrics – though the exact public wording for each hasn't been independently confirmed across enough live accounts yet to quote with full confidence. If you're seeing one of these in your own dashboard, the description text and recommended action Google shows you directly are the most reliable source in the moment.

The number that changed underneath everyone

Quick check: when someone tells you their spam complaint rate, what threshold are you mentally comparing it against?

If you said 0.3%, that's the number from Gmail and Yahoo's 2024 bulk-sender requirements, and it's genuinely still the compliance ceiling for that program. But it's not the number driving the new deliverability verdict. The spam-rate verdict fires at 0.1% – a domain can look "fine" by the widely-quoted 0.3% figure and still trigger a negative-leaning deliverability read.

Where to actually find this

If you have access to Postmaster Tools for a verified domain, go to the Compliance Status page directly – Deliverability analysis sits as its own section there now, separate from the authentication and unsubscribe checks. A few honest caveats worth flagging before you go looking:

• This is documented as a Developer Preview in Google's own API reference, and rollout has been uneven – not every account or domain sees the plain-language layer yet, even with data flowing into the older metrics.
• Exact wording has varied slightly across accounts as Google iterates on it. Treat the general shape of this post as reliable and your own dashboard's exact phrasing as the final word.
• This only covers Gmail and Google Workspace traffic, same as it always has. It tells you nothing about how Outlook or Yahoo see the same domain – that's still Microsoft SNDS and Yahoo's Sender Hub territory, and none of the three unify into one view.

What I'd actually do with this

1. Stop reporting a single blended "reputation score" to stakeholders if you've been improvising one from the old metrics. Report Compliance Status and Deliverability analysis as two separate lines, the way Google itself now does.
2. If your spam rate sits between 0.1% and 0.3%, don't treat it as "safe" anymore. That's exactly the range the new verdict is designed to catch that the old bulk-sender framing let slide.
3. If you get a USER_FEEDBACK_LOW read, don't panic – but don't ignore it either. Indifference is harder to spot than complaints, and it's a real early warning that a segment has gone stale before the numbers elsewhere show it.
4. Pull this up before your next Gmail-heavy client review, not after a placement problem forces the conversation. It's a genuinely faster way to show "configured correctly" and "actually wanted" as the two different questions they are.
5. If a bounce or rejection message is the thing actually in front of you right now rather than a dashboard read, that's a different diagnosis – our Bounce Message Decoder is built for exactly that.

The bigger pattern here matters more than any single threshold number. Google didn't just add a friendlier label – it formally separated "did you configure this correctly" from "do people actually want this," and made clear the two can disagree. That's the same argument this newsletter keeps making about open rates and authentication checks generally: passing the technical test was never the same thing as being wanted in the inbox. It's just unusually validating to see the platform say so itself.

Stephen Taunt