
Amazon Search Listing
FreeEffortlessly extract product listings from Amazon.
Free · Opens the source repo
What Amazon Search Listing does
The Amazon Search Listing skill enables users to extract structured product information from any Amazon search results or category browse page. This skill is particularly useful for developers, researchers, and marketers who need to analyze product data for competitive analysis, price monitoring, or catalog audits. By inputting a valid Amazon search or category URL, users can retrieve detailed product cards that include essential information such as ASIN, title, price, ratings, and pagination state. This functionality is supported across all Amazon regional TLDs, ensuring broad applicability for users worldwide.
To utilize the skill, users simply need to have the target Amazon page open in their browser. The skill operates by reading the data already displayed on the page, which means it does not require any authentication or special access permissions. The extraction process is straightforward: after navigating to the desired page, the skill runs a Python script that captures product details and returns them in a structured JSON format. This allows users to efficiently gather and analyze data without the need for manual copy-pasting.
The skill also supports pagination, enabling users to extract multiple pages of results. By using the provided pagination state, users can easily navigate through the results and gather comprehensive data sets. However, it is important to note that Amazon limits keyword-only searches to a maximum of seven pages, while category-scoped searches can yield more results. This makes the skill an excellent choice for users looking to conduct in-depth research or track product listings over time.
Overall, the Amazon Search Listing skill is an invaluable tool for anyone needing to extract and analyze product data from Amazon. Its ease of use, broad applicability, and structured output make it a practical addition to any developer's or designer's toolkit.
When to use it
Use this skill when you need to gather product information from Amazon search results or category pages for analysis or monitoring.
When not to use it
Avoid using this skill for pages that require authentication or for extracting data not displayed on the page.
What you can build with it
Market Research
Gather detailed product information from Amazon to analyze trends and pricing strategies.
Price Monitoring
Track price changes for specific products over time to inform purchasing decisions.
Catalog Audits
Conduct audits of product listings in specific categories to ensure data accuracy and completeness.
How to install Amazon Search Listing
View source1. Install with the skills CLI
npx skills add browser-act/skills/amazon-search-listing --agent claude-code2. Or install it manually
Download the skill folder and drop it into ~/.claude/skills/ for all projects, or .claude/skills/ to scope it to one repo. Restart Claude Code so it picks up the new skill.
Anthropic's agentic coding CLI, and the reference implementation of Agent Skills. Drop a skill folder into ~/.claude/skills and Claude Code loads it automatically whenever a task matches the skill's description. Claude Code docs
Inside SKILL.md
Written by browser-actAmazon — Search & Category Listing
Input any Amazon search results, keyword search, or category browse URL → output per-item product cards + pagination state.
Language
All process output to user (progress updates, process notifications) follows the user's language.
Objective
Extract structured product listings from any Amazon SERP or category browse page across all Amazon regional TLDs, including full pagination support to walk multiple pages of a keyword or category.
Prerequisites
- Target page is already open in the browser: any Amazon search URL (e.g.
https://www.amazon.com/s?k={keyword}), category browse URL (e.g.https://www.amazon.com/s?bbn={cat}&rh=n%3A{node}), or category deep link - No login required; results reflect the browser's geolocation and Amazon domain
Pre-execution Checks
1. Tool Readiness
If browser-act has been confirmed available in the current session → skip this step.
Invoke browser-act via Skill tool to load usage. If installation or configuration issues arise, follow its guidance to resolve then retry.
Capability Components
This Skill's operational boundary = what the user can manually do in their browser. It only reads data already displayed to the user on the page, never bypassing authentication or access controls. Its role is equivalent to copy-pasting on the user's behalf — the data is already on screen, automation merely saves time. JS code is encapsulated in Python files under the
scripts/directory, invoked viabrowser-act --session {name} eval "$(python scripts/xxx.py {params})". The$(...)is bash command substitution — it runs the python script, captures its printed JS text, and hands that JS string as a single argument tobrowser-act eval. Do not runeval "$(python ...)"as a bare shell command; that would ask bash to execute the JS as shell, which fails.
DOM: extract product cards from current search/category page
Server-rendered HTML — no XHR/fetch API for listing data. Cards use the stable [data-component-type="s-search-result"] container.
navigate {any Amazon search or category URL}(e.g.https://www.amazon.com/s?k={keyword},https://www.amazon.com/s?k={keyword}&page={pageNumber},https://www.amazon.com/s?bbn={browseNode}&rh=n%3A{nodeId},https://www.amazon.co.uk/s?k={keyword})wait stable- Extract:
browser-act --session {name} eval "$(python scripts/extract-search-results.py)"
Output example:
{
"currentPage": 1, // page number as displayed by the pagination widget
"hasNextPage": true, // true when a non-disabled next link exists
"nextPageUrl": "https://www.amazon.com/s?k=laptop&page=2&...", // absolute URL of next page, or null
"totalResultsApprox": 100000, // parsed from "1-16 of over 100,000 results", or null
"itemCount": 16, // number of cards found on this page
"items": [
{
"asin": "B09S3HNMHF", // 10-char Amazon Standard Identification Number
"uuid": "d319ac5e-6161-4e4d-8ae5-1c63b8748308", // per-render tracking id, null when absent
"positionIndex": 3, // data-index attribute, indicates ordinal position in results
"title": "Samsung 14\" Galaxy Chromebook Go ...", // product title from h2 span
"url": "https://www.amazon.com/.../dp/B09S3HNMHF/...", // absolute product detail URL
"image": "https://m.media-amazon.com/images/I/51...jpg", // thumbnail from img.s-image
"imageAlt": "Samsung 14\" Galaxy Chromebook ...", // truncated title from img alt
"price": {"value": 179.99, "currencyRaw": "$", "raw": "$179.99"}, // current price, null when no offer
"listPrice": {"value": 190.99, "currencyRaw": "$", "raw": "$190.99"}, // strike-through list price, null when absent
"stars": 4.3, // 0-5 rating, null when no reviews
"reviewCount": 632, // ratings count, null when no reviews
"ratingRaw": "4.3 out of 5 stars, rating details",
"badges": [{"label": "Overall Pick", "supp": null}], // all badges (Amazon's Choice, Best Seller, Overall Pick, deal labels)
"isAmazonChoice": true, // derived from badge text
"isBestSeller": false, // derived from badge text
"isSponsored": false, // true when sponsored ad label present
"delivery": "FREE delivery Fri, Jul 10", // primary delivery message, null when absent
"boughtInPast": "6K+ bought in past month" // social proof, null when absent
}
]
}
Pagination
URL Pagination: Amazon SERP uses ?page={N} query parameter, starting at 1. To iterate:
- After extracting current page, use
nextPageUrlfrom the output (already absolute) OR construct via URL: append/replace&page={N+1} navigate {nextPageUrl}→wait stable→ re-run extraction script- Termination:
hasNextPage == falsein output, OR the same ASIN list is returned as the previous page (Amazon returns page 1 when the requested page is out of range)
Known Amazon SERP hard cap: for keyword-only searches, Amazon limits results to 7 pages (~112 items). Category-scoped URLs (bbn={node}&rh=n%3A{node}) can return more. Combining a category node with a keyword often yields more pages than keyword alone.
Success Criteria
response.itemCount >= 1 AND response.items[0].asin matches /^[A-Z0-9]{10}$/
Known Limitations
- Amazon caps keyword-only search to 7 pages (~112 items). Use category-scoped URLs to go deeper.
- Some cards (video ads, banner slots) may be excluded — this is intentional, the
[data-component-type="s-search-result"]selector only matches organic product cards. - Prices reflect the delivery country Amazon inferred from the browsing session; use a proxy in the target region for country-specific pricing.
boughtInPastand Amazon's Choice / Best Seller badges appear only on selected cards.positionIndex(data-index) is not sequential — Amazon interleaves promoted content, so index may skip.- Search of amazon.com with browser geolocation outside the US may show region-specific interstitials; if extraction returns
error: no search result cards found, verify no interstitial or verification challenge is blocking the page.
Execution Efficiency
- Batch orchestration: Write a bash script that iterates page numbers serially within a single session; do not parallelize inside one browser. Add a 3-6 second sleep between pages to stay within normal browsing cadence. For higher throughput, distribute pages across multiple parallel browser sessions — each session maintains independent browser context and network state, so request volume spreads naturally across sessions.
- Test before batch execution: After writing a batch script, first test with 1-2 pages before running the full crawl. Never skip testing.
- Reduce redundant pre-operations: If iterating multiple keywords, keep the browser session open across keywords — reuse the
browser opensession and justnavigatebetween URLs. - Error resumption: Persist page-level results (one JSON per page) so a partial crash can resume from the failed page.
Experience Notes
Path: {working-directory}/browser-act-skill-forge-memories/amazon-scraper-amazon-search-listing.memory.md (working directory is determined by the Agent running the Skill, typically the project root or current working directory)
Before execution: If the file exists, read it first — it records unexpected situations encountered during past executions (e.g., a strategy has become ineffective); adjust strategy order accordingly.
After execution: If an unexpected situation is encountered (strategy became ineffective, page redesigned, anti-scraping upgraded, better path discovered), append a line:
{YYYY-MM-DD}: {what happened} → {conclusion}
Normal execution does not write to the file. Do not record what keywords were used or how many results were returned — those are task outputs, not experience.
Frequently asked questions about Amazon Search Listing
Similar skills
Power BI Semantic Modeling
Optimize your Power BI data models with best practices.
Data Context Extractor
Tailor data analysis skills to your company's needs.
Power BI Performance Troubleshooting
Systematic guidance for optimizing Power BI performance.
Power BI Model Design Review
Optimize your Power BI data models with expert reviews.
Power BI DAX Formula Optimizer
Optimize your DAX formulas for better performance and clarity.
Fabric Lakehouse
Optimize your data solutions with Lakehouse best practices.
