Amazon Bestsellers Scraper — Amazon Best Sellers ranks in 7 marketplaces

This Actor scrapes Amazon Best Sellers ranking pages and returns the ranked products with rank, asin, title, price, a numeric rating and a numeric reviewCount. It covers seven Amazon marketplaces in one run — US, UK, Germany, France, Spain, Japan and Australia — and every marketplace can be crossed with every category slug you give it.

No Amazon account, API key or cookies are used — the Amazon Bestsellers Scraper reads the public Best Sellers page a logged-out visitor sees. 30 products per category page, in about 2.7 seconds per page at the measured median.

What it returns

Field	Type	Notes
marketplace	string	us, uk, de, fr, es, jp, au
category	string	The category slug requested
rank	number	Bestseller position, 1-based
asin	string	Amazon's product ID — stable, use it to join or de-duplicate
title	string
price	string	As displayed, in the marketplace's own currency
rating	number	Stars out of 5. Locale decimals are handled — "4,4" on .de is 4.4
reviewCount	number	278974, not "278,974"
productUrl	string	Direct /dp/ link on the right marketplace
sourceUrl, collectedAt	string	Provenance for every row

Input

{ "marketplaces": ["us", "uk", "de"], "categories": ["books"], "maxItems": 1000 }

Field	Description
marketplaces	Any of us, uk, de, fr, es, jp, au. Required, at least one.
categories	Bestseller category slugs, e.g. books, electronics, software. Required, 1–50.
maxItems	Cap on dataset items. Default 1000. Free plans stop at 250 requests and 250 results — see below.
concurrency	Pages fetched in parallel. Default 3, maximum 10.

Marketplaces are crossed with categories, so 3 marketplaces × 2 categories is 6 pages and about 180 rows.

Category slugs are marketplace-specific. books resolves on all seven; electronics is valid on amazon.com but not on amazon.de, where computers is. An unknown slug fails that one target with a message saying so, and the other targets still return.

Use cases

• Tracking category rank and price movement over time
• Competitor and brand monitoring across several countries at once
• Product and niche research before sourcing
• Comparing what sells in the US against Europe and Japan
• Feeding a pricing or merchandising dashboard on a schedule

Reliability

Measured across 21 marketplace × category combinations in one run: 20/21 succeeded, 600 products collected, every schema field populated. The single failure was an invalid slug for that marketplace, reported as such.

Rankings are read from the Best Sellers grid itself, so ranks, prices, ratings and counts are the page's own values rather than a model's reading of them.

Frequently asked questions

Do I need an Amazon account or API key to scrape Amazon Best Sellers? No. The Amazon Bestsellers Scraper reads only the public Best Sellers pages a logged-out visitor sees.

Which Amazon marketplaces are supported? Seven: US, UK, Germany, France, Spain, Japan and Australia — all available in a single run, with marketplace on every row.

How many products does one category return? 30 — one Amazon Best Sellers page. This Actor does not paginate past the first ranking page.

Why is electronics empty on amazon.de? Category slugs differ per marketplace. Use computers there, or books, which resolves on all seven.

Is the review count a number? Yes, reviewCount is numeric, and rating handles locale decimal commas correctly — "4,4" on amazon.de is parsed as 4.4, not 44.

Does it scrape Amazon product detail pages or search results? No, Best Sellers rankings only. Use the Amazon Product Scraper for detail pages and the Amazon Search Scraper for keyword results.

Limitations

Bestseller listing pages only: no product-detail fields (description, images, variants, seller), no review text, and no search. price is the displayed string in local currency rather than a normalised number, because currency and formatting vary by marketplace. Marketplaces outside the seven listed above, including amazon.in, are not supported.

Free plan limit

Runs started from an Apify free plan stop at 250 requests and 250 results, and the run reports that it reached the limit. Any paid plan runs the full input and maxItems you set.

The limit exists because this Actor fetches through our own infrastructure, which Apify does not cover for free-plan runs. It binds on requests as well as results so that a large input list cannot spend those fetches for rows the run will not return.