# Zlaté stránky CZ Scraper (`memo23/zlatestranky-cz-scraper`) Actor

Scrape zlatestranky.cz (Zlaté stránky Czechia) into one row per business: name, phone, email when listed, website, address, weekday hours, and IČO. Keyword plus city, nationwide CZ, or a /hledani/ or /profil/ URL. JSON or CSV out. $5 per 1,000 listings plus phone and email events.

- **URL**: https://apify.com/memo23/zlatestranky-cz-scraper.md
- **Developed by:** [Muhamed Didovic](https://apify.com/memo23) (community)
- **Categories:** Lead generation, Business
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $5.00 / 1,000 results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Zlaté stránky CZ Scraper

Scrape [zlatestranky.cz](https://www.zlatestranky.cz/) (Zlaté stránky Czechia, Mediatel) into one row per **business**: name, phone, email when listed, website, address, opening hours, IČO.

Works from a keyword plus optional city, a nationwide term, or a pasted `/hledani/` or `/profil/H{id}` URL. Cards and profiles answer without Apify Proxy.

**Pricing:** $0.005 per listing (`pushData`). Extra `contact-phone` $0.002 and `contact-email` $0.05 when those fields are present.

### Why use this scraper?

- Phone, website, address, and coordinates sit on the search card.
- Profile pages add email, IČO, zip, and the weekday hours table.
- City is `{term}+{City}` in `/firmy/hledani/` — a third path segment is a page number.
- Optional harvest of the business site when the directory has no inbox.

### Overview

Built for lead lists and local research on Czech companies. Each dataset item is one listing from zlatestranky.cz (Mediatel). The Slovak WeNet/FCR site `zlatestranky.sk` is a different stack — use [zlatestranky-sk-scraper](https://apify.com/memo23/zlatestranky-sk-scraper).

### Supported inputs

| Input | What it does |
|---|---|
| `startUrls` | `https://www.zlatestranky.cz/hledani/restaurace/` or `/profil/H270008` |
| `searchTerms` | What you type in Zlaté stránky, e.g. `restaurace`, `instalater` |
| `locations` | City appended as `+City`. Empty = nationwide |
| `maxItems` | Stop after N unique listings (free plan cap 50) |
| `harvestWebsiteEmail` | Fetch the business site if the profile has no inbox |
| `proxy` | Leave off |

Unsupported: `zlatestranky.sk` (different HTML), `/overena-firma/` as a search (profile IDs still resolve).

### Use cases

| Who | Why |
|---|---|
| Sales / agencies | Czech phones and emails from a category |
| Researchers | IČO, city, and postcode coverage |
| SEO / maps | Website + coordinates per listing |

### How it works

1. Build `https://www.zlatestranky.cz/firmy/hledani/{term}` or `/{term}+{City}`. Page N is `/{N}` (20 cards). `/hledani/` redirects here.
2. Parse `li.list-listing` cards (`data-poi` for id + lat/lng).
3. Open `/profil/H{id}` for IČO, email, and the week table.
4. Charge `contact-phone` / `contact-email` after `pushData`.
5. If still no email and harvest is on, fetch the business homepage/kontakt page.

### Input configuration

| Field | Type | Required | Notes |
|---|---|---|---|
| `startUrls` | url\[] | one of terms/URLs | `/hledani/` or `/profil/` |
| `searchTerms` | string\[] | one of terms/URLs | e.g. `restaurace` |
| `locations` | string\[] | no | e.g. `Praha` |
| `maxItems` | integer | no | default 50 |
| `maxPages` | integer | no | default 20 |
| `scrapeDetails` | boolean | no | default true |
| `harvestWebsiteEmail` | boolean | no | default true |
| `maxConcurrency` | integer | no | default 5 |
| `proxy` | proxy | no | default off |

#### Example input

```json
{
  "searchTerms": ["restaurace"],
  "locations": ["Praha"],
  "maxItems": 10,
  "harvestWebsiteEmail": false,
  "proxy": { "useApifyProxy": false }
}
```

### Output overview

One JSON object per business. Search cards already carry phone, website, address, and coordinates. Profiles add email, IČO, zip, and the week of hours.

### Output samples

`restaurace+Praha`, profile merge (fields trimmed):

```json
{
  "listingId": "H270008",
  "name": "Repre restaurant",
  "phone": "+420222211451",
  "email": "rezervace@repre-restaurant.cz",
  "website": "http://www.repre-restaurant.cz",
  "street": "Nekázanka 4/857",
  "postalCode": "11000",
  "city": "Praha",
  "country": "CZ",
  "ico": "26168596",
  "hours": ["MO 10:30-23:00", "FR 10:30-23:00", "SA 12:00-23:00"],
  "profileUrl": "https://www.zlatestranky.cz/profil/H270008"
}
```

### Key output fields

| Field | Notes |
|---|---|
| `listingId` | `H` + digits |
| `phone` / `phones` | Search-card phone button |
| `email` | Profile mailto |
| `website` | Independent site, not zlatestranky.cz / mediatel.cz |
| `ico` | Czech IČ from the ARES link on the profile |
| `hours` | `MO 10:30-23:00` from the weekday table |
| `latitude` / `longitude` | `data-poi` on the card |

### FAQ

**Do I need a proxy?** Not on current HTML.

**Why did `/hledani/restaurace/Praha` look empty?** City is not a path segment. Use `/firmy/hledani/restaurace+Praha`. A third segment is page 2.

**Same actor as Slovakia?** No. SK is WeNet/FCR (`section.profile`). CZ is Mediatel (`li.list-listing`). Use `memo23/zlatestranky-sk-scraper` for `.sk`.

### Support

Questions and issues on the [actor page](https://apify.com/memo23/zlatestranky-cz-scraper).

### Additional services

Custom scrapers and data work on request.

### Explore more scrapers

[Zlaté stránky SK](https://apify.com/memo23/zlatestranky-sk-scraper) · [Bizi.si](https://apify.com/memo23/bizi-scraper) · [1188.lv](https://apify.com/memo23/1188-lv-scraper)

### 🤖 For AI Agents & LLM Apps

Compact reference for AI agents calling this actor via the [Apify MCP server](https://mcp.apify.com) or the Apify API (actor: `memo23/zlatestranky-cz-scraper`).

**Purpose:** Scrape zlatestranky.cz businesses into one row each (name, phone, email, website, address, hours, IČO).

**Minimal input:**

```json
{"searchTerms":["restaurace"],"locations":["Praha"],"maxItems":5,"harvestWebsiteEmail":false}
```

**Output:** one dataset row per business — `listingId, name, phone, phones, email, website, street, postalCode, city, country, ico, hours, latitude, longitude, profileUrl`.

**Behaviors an agent should know:**

- Always set `maxItems`. Free plan is capped at 50.
- `startUrls` and `searchTerms` are unioned. Slovak `.sk` URLs are skipped.
- Billing: `$0.005` per `pushData` row, plus `contact-phone` `$0.002` and `contact-email` `$0.05` when those fields are present. Do not charge start/listing in actor code.

### ⚠️ Disclaimer

This Actor is an independent tool and is not affiliated with, endorsed by, or sponsored by Mediatel, spol. s r.o. or Zlaté stránky. All trademarks mentioned are the property of their respective owners.

The scraper accesses only publicly available zlatestranky.cz pages — no authenticated endpoints, paid features, or content behind a login wall. Users are responsible for ensuring their use complies with zlatestranky.cz Terms of Service, applicable data-protection law (GDPR, CCPA, etc.), and any contractual obligations of their own organization.

### SEO Keywords

zlatestranky scraper, zlatestranky.cz scraper, zlaté stránky, Czech yellow pages, Czech business emails, Praha directory scraper, Brno leads, IČO scraper, Mediatel catalog, Czech company phone numbers, Czech local leads, Apify zlatestranky, Czechia business directory, restaurace scraper, Czech B2B contacts

# Actor input Schema

## `startUrls` (type: `array`):

Paste zlatestranky.cz search or profile links. Examples: <code>https://www.zlatestranky.cz/hledani/restaurace/</code>, <code>https://www.zlatestranky.cz/firmy/hledani/restaurace+Praha</code>, or <code>https://www.zlatestranky.cz/profil/H270008</code>. Slovak zlatestranky.sk URLs are rejected.

## `searchTerms` (type: `array`):

What you would type into Zlaté stránky, e.g. <b>restaurace</b>, <b>instalater</b>, <b>advokat</b>, <b>hotel</b>. One row per term. Every term is searched in every city below. Leave cities empty for a nationwide CZ query. A zlatestranky.cz /hledani/ or /profil/ URL also works here.

## `locations` (type: `array`):

Czech city, e.g. <b>Praha</b>, <b>Brno</b>, <b>Ostrava</b>, <b>Plzen</b>. Empty = nationwide. City is appended as <code>/firmy/hledani/{term}+{City}</code> (a third path segment is a page number, not a city).

## `maxItems` (type: `integer`):

Stop after this many unique businesses across the whole run. Free plan is capped at 50.

## `scrapeDetails` (type: `boolean`):

Loads the /profil/H{id} page for IČO, email, the week of hours, and zip. Turn off to keep search-card fields only (name, phone, website, address).

## `harvestWebsiteEmail` (type: `boolean`):

If the directory profile has no inbox, fetch the business website homepage/contact page.

## `maxPages` (type: `integer`):

Page N is <code>/firmy/hledani/{term}/{N}</code> (20 cards per page).

## `maxConcurrency` (type: `integer`):

How many pages and profiles to load at the same time.

## `proxy` (type: `object`):

Leave off. Search and profile pages currently answer without Apify Proxy.

## Actor input object example

```json
{
  "searchTerms": [
    "restaurace"
  ],
  "locations": [
    "Praha"
  ],
  "maxItems": 50,
  "scrapeDetails": true,
  "harvestWebsiteEmail": true,
  "maxPages": 20,
  "maxConcurrency": 5,
  "proxy": {
    "useApifyProxy": false
  }
}
```

# Actor output Schema

## `overview` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "searchTerms": [
        "restaurace"
    ],
    "locations": [
        "Praha"
    ],
    "proxy": {
        "useApifyProxy": false
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("memo23/zlatestranky-cz-scraper").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "searchTerms": ["restaurace"],
    "locations": ["Praha"],
    "proxy": { "useApifyProxy": False },
}

# Run the Actor and wait for it to finish
run = client.actor("memo23/zlatestranky-cz-scraper").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "searchTerms": [
    "restaurace"
  ],
  "locations": [
    "Praha"
  ],
  "proxy": {
    "useApifyProxy": false
  }
}' |
apify call memo23/zlatestranky-cz-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,memo23/zlatestranky-cz-scraper"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/niw6EJWD3KqscMTN5/builds/sdIvChxJghPMEskRC/openapi.json