Deliverability

How to Recover a Bad Domain Reputation with Gmail: A Six-Week Timeline and Checklist

By Artem KukharenkoPublished Updated 9 min read

Updated 1 November 2026.

an envelope climbing a six-step staircase from grey to lavender to mint
Original editorial diagram of the article’s subject; illustrations are conceptual rather than measured results.

What "bad domain reputation" means now

Postmaster Tools v2 keeps the Spam rate, Authentication, Encryption, Delivery errors and Feedback loop dashboards, adds Compliance status, and retires the Domain and IP Reputation dashboards (Google says a new Reputation dashboard replaces them). Until that arrives in your account, reputation is what you can infer from four signals:

Scroll for more → On small screens, choose cards for wide tables.

Signal Where What "bad" looks like
User-reported spam rate Postmaster, daily At or above 0.3% on any day in the last two weeks, or a sustained rate above 0.1%
Compliance status Postmaster v2 Any requirement failing: SPF/DKIM/DMARC alignment, one-click unsubscribe, spam rate
Delivery errors Postmaster; your ESP's bounce logs Temporary 4.7.x codes naming a requirement; 5.7.26 permanent rejections
Placement Seed tests; engagement by Gmail recipients Mail from your domain landing in spam for engaged recipients, not only for cold ones

If placement is poor but all four signals are clean, the problem is more likely content, a shared IP incident or a specific recipient organization's filtering; the going-to-spam diagnostic covers that triage.

Before week 1: find the cause, or you will repeat it

Reputation does not decay for no reason. Pull your sends for the last 30 days and look for the one that spiked complaints or bounces. The usual suspects: a send to a segment untouched for months; a purchased or partner list; a "transactional" template used for promotion without unsubscribe headers; a new subdomain or ESP that went out unauthenticated; a sudden volume jump. Write the cause down. The recovery plan below assumes you have removed it.

The six-week plan

Week 1: stop the bleeding, fix authentication

  1. Pause marketing and promotional sends. Keep transactional mail (receipts, password resets, order updates) flowing; it is low-risk and keeps positive engagement coming in.
  2. Suppress the segment that caused the spike. Not "pause": suppress, with a note of why, so it cannot be re-queued from another system.
  3. Confirm SPF, DKIM and DMARC pass and align on every stream, including automations, support tools and any subdomain. Send a test to a personal Gmail address and read "Show original": spf=pass, dkim=pass, dmarc=pass, with your domain next to them. Fix any 4.7.27 (SPF), 4.7.30 (DKIM), 4.7.31 (DMARC), 4.7.32 (alignment) or 4.7.23 (PTR) condition before sending anything else.
  4. Confirm one-click unsubscribe headers (List-Unsubscribe and List-Unsubscribe-Post) on every marketing template and a visible unsubscribe link in the body.
  5. Register or re-check Postmaster Tools v2 (domain verified, Compliance status visible), Microsoft SNDS and JMRP, and Yahoo's Complaint Feedback Loop. You need all three feeds for the next five weeks.

Want the week-1 checks done for you? The Data & Deliverability Audit covers authentication and alignment on every stream, unsubscribe headers, spam-rate exposure by segment and which list segments drove the damage. Request the audit →

Week 2: engaged recipients only, steady volume

  1. Build a "core" segment: recipients who clicked, replied or purchased in the last 30 days (extend to 60 if that is fewer than a few hundred people). Opens are not a qualifier; Apple Mail's privacy proxy records opens no person made.
  2. Resume marketing sends to the core only, at your normal cadence, with the same From name and domain. Do not change the sending domain; Google applies an accelerated enforcement timetable to domains without history, and a new domain starts with none.
  3. Send steady volume. Spikes and gaps both look like a changed sender. If you usually send daily, send daily, to fewer people.
  4. Watch three numbers every morning: yesterday's spam rate in Postmaster, bounces and complaints per send in the ESP, and the delivery-error share. Record them in a sheet. The seven-day counter starts on the first day the spam rate reads below 0.3%.

Week 3: the seven-day rule and the first expansion

  1. When the spam rate has stayed below 0.3% for seven consecutive days, you are eligible for mitigation again. Keep going; eligibility is not recovery.
  2. Expand the audience to recipients engaged in the last 90 days, in steps of no more than 20–25% of the current volume every two or three days. If any step produces complaints at or above 0.1% or hard bounces above 1%, roll back to the previous step for a week.
  3. Keep the suppressed segment suppressed. If it has real consent and past engagement, it is a separate reactivation project with its own stop conditions, not part of recovery.

Week 4: compliance clean, placement improving

  1. Compliance status should now show every requirement passing. If one still fails, nothing else you do matters until it passes; the Postmaster v2 guide explains each row.
  2. Run a seed test to a handful of Gmail, Outlook and Yahoo mailboxes you control, with a normal campaign. Note where it lands. Placement typically improves before any dashboard looks fully normal.
  3. Expand to recipients engaged in the last 180 days, same step size, same rollback rule.

Week 5: rebuild to normal audience, keep the gates

  1. Reach your normal engaged audience (the sunset-policy window for your cadence). Anyone outside it stays excluded from regular sends; that exclusion is permanent policy from now on, not a recovery measure.
  2. Put the daily checks on a weekly schedule, and set an alert for any day above 0.1% spam rate.

Week 6: decide what to do with the segment that started it

  1. If the suppressed segment had documented consent and some past engagement, treat it as a dormant list: eligibility checks, a scan, a 1/30 daily stream and written stop conditions, as in the reactivation playbook. If it was purchased or has no consent evidence, delete it from sending systems and keep a hashed suppression list so it cannot come back.
  2. Write up the incident: cause, date, numbers, what changed. The next person to touch the list will need it.
The six-week planWeek 1: stop the bleeding, fix authenticationWeek 2: engaged recipients only, steady volumeWeek 3: the seven-day rule and the first expansionWeek 4: compliance clean, placement improvingWeek 5: rebuild to normal audience, keep the gatesWeek 6: decide what to do with the segment that started it
The six-week plan. Read the full qualifications and dated sources in the accompanying table.

What not to do (each one restarts the clock)

Scroll for more → On small screens, choose cards for wide tables.

Tempting move Why it hurts
Switch to a new domain or subdomain "with a clean slate" No history means Google's accelerated enforcement timetable; your worst traffic now runs on a domain with zero trust. A subdomain of your main domain can isolate risk for a new stream, but it is not an escape from the main domain's spam rate
Switch ESPs mid-recovery Loses the data that tells you what went wrong; reputation at Google is per domain, so it follows you anyway
Remove or loosen DMARC Google lists a missing DMARC record under "delivery support or mitigations unavailable"
Send more to engaged users to "dilute" the rate Volume changes are themselves a signal; the rate is per day and per domain, and a spike of unusual volume reads as a changed sender
Re-import an old export to replace "bad" segments Brings back suppressed addresses, traps and complainers
Buy a "reputation repair" service that promises a date Nobody outside Google can change Google's rate; what such services do, when they work, is weeks 1–5 above

How long does it take?

Google documents the rules, not the durations: the spam rate is calculated daily, mitigation eligibility returns after seven consecutive days below 0.3%, and enforcement is progressive. From practitioner reports, changes become visible in Postmaster after about 5–10 days, placement for engaged recipients improves within two to three weeks of clean sending, and a program that was heavily damaged takes the full six weeks to reach normal volume. The variable you control is whether the cause is really gone.

FAQ

How do I check my Gmail domain reputation now that the dashboard is gone? Read the Spam rate, Compliance status and Delivery errors dashboards in Postmaster Tools v2 together, and seed-test placement. Google says a new Reputation dashboard replaces the retired ones; until it is in your account, those three signals are the measure.

What spam rate counts as "bad"? Any day at or above 0.3% ends mitigation eligibility until seven consecutive days below. Sustained rates above 0.1% are the warning zone. Healthy lists measure under 0.01%.

Should I stop sending completely? Stop marketing sends for a week; keep transactional mail. Then resume to engaged recipients only. A total stop for weeks leaves Google with no new evidence that your mail is wanted.

Will a new domain fix it faster? No. New domains face Google's accelerated enforcement timetable, and the behavior that caused the problem moves with you. Fix the list and the authentication on the domain you have.

Does Postmaster Tools show Outlook or Yahoo reputation? No. Use Microsoft SNDS (filter result and complaint rate per IP) and JMRP, and Yahoo's Complaint Feedback Loop. The sender-requirements tracker lists what each provider requires.

Can a dormant list be mailed again after recovery? Yes, as a separate project with eligibility checks, a scan, daily micro-cohorts and stop conditions, which is what the reactivation playbook describes. Never as a single send.

Sending at volume and need the daily monitoring done for you? Managed Mailing Ops runs sending infrastructure, pacing and reputation monitoring as an ongoing service. Talk to us →

Sources

Cite this page

How to Recover a Bad Domain Reputation with Gmail: A Six-Week Timeline and Checklist. Artem Kukharenko. EngageMKTG. 2026-11-02. https://engagemktg.com/knowledge/recover-domain-reputation-gmail

Related articles