CZ Reality Scraper

What does CZ Reality Scraper do?

CZ Reality Scraper is a public property-listing extractor for Sreality and Bezrealitky. It extracts visible listing facts and does not require an account or private endpoint.

Why scrape Czech property portals?

Use structured listings for market research, comparable-property analysis, rental monitoring, and lead qualification. Select one or both portals, filter by sale/rent, category, region, price, and floor area, and optionally keep a local price history between runs. Apify adds scheduling, API access, exports, monitoring, and integrations.

What data can it extract?

Field	Type	Description
sourceId, title, url, sourceUrl, canonicalUrl, portal	string	Normalized public listing identity, canonical URL, and source portal.
source, sourceDomain, scrapedAt	string/date-time	Source and provenance for the public observation.
price, currency, area	number/string	Observed price and area values.
category, offerType, propertyType	string	Public classification fields.
locality, region, latitude, longitude	string/number	Visible location information.
images	array	Absolute public image URLs.
priceChanged, previousPrice, daysTracked	mixed	Optional local history indicators.
scrapedAt	date-time	Time the public observation was normalized.

How to scrape Sreality or Bezrealitky

1. Choose portals, categories, and offerType in the Input tab, or provide exact public startUrls for individual Sreality or Bezrealitky listing/detail pages.
2. Add optional regions, maxPrice, or minArea filters.
3. Set maxListings and run the Actor.
4. Download the dataset as JSON, CSV, Excel, or HTML, or call it through the API.

You can download the dataset in various formats such as JSON, HTML, CSV, or Excel.

Cost and performance

The Actor uses standard Apify compute units. Keep maxListings bounded and schedule only as often as your market-monitoring use case requires.

Input and output

See the input tab for full configuration options. A listing row resembles:

{
  "sourceId": "cz-reality:sreality:42",
  "sourceDomain": "www.sreality.cz",
  "canonicalUrl": "https://www.sreality.cz/detail/42",
  "source": "cz-reality",
  "portal": "sreality",
  "id": "42",
  "title": "Byt 2+1",
  "url": "https://www.sreality.cz/detail/42",
  "sourceUrl": "https://www.sreality.cz/hledani/prodej/byty",
  "scrapedAt": "2026-09-17T00:00:00.000Z"
}

If a portal blocks a public request, an exact diagnostic row with recordType: "diagnostic", diagnosticType, source/final URL provenance, sourceDomain, error, errorCode, and scrapedAt explains the boundary instead of inventing listings. Exact startUrls are limited to HTTPS on the two official portal hosts and are useful when a public detail page is available while a generated search page is not.

Normal listing rows contain business and source fields only; instrumentation is not part of the active dataset contract. Requests stay public; proxyConfiguration optionally enables standard Apify Proxy routing and OUTPUT_SUMMARY reports whether it was used. No reader service, login, or access-control bypass is attempted.

For local verification, set testMode with a safe relative fixtureFile or bounded fixtureJson. Fixture mode never contacts either portal.

FAQ, disclaimers, and support

Only public listing information is collected. Respect each portal's terms, robots guidance, rate limits, and applicable law. Public pages can contain personal data; do not process it without a legitimate reason. Use the Issues tab for feedback and the API tab for programmatic access.