Amazon Compare With Similar Items: How to Win the Comparison Table on Your Own Detail Page

Scroll down any detail page you own until you hit the grid of four to six products sitting side by side with prices, star ratings, and a stack of attribute rows underneath. That's the compare with similar items table, and three of the products in it are not yours. Amazon built a competitor comparison into your own listing, populated it without asking you, and put it below the fold where almost nobody audits.

Here's the part most sellers miss: your hero image renders in that table at roughly 150 to 220 pixels, stripped of every bit of context that made it work in search. The image you spent $2,000 photographing gets judged against three rivals at postage-stamp scale, in a grid designed to make products look interchangeable. After optimizing 14,000+ hero images and auditing 50,000+ listings, I can tell you that the compare with similar items widget is the single most under-audited conversion surface on Amazon — and unlike the ad carousels, you can't outbid your way out of it.

What Is Amazon's Compare With Similar Items Widget?

The compare with similar items widget is an Amazon-generated comparison table on the product detail page that displays your product beside three to five algorithmically selected alternatives, comparing them on thumbnail image, title, price, customer rating, and a set of structured attribute rows drawn from each listing's catalog data.

It is not an ad. Nobody paid to be there. It's not the "Products related to this item" carousel, and it's not "Similar brands on Amazon" — those are separate surfaces with separate logic. The comparison table is Amazon's attempt to do the shopper's evaluation work for them, using the structured data you and your competitors uploaded.

Three things matter about it operationally:

• You cannot remove it. There is no Seller Central toggle, no case you can open, no brand-registry lever. Sellers ask about this constantly on the forums and the answer has not changed.
• You cannot choose who appears. Selection is algorithmic and behavioral.
• You control exactly two inputs into it — your main image at thumbnail scale, and the completeness and wording of your structured attributes.

That last point is the whole game. Most of this article is about those two inputs.

Why the Compare With Similar Items Table Is a Second Search Page Inside Your Listing

Think about what a shopper has already done by the time they reach this widget. They searched. They compared thumbnails in the grid. They picked yours. They clicked. You won the CTR battle and paid for the privilege.

Then Amazon hands them a fresh grid of alternatives, halfway down the page you earned.

Functionally, the compare with similar items table is a second search results page rendered inside your detail page — except this one has no organic rank advantage for you, no sponsored placement to buy, and a layout that explicitly invites side-by-side judgment. The shopper isn't browsing anymore. They're evaluating on a spec sheet.

The revenue math is worse than sellers assume, because the damage isn't only click-out. Take a listing doing 60,000 monthly sessions at a 12% conversion rate and a $34 average order value — about $245,000/month. In the audits I run, roughly a quarter to a third of detail page sessions reach the comparison widget's scroll depth on desktop, less on mobile.

Some of those shoppers click a competitor and leave. That's the visible loss, and it's usually smaller than people fear — low single digits of the sessions that see it.

The invisible loss is bigger. A shopper who looks at a table where your product shows three filled attribute rows and the competitor shows eight doesn't necessarily click away. They just stop being sure. They add to cart later, or not at all, or they go read reviews looking for a reason to feel confident. A comparison table you lose on doesn't only redirect traffic — it injects doubt into shoppers who were already sold. In my experience that shows up as a CVR sag you'll never attribute correctly, because nothing in Business Reports tells you the widget did it.

If you want the full picture of how competitors land on your page through every other surface too, I've written a companion piece on Amazon detail page defense. The comparison table is the one lever that piece doesn't solve, because PPC defense can't touch it.

How Amazon Chooses Which Products Appear in the Comparison Table

You can't control selection, but understanding it tells you where you can still push.

From what I've observed auditing these tables across thousands of listings, selection leans on four signals:

1. Browse node and product type. The table pulls from your immediate category neighborhood. Products with a mismatched or overly generic product type often get compared against a strange assortment — a signal your catalog data is off.
2. Co-view and co-purchase behavior. Products shoppers actually look at in the same session are strong candidates. This is the signal you can influence indirectly.
3. Price band. Amazon tends to pull comparables within a reasonable multiple of your price, which is why a premium product with sparse data often gets slotted next to budget alternatives and looks overpriced rather than premium.
4. Attribute overlap. The table needs shared attribute rows to render. Products with similar filled attributes are easier for the algorithm to compare, which makes them likelier picks.

The tactic that follows from this is the one almost nobody runs: get your own ASINs into your own comparison table.

If you sell a product family, every slot occupied by your own SKU is a slot a competitor doesn't get. You influence this by tightening attribute overlap across your catalog (same product type, same attribute fields filled with consistent phrasing), keeping family members in a coherent price band, and driving co-views between your own ASINs — through your A+ comparison chart module, your Brand Store navigation, and variation relationships where they legitimately apply.

I've watched brands go from zero owned slots to two of four over a couple of months doing nothing but cleaning up attribute consistency across a product family. It isn't guaranteed and it isn't fast. It's also the only real form of offense available here.

The Thumbnail Problem: Your Hero Image at 180 Pixels

Here's the audit almost nobody runs.

Your hero image was approved at 1600px+ so it supports zoom. It was probably designed on a 27-inch monitor. In the compare with similar items table it renders at roughly 150-220px on desktop, and on mobile the table becomes a horizontally scrollable strip where you see about two and a half columns at once — each thumbnail smaller still.

At that scale, a lot of hero images that perform beautifully in search fall apart:

• Products shot small in frame — the classic mistake of leaving too much white margin — become an ambiguous blob next to a competitor who filled the frame.
• Multi-piece sets turn into visual clutter. Eight components at 180px read as noise, not value.
• Dark products on white lose all edge definition and silhouette.
• Fine texture and material detail — the thing that justifies your price — disappears entirely.
• Any legible text you've pushed to the edge of policy is now genuinely unreadable, which means the shopper gets the visual cost of the overlay with none of the benefit.

Run this audit in five minutes:

1. Open your detail page in an incognito window and scroll to the comparison table.
2. Screenshot the whole table, all columns.
3. Shrink the screenshot to 50% and look at it from arm's length.
4. Ask one question: without reading a single word, which product looks like the best one?
5. Repeat on your phone, scrolling the table sideways through every column.

If the honest answer in step 4 isn't yours, you have a thumbnail problem, and it's costing you in every small-format surface Amazon renders — search grid, related carousels, this table. The fix is silhouette and frame-fill, not detail. I've covered the underlying principle in depth in the 160-pixel mobile hero test and in how images behave in the pre-click swipe in search results. The same discipline that wins the search grid wins this table. That's the good news: this is one fix, not two.

The bad news is the reverse. If your hero is losing here, it's almost certainly losing in search too, and you've been reading the CTR damage as a keyword problem.

Attribute Fill Rate: The Rows Most Sellers Forfeit Without a Fight

The bottom half of the comparison table is rows of structured attributes — material, item weight, special feature, capacity, whatever Amazon has decided matters in your category. Those values come straight from your listing's catalog data.

When a field is empty on your listing, the row doesn't vanish. It renders as a dash, or blank, right next to a competitor's filled value. Amazon is showing the shopper a table where your product visibly has less.

That's the whole mechanism, and it's brutal in its simplicity. You don't lose this comparison because your product is worse. You lose it because someone in your ops chain skipped fifteen optional fields in the flat file two years ago.

Here's the protocol I run:

1. Pull the live table first. Incognito, screenshot it. Note the exact attribute rows Amazon chose for your category — these are the fields that actually matter, and they're often not the ones you'd guess.
2. Diff yourself against every competitor in the table, row by row. Mark every cell where you're blank and they're filled. This list is your work order.
3. Fill every one of those fields in Seller Central, using the category's controlled vocabulary rather than freeform text where the field offers a dropdown.
4. Check the values that are already filled but weak. "Multi" as a color, "1 count" as a size, a material listed as "Other" — these render as filled but read as evasive. A filled-but-useless cell can be worse than a dash, because it looks like you're hiding something.
5. Fix the units. I see listings where the competitor shows "32 fl oz" and the seller shows "0.95" with no unit because the field was populated wrong. The shopper doesn't investigate. They just read the clean number.
6. Re-pull the table in 7-14 days and confirm the rows updated.

Across the listings I've audited, attribute fill on the fields that feed this table sits far lower than sellers believe — plenty of otherwise well-run listings are at half or less on the optional fields. Listings I've seen at near-full fill tend to convert better than their sparse neighbors, though I'll be straight with you: that's correlation from audit work, not a controlled test. Brands that fill every attribute field usually do a lot of other things right too.

What I'd defend as causal is narrower and enough to act on: a dash in a comparison row is a visible deficiency shown to a shopper at the exact moment they're evaluating alternatives, and removing it costs you nothing but an hour in the flat file. There is no version of this where losing the row is better.

Attribute completeness also feeds your CDQ score, so this work pays twice. If you're running a large catalog and need this systematized rather than done by hand, I built an attribute fill-rate auditor that flags the gaps across every ASIN at once.

Compare With Similar Items vs. Your A+ Comparison Chart: Which One to Fight

Sellers conflate these constantly. They're different weapons and they need different strategy.

The strategic read: your A+ comparison chart is the pre-emptive strike, and it needs to sit above the Amazon table.

If a shopper hits your A+ comparison chart first — a clean, honest table showing which of your SKUs fits which use case — a large share of the comparison work is finished before Amazon's widget appears. They've already decided which model they want. The competitor table lands on someone who has moved from "which product" to "which of theirs," which is a much harder shopper to peel away.

Skip the A+ chart and you've conceded the entire comparison job to a table you don't control. That's the actual reason the A+ comparison chart is the highest-CVR module in my testing, and I go module-deep on it here.

One firm warning: never name or picture a competitor in your own A+ chart, and never build a comparison referencing a competitor's ASIN. That's a policy violation that gets content rejected and can put the listing at risk. Compare your products to your products. The us-versus-them argument belongs in your image stack's comparison slot, made on attributes rather than named brands.

Common Mistakes: What Not to Do About the Comparison Widget

Opening a case to have it removed. It won't work and you'll burn a week. There's no mechanism. Sellers have been asking since the widget launched.

Trying to break the algorithm's category read. I've seen sellers deliberately mis-set product type or browse node hoping to escape the comparison set. It sometimes works — and it wrecks your organic discoverability, because the same catalog data drives search relevance. You'll trade a below-the-fold comparison for a rank collapse. Never worth it.

Dropping your price to win the price row. The table shows price, so the reflex is to undercut. But you've now cut margin to win one row of a table that maybe a third of your visitors see, while the shopper who reaches it is comparing on eight dimensions. Win the rows that are free first. If you're being squeezed on price positioning, the answer is premium creative positioning, not a race down.

Stuffing attribute fields with keywords. These are structured fields feeding a customer-facing table. "Premium Heavy Duty Stainless Steel Best Kitchen" in the material field renders exactly like that to the shopper, truncated and desperate, next to a competitor's clean "Stainless Steel." Fill fields accurately. Keywords go in search terms.

Auditing it once. The comparison set rotates as behavior and catalog data shift. A table you won in March can have three different competitors in it by August. Put it on the same cadence as your competitor creative analysis — quarterly at minimum, monthly on your top ten ASINs.

Ignoring it because it's below the fold. This is the real one. Every seller I raise this with says some version of "does anyone even scroll that far?" Enough of them do, and the ones who do are your highest-intent shoppers — people deep enough in evaluation to be comparing specs. Losing the comparison table means losing shoppers at the bottom of the funnel, which is the most expensive traffic you have.

The 45-Minute Comparison Table Audit

Run this on your top ten revenue ASINs, once a quarter:

1. Incognito, desktop. Load the detail page, scroll to the compare with similar items table, screenshot all columns.
2. Incognito, mobile. Same thing, scrolling the table sideways through every column. Note where your product sits in the column order.
3. Score the thumbnails. Shrink to 50%, arm's length, no reading. Rank all products by "which looks best." Write down your honest position.
4. Diff the attribute rows. Every cell where you're blank or weak and a competitor is filled and clean.
5. Check who's in the table. Are any of them yours? Are any of them wildly off-category, indicating a product-type problem on your end?
6. Check the title truncation. Since the 75-character title rule, titles render differently in compressed columns — confirm your critical words survive the cut. If they don't, the fix belongs in your item highlights and title strategy.
7. Write the work order. Attribute fixes go in this week — they're free. Hero image changes go into your normal testing queue, because a hero change affects search CTR and must be measured properly, not shipped on a hunch.

That last distinction matters. Attribute fills are pure downside-removal and can ship immediately. A hero image change is never a free action — it moves your search CTR too, and it needs to run through a real test protocol so you can isolate the lift rather than guessing.

Frequently Asked Questions

Can you remove the compare with similar items section on Amazon?

No. There's no Seller Central setting, brand registry option, or support case that removes the compare with similar items widget from your detail page. Amazon generates it automatically from catalog data and shopper behavior. Your options are to influence what appears in it — through attribute consistency and driving co-views between your own ASINs — and to win the comparison on the two inputs you control: thumbnail image and attribute completeness.

How does Amazon decide which products show in the comparison table?

Selection appears to be driven by browse node and product type proximity, co-view and co-purchase behavior, price banding, and attribute overlap between listings. Products that shoppers view in the same session and that share filled attribute fields are the strongest candidates. This is why cleaning up attribute consistency across your own product family can, over time, pull your own ASINs into your comparison table instead of competitors'.

Why does my competitor appear on my Amazon listing?

Competitors reach your detail page through several separate surfaces: sponsored product carousels (paid ASIN targeting), "Products related to this item," "Similar brands on Amazon," and the compare with similar items table. Only the ad placements can be countered with defensive bidding. The comparison table is organic and algorithmic — you counter it with creative and catalog data quality, not spend.

Does the compare with similar items widget hurt conversion rate?

It costs you in two ways. A small number of shoppers click a competitor and leave. A larger number stay but lose confidence, because a table showing your product with fewer filled attribute rows reads as a product with fewer features. The second effect is the expensive one and it's essentially invisible in your reports — you'll see it as unexplained CVR softness, not as widget damage.

Should I lower my price to win the comparison table?

Almost never as a first move. Price is one row in a table with many, and the shopper reaching it is evaluating on multiple dimensions. Fill every attribute row and fix your thumbnail first — those cost nothing but time. Cutting price to win one visible row while leaving five rows blank is paying margin to fix the wrong problem.

The Three Actions That Matter

Amazon put a competitor comparison table on your detail page and gave you no button to remove it. That's not a reason to ignore it — it's a reason to win it.

One: audit the thumbnail. Screenshot your compare with similar items table, shrink it, and honestly rank which product looks best at 180 pixels. If it isn't yours, that's a hero image problem hurting you in search too.

Two: fill every attribute row. Diff yourself against every competitor in the table and populate every blank field with accurate, correctly-united, controlled-vocabulary values. It's an hour of work, it's free, and every dash you remove is a visible deficiency you stop showing to a shopper mid-evaluation.

Three: build the A+ comparison chart that pre-empts the table. Finish the shopper's comparison work with your own SKUs, higher on the page, before Amazon does it for them with someone else's.

Do those three and the compare with similar items widget stops being a hole in your detail page and starts being one more surface where your listing quietly outclasses everyone standing next to it.