One piece of housekeeping. Last Tuesday's ask was an Ads Support case requesting full removal from off-Amazon creator placements. Mine is still open — no removal, no denial, one request for information I'd already sent. If yours moved either direction, reply and tell me. The pattern is still worth publishing.
This week's is a different kind of clock, and this one runs whether you look at it or not.
|
Where your listings stand this morning
Four dates, and you need all four to know which situation you're in.
June — Amazon announced the cap. Item name drops to 75 characters. A second field, Item highlights, holds 125. Two hundred total, same as the old single title field.
July 27 — Amazon's model started generating title recommendations on non-compliant listings. Brand owners get 14 days to review, modify or reject. Approval is what happens if nobody does anything.
August 3 — enforcement, pushed back from July 26.
August 10 — Item highlights started rendering to shoppers. Reported as a stacked pair of grey lines beneath the title on mobile, and merged into one line with a pipe separator on desktop.
Amazon says over 984 million titles have been updated since June.
One detail that got almost no coverage and reframes the whole thing. A seller asked in the forums whether Amazon was exempting its own retail listings. A moderator answered: "This policy applies to Amazon listings as well." Amazon does not police itself for keyword stuffing — so this was never a crackdown on seller behavior. It's a shelf redesign, applied to everything on the shelf.
Which is good news, and also why the correct response is an audit rather than a defensive crouch.
Because here's the operator question. That 984 million counts titles that changed. It does not tell you which of yours changed because a person on your team made a decision, and which changed because nobody opened the notification in time.
Those two categories look identical in Seller Central. They are not identical in your catalog, and one of them is a list of ASINs where a language model set your keyword priority.
Why this isn't a cosmetic change
Two reasons, and the second one is the one that costs money.
Item highlights is indexed. Amazon's FAQ, verbatim: "Item name and Item highlights are both inputs for search, and one isn't prioritized over the other." That is Amazon stating that a field most catalogs are running empty carries the same declared search weight as the title.
And your ad structure sits on top of listing content that just moved. Auto campaigns and broad targeting derive candidates from indexed listing copy. Your indexed listing copy was restructured. I'm not going to tell you the effect, because Amazon has published nothing on how Item highlights feeds ad relevance or auto-targeting, and everyone who tells you otherwise this week is inferring. What I will tell you is that a change happened to an input, on most of the catalog, in a three-week window, and there is no field in your advertising console that will surface it.
An unmeasured change to an input is not a crisis. It's a work order. That's the rest of this issue.
The three ways this goes wrong, in order of how much it costs
Cheapest — the empty field. Title trimmed to 75, Item highlights left blank. You are running 125 indexed characters at zero across the catalog. Pure opportunity cost, fully recoverable, fix it in an afternoon.
Mid — the overflow dump. Somebody pasted the back half of the old title into Item highlights and called it done. It indexes. It also renders to shoppers on the detail page, which means a shelf-facing surface on your best ASINs currently reads like a keyword string. Amazon built a field that is simultaneously an index entry and a conversion element, and treating it as only the first one is a CRO decision nobody made on purpose.
Most expensive — the silent drop. Keywords that lived in the 200-character title, survived nowhere else, and are now in neither field. Not in the title, not in Item highlights, indexed only if they coincidentally appear in bullets or backend terms. Nobody audited that. This is the one that shows up as a quiet impression-share decline in six weeks and gets blamed on bids.
Every one of those is findable in a spreadsheet this week. None of them is findable in the advertising console at all.
14 days — review window on an AI-generated title recommendation. Approval is the default outcome
984 million — titles Amazon says have been updated since June. How many were deliberate is not published
75 / 125 — item name cap and item highlights cap. Two hundred total, split across two fields
August 10 — the day Item highlights started rendering to shoppers. It is a conversion surface now, not just metadata
0 — Amazon statements on Item highlights and ad relevance. Treat every confident take you read this week accordingly
Translation: The expensive version of this isn't the rewrite you can see in Seller Central — it's the keywords that were in your title in June, are in neither field today, and produce no alert anywhere in your stack. That gap is findable this week with a spreadsheet and invisible by October, when it will look like a bidding problem and get treated as one.
The Brief
August 13 — stop modeling a de minimis reversal. The Court of International Trade upheld the termination of the $800 duty-free exemption, closing the main legal path back. If your 2027 landed-cost model still carries a contingent reversion line, delete it. The other half of the ruling is the one worth planning against: the China-direct sellers undercutting your ASINs don't get relief either, and their cost floor just became permanent at the same time yours did.
August 14 — the arbitration reversal, and why the date matters. Amazon's updated US Conditions of Use restore binding individual arbitration and waive class actions — five years after Amazon dropped arbitration when roughly 75,000 Alexa users filed individual demands and turned filing fees into a weapon. This is the customer agreement, not the Business Solutions Agreement, and it does not touch your seller dispute rights. Read it for the pattern instead: Amazon closed a collective route on the buyer side ten days before the BSA closes the assignment-and-pledge route on yours.
September 5 — a $50 line item you will otherwise donate. BFCM deal fees are $100 upfront plus 1.5% of promo sales, capped at $5,000, flat year over year. Submissions filed by September 5 get $50 off the upfront fee. Per deal. Across a catalog it's real money for moving one date forward on a submission you were making anyway.
Quick Win
Delegate to whoever owns your catalog. Two hours, one spreadsheet, and one number at the end you can act on.
Do these in order. Step 1 before anybody edits anything.
Snapshot before you touch it. Search Query Performance at ASIN level, top 20 revenue ASINs, August 3 through August 16, saved with the pull date in the filename. Every day you delay, this baseline gets more contaminated. It is not recoverable later.
Open Review Listing Changes and clear the queue. Any pending AI title recommendation is on a 14-day clock with approval as the default. Approve it, modify it, or reject it — but decide it. An expired clock is a decision you didn't make, recorded as one you did.
Build the four-column audit off the Category Listings Report. ASIN, current item name character count, Item highlights populated yes or no, trailing-90-day revenue. Sort descending by revenue. Every "no" in the top quartile is 125 indexed characters you are running at zero on your best listings.
Run the drop-out diff — this is the step nobody else will do. For your top 20, pull the pre-June 200-character title from listing history or your own records and compare it to the current item name plus Item highlights combined. Every keyword present then and absent now goes in a column called Dropped. Then check each one against bullets and backend terms. Whatever is dropped and appears nowhere else is unindexed, and until this exercise nobody knew it.
Reinstate deliberately, not by paste. Dropped keywords that still matter go into Item highlights as a phrase a shopper would accept reading — materials, use case, compatibility, size. The field renders on the detail page. It is shelf-facing copy that happens to index, and writing it as a keyword string costs conversion to buy ranking. Bulk edits reportedly process within about eight hours.
Hold 20 ASINs back as a control, and calendar the recheck for October 13. Same SQP pull, treated versus untouched. The control group is what turns this from housekeeping into a number.
The artifact: a title audit sheet with a Dropped column and a dated pre-change SQP baseline attached. The Dropped column is the deliverable — it is the only place in your entire stack where the cost of the August split is written down, and it will not exist unless somebody builds it this week.
It was in your title in June, is in neither field today, and never generated a single alert on its way out.
See you Friday.
Have any questions? Grab a 15-minute slot here: book a time here.
Subscribe to The Elite Edge here.
— Dan
