# Seznam.cz Search Scraper – SERP with Sklik Ads, Firmy & Zboží (`budoucnost-ai/seznam-search-scraper`) Actor

Seznam.cz search results (SERP) as clean JSON: organic results, Sklik ads with advertiser company, Firmy.cz businesses with contacts, Zboží.cz products and shop offers, news, AI answers, related searches, videos and wiki card. Rank tracking for your domains. MCP-ready.

- **URL**: https://apify.com/budoucnost-ai/seznam-search-scraper.md
- **Developed by:** [Budoucnost AI](https://apify.com/budoucnost-ai) (community)
- **Features:** Limited permissions, Single-tenant, Server interface
- **Stats:** 1 total users, 1 monthly users, 100.0% runs succeeded, 1 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.60 / 1,000 organic search results

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.

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

## Seznam.cz Search Scraper – SERP with Sklik Ads, Firmy & Zboží

Scrape **search.seznam.cz** – the Czech search engine – and get the whole results page as clean JSON, not just ten blue links:

- **Organic results** – title, URL, domain, snippet, rank, language, publication date and Seznam's page categories (shopping, product list, informative…)
- **Sklik ads** (top and bottom) – headline, description, landing URL with UTM, sitelinks, labels, phone and the **advertiser's company name**
- **Firmy.cz businesses** – name, category, address, phones, e-mails, website, paid listing flag
- **Zboží.cz** – products with price range and number of offers, and shop offers with price and shop rating
- **Seznam AI answers** („Odpověď od Seznam AI“, „Shrnutí od Seznam AI“, news summaries) – **full text**, cited sources with URL and domain, entities and follow-up questions, plus a flag whether **your domains are cited or mentioned**
- **News**, **AI questions**, featured snippet
- **Related searches**, **videos**, **images**, **wiki / knowledge card** with infobox
- **One summary row per query** – total results, ads top/bottom, which blocks Seznam showed, related searches and **positions of your tracked domains**

Data come from the JSON that Seznam embeds in its own page, so the fields are exact and stable – no fragile HTML parsing, no browser.

### Use cases

- **Rank tracking on Seznam** – organic rank, ad rank and Firmy presence for your domains, for a list of keywords
- **Sklik competitor research** – who advertises on your keywords, with which ads, landing pages and UTM campaigns
- **AI visibility on Seznam (GEO)** – what Seznam AI answers for your topics, which websites it cites, and whether your brand is cited or named
- **SEO / SERP feature analysis** – does Seznam show an AI answer, a wiki card, Firmy or Zboží for the keyword?
- **Lead generation** – businesses that Seznam shows for a service query, with contacts
- **Price monitoring** – Zboží.cz products and offers shown on the SERP
- **Keyword ideas** – related searches (combine with [Seznam.cz Keyword Planner](https://apify.com/budoucnost-ai/seznam-keyword-planner) for search volumes)

### Input

| Field | Description |
|---|---|
| `queries` | Search queries, one per line |
| `maxPagesPerQuery` | Result pages per query (10 organic results each, max 50) |
| `includeBlocks` | Which blocks to save (default: all except images, Zboží shop offers and AI answers – add `ai_answer` to get them): organic, ad, business, product, offer, news, ai_answer, ai_question, related, video, image, wiki, snippet |
| `trackDomains` | Domains to find (rank tracking) |
| `onlyTrackedDomains` | Save only rows of tracked domains – cheapest rank tracking |
| `includeSummary` | One summary row per query (default on) |
| `aiAnswersFromCzechIp` | Seznam shows AI answers only to Czech visitors – page 1 is loaded from a Czech IP when AI answers are requested (default on, no extra charge) |

```json
{
    "queries": ["elektrokolo", "servis elektrokol praha"],
    "maxPagesPerQuery": 2,
    "trackDomains": ["ekolo.cz"]
}
```

### Output

Every row has `query`, `page`, `blockType`, `placement` (`top` / `main` / `bottom` / `right`), `pagePosition` (order in the main column), `rank` (order within the block type across pages), `title`, `url`, `domain`, `description` plus block-specific fields.

Sklik ad example:

```json
{
    "query": "elektrokolo",
    "blockType": "ad",
    "placement": "top",
    "pagePosition": 1,
    "rank": 1,
    "title": "Elektrokola CRUSSIS – Nové modely elektrokol",
    "url": "https://www.crussis.cz/produkty/celoodpruzena-elektrokola",
    "domain": "crussis.cz",
    "advertiserName": "CRUSSIS electrobikes s.r.o.",
    "displayUrl": "crussis.cz",
    "landingUrl": "https://www.crussis.cz/produkty/celoodpruzena-elektrokola?utm_source=seznam&utm_medium=cpc&…",
    "sitelinks": [{ "name": "Treková elektrokola", "url": "https://www.crussis.cz/eshop-kategorie-trekova-elektrokola-33.html" }]
}
```

Summary row example:

```json
{
    "query": "elektrokolo",
    "blockType": "summary",
    "totalResults": 15000000,
    "adsTop": 4,
    "adsBottom": 3,
    "hasAiAnswer": null,
    "hasAiQuestions": false,
    "hasFeaturedSnippet": false,
    "hasWikiCard": true,
    "hasFirmy": true,
    "hasZbozi": true,
    "relatedQueries": ["elektrokolo recenze", "elektrokolo bazar", "elektrokolo cena"],
    "trackedDomains": { "ekolo.cz": { "organicRank": 12, "adRank": 7, "adPlacement": "bottom", "otherBlocks": ["business"] } }
}
```

### Seznam AI answers

Seznam loads its AI block after the page itself, so a plain HTML scraper sees only an empty placeholder. This actor reads the answer the same way the Seznam page does – from Seznam's own answer stream – and still needs no browser. One `ai_answer` row per AI block:

| Field | Meaning |
|---|---|
| `aiType` | `answer` (Odpověď od Seznam AI), `serp_summary` (Shrnutí od Seznam AI), `news_summary`, `assistant_hint` |
| `answerText` / `answerHtml` | Full answer as plain text and as Seznam's HTML |
| `sentences` | Summary sentences with the numbers of the sources they come from |
| `sources` | Cited sources: `number`, `title`, `url` (tracking parameters removed), `domain`, `siteName`, `publishedAt` |
| `unusedSources` | Sources Seznam retrieved but did not cite (when provided) |
| `citedDomains` | Unique domains of the cited sources |
| `entities` | Linked entities in the answer (product, business…) with the follow-up search query |
| `followUpQuestions` | Questions Seznam offers to continue in Seznam Asistent |
| `trackedDomainsCited` / `trackedDomainsMentioned` / `citesTrackedDomain` | Which of your `trackDomains` are cited as a source, or named in the text (e.g. „Bramac“ for bramac.cz, diacritics-insensitive) |
| `aiStatus` | `complete`, `partial` (stream ended early) or `failed` |
| `aiDelivery` | `page` (Seznam had the answer ready in the page) or `stream` (generated live and read from Seznam's answer stream) |

The `answer` type is generated from Seznam's index without a list of source links – it then has empty `sources` and links only to entities; summaries always cite sources. Seznam shows AI blocks only to visitors from the Czech Republic, so AI answers are **opt-in**: add `ai_answer` to `includeBlocks` and page 1 of each query is loaded from a Czech IP (see `aiAnswersFromCzechIp`). Seznam also decides per query whether to show an AI block at all; the summary row reports `hasAiAnswer` (`null` when `ai_answer` was not requested – it cannot be seen without a Czech IP), `hasAiQuestions`, `hasFeaturedSnippet`, `aiAnswerStatus`, `aiAnswerSourceCount` and `aiAnswerCitedDomains`, and `trackedDomains.<domain>.citedInAiAnswer` / `mentionedInAiAnswer`.

```json
{
    "query": "kdo vyhrál tour de france 2025",
    "blockType": "ai_answer",
    "aiType": "serp_summary",
    "aiStatus": "complete",
    "answerText": "Tadej Pogačar z UAE Team Emirates XRG vyhrál Tour de France 2025, …",
    "sentences": [{ "text": "Tadej Pogačar z UAE Team Emirates XRG vyhrál Tour de France 2025, …", "sourceNumbers": [1] }],
    "sources": [{ "number": 1, "title": "Tour de France 2025: Konečné výsledky závodu - Sport.cz", "url": "https://www.sport.cz/clanek/cyklistika-tour-de-france-2025-program-etapy-trasa-5247335", "domain": "sport.cz", "siteName": "Sport", "publishedAt": "2025-06-12T20:41:20+02:00" }],
    "citedDomains": ["sport.cz"],
    "followUpQuestions": ["Proč Evenepoel odstoupil z Tour de France 2025?"],
    "trackedDomainsCited": [],
    "citesTrackedDomain": false
}
```

If the answer cannot be loaded, the row is saved with an `error` and is **not charged**.

Prices are in CZK. Which blocks appear depends on the query – a product query shows Zboží and ads, a city shows a wiki card and news, a service shows Firmy.

### Pricing

Pay per result – you pay only for rows saved to the dataset:

- **Organic result** – per row
- **Sklik ad** – per ad
- **Seznam AI answer** – per answer with full text and sources (failed answers are free)
- **Other SERP item** (business, product, offer, news, AI question, related search, video, image, wiki, snippet) – per row, cheaper
- **Query summary** – per query

Turn off blocks you don't need in `includeBlocks`, or use `onlyTrackedDomains` for cheap rank tracking. Failed pages are never charged.

### Notes

- Results are what an anonymous desktop visitor sees. Seznam localises **Firmy.cz businesses** (and regionally targeted ads) by the visitor IP: without a Czech proxy you get a nationwide mix of businesses, with a Czech residential proxy (Advanced → Proxy) the businesses near that IP. Organic results barely change.
- Seznam shows at most 50 pages (500 organic results) per query.
- No proxy needed for normal volumes; enable Apify Proxy in *Advanced* if you run thousands of queries.
- Works with AI agents through the Apify MCP server.

### Changelog

- **1.1** (Nov 2026) – Seznam AI answers with full text, cited sources, entities, follow-up questions and tracked-domain citation/mention flags (previously only the news summary was captured).
- **1.0** (Nov 2026) – first release.

# Actor input Schema

## `queries` (type: `array`):

What to search on search.seznam.cz – one query per line (e.g. elektrokolo, praha, iphone 16). Each query is one SERP.

## `maxPagesPerQuery` (type: `integer`):

How many result pages to load per query (10 organic results per page, Seznam shows at most 50 pages). Ads, Firmy, Zboží and other blocks are mostly on page 1.

## `includeBlocks` (type: `array`):

Which SERP blocks become dataset rows (each block type is billed as listed in Pricing). Empty = all except images, Zboží shop offers (~35 rows per product query – add them for price monitoring) and Seznam AI answers (add ‘ai_answer’ – loaded from a Czech IP). The per-query summary always reports every block Seznam showed.

## `trackDomains` (type: `array`):

Optional. Domains to find in the results (e.g. ekolo.cz). The summary row then shows each domain's organic rank, ad rank/placement and other blocks it appears in (Firmy businesses are matched by their website). Subdomains count.

## `onlyTrackedDomains` (type: `boolean`):

Cheap rank tracking: save only rows that match a tracked domain (plus the summary). You pay only for those rows.

## `includeSummary` (type: `boolean`):

Row with blockType = summary: total results, number of ads top/bottom, which blocks Seznam showed (AI, wiki card, Firmy, Zboží, news), related searches, and tracked-domain positions.

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

Stop after this many dataset rows (cost cap).

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

How many queries run at once (1–5). Keep low to stay polite.

## `aiAnswersFromCzechIp` (type: `boolean`):

Seznam shows its AI answers only to visitors in the Czech Republic. When on (default) and ‘ai_answer’ is among the saved blocks, page 1 of each query is loaded through a Czech IP at no extra charge. Turn off only if you supply your own Czech proxy below.

## `proxyConfiguration` (type: `object`):

Not needed normally – Seznam answers directly. Turn on Apify Proxy only if runs start failing on blocked responses. A proxy set here is used for all requests, including AI answers (use a Czech IP if you want AI answers).

## Actor input object example

```json
{
  "queries": [
    "elektrokolo"
  ],
  "maxPagesPerQuery": 1,
  "includeBlocks": [
    "organic",
    "ad",
    "business",
    "product",
    "news",
    "ai_question",
    "related",
    "video",
    "wiki",
    "snippet"
  ],
  "onlyTrackedDomains": false,
  "includeSummary": true,
  "maxItems": 100000,
  "maxConcurrency": 2,
  "aiAnswersFromCzechIp": true,
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}
```

# Actor output Schema

## `results` (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 = {
    "queries": [
        "elektrokolo"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("budoucnost-ai/seznam-search-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 = { "queries": ["elektrokolo"] }

# Run the Actor and wait for it to finish
run = client.actor("budoucnost-ai/seznam-search-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 '{
  "queries": [
    "elektrokolo"
  ]
}' |
apify call budoucnost-ai/seznam-search-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,budoucnost-ai/seznam-search-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/KuGQ18geentLemhYw/builds/dG7in6AHpOLeT7cZJ/openapi.json
