This tutorial shows how to scrape Amazon Italy product listings from Amazon.it keyword search results into CSV with the Amazon Italy Product Scraper for CSV Export template for UScraper. You will import the workflow, change the keyword, choose an export folder, run one validation page, and audit ASIN, title, sponsored flag, price, rating, review count, image URL, keyword, and page number before collecting more rows.
Before you start
Prerequisites and source checks
You need UScraper installed, the free JSON template, one Amazon.it keyword you are allowed to research, and a local folder where CSV files can be written. The bundled workflow starts with the keyword baby monitor and the Amazon.it search URL https://www.amazon.it/s?k=baby+monitor&page=1. Treat that as a placeholder, not a production data source.
This guide covers supervised collection from visible search result pages. It does not cover sign-in pages, seller dashboards, order data, checkout flows, CAPTCHA solving, or access-control bypassing. Before any commercial use, review Amazon's current terms, robots directives, and your own legal basis for collection.
Technical access is not permission. Keep the browser visible during early runs, avoid bypassing restrictions, document why the data is being collected, and use official or licensed routes when the dataset will feed a production product.
Workflow shape
What the Amazon Italy product scraper does
The Amazon Italy product scraper template is a keyword listing workflow, not a full product-detail crawler. It opens an Amazon.it search page, waits for loading, checks for automated-access signals, waits for real product result cards, exports each card, then checks whether the Next pagination link is enabled.
The JSON export is the authoritative workflow definition. In plain English, its main path is:
{
"startUrl": "https://www.amazon.it/s?k=baby+monitor&page=1",
"captchaCheck": "form[action*='/errors/validateCaptcha'], input[name='amzn-r']",
"rowSelector": "div[data-component-type=\"s-search-result\"][data-asin]:not([data-asin=\"\"])",
"fileName": "crawler_elenchi_prodotti_amazon.csv",
"fileMode": "append",
"nextButton": "a.s-pagination-next:not(.s-pagination-disabled)",
"stopBehavior": "end the run if CAPTCHA appears or no enabled Next button exists"
}
Runbook
How to configure the Amazon.it listing scrape
Download and import
Open Amazon Italy Product Scraper for CSV Export, download the JSON template, and import it into UScraper.
Change the keyword
In the Navigate block, replace baby+monitor with your approved Amazon.it search term. Keep the marketplace on amazon.it unless you are intentionally creating a separate country workflow.
Set the export location
In Structured Export, change the save folder to your project directory. The bundled filename is crawler_elenchi_prodotti_amazon.csv, headers are enabled, and append mode is used.
Run one page first
Start with page 1 and watch the browser. Confirm that product cards load before export and that the run stops cleanly if Amazon shows an automated-access page.
Validate before scaling
Open the CSV and compare several rows against the visible Amazon.it page. Continue pagination only after ASIN, title, price, review count, sponsored flag, and page number look correct.
Output
CSV columns and validation checks
The workflow writes one row per visible Amazon.it search result card. Column names follow the bundled Italian template labels, so downstream spreadsheets can keep the marketplace context and source query with every product row.
| Column | What it captures | How to validate it |
|---|---|---|
sito | Fixed marketplace label, Amazon.it | Check that mixed-marketplace runs did not land in the same file. |
codice_postale | Postal-code context stored by the workflow | Confirm the value matches the browser context you expect. |
parola_chiave | Keyword parsed from the current URL | Compare the CSV value with the k= parameter in the address bar. |
pagina_attuale | Current search results page | Check page 1 and one later page before trusting pagination. |
titolo_prodotto | Visible product title | Compare long titles for truncation or missing variants. |
sponsorizzato | Sponsored placement flag | Spot-check rows with visible Sponsored or Sponsorizzato labels. |
product_page and asin | Detail-page URL and ASIN | Open two sample URLs and confirm the ASIN matches the listing row. |
valutazione and quantita_valutazioni | Rating text and review count | Expect blanks when Amazon does not render rating data for a card. |
prezzo_attuale and prezzo_consigliato | Current and list price text | Verify currency, decimal format, and blank price cases. |
pagina_recensioni_url and imagine_url | Review anchor and image URL | Open a sample link only after confirming the product URL is correct. |
sito,codice_postale,parola_chiave,pagina_attuale,titolo_prodotto,sponsorizzato,product_page,asin,valutazione,quantita_valutazioni,prezzo_attuale,prezzo_consigliato,imagine_url
Amazon.it,16129,baby monitor,1,Baby Monitor Video con Telecamera HD,false,https://www.amazon.it/dp/B0ITEXAMPLE1,B0ITEXAMPLE1,"4,4 su 5 stelle",1284,"59,99 EUR",,"https://m.media-amazon.com/images/I/example.jpg"
Troubleshooting
Common issues during an Amazon.it listing scrape
Alternatives
Desktop scraper, API, or code?
Amazon scraping tools solve different jobs. A local desktop scraper is useful when an analyst needs to inspect the rendered search page, keep a small CSV locally, and adjust a no-code workflow. An Amazon scraper API can be better when your application needs hosted infrastructure, response normalization, retries, and an API-shaped contract. The Product Advertising API or other official routes are the right starting point when your use case needs approved programmatic access and compliant reuse terms.
| Approach | Best for | Trade-off |
|---|---|---|
| UScraper template | Supervised keyword research, spreadsheet exports, no-code editing, local custody | You still need to validate source permissions, layout changes, and access checks. |
| Scraper API provider | Backend integrations, managed retries, normalized responses | Usually subscription-based and sends requests/data through a third-party service. |
| Python or Scrapy script | Developer-controlled pipelines and custom enrichment | Requires maintenance when Amazon markup, prompts, or anti-abuse behavior changes. |
| Official product-data API | Approved programmatic access and production use | Access, fields, locale support, and reuse terms are governed by the API program. |
For a first Amazon.it keyword research export, start with the template. For broader ecommerce workflows, browse the UScraper template library, then use the UScraper blog for runbooks, comparisons, and use-case guides.
FAQ
FAQ
Is it legal to scrape Amazon Italy product listings?
Amazon.it listings may be publicly visible, but automated collection can still be restricted by Amazon terms, robots directives, anti-abuse controls, intellectual property rights, privacy law, and local rules. Do not bypass CAPTCHA, login walls, account controls, or access restrictions, and get legal review before commercial reuse.
Do I need an Amazon Product Advertising API key?
No Product Advertising API key is built into this workflow. The template opens visible Amazon.it search result pages in the desktop app browser and exports fields from rendered listing cards. Use official or licensed API routes when your use case requires contracted access or production integration.
What does the Amazon Italy product scraper export?
The workflow writes crawler_elenchi_prodotti_amazon.csv with columns for sito, codice_postale, parola_chiave, pagina_attuale, titolo_prodotto, sponsorizzato, product_page, asin, valutazione, quantita_valutazioni, pagina_recensioni_url, prezzo_attuale, prezzo_consigliato, and imagine_url.
Where does the CSV file get saved?
The save location is controlled by the Structured Export block. Change the bundled local folder before running client, category, or keyword-specific batches so append-mode rows land in the right project directory.
Why did the scraper return zero rows or blank prices?
Zero rows or blank prices usually mean Amazon served a different layout, delayed product cards, showed an automated-access page, hid prices for the session, returned CAPTCHA, or changed markup. Inspect the browser and rerun one page before editing selectors or scaling.