Listing Content Pull — guide

Pulls the live public content of any Amazon listings — yours or a competitor's — into one workbook. No AI and no rewriting: exactly what the detail page shows today, ready for audits, competitor research, or a before-snapshot ahead of an optimization.

Step by step

Open Tools → Research existing listings → Listing Content Pull and sign in.
Paste ASINs, one per line (commas or spaces work too). Up to 500 per run. Duplicates are dropped, and anything that is not a 10-character ASIN is named in the quote step — before anything is charged.
Choose the Amazon marketplace. Content comes from that site's detail pages, in that site's language.
Click Get cost estimate: 1 credit per 5 ASINs, rounded up per run — for example "12 ASINs = 3 credits". Nothing runs until you confirm.
Confirm & run. A run takes a few seconds per ASIN; the run page refreshes itself.

What you get back

A Listing content workbook, one row per ASIN: asin, brand, item_name (the page heading — on variation pages Amazon shows the parent's short title there), child_title (the variation's own title, the one search results and the cart show), color and size (the variation selected on the page), bullet_point1-5, product_description, product_details (the page's specification table — fabric, sole material, closure, weight, date first available… — as "Label: Value" lines in one cell), price_from, price_to, currency, rating, review_count, the product url, and — with your Amazon account connected — backend_item_name, backend_color, backend_size, backend_bullet_point1-5, and backend_product_description holding Amazon's stored attributes next to what the page shows. The column names match Amazon's flat files.
A Not found tab listing ASINs that could not be fetched (no listing on that marketplace, or an unavailable page) with the reason. Their share of the credits is refunded automatically.
On the run page, a table of the pulled listings — bullet count, description type, price, and rating — each linked to the marketplace.

Where the content comes from

The public detail page — title, bullets, description, price, and rating: what shoppers see. The pull fetches the page itself and reads every column from its HTML (a data provider steps in only when the page cannot be fetched, and the run page marks such rows). Bullets are only topped up from your own synced catalog when the page carried none, and the content_source column says so.
Amazon's stored attributes, when your Amazon account is connected. The pull also reads every ASIN's own attributes (title, bullet points, description) straight from Amazon's catalog through your connection — for any listing, not just yours — into separate backend_ columns. These are what is stored in the backend, and Amazon does not always display them (a vendor update it has not accepted yet, or another contribution winning the page). The run page flags rows where the page and the backend bullets differ, so you can spot an update that never went live. Your connection must be in the same region as the marketplace (North America, Europe, or Far East). An ASIN the page fetch cannot load but Amazon knows still gets a row, marked backend only (no price or rating).

What it cannot include

Backend search terms from the public page. They are never shown there, and Amazon's catalog does not expose them either. For your own listings the pull fills them in from your synced catalog — connect your Amazon account and pull your catalog first.
A+ Content built from images. When a page has no description text, the description cell says so instead of staying blank.
Images, videos, Q&A, and review text are out of scope.

Good uses

A competitor sweep before you optimize: pull the top 20 ASINs in your category and read their titles and bullets side by side.
A before-snapshot of your own listings ahead of a bulk optimization.
A cross-marketplace audit: run the same ASINs against amazon.de, amazon.co.uk, and amazon.fr.

Variations that are not offered redirect. When a child ASIN has no offer, Amazon shows the family's default child instead. The pull detects this: the row's content_source carries a warning naming the ASIN the page actually showed, and the run page marks the row redirected. The page columns then describe that default child; the backend_ columns (with your Amazon account connected) still hold the requested ASIN's own attributes.

Content is fetched when the run starts — treat the sheet as a dated snapshot, not a live feed.