Google Postmaster Tools in 2026: v2 Dashboards, Compliance Status, and Deliverability Analysis

Google Postmaster Tools is the closest thing to ground truth on how Gmail treats your sending domain. The tool has changed shape in two steps: the redesigned v2 interface replaced the legacy dashboards as the default, the v2 API went generally available in February 2026, and June brought a Deliverability Analysis section that gives you a plain-English verdict on whether Gmail users want your mail. This guide covers what v2 shows today, what disappeared, how to set it up, how to call the API, and how to fix the issues senders hit most often.

Timeline from v1 sunset to Deliverability Analysis

The transition happened in a few checkpoints. Dates below come from Google’s Postmaster Tools API release notes and the Postmaster Tools help center.

What Postmaster Tools v2 shows today

The v2 dashboard consolidates everything into a single Compliance Status page with subsections. Here is what each metric measures and where healthy senders should sit.

The Deliverability Analysis verdicts

The June 2026 update is the most consequential addition since v2 launched. Instead of leaving you to guess what a 0.2 percent spam rate means for placement, Google now states a verdict in plain English, with a recommended action underneath. In the API the field is DeliverabilityStatusVerdict, returned by domains.getComplianceStatus; it carries seven documented reasons plus REASON_UNSPECIFIED (see the Postmaster Tools API documentation).

What was retired and why

The retirement was not cosmetic. Google removed the reputation buckets because they were routinely misinterpreted, and because static labels tend to lag actual sending behavior by weeks.

How to set up Google Postmaster Tools

Setup takes about ten minutes plus DNS propagation.

1. Sign in at postmaster.google.com

Use the Google account that will own the domain. For team access, add other users after verification, either from the interface or via the API.

2. Add your sending domain

Click the plus icon and enter your root domain (example.com, not mail.example.com). Postmaster Tools tracks the root and its subdomains together for most metrics.

3. Verify with the TXT record

Google gives you a verification token to add as a DNS TXT record at the root:

example.com.  IN TXT  "google-site-verification=abc123XYZ..."

Publish and wait for propagation. Verification usually resolves within an hour on managed DNS. Once the record is live, click Verify in the Postmaster Tools UI.

4. Wait for data

Postmaster Tools needs sustained volume before it displays anything. Under a few hundred messages a day to Gmail, most panels stay empty. This is the single most common cause of a no-data state and it is not a bug.

5. Manage users and multi-domain via the API

Since June 2026, the v2 API supports programmatic add, verify, and remove for domains and users. Multi-brand senders and agencies should script this rather than clicking through the UI for each property. See the API section below.

The Postmaster Tools v2 API

API v2 general availability landed on February 3, 2026. It is meant to replace v1 completely, and Google has said the v1 API will be retired now that v2 has launched (release notes).

What changed vs v1

• The v1 base URL and paths are gone. All calls now go through the v2 endpoints under gmailpostmastertools.googleapis.com.
• queryDomainStats replaces the paginated get and list pattern of v1 with flexible querying, including date ranges and specific metric subsets.
• Batch operations let you fetch stats for many domains in one call, which matters for agencies and platforms with many client domains.
• GetDomainComplianceStatus now returns the Deliverability Analysis verdict, the same one shown in the June UI update.
• Domain and user management (add, verify, remove, update permissions) moved from console-only to full API coverage.

Python example: read compliance and deliverability status

from googleapiclient.discovery import build
from google.oauth2 import service_account

SCOPES = ["https://www.googleapis.com/auth/postmaster.readonly"]
creds = service_account.Credentials.from_service_account_file(
    "service-account.json", scopes=SCOPES
)
service = build("gmailpostmastertools", "v2", credentials=creds)

resp = service.domains().getComplianceStatus(
    name="domains/example.com"
).execute()

print("Compliance:", resp.get("complianceStatus"))
print("Deliverability:", resp.get("deliverabilityStatus"))

Migration checklist v1 to v2

• Replace v1 base URL and paths with the v2 equivalents.
• Update auth scopes if you were using the older postmaster scope names.
• Adapt to the new schema: v2 returns typed objects rather than the v1 rows array in many endpoints.
• Switch reputation reads to the new Compliance Status and Deliverability verdict fields; the old reputation buckets no longer exist as returned values.
• Add error handling for REASON_UNSPECIFIED and empty responses on low-volume domains.
• If you built alerting on High to Medium transitions, rebuild it on Deliverability Analysis verdict changes instead.

How Postmaster Tools ties into the bulk sender rules

Since February 2024, senders above 5,000 messages per day to Gmail or Yahoo consumer addresses have had to pass three gates: aligned authentication (SPF and DKIM with DMARC), a spam complaint rate under 0.3 percent, and a working one-click unsubscribe. Postmaster Tools is where Google shows you whether you clear those gates.

• Authentication status confirms SPF and DKIM alignment plus DMARC policy.
• Spam Rate is the exact metric measured against the 0.3 percent alert line.
• Compliance Status calls out failures against the bulk sender requirements directly, including missing List-Unsubscribe headers.

See the list-unsubscribe header setup guide for the one-click implementation, suppression lists for the cleanup side, and the twelve reasons your emails go to spam if you are already over 0.3 percent and need to rank the fixes.

Complementary tools and alternatives

Google Postmaster Tools only sees Gmail traffic. For a full deliverability picture, pair it with the equivalents at the other major receivers.

For the complaint reporting side across all receivers, including ARF parsing and per-provider signup, see the Feedback Loops and ARF guide.

Common issues and how to fix them

No data on every panel

The most common cause is volume below the display threshold. Postmaster Tools needs sustained volume to Gmail (roughly hundreds of messages a day, minimum) before it shows anything. If your warmup schedule is still in early ramp, this is expected. Cross-check your daily volume against target with the warmup calculator.

Verification TXT record is ignored

Check the record is at the root, not on a subdomain. Some DNS panels wrap TXT values in extra quotes, which breaks the match. Wildcards do not cover verification. If your DNS provider is slow to propagate, allow twenty-four hours before troubleshooting further.

Domain ownership lost after admin turnover

Re-verify from any Google account by re-adding the domain and publishing a fresh TXT record. Previous verifications persist but only tied to the original account, so account handoff is worth doing on purpose rather than after the fact.

DKIM d= alignment fails

Your SPF might align while your DKIM d= domain does not match the visible From address. Postmaster Tools flags this under Authentication. The fix is on the sending platform side: use a DKIM key signed with your root domain, not the ESP subdomain, so DMARC alignment passes.

Empty Feedback Loop tab

Google’s Feedback Loop uses the Feedback-ID header. If your ESP does not set one, or sets a static value across all campaigns, the tab stays empty because Google cannot group complaints. See the FBL and ARF guide for the header format and per-campaign strategy.

Deliverability Analysis stuck on MESSAGE_VOLUME_LOW or USER_FEEDBACK_LOW

MESSAGE_VOLUME_LOW means you send too little to personal Gmail accounts; USER_FEEDBACK_LOW means recipients barely interact with your mail. In both cases Gmail does not have enough signal to say either way. Ramp volume gradually and expect the verdict to shift within a few weeks of consistent sending. Adding volume in the form of unengaged recipients will not help; it may push you into a worse verdict.

A ten-minute monthly routine now that v1 is gone

Without the old reputation charts, there is no single line to glance at. This routine covers what v2 gives you and what it no longer keeps for you.

Five common mistakes senders make with Postmaster Tools

The tool is only as useful as how you read it. These five patterns cost more than the metrics themselves.

Frequently asked questions

Where to go next

Postmaster Tools is the closest thing to ground truth on Gmail inbox placement, but it only covers Gmail. For a full picture, pair it with the receiver-side tools at Microsoft and Yahoo and with the complaint reporting side of the FBL hub.

• Feedback Loops (FBL) and ARF: signup, parsing, and suppression
• List-Unsubscribe and one-click headers setup
• Domain reputation vs IP reputation in 2026
• IP warmup schedule that works in 2026
• Cold IP recovery playbook