Amazon Bestseller Scraper: Operational Guide and Workflows

To extract ranking positions, ASINs, titles, prices, star ratings, and badge markers across Amazon chart pages, use Amazon Bestseller Scraper. The actor extracts product listings across 20 regional marketplace domains and five chart types: Best Sellers, New Releases, Most Wished For, Most Gifted, and Movers & Shakers. When a chart contains no products or a page load fails, it emits a structured chart metadata record rather than returning zero items silently.

Practical use cases

Use case 1: Category rank monitoring

Outcome: Track chart position trends, price points, and badge assignments for competing products in specific marketplace categories over time. Question to answer: Which products consistently hold top positions in a target category, and how frequently do top rankings change? Configure: Set chartType to bestSellers, domain to amazon.com, categoryUrls to ["electronics"], maxPages to 2, and maxItemsPerCategory to 60. Working method: Run scheduled daily extractions against your designated category slugs or browse node identifiers. Collect output records and filter for entries where recordType equals chartItem. Store the records in a relational database table indexed by asin, category, and scrapedAt. Calculate daily position variations by comparing current rank values against previous extraction runs. When an ASIN drops off the chart or a new product enters, record a position shift event. Deliverable: A structured position log showing daily rank trends, price stability, rating counts, and active badge assignments per ASIN. Stop condition: Stop extraction when all requested chart pages for the category are processed or when maxItemsPerCategory reaches 60 records.

Use case 2: Gift guide catalog curation

Outcome: Build a verified collection of popular gift items and highly desired products to power buying guides and convert AI referral traffic. Question to answer: Which items are currently leading the Most Gifted or Most Wished For charts with active detail page verification? Configure: Set chartType to mostGifted, domain to amazon.com, categoryUrls to ["electronics"], includeProductDetails to true, and maxProductDetails to 10. Working method: Fetch product listings from the Most Gifted or Most Wished For chart for a target category. Enable includeProductDetails to fetch individual product detail pages for verification. Filter output records to retain items where listPrice and inStock fields are populated alongside star ratings and review counts. Extract product titles, thumbnail URLs, prices, and badges to compose structured editorial recommendations. Deliverable: A verified publication catalog containing product ASINs, titles, verified list prices, stock indicators, and review metrics. Stop condition: Stop processing when maxProductDetails reaches its limit of 10 enriched detail fetches or when all chart items on the target page are evaluated.

Use case 3: Vertical taxonomy mapping

Outcome: Map subcategory hierarchies and evaluate chart depth across complex multi-level category trees. Question to answer: How are subcategories organized under a root department, and what top products occupy those subcategory charts? Configure: Set chartType to bestSellers, domain to amazon.com, categoryUrls to ["electronics"], maxDepth to 2, maxItemsPerCategory to 20, and maxItems to 500. Working method: Start a recursive crawl beginning at a root category slug. As the actor parses left navigation links on chart pages up to maxDepth 2, collect childCategories arrays containing category name, path, URL, and node ID attributes. Group extracted chartItem records by categoryNodeId to pair top-ranked items directly with their corresponding subcategory taxonomy node. Deliverable: A structured category taxonomy map connecting parent and child subcategories to top product listings across two depth levels. Stop condition: Stop execution when total extracted items reach the maxItems cap of 500 or when all subcategory links up to depth 2 are traversed.

Step-by-step execution workflow

Executing an extraction pipeline with Amazon Bestseller Scraper requires configuring targeted inputs, managing payload boundaries, and handling structured output records. Follow this operational workflow:

1. Select chart type and marketplace domain: Determine which chart family fits your research goal (bestSellers, newReleases, mostWishedFor, mostGifted, or moversAndShakers). Select your target domain from the 20 supported Amazon marketplace domains, such as amazon.com, amazon.co.uk, or amazon.de.
2. Define category targets: Provide category slugs (such as electronics), combined slug and browse node pairs (such as electronics/172541), or full chart URLs in categoryUrls. You can also supply additional browse node IDs in categoryNodeIds.
3. Set recursion and volume caps: Set maxDepth between 0 and 3 depending on whether you want to recurse into subcategories. Configure startPage, maxPages, maxItemsPerCategory, and maxItems to establish clear boundaries for payload size and execution expenditure.
4. Configure optional product detail enrichment: If your workflow requires verifying list price or stock status, toggle includeProductDetails to true. Set maxProductDetails between 1 and 100 to limit the number of individual detail page fetches.
5. Configure proxy settings: The actor uses Apify AUTO datacenter proxies by default. If target pages block requests repeatedly during a session, the scraper automatically escalates to a residential proxy session.
6. Run scraper and process output records: Execute the actor and parse the dataset. Process records where recordType is chartItem for standard chart listings. For empty charts or failed fetches, inspect records where recordType is chartMetadata.
7. Pipeline integration and cleaning: Ingest raw records into downstream data stores. Omit missing optional fields, format price currency objects, and log metadata messages for operational monitoring.

Specialized Amazon scrapers and their roles

Building robust e-commerce data pipelines often requires pairing ranking data with specialized scrapers across the Amazon marketplace ecosystem:

• Amazon Bestseller Scraper: Extracts rank position, ASIN, title, price, rating, badge, and category metadata across five Amazon chart types and 20 marketplace domains.
• Amazon Category Scraper: Collects broad product listings from standard Amazon search and category browsing pages beyond ranked chart lists.
• Amazon Product Scraper: Extracts comprehensive detail page data, including full specifications, bullet points, image galleries, and buy box seller details.
• Amazon Reviews Scraper: Scrapes customer review text, star ratings, review dates, and verified purchase flags for specific ASINs.
• Amazon Reviews Scraper Pro: Provides expanded review extraction capabilities, including sentiment signals, deeper filtering options, and detailed reviewer metadata.
• Amazon Offers Scraper (All Offers Display): Captures all active seller offers, merchant pricing, shipping terms, and buy box status for targeted product listings.
• Amazon Seller & Shop Scraper: Gathers merchant storefront profiles, seller feedback scores, business information, and seller product catalogs.
• Amazon Deals Scraper: Scrapes limited-time promotions, lightning deals, and percentage discounts from Amazon deal hubs.
• Amazon Brand Store Scraper: Extracts official brand store layouts, curated product collections, and brand media content.
• Amazon Creator Shop Scraper: Collects influencer storefront layouts, recommended product lists, and social curation content on Amazon.
• Amazon Wishlist & Registry Scraper: Captures public customer wishlists, wedding registries, and baby registries to analyze consumer interest.
• Amazon Keyword Suggestions Scraper: Extracts search auto-complete keyword suggestions to analyze search intent and search engine optimization trends.

Data quality and operational limits

Understanding platform behaviors and operational constraints ensures clean data ingestion and pipeline stability:

• Pagination and chart item variation: Amazon does not guarantee a fixed count of 100 items on every category chart. Pagination structures vary across categories and marketplaces. Check declaredItemCount against extractedItemCount in chartMetadata records to detect coverage gaps.
• Field omission policy: When Amazon leaves price displays, star ratings, format summaries, or badge markers off a chart card, the scraper omits those fields from the output record rather than inserting fabricated placeholder values.
• Detail page enrichment caps: Enabling includeProductDetails instructs the actor to fetch individual product detail pages for explicit list price and stock evidence. This operation is bounded by maxProductDetails to maintain performance control.
• Movers and Shakers empty states: Niche categories on the Movers & Shakers chart frequently contain zero items on Amazon. The actor handles this state by emitting a chartMetadata record containing extractedItemCount set to 0 and an explanatory message.
• Rank change indicators: rankChangeDirection and rankChangeAmount are populated exclusively for Movers & Shakers charts when Amazon displays an explicit rank change marker on the page card. The actor does not calculate rank changes by comparing separate runs.
• Proxy escalation behavior: Requests use Apify AUTO datacenter proxies by default. If target pages block requests repeatedly during an active session, the actor automatically escalates to a residential proxy session.

Frequently asked questions

How does the scraper handle empty or failing chart pages?

When a chart page contains no products or cannot be fetched, the actor emits a chartMetadata record. This record includes chartType, category, categoryNodeId, categoryUrl, domain, extractedItemCount set to 0, and a human-readable message explaining the state. It never returns zero items without context.

Why do some chart item records omit price or rating fields?

Amazon only displays price values or star ratings on certain chart cards when explicit data exists. If Amazon omits these elements on the page card, the actor omits price or stars from the JSON output record.

Do I need to configure custom proxies to run this actor?

No custom proxy configuration is required. The actor uses Apify AUTO datacenter proxies by default. If a session experiences repeated blocking, the actor automatically escalates to a residential proxy session as a fallback.

Which Amazon marketplace domains are supported?

The scraper supports 20 Amazon marketplace domains: amazon.com, amazon.co.uk, amazon.de, amazon.fr, amazon.it, amazon.es, amazon.ca, amazon.com.au, amazon.co.jp, amazon.in, amazon.com.br, amazon.com.mx, amazon.nl, amazon.se, amazon.pl, amazon.com.tr, amazon.ae, amazon.sa, amazon.sg, and amazon.eg.

Can the actor navigate subcategories automatically?

Yes. By setting maxDepth between 1 and 3, the actor walks subcategory links visible in Amazon left navigation menus up to that depth level, scraping every subcategory chart encountered.

Resources

• Amazon Bestseller Scraper Actor
• Apify Proxy Documentation
• Apify Dataset API Reference