Firmy.cz Scraper — Czech Business Directory, Contacts

Extract Czech business listings from Firmy.cz (the leading Czech business directory, operated by Seznam.cz).

What you get

Field	Description
id	Firmy.cz premise ID
name	Business name
category	Primary business category (Czech)
phone	Phone number
email	Email address
website	Business website (clean, no UTM params)
street	Street address
city	City / district
postalCode	5-digit Czech postal code
lat / lng	GPS coordinates
rating	Rating score 0–100 (Firmy.cz scale)
reviewCount	Number of reviews
openingHours	Opening hours string
description	Business description
businessUrl	Canonical Firmy.cz listing URL

Use cases

• B2B lead generation in Czechia — phone + email lists by category and city
• Market research — find competitors, suppliers, service providers
• Sales prospecting — restaurants, contractors, dentists, law firms, etc.

Input

{
  "query": "restaurace",
  "locality": "Praha",
  "maxItems": 100,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": ["RESIDENTIAL"],
    "apifyProxyCountry": "CZ"
  }
}

Parameter	Required	Default	Description
query	Yes	—	Czech keyword (e.g. restaurace, instalatér, zubař)
locality	No	—	City or region (e.g. Praha, Brno). Leave empty for nationwide.
maxItems	No	100	Max results. 0 = all available.
proxyConfiguration	No	RESIDENTIAL/CZ	Apify proxy settings.

Output sample

{
  "id": "12345678",
  "name": "Restaurace U Zlatého Kohouta",
  "category": "Restaurace",
  "phone": "+420 222 111 000",
  "email": "info@kohoutu.cz",
  "website": "https://www.kohoutu.cz",
  "street": "Václavské náměstí 15",
  "city": "Praha 1",
  "postalCode": "11000",
  "lat": 50.0808,
  "lng": 14.4259,
  "rating": 84,
  "reviewCount": 312,
  "openingHours": "Po–Pá 11:00–23:00, So–Ne 12:00–23:00",
  "description": "Tradiční česká kuchyně v centru Prahy.",
  "businessUrl": "https://www.firmy.cz/detail/12345678-restaurace-u-zlateho-kohouta-praha.html",
  "parse_confidence": 0.97
}

Pricing

Pay-per-result: $2 per 1 000 businesses extracted.

Technical notes

• Scrapes Firmy.cz search results (SSR HTML with embedded JSON-LD) + detail pages
• Access: lightweight HTTP requests — no heavy browser needed; handles the CMP consent gate automatically
• Polite 1.2s delay between requests
• RESIDENTIAL CZ proxy recommended for cloud runs

More scrapers from our toolkit

Building a data pipeline? These actors pair well with this one — each runs on your own Apify account with the same pay-per-result pricing, no subscription:

• Gelbeseiten Directory
• Google Maps Leads
• Google Maps Scraper
• Hiring Signal Monitor
• Linkedin Profile Scraper
• PagesJaunes Directory Scraper

Chain any of them together from the Integrations tab (the Run succeeded trigger) to build a multi-step workflow — one actor's output feeds the next.

Usage statistics

This Actor creates a small, content-free summary at the end of each run. It is used only to monitor reliability and improve this Actor. A copy is saved as USAGE_STATS in your own Apify key-value store, so you can see the exact record created for your run.

Set disableUsageStats to true in the input to opt out. Nothing is sent then; your USAGE_STATS record only says that statistics were disabled.

Only these fields are recorded:

• schema version, Actor name and build number;
• UTC start and finish hour (not a precise timestamp);
• run duration, number of results and time to the first result, each as a coarse range;
• whether the result was empty, the end status, and an error type from a fixed list;
• memory setting and counts of charged events;
• names of the input fields you set, never their values;
• the selected option for input fields that offer a fixed list of choices (for example a sort order).

We do not collect input text, search terms, URLs, domains, usernames, email addresses, names, proxy credentials, tokens, scraped records, output items, raw error messages, stack traces, or hashes of any of those values. Records are kept for no longer than 13 months, used only as aggregated operational statistics, and never sold or shared.

Additional fields (Phase 2)

This Actor also records your Apify user ID, whether Apify marks the account as paying, the size range of list inputs, the selected country when the input offers a fixed list of countries, and one category from a fixed Actor taxonomy. We use these fields only for aggregate reliability, repeat-use and cross-Actor analysis; reports suppress any cell with fewer than five distinct users.

The same disableUsageStats: true input flag turns these fields off too. The user ID is removed after 13 months; we do not export, sell, share, or attempt to re-identify this data.

Run-outcome signals (v2)

To learn whether a run did what it was asked to do, the record also holds a few more coarse ranges and yes/no flags. None of them contains content:

• the result limit you asked for (a range, when the input has one) and what share of it was delivered;
• results delivered per input item you listed (a range);
• output quality as ranges: how fully the result fields were filled, the share of rows that look like errors, the share of duplicate rows, and how many different fields appeared. These are counted in memory while results are saved; no result content is kept;
• how the run was started (console, API, schedule, webhook, another Actor);
• how it ended: stopped by you, timed out, reached the requested limit, stopped by the charge limit, and how many times the platform moved the run;
• if this Actor reports it: how many items to process worked or failed (ranges) and one failure reason from a fixed list;
• a short code made from the names of the input fields you set, never their values.

Repeat-run fingerprint (v2)

When your Apify user ID is recorded (see above), the record also holds an 8-character one-way code made from your input (proxy settings left out) and this Actor's name. It only lets us see that the same account ran the same input again soon after an unsatisfying run; we never see the input itself. It is stored only in the database, never published, and reports use it in aggregate with the same five-user minimum. It is the one exception to the statement above that no hashes are collected, and disableUsageStats: true turns it off.