{"id":1629,"date":"2026-08-23T09:15:52","date_gmt":"2026-08-23T09:15:52","guid":{"rendered":"https:\/\/e-warmup.com\/blog\/?p=1629"},"modified":"2026-08-23T09:28:51","modified_gmt":"2026-08-23T09:28:51","slug":"google-postmaster-tools-v2-after-v1-retired","status":"publish","type":"post","link":"https:\/\/e-warmup.com\/blog\/google-postmaster-tools-v2-after-v1-retired\/","title":{"rendered":"Google Postmaster Tools V2: Reading the New Verdicts After V1 Retired (2026)"},"content":{"rendered":"\n

There was a time when checking Google Postmaster Tools meant one thing. Pull up the Domain Reputation graph, hope it said High, move on with your day.<\/p>\n\n\n\n

That graph is gone now. If you logged in recently and the reputation panel wasn’t where you left it, you’re not missing a setting. Google removed it.<\/p>\n\n\n\n

Google Postmaster Tools v2 replaced the old reputation scores with something more specific. A Compliance Status page built from eleven checks. A Deliverability Analysis verdict that grades whether Gmail users actually want your mail.<\/p>\n\n\n\n

This post covers what changed, what the new schema actually contains, and what to check first if you’re staring at a verdict you don’t recognize.<\/p>\n\n\n\n

What Is Google Postmaster Tools V2?<\/strong><\/h2>\n\n\n\n

Google Postmaster Tools v2 is Google’s current dashboard and API for monitoring how Gmail treats your sending domain.<\/p>\n\n\n\n

It replaced the original interface in stages between 2024 and 2026. The old Domain Reputation and IP Reputation scores gave way to a Compliance Status page and a Deliverability Analysis verdict.<\/p>\n\n\n\n

It’s still free. You still verify ownership with a DNS TXT record on your root domain. What changed is what the tool tells you once you’re in, and how granular that data now is.<\/p>\n\n\n\n

One practical detail worth flagging early: if you built a monitoring script that pulls from the Postmaster Tools API<\/a>, and it’s still hitting v1 endpoints like trafficStats, it has been returning empty responses since October 31, 2025.<\/p>\n\n\n\n

That’s not a bug on your end. Google shut the door on v1 for good.<\/p>\n\n\n\n

What Changed: The v1 to v2 Timeline<\/strong><\/h2>\n\n\n\n

The shift happened in stages, not all at once, which is part of why so many senders missed it.<\/p>\n\n\n\n

Date<\/strong><\/td>What happened<\/strong><\/td><\/tr>
2024<\/td>Postmaster Tools v2 launches alongside v1, introducing the Compliance Status page<\/td><\/tr>
September 30, 2025<\/td>v1 dashboard officially retired, all users redirected to v2<\/td><\/tr>
October 31, 2025<\/td>v1 API decommissioned, old integrations stop returning data<\/td><\/tr>
February 3, 2026<\/td>v2 API reaches general availability with batch queries and compliance endpoints<\/td><\/tr>
June 2026<\/td>Deliverability status verdict added to Compliance Status<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

If your reporting stack has been showing flat zeros since late 2025, this timeline is probably why.<\/p>\n\n\n\n

According to Google’s own migration guide<\/a>, the fix is replacing the old trafficStats resource with domainStats. Switch any get or list calls to the single domainStats.query method.<\/p>\n\n\n\n

What Happened to Domain Reputation and IP Reputation?<\/strong><\/h2>\n\n\n\n

The Domain Reputation and IP Reputation dashboards were retired along with v1.<\/p>\n\n\n\n

The High, Medium, Low, and Bad labels they used to show don’t exist anymore, not as a UI panel and not as an API field.<\/p>\n\n\n\n

Google’s stated reasoning was that static reputation labels were being routinely misread and tended to lag actual sending behavior. A domain could sit on “High” for weeks after engagement had already started slipping.<\/p>\n\n\n\n

Eleven specific compliance checks and a separate engagement-based verdict took their place. That’s a real shift in how you’re supposed to read the data, not just a redesign.<\/p>\n\n\n\n

What the Compliance Status Dashboard Actually Tracks<\/strong><\/h2>\n\n\n\n

This is the part most write-ups get wrong. Compliance Status isn’t a handful of metrics like spam rate and encryption sitting side by side.<\/p>\n\n\n\n

It’s eleven distinct requirements. Google’s API reference<\/a> grades each one as simply compliant or needing work.<\/p>\n\n\n\n

Requirement<\/strong><\/td>What it checks<\/strong><\/td><\/tr>
SPF<\/td>SPF is configured correctly<\/td><\/tr>
DKIM<\/td>DKIM is configured correctly<\/td><\/tr>
SPF and DKIM<\/td>Both are properly configured together<\/td><\/tr>
DMARC policy<\/td>A DMARC policy is published<\/td><\/tr>
DMARC alignment<\/td>The From: header aligns with DKIM or SPF<\/td><\/tr>
Message formatting<\/td>Messages follow RFC 5322 formatting<\/td><\/tr>
DNS records<\/td>Forward and reverse DNS records exist<\/td><\/tr>
Encryption<\/td>Messages are sent over TLS<\/td><\/tr>
User-reported spam rate<\/td>Spam rate stays under Google’s threshold<\/td><\/tr>
One-click unsubscribe<\/td>Sufficient one-click unsubscribe support<\/td><\/tr>
Honor unsubscribe<\/td>Sender actually honors unsubscribe requests<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

Two of these get extra detail when something fails. A missing or broken one-click unsubscribe setup shows up with a specific reason, like not supporting it for most messages.<\/p>\n\n\n\n

Ignoring unsubscribe requests entirely gets flagged separately from simply lacking the header. That specificity is new, and it’s a real improvement over guessing which part of your setup Google didn’t like.<\/p>\n\n\n\n

What Is the Deliverability Analysis Verdict?<\/strong><\/h2>\n\n\n\n

Deliverability Analysis is a separate verdict layered on top of Compliance Status. It doesn’t grade your setup.<\/p>\n\n\n\n

It grades whether Gmail users actually want your mail, based on real engagement rather than a configuration checklist.<\/p>\n\n\n\n

The verdict itself is simple: your domain is compliant or it needs work. The part worth reading closely is the reason attached to it.<\/p>\n\n\n\n

Reason<\/strong><\/td>What it means<\/strong><\/td><\/tr>
Message volume low<\/td>Not enough outgoing email to compute a verdict<\/td><\/tr>
SMTP errors high<\/td>Too many messages hitting delivery errors<\/td><\/tr>
Sender not compliant<\/td>Domain fails one or more sender requirements<\/td><\/tr>
Spam rate high<\/td>Spam rate is above 0.1%<\/td><\/tr>
User feedback negative<\/td>Recipients signal they don’t want the mail<\/td><\/tr>
User feedback low<\/td>Recipients aren’t engaging with messages either way<\/td><\/tr>
User feedback positive<\/td>Recipients signal they do want the mail<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

A verdict flagged with message volume low usually isn’t a red flag. It just means Gmail hasn’t seen enough sending activity yet to compute anything meaningful.<\/p>\n\n\n\n

User feedback low is the one worth watching more closely. We’ve seen domains with a clean 0.05% spam rate still land there, because engagement had been quietly sliding for months and nobody was watching it.<\/p>\n\n\n\n

How This Ties Into Bulk Sender Requirements<\/strong><\/h2>\n\n\n\n

If you send 5,000 or more messages a day to Gmail or Yahoo consumer addresses, three things are non-negotiable. Aligned authentication across SPF and DKIM with a DMARC policy in place. A spam complaint rate under 0.3%. A working one-click unsubscribe header on promotional mail.<\/p>\n\n\n\n

Compliance Status checks these directly, but it actually uses a stricter internal bar than the bulk sender ceiling. The spam rate high reason on the Deliverability Analysis verdict triggers above 0.1%, well before you’d approach the 0.3% bulk sender limit.<\/p>\n\n\n\n

Treat 0.1% as your real warning line. Waiting for 0.3% means you’re already in trouble.<\/p>\n\n\n\n

How to Set Up Google Postmaster Tools<\/strong><\/h2>\n\n\n\n
    \n
  1. Sign in at postmaster.google.com<\/strong> using the Google account tied to your sending domain.<\/li>\n\n\n\n
  2. Add your root domain<\/strong>, not a subdomain. Postmaster Tools tracks the root and its subdomains together for most metrics.<\/li>\n\n\n\n
  3. Verify with a DNS TXT record.<\/strong> Google gives you a verification token to publish, and it usually resolves within an hour on managed DNS.<\/li>\n\n\n\n
  4. Wait for volume.<\/strong> Under a few hundred messages a day to Gmail, most panels stay empty, and a low volume verdict is exactly what you’ll see. That’s expected, not a setup error.<\/li>\n\n\n\n
  5. Migrate any existing API integration to v2<\/strong> if you haven’t already, since v1 endpoints return nothing.<\/li>\n<\/ol>\n\n\n\n

    <\/p>\n\n\n\n

    What Google Postmaster Tools Still Won’t Show You<\/strong><\/h2>\n\n\n\n

    Postmaster Tools only sees Gmail. It says nothing about how Outlook, Yahoo, or any other provider is treating your domain.<\/p>\n\n\n\n

    It also won’t tell you if you’ve landed on a blacklist. And its data carries a lag, sometimes a week or more before a real change in sending behavior shows up in the deliverability reason.<\/p>\n\n\n\n

    That’s not a knock on the tool. It’s doing what it’s built to do. It’s just one input, and a Gmail-only one at that.<\/p>\n\n\n\n

    Compliance Is a Checklist. Reputation Is Something You Build Every Day.<\/strong><\/h2>\n\n\n\n

    Here’s the gap. Compliance Status tells you if you passed eleven specific checks. Deliverability Analysis tells you what Gmail users did recently.<\/p>\n\n\n\n

    Neither one tells you what’s happening on Outlook right now, or whether a new blacklist listing just hit your domain an hour ago.<\/p>\n\n\n\n

    Reputation isn’t something you check once a week and move on from. It gets built, or damaged, with every send, across every provider your list actually uses.<\/p>\n\n\n\n

    That’s the layer E-Warmup<\/a> sits in. A real-time sender reputation dashboard tracks your standing continuously instead of waiting for a Gmail report to catch up.<\/p>\n\n\n\n