This tutorial shows how to scrape Amazon search results by keyword into CSV with the Amazon Product Scraper by Keywords template for UScraper. You will import the workflow, edit the search term, confirm the export path, run a one-page validation pass, and decide when an API or hosted scraper is a better fit.
Before you start
Prerequisites and Amazon policy checks
You need UScraper installed as a local desktop app, the free JSON template, one approved keyword to test, and a folder where CSV exports can be written. The bundled workflow is configured for Amazon.de, the keyword Sportschuhe, English-language search results, and a best-effort ZIP setup for Berlin. Treat those as editable defaults, not fixed requirements.
Review Amazon's Conditions of Use and current robots.txt before automating. This guide is for supervised research from pages you can inspect in a browser. It is not for bypassing CAPTCHA, account controls, checkout flows, private seller dashboards, or anti-abuse systems.
Technical access is not the same thing as permission. Keep batches modest, collect only fields you need, document why the dataset exists, and get legal review before commercial reuse or redistribution.
Workflow shape
What the Amazon keyword scraper does
The JSON workflow is the authoritative sample for this post. In plain English, it does five things: opens Amazon, handles the location prompt when it appears, navigates to a keyword search URL, runs Structured Export over product cards, and loops through the enabled Next button.
| Workflow block | Purpose | What to check |
|---|---|---|
| Navigate and wait | Opens Amazon.de, then the keyword URL | Confirm marketplace, language, keyword, and delivery context. |
| Location setup | Clicks the location control and enters 10243 when the ZIP field exists | Disable or edit this if location is not part of your research. |
| Product-card wait | Waits for s-search-result rows with ASINs | Stop if the page shows CAPTCHA, sign-in, or an empty layout. |
| Structured Export | Appends one CSV row per visible result card | Verify headers, file name, save folder, and append mode. |
| Pagination loop | Checks for a.s-pagination-next:not(.s-pagination-disabled) | Continue only when page number and URL advance correctly. |
The export is search-result data, not full product-detail data. It is useful for keyword visibility, assortment snapshots, quick price checks, review-count screening, and product discovery before deeper ASIN research.
Runbook
How to scrape Amazon product search results to CSV
Import the template
Open Amazon Product Scraper by Keywords, download the JSON, and import it into UScraper.
Edit the keyword URL
In the keyword Navigate block, replace Sportschuhe with the search term you are allowed to review. Preserve marketplace, language, and location assumptions when they matter.
Confirm location behavior
The sample workflow tries a ZIP setup when Amazon exposes the location popover. Remove or adjust that path if your analysis should not use Berlin delivery context.
Set the CSV destination
In Structured Export, confirm amazon-produkt-scraper-mit-schluesselwoerter.csv, headers enabled, append mode, and a project-specific save folder.
Run one page and pause
Compare several exported rows against the browser: product title, ASIN, rating, review count, current price, original price, product URL, image URL, badge, and delivery text.
Continue pagination
Let the Next loop continue only after the first page passes QA. Watch for repeated pages, blank exports, verification screens, or sudden region changes.
Output
CSV columns from the Amazon product search scraper
The bundle does not include a static CSV sample. Use the workflow export shape and your first validation run as the sample for the marketplace, keyword, and delivery context you actually collected.
| CSV column | Meaning | QA note |
|---|---|---|
webseite | Marketplace hostname, such as Amazon.de | Confirms which marketplace rendered the row. |
adresse | Visible delivery or location text | Useful when prices or delivery vary by region. |
schluesselwort | Keyword from the current search URL | Check that URL encoding did not change the intended term. |
seite | Result page number | Required for ranking and pagination review. |
produktname, produktseite, asin | Product identity fields | Dedupe by ASIN when product cards repeat across pages. |
badge | Visible badge or sponsored-style label when present | Expect blanks when Amazon renders no badge. |
kundenbewertung, anzahl_der_bewertungen, rezensionsseite | Rating and review signals | Compare several rows against the visible card before reporting. |
aktueller_preis, urspruenglicher_preis | Current and struck-through price text | Price modules can be hidden or delayed. |
bild, gratis_lieferung | Image URL and delivery text | Delivery wording is locale-specific and may need selector tuning. |
The fastest validation check is sorting the CSV by seite and scanning for empty produktname or repeated first-page rows. If either appears, stop the run and inspect the browser before collecting more pages.
API fit
Amazon Product Advertising API vs scraper workflow
Searchers often compare an Amazon product search scraper with Amazon Product Advertising API, SerpApi, Scrape.do, Bright Data, Apify, Octoparse, or a Python script. The right choice depends on whether you need a spreadsheet, a production API, or managed scraping infrastructure.
Use UScraper when the job is analyst-led, CSV-first, and small enough to supervise. The workflow is local, inspectable, and easy to edit without writing scraper code.
For a quick research CSV, start with the UScraper template library. For a production catalog feed, compare official API access and managed providers before building a long-running scraper.
Troubleshooting
Common issues when scraping Amazon keyword results
| Symptom | Likely cause | Fix |
|---|---|---|
| No product rows exported | CAPTCHA, bot check, sign-in gate, regional redirect, or selector drift | Stop, inspect the browser, and do not try to bypass access controls. |
| Product names are blank | Amazon changed the card title markup or the page did not finish rendering | Increase waits, rerun one page, then update the selector if needed. |
| Prices are missing | No visible price, unavailable item, delayed module, or location-dependent price | Keep blanks when the browser has no price; do not invent values. |
| Pagination repeats page one | The Next click fired before navigation completed | Add wait time and confirm the URL or selected page number changes. |
| Ratings do not match | Locale text or review module changed | Compare live cards and update the extraction pattern for that marketplace. |
FAQ
Amazon keyword scraper FAQ
Amazon search results may be visible in a browser, but automated collection can still be restricted by Amazon conditions of use, robots directives, anti-abuse systems, intellectual property rights, privacy law, and local regulations. Review the current source rules, avoid bypassing CAPTCHA or access controls, keep batches modest, and get legal review before commercial reuse.
Next step
Download the Amazon product scraper by keywords template
Use Amazon Product Scraper by Keywords as the download path, then keep this tutorial open while you validate the first CSV. For adjacent workflows, browse all UScraper templates or return to the UScraper blog for more scraper tutorials.