Methodology · Verified against Amazon Seller Central, 27 August 2026
Revenue is down 20% on the month. Sessions look normal. The instinct is to
raise bids until the number comes back, and it’s usually the most expensive available option.
What this is. The diagnostic order we work every declining account in, published
in full. No client data — the sequence and the thresholds are the asset, and they’re the same
whether we run it or you do.
Why bids are the wrong first move
If the cause is a conversion problem, higher bids buy more traffic into a listing that has already
stopped converting. If it’s lost organic position, they paper over a rank slide that keeps widening
underneath. Either way you spend more to stand still, TACoS climbs, and the real problem gets a month
older.
Step one: traffic problem, or conversion problem?
Two numbers answer it, and Amazon states the logic itself in Seller Central: “If sessions are
down but conversion rate is stable, you have a traffic problem. If sessions are steady but conversion
is dropping, you have a listing or pricing issue.”
Business Reports → Detail Page Sales and Traffic by Child ASIN. Pull sessions and
unit session percentage over a rolling 30 to 60 days, against the same period last
month and last year.
At child ASIN level, not account level. Account averages hide exactly what you’re
looking for — one collapsing SKU inside a stable catalogue disappears into the mean.
| Sessions | Unit session % | What it is | Where to look |
|---|---|---|---|
| Flat | Falling | Conversion problem | Price, images, reviews, Featured Offer, a competitor’s new offer |
| Falling | Flat | Visibility problem | Organic rank, indexing, impressions, ad budget |
| Falling | Falling | Structural | Suppression, variation split, category change, account issue |
| Flat | Flat, revenue down | Mix or price | Discounting, unit price, which SKU is selling |
That last row catches people out. If both metrics hold and revenue still falls, you haven’t lost
customers — you’ve changed what they’re buying or what they’re paying.
Step two: cliff, or bleed?
The shape tells you which family of causes to investigate.
A cliff is 30% or more inside a day or two, with a clear before and after.
Something broke, and it’s almost always technical.
A bleed is 3–5% a week for six weeks, no obvious start date, and by the time it
reaches a meeting the account is down a third. This is nearly always rank decay, and it does the real
damage — because Seller Central sends no alert when a product slips from position 3 to
position 14. The traffic simply stops arriving.
Step three: rule out the five technical causes
Two minutes each. Do all five before considering anything more sophisticated.
- Featured Offer loss. Check the percentage in Business Reports. Fastest possible
explanation, most commonly missed — sellers assume the Buy Box only moves on price, but late shipment
rate, inventory availability and fulfilment performance all affect rotation. - Suppression. Manage All Inventory, filter by suppressed. The listing stays live
enough to look fine while ranking nowhere. - Stockout, including a brief one. It costs the position you spend weeks
rebuilding. And low inventory hurts before you run out — Amazon deprioritises listings with weak
inventory signals. - Variation split. If a parent-child relationship breaks, the reviews and history
carrying the child vanish from view. - Price move. Yours or a competitor’s. Check whether a coupon ended on the day the
graph turns.
Step four: the six 2026 causes most checklists miss
The steps above haven’t changed in years. These have, and they’re where unexplained cases are
landing right now.
1. Amazon rewrote your title
On 27 July 2026 Amazon cut titles to 75 characters and began rewriting non-compliant ones with AI,
gradually, listing by listing. Non-Brand-Registry sellers got no review window; Brand Registry sellers
who let the 14 days lapse got Amazon’s version. Those rewrites can drop a keyword that was holding
organic position, and the loss surfaces weeks later as a slow bleed. Compare your titles
against what they said in June.
2. Amazon changed other listing content
Bullets removed, categories reassigned, images suppressed. Pull your live listing content weekly
and diff it against your master copy.
3. Discovery moved to Alexa for Shopping
Amazon retired the standalone Rufus assistant on 13 May 2026, replacing it with Alexa for Shopping
— built into the main search bar, showing AI overviews above results, default for signed-in US
customers with no Prime or Echo required. Expect 30 to 60 days of volatility in PPC metrics while
discovery patterns settle.
4. Impressions fell before sessions did
Genuinely diagnostic. Impressions declining ahead of sessions points to partial suppression or lost
keyword indexing rather than reduced demand — demand shifts move both together.
5. One bad ASIN is dragging the rest
Late shipments and complaints on a single SKU can pull performance across a catalogue. Broad and
shallow decline? Look for the ASIN with the worst fulfilment history.
6. Account Health is green and still hiding something
Green means no open violations. It doesn’t mean no soft suppressions or latent policy risk.
Step five: confirm rank decay, and find who took it
Sessions falling, conversion holding, technical causes ruled out — you’re looking at lost position.
Now prove it.
- Baseline. Search Query Performance in Brand Analytics gives impressions, clicks
and purchases by query for your ASIN. That’s the list that matters, not the one in your listing. - Current position. Compare against rank history. If you have none, start recording
today — you can’t diagnose a slide you never measured. - Who took it. Run a reverse ASIN lookup on the products now sitting where you
used to.
“We lost rank” isn’t actionable. “We lost positions three through seven on our two
highest-converting terms to a competitor who launched a 3-pack at £4 under us” is.
We run this on every account before we touch a bid
The forensic audit works the full sequence, including the rank baseline most accounts have never
established.
Prepared by Ecom Enable. Amazon guidance, policy dates and platform changes
verified against Seller Central on 27 August 2026.