This tutorial shows how to scrape Amazon Spain reviews from amazon.es review pages into a CSV using the Amazon Spain Reviews Scraper template for UScraper. You will import the workflow, replace the sample ASIN review URLs, confirm the export path, run a small validation batch, and handle the common page states that make Amazon review scraping unreliable.
Before you start
Prerequisites and policy checks
You need UScraper installed as a local desktop app, a short list of amazon.es review URLs you are allowed to process, and a folder where CSV files can be written. Start with one to three ASIN review pages, not a large catalog. Amazon pages can vary by language, marketplace, session state, cookie consent, availability, and automated-access response.
Use review-page URLs that look like https://www.amazon.es/product-reviews/<ASIN>/?reviewerType=all_reviews&sortBy=recent&pageNumber=1. The template can loop through multiple URLs, but the first run should stay small so you can confirm that the browser sees real review cards before exporting a project dataset.
Also review Amazon's current policies before you collect or reuse review text. Public visibility does not automatically grant redistribution rights, and automated collection can be limited by terms, robots directives, copyright, privacy law, marketplace rules, and local regulation. If you need contractual access for a production integration, compare this browser workflow against Amazon's official Product Advertising API documentation and other approved partner routes.
Treat this tutorial as a supervised research workflow. Do not bypass CAPTCHA, sign-in walls, account-only pages, payment flows, or other access controls.
| Item | What to prepare | Why it matters |
|---|---|---|
| Review URLs | Approved amazon.es product-reviews pages | The workflow is built around review-page markup, not search results or seller dashboards. |
| Export folder | A project-specific local folder | Keeps test CSVs separate from client or production exports. |
| Validation sample | One ASIN with visible reviews | Lets you check selectors, pagination, and blank fields before scaling. |
| Policy notes | Terms, robots, and permitted use | Keeps collection scope separate from analysis and publication decisions. |
Workflow anatomy
What the Amazon Spain review scraper does
The companion JSON is a best-effort workflow for amazon.es review pages. Its core path is simple: Set Window Size -> Navigate -> Wait for Page Load -> cookie check -> CAPTCHA check -> scroll -> review-row check -> Structured Export -> pagination click -> Loop Continue.
The template uses a stable browser viewport, then opens each URL configured in the Navigate block. It waits for the page to load, clicks the cookie consent selector when it appears, and checks for common CAPTCHA indicators such as validateCaptcha, captchacharacters, or CAPTCHA images. If a challenge is detected, the workflow waits 90 seconds so it can be handled manually in the visible browser. If review rows still do not render, it skips the current URL and continues to the next input.
The bundle does not include a CSV sample, so the JSON export is the authoritative sample of the workflow definition. Structured Export uses div[data-hook='review'], customer_review-*, and related review selectors as row targets. It writes headers, uses append mode, and saves to the configured local folder.
| Output group | CSV fields | How to use it |
|---|---|---|
| Source context | asin, source_url, review_id, review_url | Deduplicate rows and trace records back to the original review page. |
| Reviewer | reviewer_name, reviewer_profile_url | Audit visible reviewer identity fields where Amazon exposes them. |
| Review content | rating, review_title, review_date, review_body | Build sentiment, issue tagging, and voice-of-customer analysis. |
| Purchase context | product_variant, verified_purchase, helpful_votes | Compare complaints by variant and prioritize higher-signal reviews. |
| Media | image_urls | Capture visible review image URLs for manual inspection. |
Runbook
How to scrape Amazon Spain reviews to CSV
Import the workflow
Open the Amazon Spain Reviews Scraper template, download the JSON, and import it into UScraper.
Replace the sample URLs
In the Navigate block, replace the sample amazon.es review pages with the ASIN review URLs you are allowed to collect. Keep reviewerType=all_reviews, sortBy=recent, and pageNumber=1 when those parameters match your analysis plan.
Keep the waits
Leave the load waits, cookie check, CAPTCHA check, 90-second challenge wait, scroll step, and review-row check in place for the first run. They make the workflow slower, but they also protect the CSV from challenge-page rows.
Set the export path
In Structured Export, confirm amazon-spain-review-scraper.csv, headers, append mode, and the save folder. Use a clean folder for each project so test rows do not mix with final exports.
Run one ASIN first
Run a single review URL, open the CSV, compare three rows against the browser, then reconnect or expand the loop for the remaining URLs once the fields look correct.
After the first successful run, sort the CSV by asin and review_id. A single review should have one review ID and one source URL. If rows duplicate, check whether the same input URL was pasted twice or whether a run was restarted after append mode had already written rows.
Validation
Validate review rows before analysis
Amazon review pages are dynamic enough that validation should be part of the workflow, not a cleanup afterthought. Keep the browser and CSV side by side. Check one row from the first page, one row after pagination, and one row from the last ASIN in the batch.
| Symptom | Likely cause | Fix |
|---|---|---|
| CSV has headers but no rows | Amazon returned a CAPTCHA, unavailable page, or layout without matching review rows | Watch the browser during one URL, handle allowed prompts, and rerun with the default waits. |
Missing asin | URL does not match the expected product-reviews/<ASIN> pattern | Replace the input with a canonical review-page URL. |
Blank review_body | Review text was collapsed, translated, hidden, or the selector changed | Open the row in the browser and refresh the review-body selector if the text is visible. |
| No pagination | Amazon did not expose an active next-page control | Confirm the ASIN has enough visible reviews and that the page is not filtered too narrowly. |
| Mixed old and new rows | Append mode wrote into an existing CSV | Rename the output file or clear the prior export before the final run. |
For recurring research, keep a tiny audit log with the ASIN list, run date, CSV filename, export folder, template version, and any selector edits. That context is useful when a product manager, analyst, or legal reviewer asks where a row came from.
Alternatives
UScraper vs cloud scrapers vs Amazon APIs
UScraper is a good fit when you want a supervised local desktop workflow, visible browser QA, and a CSV you can inspect immediately. The tradeoff is that you own the run quality: you still need to check policy, handle page states, maintain selectors, and validate rows.
Cloud review scrapers from platforms such as Octoparse, Apify, Bright Data, Outscraper, or API providers can be better when you need hosted scheduling, managed infrastructure, proxy operations, or developer APIs. Those tools may also introduce account requirements, usage pricing, data custody questions, and a different debugging model.
Official Amazon API routes are the better starting point when your use case needs approved production access, product catalog integration, affiliate workflows, or contractual data rights. A browser export is easier to test for small research jobs, but it is not a substitute for approved access where policy, uptime, and redistribution rights matter.
| Path | Best for | Watch-outs |
|---|---|---|
| UScraper template | Local CSV research, small batches, analyst QA | Selector drift, CAPTCHA states, manual validation. |
| Hosted scraper | Scheduling, scale, API-driven pipelines | Usage cost, vendor custody, account setup, platform limits. |
| Official API | Approved production integration | Eligibility, available fields, policy requirements, implementation work. |
FAQ
Amazon Spain review scraper FAQ
Amazon Spain reviews may be publicly visible, but automated collection can still be limited by Amazon terms, robots directives, marketplace policy, copyright, privacy law, and local regulations. Use modest runs, avoid bypassing access controls, and get legal review before commercial reuse.
Next step
Download the Amazon Spain review scraper template
Use the Amazon Spain Reviews Scraper to CSV template as the download path, then keep this tutorial open while you configure URLs, export location, and validation checks. For adjacent workflows, browse the UScraper template library, compare other review templates, or read more tutorials on the UScraper blog.