Why are my emails suddenly going to spam in Gmail?
Matthew Whittaker
Co-founder & CTO, Suped
Published 26 Jul 2025
Updated 19 Jun 2026
23 min read
Summarize with
Updated on 19 Jun 2026: We updated this guide to separate Gmail spam placement from sender score checks, clean authentication, recipient settings, link reputation, and recovery pacing.
Your emails are suddenly going to spam in Gmail because Gmail has started seeing a stronger risk signal than it saw before. The usual causes are a flagged tracking domain or landing page, a shared sending or link domain problem, raw IP URLs or unbranded CDN/S3 asset hosts in the email, visible link text that does not match the actual href, mixed transactional and promotional mail on one reputation stream, a recent SPF, DKIM, or DMARC break, a new sending domain with too little Gmail history, a delayed Postmaster Tools complaint spike on a low-volume Gmail day, weak list quality, a new template, misleading sender identity, a sender or reply-to address that bounces, or an IP or domain reputation event. A good sender score or clean setup does not override Gmail's view of the exact From domain, subdomain, DKIM domain, sending IP, and Gmail audience relationship.
When this happens overnight, do not assume the body copy changed. First look at every domain Gmail can see: the sending domain, return-path domain, DKIM signing domain, link tracking domain, image host, redirect target, and any file or landing page domain in the message. For linked pages, check whether the destination, redirect domain, CDN asset host, file host, or affiliate partner domain has been labeled dangerous or unsafe by Google. Google's dangerous site guide explains that malware, hacked content, phishing, and policy issues can produce warnings that affect links users reach from email. If Gmail is also slow or returning temporary errors, inspect Received timestamps and SMTP responses before changing content. If unrelated senders report Gmail misclassification at the same time, check for a Gmail-side incident before changing DNS.
If your ESP reports delivered while Gmail recipients cannot see the message, treat delivered as SMTP acceptance, not inbox proof. If Gmail mobile or an IMAP client shows the message in Spam while desktop Gmail shows nothing, treat that as a Gmail view mismatch first: hard refresh desktop Gmail, test a private browser window, and search in:anywhere by sender, subject, and Message-ID before changing DNS. Search Spam, Promotions, Updates, All Mail, labels, forwarding destinations, and Google Workspace quarantine before assuming Gmail dropped the message. Promotions and Updates are inbox categories, not spam folders. A campaign that moved from Primary to Promotions is a category issue; a campaign that moved to Spam is a trust and filtering issue. For promotional campaigns, Promotions is often normal Gmail classification. For password resets, receipts, security alerts, and support replies, unexpected tab placement can point to stream separation, template reuse, or shared tracking patterns.
Fast answer
If every Gmail seed starts going to spam at once, check links before rewriting the campaign. A single shared tracking root domain, hosted asset domain, or redirected URL can drag the whole message down even when SPF, DKIM, and DMARC still pass.
- Most likely: A link tracking, hosted asset, or URL reputation issue, especially on a shared ESP domain.
- Also common: A sudden authentication, complaint, engagement, frequency, volume, template, new-domain, display name, unsubscribe, or blocklist (blacklist) signal.
- Best first move: Send controlled variants that remove links, keep the old template as a control, swap tracking, replace raw IP or unbranded asset URLs, verify headers, rule out stale Gmail views, separate Promotions and Updates from Spam, check for Gmail 4xx deferrals, and compare Postmaster Tools dates with Gmail-only send volume.
Why this happens overnight
Gmail filtering is not a fixed pass or fail gate. It evaluates the message, the sender, the recipient relationship, and the domains inside the message at delivery time. That means yesterday's good result does not guarantee today's placement if Gmail updates a reputation signal, sees new complaint behavior, or connects the message to a newly risky link.
The sudden pattern matters. If only one campaign goes to spam, suspect content, links, offer, template, asset host, or audience. If every campaign goes to spam, suspect authentication, sending reputation, tracking domain reputation, or a shared infrastructure issue. If Gmail is the only mailbox provider affected, focus on Gmail-specific reputation, volume, and recipient feedback signals instead of changing everything at once.
A template launch can create the same overnight pattern. New HTML structure, heavier images, a different footer, changed plain-text content, new tracking pixels, raw IP image URLs, a misleading display name, or a different link setup can make the mailstream look less familiar to Gmail even when the sender, ESP, and domain stay the same.
- Tracking domain: Shared tracking roots carry shared risk. One bad actor on the same root can affect many senders.
- URL target: A clean visible link can redirect through a domain Gmail treats as risky.
- Asset host: Unbranded CDN, S3, raw-IP, or generic file hosts can make harmless images look disconnected from the sender.
- Partner or affiliate domain: A partner offer, affiliate path, or short-lived redirect can add reputation risk even when your own domain is clean.
- Template fingerprint: HTML structure, image weight, footer format, and tracking pixels create a pattern Gmail can re-evaluate.
- Volume pattern: A sudden Gmail-specific send after a quiet period, or a low-volume launch from a new domain, can create spam placement, deferrals, or both.
- Authentication: A DNS edit, expired key, or sender routing change can break SPF, DKIM, or DMARC.
- Audience shift: A colder segment, older list, or higher complaint rate can move Gmail's decision quickly.
- Blocklist risk: A domain or IP listing on a blocklist or blacklist can add pressure to Gmail filtering.
Flowchart for diagnosing a sudden Gmail spam placement spike by checking links, authentication, reputation, and resend timing.
There is a reason links come first in the investigation. Gmail sees the message as a package. The From domain has reputation, the IP has reputation, the DKIM signing domain has reputation, and every linked hostname has reputation. Google's sender guidance also tells senders to check linked domains for unsafe status, so a flagged landing page, hosted file, image host, or redirect chain can explain a sudden Gmail spam shift.
The first checks to run
Use a short triage path because random edits make Gmail diagnosis harder. First, prove whether the problem is the message, the sending setup, or the domains inside the message. Send one copy of the exact message to an email tester and inspect the headers, authentication results, link list, image hosts, display name, and visible rendering. Then compare Gmail recipients with non-Gmail recipients from the same send so you know whether the issue is Gmail-specific or mailstream-wide.
Then run a domain health check on the sending domain, tracking domain, and any branded asset host. The point is not to chase one score. The point is to catch the obvious failures before you spend hours rewriting copy.
Do not stop at a good sender score, a clean template score, or SPF, DKIM, and DMARC pass results. Those checks prove parts of the setup, but Gmail still decides placement from Gmail-specific recipient behavior, complaint history, domain and IP reputation, link reputation, volume pattern, and whether the sender path has enough trusted history.
Open Google Postmaster Tools for the affected sending domain or subdomain and compare domain reputation, IP reputation, spam rate, authentication, encryption, delivery errors, and Compliance status against the date the Gmail spam placement began. Treat a spam-rate spike as a lead, not proof of a same-day campaign problem, because user spam reports can lag the send date and low Gmail volume can inflate the rate. If Postmaster data is missing, Gmail lacks enough authenticated volume for that domain, so controlled seed tests and real-recipient reports matter more.
A low bounce rate or low complaint rate does not clear Gmail. Accepted mail can still land in Spam, and complaint rates can look calm when fewer recipients see the message. Compare accepted, deferred, bounced, rejected, and expired counts by Gmail domain before trusting aggregate dashboard numbers.
Email tester
Send a real email to this address. Suped opens the report when the test is ready.
?/43tests passed
Preparing test address...
|
|
|
|---|---|---|
All Gmail spam | Shared link issue | Remove links |
Raw IP or unbranded asset | CDN or hosted-content risk | Brand host |
Mobile Spam, desktop missing | Cached view or filter | Search in:anywhere |
Promotions or Updates only | Gmail tab category | Separate from spam |
Gmail 4xx or 4.7.28 deferrals | Volume, quota, or reputation pressure | Throttle Gmail |
Gmail complaint spike | Cadence, list fatigue, delayed complaint, or low volume | Compare send dates |
No campaign sent | Hidden automation or old mail | Pull automation logs |
Low bounces, low complaints | Accepted but filtered | Compare logs and Spam |
One campaign | Content, offer, or template | Variant test |
New template | HTML or URL pattern | Old-template control |
SPF fail | Sender path | Header result |
DKIM fail | Key or signing | Header result |
DMARC fail | Domain mismatch | Report data |
IP listed | Reputation hit | Blocklist or blacklist check |
Use this table to keep the first pass tight.
Do not treat a low open rate alone as proof of Gmail spam placement. Google Postmaster Tools does not report opens, so Gmail-side complaint rate, deferrals, authentication, domain and IP reputation, seed placement, and recipient reports give a cleaner diagnosis than pixel opens.
If SMTP logs show Gmail sender requirement codes such as 4.7.23, 4.7.27, 4.7.29, 4.7.30, 4.7.31, or 4.7.32, fix the named requirement before testing subject lines or templates.
If you administer Google Workspace, Google's Gmail spam troubleshooting guidance is useful for separating recipient-side filtering, content issues, sender authentication problems, and admin spam bypass settings.
Read Postmaster Tools spam spikes carefully
A Gmail spam spike in Google Postmaster Tools does not always mean the campaign sent on that date caused the problem. A recipient can open an older message and click spam later, so the spike can reflect the complaint date instead of the original send date. On a quiet Gmail day, one or two reports can also create an ugly percentage.
This matters when the team says no email was sent. Usually that means no campaign was sent, while password resets, invoices, onboarding emails, support replies, form notifications, or other automations still used the same domain. It can also mean another approved sender, forgotten integration, or unauthorized source used the visible From domain.
Operational spam-rate modeltext
spam rate = Gmail user spam reports / Gmail mail counted for that day A low denominator makes one complaint look large.
- Map dates: Put the Postmaster Tools spike beside prior campaign dates, quiet-day Gmail volume, automation sends, and any Gmail deferrals.
- Ask for exports: Pull timestamps, recipient domain, campaign or automation ID, sending IP, From domain, return-path domain, DKIM domain, bounces, deferrals, and complaints.
- Use identifiers: If the sender supports Google's Feedback Loop, add a Feedback-ID pattern that separates campaigns, automations, brands, and mail classes.
- Check sources: Use DMARC reports in Suped's product to find senders that do not appear in the ESP dashboard, then separate approved sources from spoofed or misconfigured mail.
Do not overread one quiet day
A single low-volume spike is often a triage note, not a reason to rebuild the program. Repeated spikes, matching Gmail deferrals, reputation drops, blocklist or blacklist changes, or the same automation appearing each time deserve a deeper fix.
Check for a Gmail filtering incident
Sometimes the changed signal is not under the sender's control. A Gmail-wide filtering problem can create mixed symptoms: spam warnings on normal mail, delayed delivery, unexpected Primary or Promotions placement, and reports from unrelated senders at the same time. Treat that pattern differently from a domain-specific reputation failure.
A recent public example was January 24, 2026, when Google reported Gmail classification problems, extra spam warnings, and delivery delays. In that pattern, a clean retest after resolution gives better evidence than changing DNS, copy, and sending infrastructure during the incident window.
- Scope: Compare several unrelated sending domains, business mail, and personal mail before changing DNS or campaign content.
- Timing: Check whether the spam spike began within the same hour as delayed mail, warning banners, or user reports across unrelated Gmail accounts.
- Response: Pause risky tests, keep necessary mail moving, and wait for the incident to clear before judging a new campaign result.
- Retest: After Gmail stabilizes, send the same message again and compare headers, delays, spam placement, and tab placement.
If the problem remains limited to your domain, your campaigns, or your linked domains after that retest, resume the normal link, authentication, and reputation investigation. A real Gmail incident explains broad noise, but it does not clear a sender-specific failure.
Rule out recipient-side Gmail settings
Not every Gmail spam report means domain-wide deliverability failure. If one account, one company, or one Google Workspace tenant reports the problem, compare that report against seed inboxes, other Gmail recipients, and non-Gmail recipients before changing infrastructure. For a single internal recipient, treat the affected mailbox as the first suspect until headers, Google Workspace logs, or repeated reports prove a wider pattern.
Use the exact same message, sender, and time window when comparing an affected recipient with a working Gmail recipient, and keep the original headers before the user moves the message out of Spam. The common one-mailbox causes are Gmail filters, blocked addresses, contact state, prior Not spam training, forwarding, and Workspace policy assignment.
When the same mailbox disagrees across clients, such as Gmail mobile showing Spam while desktop Gmail shows nothing, fix the view before fixing the sender. Hard refresh Gmail web, clear browser cache, disable extensions, open a private window, and search All Mail with the sender, subject, recipient, and Message-ID.
Gmail searches to runtext
from:sender@example.com in:anywhere to:recipient@example.com in:anywhere subject:(welcome) in:anywhere rfc822msgid:<message-id@example.com>
Tabs are a different layer from spam filtering. If the message sits in Promotions or Updates for one recipient, diagnose category placement separately from a spam-folder complaint. Gmail category placement changes by recipient behavior, filters, and account settings; spam placement means Gmail distrusted the message enough to move it out of the inbox.
Forwarding can also change the evidence. If Gmail spam placement appears only after forwarding, inspect whether DKIM survives, whether ARC is present, whether SPF matching breaks at the forwarder, and whether the final Gmail account has filters, quarantine rules, or organization policy in the path.
- Capture the original headers before moving a message out of Spam because the move can change the evidence while retraining Gmail.
- Clear desktop Gmail cache or test a private window when mobile Gmail, Apple Mail, or IMAP shows Spam but desktop Gmail shows nothing.
- Ask recipients to mark the message as Not spam and move it to the inbox when they trust the sender; this gives Gmail a user-level correction signal.
- Ask known recipients to add the sender to contacts when they have an ongoing relationship with the sender.
- Ask affected recipients to check Gmail filters and blocked addresses because a personal rule can keep future messages out of the inbox even after a sender is trusted.
- For a trusted business relationship, a Workspace admin can check quarantine, routing, compliance rules, spam bypass filters, allowlists, and email log search, but suspicious messages can still be rejected or sent to spam.
This does not replace sender-side fixes. It only prevents a single recipient's Gmail settings, filters, tab training, forwarding path, organization policy, or stale client view from being mistaken for a sender reputation incident.
How to isolate a tracking domain problem
The cleanest test is to hold everything still and change one thing at a time. If the same creative goes to spam with tracked links but inboxes when links are removed, the tracking or destination path is part of the problem. If a plain-text version with the same sender also lands in spam, move back to authentication and reputation.
If image-only variants improve when you remove a raw IP, S3 bucket, or generic CDN hostname, treat the asset host like any other linked domain. Use a branded CNAME and readable paths before changing the whole creative.
Shared tracking root
A shared root domain is fast to launch, but other senders can affect its reputation.
- Risk: You inherit reputation signals from unrelated senders.
- Symptom: Many senders see Gmail spam placement at the same time.
- Fix: Ask the provider to swap the flagged root or move you to a branded domain.
Custom tracking domain
A branded tracking domain gives you cleaner ownership, but Gmail still needs time to trust it.
- Risk: A brand-new hostname can look unfamiliar during the first sends.
- Symptom: Placement improves after smaller, steady sends.
- Fix: Introduce the domain with conservative volume and stable audiences.
Do not replace every link, subject line, and segment in the same test. Gmail delivery investigations work better when each version answers one question. A common four-version test uses the original, no links, branded tracking only, and one link to the primary landing page without redirects.
Spam placement response bands
Use seed results as a triage signal, then validate with real recipients and authentication data.
Normal noise
0-5%
A small seed shift with stable engagement rarely justifies major edits.
Investigate
6-25%
A visible Gmail-only shift deserves controlled content and link tests.
Pause and isolate
26%+
A broad Gmail spam spike calls for immediate link, auth, and reputation checks.
If the issue is a shared tracking domain, the practical fix is usually a domain swap by the sending provider or a branded tracking CNAME under your control. After the swap, send smaller batches first. New domains do not need a theatrical warmup, but they do need normal-looking traffic, real engagement, and no sudden blast to a cold segment.
Also inspect the final destination and every redirect hop. A landing page that is unsafe, inaccessible, newly redirected, or different for security crawlers than it is for users can pull a clean-looking email into the spam folder.
Fix Gmail sender requirements
Even if the root cause is a link domain, authentication still needs to be boring and correct. The current Gmail sender guidelines make the foundation explicit: all senders need SPF or DKIM, valid forward and reverse DNS, TLS for mail transport, RFC 5322 formatting, and Gmail-reported spam rates kept under 0.30%, with below 0.10% as the practical target. For Gmail, a bulk sender sends more than 5,000 messages per day to personal Gmail accounts, counted by primary domain, so subdomains do not avoid the requirement. Bulk senders need SPF and DKIM, DMARC, From-domain matching with SPF or DKIM for direct mail, one-click unsubscribe for marketing or subscribed mail, and a clearly visible unsubscribe link in the body. The requirements are active, so missing requirements can show as temporary failures, permanent failures, spam foldering, or loss of mitigation eligibility. For DKIM, use keys of at least 1024 bits for Gmail and 2048 bits where the DNS provider supports it. Passing authentication does not buy inbox placement, but failing it gives Gmail a simple reason to distrust the message. Do not look for a provider allowlist request as the fix; Google does not accept allowlist requests from email providers. Also check that each message has one clear From address, a valid Message-ID, accurate headers, visible sender information, a working reply-to path, a display name that identifies the sender, visible links that match user expectations, no hidden HTML or CSS content, and no invisible link styling. Keep each message type on a consistent From address and do not mix promotions into receipts, account notifications, or other transactional mail. After DNS changes, allow for resolver caching and TTLs before judging the next Gmail result; some changes take hours and stale records can make a fixed setup look broken.
Example DMARC record for monitoringdns
Host: _dmarc.example.com Type: TXT Value: v=DMARC1; p=none; rua=mailto:dmarc-reports@example.com; adkim=s; aspf=s
Start at p=none if you are still collecting data, then move toward stricter policy once legitimate sources pass. Current DMARC records do not need pct=100; full rollout is the default when you are not doing a partial rollout. Use rua for aggregate reports, and use ruf only when you have a clear privacy and processing plan because failure reports are not consistently sent by receivers. Use DMARC monitoring to see which sources pass, which fail, and whether a sudden Gmail issue lines up with a sending source, domain change, or unauthorized source.
What not to overreact to
Do not move straight to a new IP, new domain, or new sending platform because one Gmail seed test got worse. That can create a larger reputation reset. Isolate the signal first, then make the smallest fix that addresses it.
For one-click unsubscribe, check that marketing and subscribed mail includes the List-Unsubscribe and List-Unsubscribe-Post headers, that List-Unsubscribe-Post uses the List-Unsubscribe=One-Click value, and that the unsubscribe link in the message body is easy to find. Use an HTTPS URL for the one-click header flow and honor unsubscribe requests within 48 hours. If Gmail users cannot leave cleanly, complaints become the fallback signal.
Also check blocklist monitoring for the sending IPs, sending domain, and linked domains. Gmail does not outsource its filtering to one blacklist, but listings still show reputation pressure and help explain why filters changed.
Infographic showing Gmail reputation signals across From domain, DKIM domain, return path, tracking links, and landing page.
How Suped fits into the workflow
Suped's product is useful when a Gmail spam spike needs more than a one-off check. Suped brings DMARC, SPF, DKIM, blocklist, blacklist, and deliverability monitoring into one place, then turns failures into specific steps to fix. That matters because sudden Gmail issues usually involve more than one signal.
Issues page showing top issues, verified sources, unverified sources, and authentication pass rates
In Suped, the useful parts for this workflow are verified and unverified source views, policy status, authentication pass rates, blocklist signals, blacklist alerts, and alerts when failures exceed a threshold. Hosted SPF and SPF flattening help keep sender records clean without constant DNS edits. Hosted DMARC and hosted MTA-STS help teams make controlled policy changes without building extra infrastructure.
The practical value is speed. When Gmail starts filtering differently, teams need to know whether the issue began with a new source, broken DKIM key, SPF lookup limit, unverified sender, policy change, or reputation event. Suped gives teams and MSPs one workflow for that investigation, including multi-tenant views when an agency manages many domains.
Preferred workflow
- Confirm: Check whether the issue is Gmail-only, campaign-specific, or domain-wide.
- Isolate: Test links, tracking, authentication, template, and sending source changes separately.
- Fix: Change the smallest broken piece, then resend gradually to engaged Gmail users.
- Monitor: Keep alerts on so the next DNS or reputation change is caught early.
What to change after you find the cause
Once the likely cause is clear, act narrowly. If the tracking root is the issue, replace or brand the tracking domain. If a specific URL, CDN asset host, raw IP, or visible-link mismatch is the issue, remove or fix it until the destination and rendered link path are clean. If DKIM fails, rotate or republish the key. If DMARC fails, identify the legitimate source that is not passing and fix that source before tightening policy.
If a new template launched at the same time, compare it with the previous version before rewriting everything. Keep the same audience and sender setup, then test HTML weight, plain-text fallback, image hosts, footer, unsubscribe link, tracking domain, display name, and redirect path one at a time.
If the sudden change followed a new sending domain or branded tracking hostname, do not assume low volume protects it. Gmail still lacks domain age, engagement history, and complaint history, so warm with recent engaged recipients before broad Gmail sends.
If the evidence shows a move from Primary to Promotions, do not use the spam recovery path. Review the message purpose, stream separation, template content, recipient expectations, and whether the mail is actually commercial. Promotional campaigns often belong in Promotions; transactional mail should stay single-purpose, with no coupon blocks, product recommendations, or broad newsletter framing.
If the problem is engagement, high cadence, or a volume spike, stop sending to the weakest Gmail segment for a few sends. Use recent clicks, purchases, logins, replies, active customers, or transactional recipients where permission and expectation are strongest. Audit signup sources, default-checked forms, imported contacts, and partner lists before resuming broad sends because unclear consent turns user complaints into a reputation problem. Gmail responds to recipient behavior, so a cleaner audience can help rebuild confidence faster than a full-list blast. Do not restart with the full Gmail list; add older segments only after complaints, bounces, deferrals, and spam placement stay stable.
High frequency is not automatically bad, but it amplifies every negative signal when the audience is tired. Set recipient-level caps, suppress recent non-engagers, and raise cadence only for Gmail recipients with current positive behavior.
If Gmail is returning temporary failures or mail is arriving late, give Gmail traffic its own rate cap, hold colder segments, and increase volume only after delays and spam placement settle. For 4.7.28 rate-limit style errors, pause for at least 10 minutes, restart from a single connection, and increase connections only after errors settle.
For a deeper recovery path, use a focused fix Gmail spam placement process after the technical checks are clean. The important part is sequencing: fix measurable failures first, then tune content and audience.
Recover after the Gmail spam spike
After the measurable issue is fixed, do not resume full Gmail volume. Gmail needs a cleaner pattern: recent engagers, normal cadence, low complaints, low bounces, and stable authentication. Treat recovery as a controlled sending process, not one corrected resend.
- Start with recent Gmail engagement: Use recipients who recently clicked, purchased, logged in, replied, opened where tracking is reliable, or completed another high-intent action.
- Hold risky cohorts: Exclude bot signups, old inactive leads, purchased addresses, unvalidated contest entries, bounced contacts, and winback audiences until placement is stable.
- Increase only after clean sends: Raise Gmail volume after the previous batch has low spam placement, low complaints, low bounces, and no repeated deferrals.
- Keep streams separate: Protect receipts, security alerts, account notifications, and other transactional mail from risky promotional reputation.
|
|
|
|---|---|---|
Single broken link or DNS issue | Fix and retest | Next few sends |
Light reputation damage | Engaged Gmail only | 2-3 weeks |
Low or Bad Gmail reputation | Strict rewarm | 1-2 months |
Reputation-based rejections | Stop risky mail | Variable |
Use recovery ranges for planning, not guarantees.
The common mistake is one good batch followed by a full-list Gmail campaign. That teaches Gmail the old pattern again. Recovery is stable when engaged segments, normal segments, and key automated flows can send without the spam placement returning.
Views from the trenches
Best practices
Test the exact same message with and without tracking before changing creative first.
Keep a branded tracking domain ready so shared root problems are easier to isolate.
Compare Gmail-only movement against all-provider movement before changing infrastructure.
Common pitfalls
Assuming unchanged content means unchanged risk misses shared link domain failures.
Changing IP, domain, copy, and audience together makes the cause almost impossible to prove.
Moving to a new tracking hostname at full volume can create another Gmail trust problem.
Expert tips
Treat every hostname in the email as part of the message reputation Gmail evaluates.
Slow the next send after a domain swap so Gmail sees normal engagement signals again.
Keep DMARC and blocklist alerts live so sudden placement shifts have clear context.
Marketer from Email Geeks says sudden Gmail spam placement often points to a URL or tracking domain problem, even when the sender believes nothing changed.
2024-04-19 - Email Geeks
Marketer from Email Geeks says a specific shared tracking root can cause many otherwise stable campaigns to move to Gmail spam at the same time.
2024-04-19 - Email Geeks
The practical next move
Do not start by rewriting the whole email. Start by proving whether Gmail changed its view of your links, sender setup, template, audience, volume, SMTP behavior, raw IP URLs, unbranded asset hosts, whether Postmaster Tools is showing delayed complaints against earlier sends, or whether Gmail itself had a broader filtering issue. Compare the exact message that inboxed yesterday with the exact message that goes to spam today. Remove links, search all Gmail labels when one client disagrees, check authentication, inspect every hostname, review Gmail 4xx deferrals, compare tabs separately from Spam, match Postmaster Tools dates to Gmail-only volume, and look for blocklist (blacklist) pressure.
If the tracking domain is the cause, move to a branded domain or have the provider replace the flagged root. If an asset host or landing page is the cause, replace raw IPs and generic CDN paths with branded hostnames, then verify the final destination is clean. If authentication is the cause, fix DNS and verify results before the next send. If engagement or volume is the cause, reduce Gmail volume and send first to the audience that reliably wants the email.
The fastest recoveries usually come from controlled changes, not panic changes. Gmail is strict, but it is also signal-driven. Find the changed signal, fix that signal, and keep monitoring so the next sudden move is caught before it affects a full campaign.
