2 min read
In brief
- A warning is a notice that enforcement will follow if the condition persists; a suspension is enforcement already applied.
- The warning window is the only period where you can fix the cause without a review, a request, or lost serving time.
- Most suspensions we see had a warning attached to the same issue first — the warning was scrolled past or never seen.
The difference that matters
| Warning | Suspension | |
|---|---|---|
| Account state | Still serving, usually with reduced reach | Not serving |
| What is required | A fix, no request | A fix and a review request |
| Who decides | You, by fixing it | A reviewer, on evidence |
| Time cost | Days, if acted on | Weeks, sometimes longer |
| Risk if ignored | Escalates to suspension | Escalates to account-level enforcement |
The trap is that a warning often does not stop anything. Products still show, spend still runs, and the notice sits behind a bell icon that nobody opens. By the time it becomes a suspension, the warning is weeks old and the evidence of a fix that could have resolved it nobody kept.
What to do inside the window
- 1
Screenshot the wording and the date
The message is the specification. Copy it exactly into your log; paraphrasing loses the category detail that tells you what to fix.
- 2
Scope it
Account-level, category, or named items. Scope decides whether this is a two-hour fix or a catalogue project.
- 3
Find the cause, not the symptom
If the warning names missing policy pages, the cause is a redirect that broke. If it names price accuracy, the cause is a sale price the feed does not know about.
- 4
Fix at the source
Store records or supplier mapping, never the feed alone — the next sync reverts a feed-only fix, and the warning returns with a history attached.
- 5
Verify as an outsider
Check from a fresh browser, logged out, in the target country. Your own session hides exactly the mismatches the crawler sees.
The habit that prevents the escalation
- Open the account notices weekly, not when something breaks. Most warnings have no visible symptom.
- Log every warning the day it appears, with the wording and the fix date — this is the history a later review is judged against.
- Treat an unresolved warning older than a fortnight as a live risk, not a to-do.
- After fixing, confirm the notice has cleared. A fix that did not clear the notice did not fix the cause.
A warning is the version of this problem that costs days instead of weeks. The whole skill is noticing it while it is still a warning — which means looking at the account when nothing appears to be wrong.
