This tutorial shows how to scrape Idealista listings in Italy into CSV with UScraper. You will import the Idealista real estate listing scraper Italy template, replace the sample results page, validate the export fields, and decide when official API access is a better fit.
Before you start
Prerequisites for scraping Idealista listings
You need UScraper installed as a local desktop app, a folder for CSV output, and one Idealista.it results page you are allowed to review. Start from the official Idealista Italy site, apply your city, sale or rent, category, and budget filters in the browser, then copy the final results URL into the workflow.
The maintained download path is the Idealista real estate listing scraper Italy template page; keep this article open as the operational checklist while you run the workflow.
Before automation, review Idealista's current robots.txt, general terms, and your own data-use policy. If your project needs approved programmatic access rather than a supervised CSV export, the official Idealista API access request is the route to evaluate first.
Technical access is not permission. Keep runs modest, collect only fields you actually need, stop when a challenge appears, and use official or partner routes when you need contractual data rights.
Workflow shape
How the Idealista listing scraper works
The JSON workflow is the source of truth. It starts with a sample Verona rental URL, waits for listing rows, exports data from article.item[data-element-id], article.item, checks for a next-page control, clicks it, waits again, and loops back into the same export block.
CSV
13
Successivo
1 page
Local
| Workflow block | Purpose | What to verify |
|---|---|---|
| Navigate | Opens the configured Idealista.it results URL | City, category, rent or sale, and filters are correct. |
| Wait and sleep | Gives the page time to render listing cards | The browser shows real listings, not a challenge page. |
| Element Exists | Confirms listing rows are present | False branch should end cleanly when rows are unavailable. |
| Structured Export | Appends one CSV row per visible card | Headers, save folder, append mode, and field mapping are correct. |
| Next click | Follows Successivo pagination | The URL and visible listings change before the next export. |
Runbook
How to scrape Idealista listing pages to CSV
Import the template
Open the Idealista real estate listing scraper Italy template page, download the JSON, and import it into UScraper.
Set the results URL
Replace the sample https://www.idealista.it/affitto-case/verona-verona/ URL with your approved search results page.
Confirm access
Open the same URL in the browser session. Continue only when listing cards, prices, and detail links are visible.
Check the export path
In Structured Export, confirm crawler-lista-immobili-idealista.csv, headers enabled, append mode, and the project folder.
Run one page
Compare exported rows against the browser: title, price, locality, detail URL, description, image URL, and visible detail chips.
Continue pagination
Let the next-page loop run only after the first page passes QA. Watch for repeated pages, blank rows, or access prompts.
Because file mode is append, reruns add rows to the same CSV. Use a dated output folder or clear the file before repeating the same search.
Output
CSV fields from Idealista listing pages
The bundle does not include a static CSV sample. Use the export shape summary below together with the JSON workflow definition: the JSON controls the selectors, while your first validation run proves those selectors still match the live page.
crawler-lista-immobili-idealista.csvColumn
url
Current Idealista results page URL.
Column
vendita_o_affitto
Sale or rent label inferred from the URL path.
Column
categoria
Broad category such as homes, garages, land, offices, or commercial spaces.
Column
localita
Readable locality derived from the Idealista URL slug.
Column
titolo_appartamento
Visible listing-card title.
Column
dettagli_appartamento_url
Property detail URL for manual review or detail-page extraction.
Column
prezzo
Displayed price text.
Column
dettagli_1
First visible listing detail.
Column
dettagli_2
Second visible listing detail.
Column
dettagli_3
Third visible listing detail.
Column
dettagli_4
Fourth detail or visible update label when present.
Column
descrizione
Description snippet from the result card.
Column
immagine_url
First listing image URL normalized against the page.
| QA symptom | Likely cause | Fix |
|---|---|---|
| No rows exported | Listing cards did not render, access was blocked, or the search returned no results | Resolve the browser state, reduce scope, and rerun one page. |
| Same rows repeat | Pagination did not advance before the next export | Check the Successivo selector and increase the wait after click. |
| Blank price or title | Selector drift or a different listing-card variant | Inspect the live card and update Structured Export columns. |
| Detail URL is missing | The card did not expose a.item-link | Treat the row as incomplete and validate manually before use. |
API or scraper
Idealista API alternative vs no-code scraper
Searches for idealista api alternative, idealista scraper python, and best Idealista scraper usually split into three paths. The right choice depends on whether you need a quick spreadsheet, a maintainable coded crawler, or an approved data integration.
Use UScraper when an analyst needs local CSV output, visible workflow blocks, editable selectors, and a supervised run against selected Idealista.it result pages.
Hosted tools and scraper APIs can also fit. Apify actors, Octoparse templates, ScrapingBee-style APIs, and proxy-backed scraping services are useful when you want cloud scheduling, API delivery, or vendor-managed infrastructure. UScraper is better when the operator wants a local desktop workflow they can inspect before exporting a CSV.
Frequently asked questions
Idealista listing pages may be publicly visible, but automated collection can still be restricted by Idealista terms, robots directives, database rights, privacy law, anti-abuse systems, and local real estate rules. Review current source rules, avoid bypassing access controls, keep runs modest, and get legal review before commercial reuse.