Direct Answer
To scrape ImmobilienScout24 market data, collect only public listing fields — asking price, size in m², rooms and region — through a real German mobile proxy, then aggregate them into market metrics such as average €/m² by district. Poll slowly, honour robots.txt, and never collect or store personal data like agent names or contact details. This is public-market research on aggregate data, not a way around access protection.
[!WARNING]
Public, non-personal market data only. This guide covers collecting publicly visible listing fields and aggregating them into market metrics. Respect ImmobilienScout24'srobots.txtand terms, do not circumvent access protections, and never collect or store personal data (agent names, phone numbers, email addresses). For legitimate market research — nothing more. (General information, not legal advice.)
Why ImmobilienScout24 Market Data Is Worth Collecting
For a data engineer working on alternative data, German residential real estate is a rich, structured signal. ImmobilienScout24 is the largest German property portal, and its public listings carry exactly the fields that turn into a market model: asking price, living area in m², number of rooms, property type and the region or district a listing sits in. Aggregate enough of those and you can compute average €/m² by district, track how asking prices shift over a quarter, or compare rental yields across cities.
The value is in the aggregate, not the individual listing. You are not interested in who is selling — you are interested in what the market is doing. That framing is not just cleaner ethics; it is the whole safe corridor for this kind of work, and it is what keeps the pipeline both lawful and low-friction. Once you decide up front that the output is a district-level metric and never a person, most of the compliance questions answer themselves.
This is the same discipline behind our guides on scraping Amazon.de price data and comparing prices across idealo and Geizhals: collect public data carefully, keep it non-personal where you can, and let the aggregate drive the decision.
Collect Only Public, Non-Personal Fields
Draw a hard line before you write a single selector. The table below is the rule this guide follows.
| Field | Collect? | Why |
|---|---|---|
| Asking price (EUR) | Yes | Public, the core market signal |
| Living area (m²) | Yes | Public, needed for €/m² |
| Number of rooms | Yes | Public listing attribute |
| Property type (flat, house) | Yes | Public, segments the market |
| Region / district / postcode area | Yes | Public, the aggregation key |
| Listing date | Yes | Public, drives trend analysis |
| Agent or seller name | No | Personal data — out of scope |
| Phone number, email, contact form | No | Personal data under GDPR |
| Photos of people, private descriptions | No | May carry personal data |
| Anything behind a login | No | Not public — never |
Everything on the "Yes" side is a non-personal market fact. Everything on the "No" side either identifies a person or sits behind an access protection. Under the GDPR, agent names and contact details are personal data — collecting or storing them for market research is both unnecessary and a liability, so drop them at the parsing stage, not later. When your dataset is nothing but prices, sizes, rooms and regions keyed by district, you have removed the single biggest legal risk in the whole project.
If you are new to where these lines fall in the EU, is web scraping legal in the EU and our ethical web-scraping checklist are worth reading before you start.
The Legal Reality, Honestly
Here is the situation in plain terms. Scraping public data is generally permissible in Germany as long as you do not circumvent access protections — you are reading pages that any visitor can load. That is the good news, and it is why the public-listing corridor exists at all.
But three real limits sit alongside it. First, ImmobilienScout24's terms of service restrict automated use regardless of whether the data is public, so a large automated run can breach the contract you accept by using the site. Second, database rights (the EU's sui generis database protection) can apply to bulk extraction of a substantial part of a structured collection — pulling the entire catalogue is a different legal question from sampling a district. Third, the GDPR governs any personal data, which is exactly why the non-personal, aggregate framing above matters so much.
The practical conclusion: keep to public, aggregate, non-personal data, sample rather than exhaustively mirror, respect the terms and robots.txt, and you stay inside the corridor that is defensible. This is general information, not legal advice — for a specific project, get your own.
Why a German Mobile IP, and Why Aggressive Requests Get Blocked
ImmobilienScout24 is bot-protected, and it should be — a portal that large has to defend itself against abusive traffic. Understanding why the protection reacts is the difference between a pipeline that runs quietly for months and one that gets throttled on day one.
Bot protection responds to volume and pattern, not intent. A burst of fast, identical requests coming from a datacenter IP range that already has low reputation looks exactly like abuse, so it gets rate-limited, served a challenge, or blocked outright. Nothing about "bypassing" enters into it — the site is simply doing pattern-matching, and aggressive traffic matches the abuse pattern.
Two things move you out of that pattern, and neither is a trick:
- A clean, dedicated German mobile IP. A real German mobile connection sits behind CGNAT, shared by thousands of ordinary subscribers, so it carries the reputation of normal mobile traffic rather than a flagged datacenter range. A dedicated endpoint means that reputation is not being spent by anyone else's jobs. It is also region-true: a German portal serves German visitors the pages you actually want.
- A slow, polite cadence. Space your requests out — a few per minute, not a flood — cache what you already have, and never hammer the same path. Polite pacing keeps you below the thresholds that trigger protection in the first place, and it is kinder to the target server.
Good manners plus a trusted IP reduce blocks because together they make your traffic indistinguishable from what it actually is: a modest, well-behaved German visitor reading public pages. That is the legitimate path. There is no honest "bypass" here, and you do not need one.
A Responsible Collection Recipe
Put the pieces together into a repeatable, polite pipeline:
- Read
robots.txtfirst. If a path is disallowed, it is out of scope — full stop. - Route through a dedicated German mobile endpoint. Point your HTTP or SOCKS5 client at the host, port and credentials from your dashboard. There is no hardware — it is an IT-routing proxy service that gives your requests a real German mobile IP.
- Sample, don't mirror. Pull a representative slice per district on a schedule; you rarely need the whole catalogue, and sampling stays clear of database-right concerns.
- Parse only the market fields. Extract price, m², rooms, type, region and date. Discard everything that could identify a person at the parsing step, before it ever reaches storage.
- Pace slowly and keep a sticky session across a multi-page district crawl, so one German IP carries the run; rotate between separate jobs.
- Aggregate immediately. Roll listings up into district-level metrics — average €/m², median asking price, count per property type. The aggregate is your product; individual rows are just an intermediate step.
- Fetch HTML only where you can, skip images, and cache so you never re-request a page within the hour. This keeps you comfortably inside the fair-use 20 GB/day allowance.
The result is a clean panel of German real-estate market metrics, built from public data, holding no personal data, and collected at a cadence the portal barely notices.
From One Portal to a Market Model
ImmobilienScout24 is one source. The same disciplined setup — public fields only, aggregate output, a clean German mobile IP, polite pacing — extends naturally to cross-checking other German property portals or feeding a broader alternative-data model. Because the reputation problem is solved by a real German mobile connection rather than by datacenter ranges that get blocked, the same pipeline scales across regions without a running battle with bot protection.
Keep the corridor narrow on purpose: public, non-personal, aggregate, polite. That is not a limitation on the work — it is what makes the dataset both trustworthy and sustainable.
FAQ
Is it legal to scrape ImmobilienScout24 in Germany?
Collecting publicly visible listing data is generally regarded as permissible in Germany when you do not circumvent access protections and keep to non-personal fields. But ImmobilienScout24's terms restrict automated use, database rights can apply to bulk extraction, and GDPR governs any personal data. Keep to public, aggregate, non-personal market fields, sample rather than mirror the whole catalogue, and get your own legal advice — see the EU legal view on web scraping for the background. This is general information, not legal advice.
What ImmobilienScout24 data can I collect without touching personal data?
Stick to non-personal market fields: asking price, size in m², number of rooms, property type, listing region or district, and the listing date. Aggregate these into metrics like average €/m² per district. Do not collect or store agent names, phone numbers, email addresses, or any other data that identifies a person — that is personal data under GDPR and it is unnecessary for market research. Our ethical web-scraping checklist covers where to draw the line.
Why does ImmobilienScout24 block aggressive scrapers, and how do I avoid it?
Bot protection reacts to volume and pattern, not intent: a burst of fast, identical requests from a low-reputation IP range looks like abuse and gets throttled or blocked. The reliable path is a clean, dedicated German mobile IP, a slow polite cadence and honouring robots.txt — good manners plus a trusted IP, never a way around the protection itself. See why datacenter proxies get blocked for the mechanism.
Related guides
- Scrape AutoScout24 Car-Market Data Without Getting Blocked
- Scrape OTTO.de and Zalando Data with a German Mobile Proxy
- How to Scrape Google Maps Business Data in Germany
- How to Scrape Indeed and StepStone Job Data in Germany
Build a Clean German Real-Estate Panel
Real German 5G mobile IPs, dedicated or shared, with HTTP/SOCKS5, sticky sessions and on-demand rotation — fair-use 20 GB/day, from a transparent EU-based provider. The right vantage point for polite, public, aggregate market research — browse the German mobile proxy plans.
Telegram Support — @germanproxy_io_bot
Get a German mobile proxy: Real 4G/5G IPs from Germany, fair-use 20 GB/day — compare German mobile proxy plans or try a shared 5G German proxy.