Yandex Maps Scraper

Use Yandex Maps Scraper to export public place-search records by category or keyword within a supplied city context. Keep place identity, location, rating and review counts, exposed contact and hours fields and source links. Embedded detail extraction adds available search-result fields rather than collecting individual reviews or verifying a business's current operations.

Quick start

Choose one city and a focused query with a small shared place cap. The existing Moscow example combines coffee and plumber searches:

{
  "queries": ["coffee", "plumber"],
  "cityUrl": "https://yandex.com/maps/213/moscow",
  "maxItems": 25,
  "language": "en-US,en;q=0.9",
  "includeDetails": true,
  "includeReviews": false
}

Prefer a video guide? This short Apify walkthrough shows you how to set up and run an Actor. It uses a different Actor, but the setup steps are the same.

Ready-to-run examples

Choose an example to prefill the search input, then adjust the city, query and shared place cap.

• Find Moscow Coffee Shop Leads — Inspect public coffee-shop names, ratings and available contact fields.
• Map Moscow Restaurant Competitors — Collect a restaurant sample for your own category comparison.
• Export Saint Petersburg Dentists — Retrieve dental-practice listings in a second city.

What you get

One public place row with query and observed result position, place ID and Yandex URL, available category, rating and location data, plus optional embedded contact and other detail fields. Values depend on what the public search result exposes. A rating or open/closed label is source context rather than an independently verified business assessment.

Who is it for?

• Local-market researchers reviewing category samples in a named city.
• Directory-data teams retaining source-linked place identities and contact references.
• Local SEO analysts comparing observed ratings, categories and website coverage.
• Data developers exporting place records into their own maps or reporting tools.

How you can use the data

• Inspect a Moscow coffee sample. Use the existing city URL and coffee query, keeping placeId, url, address, query and rank. The observed position is a source-search sample rather than stable overall category visibility or a complete list of venues.
• Review exposed contact context. Retain embedded phones, websites, hours and coordinates when present. Missing values are unknown rather than proof that a business has no website or phone, and a contact reference does not grant outreach permission.
• Build separate city/category observations. Use your known city URL and the existing restaurant, hotel, dentist or plumber terms in separate focused exports. A text location is only a fallback when cityUrl is absent, so keep the requested area with each stored sample.
• Prepare your own place enrichment join. Retain place IDs and source URLs before joining to a separate contact or review workflow. This Actor exports rating and review counts, while includeReviews is reserved and does not create review text rows. Notifications and longitudinal comparisons stay in your own destination.

Input settings

Setting	JSON key	Use it for
Search queries	queries	Up to 100 non-empty keywords or business categories, not URLs. Console/API validation prevents URL entries. Runtime paths bypassing that validation skip URL entries with a warning and preserve other queries.
Yandex Maps city URL	cityUrl	Public Yandex Maps city URL used as the search area. Example: https://yandex.com/maps/213/moscow.
Location fallback	location	Named location or coordinate text, used only when no city URL is provided. Resolved through Yandex Maps before searching, with a town-qualified retry for ambiguous Russian names. For best precision use town plus region, for example Чайковский, Пермский край. A genuinely unresolved location succeeds empty with a warning naming the location and unresolved_location in RUN_SUMMARY; another city is never substituted. Request failures and unrecognized responses still fail rather than pretending the town has no businesses.
Maximum places	maxItems	Shared cap across queries. At most 25 places are currently saved per run, including when a larger legacy value is supplied.
Language header	language	Accept-Language header sent to Yandex Maps. Use en-US,en;q=0.9 for English output where available.
Include embedded details	includeDetails	Compatibility setting. Available embedded detail fields are always included, even when false.
Include reviews (reserved)	includeReviews	Reserved for a later version. The current build returns place records and rating/review counts, not individual review rows.

Output data

The existing illustrative row contains historical values rather than a current place or rating measurement:

{
  "query": "coffee",
  "rank": 1,
  "name": "Surf Coffee",
  "url": "https://yandex.com/maps/org/surf_coffee/238919133832/",
  "placeId": "238919133832",
  "category": "Coffee shop",
  "rating": 4.8,
  "reviewCount": 517,
  "address": "Okhotny Ryad Street, 2",
  "phone": "+7 (985) 111-91-64",
  "website": "https://surfcoffee.ru/",
  "coordinates": {
    "longitude": 37.61823,
    "latitude": 55.757274
  },
  "scrapedAt": "2026-06-28T00:00:00.000Z"
}

Field	Description
query	Search query that produced the place.
rank	Position of the place in the scraped search results.
name	Place or business name.
category	Primary category shown by Yandex Maps.
categories	Additional category values when available.
rating	Public rating value when available.
ratingCount	Count behind the rating when available.
reviewCount	Public review-count value when available.
address	Short address text.
fullAddress	Longer address text when available.
postalCode	Postal code from the same public search payload when available.
phone	Primary phone number when available.
phones	Additional phone values when available.
website	Public business website when available.
url	Public Yandex Maps place URL.
placeId	Yandex Maps place identifier when available.
coordinates	Latitude and longitude values when available.
hours	Human-readable opening-hours text when available.
workingTimeText	Human-readable opening-hours text when available.
status	Current open/closed or place status text when available.
features	Public feature tags when available.
socialLinks	Public social links when available.
imageUrl	Public image URL when available.
snippet	Search-result snippet text when available.
scrapedAt	Timestamp when the row was saved.

Download your results

Open your run's dataset, choose Export and select JSON, CSV or Excel. JSON keeps nested fields together. CSV and Excel are useful when you want to review the records in a spreadsheet.

See Apify's download and export guide for the available formats and field options.

Pricing

The start event is charged once when a valid run begins extraction. A started run can incur this charge even when no places are found.

The item event is charged for each place saved to the dataset. Only saved place records are billed as items. Extraction stops when the applicable run charge limit is exhausted, and already saved places remain accessible.

Platform compute, storage or transfer can also apply. This Actor uses direct access without a paid proxy fallback. See the live Pricing tab for current rates and plan discounts.

Tips for best results

• Use category terms: Queries such as dentist, hotel, or coffee usually work better than vague phrases.
• Run cities separately: Separate tasks make outputs easier to compare and retry.
• Start with a small cap: Try maxItems: 5 first. This build saves at most 25 places across all queries and does not collect later search pages.
• Inspect available details: Phones, websites and other embedded fields are included when Yandex Maps exposes them. Missing values stay unknown.
• Do not expect review text: The current version returns rating and review counts, not individual reviews.

Limits and caveats

• The actor extracts public Yandex Maps search-result data. It does not log into Yandex or access private records.
• Phone, website, hour, image, and coordinate fields depend on what Yandex Maps exposes for each place.
• includeReviews is reserved. This actor does not currently save individual review rows.
• Review your use of exported data against Yandex terms, Apify terms, and applicable privacy rules.

The shared cap limits saved places across queries. Search ranking, available fields and public place status can change, so one export is not an exhaustive directory or proof of current business operations. Coordinates, phone numbers and hours remain source data rather than independent validation.

The language value is a preference and does not guarantee translated names or fields. Available embedded detail fields are always returned. The compatibility setting includeDetails does not switch them off. Individual review text belongs to a separate review scraper.

Enter a keyword such as coffee in queries, not a Yandex Maps link. To choose an area, use location and clear the prefilled cityUrl, or supply a city URL in cityUrl. Console/API input validation prevents URL queries before startup. Runtime paths bypassing schema validation and containing only URL queries succeed with no results, a visible warning and no_supported_queries in RUN_SUMMARY; no search requests or manual charges are made. Mixed batches retain valid keyword results.

A confirmed no-match search succeeds without dataset rows and records its reason in RUN_SUMMARY. An unrecognized response or access challenge is not treated as proof of no matches. Isolated query failures preserve other queries' useful records and are identified in the summary. If all queries fail, or the processing deadline leaves queries unfinished, the run fails while retaining saved records.

The run has a finite processing budget. Resurrecting the same run does not repeat extraction. Start a new run if you need a new search.

Automation and integrations

Save your settings for next time

Once you have an input that works for you, save it as an Apify task. This keeps your settings together so you can use them again without filling in the form from scratch.

Run on a schedule

Need fresh results regularly? You can schedule the Actor or a saved task to run at a time that suits you.

Each scheduled run collects the data again. If you want to compare results or highlight changes, add that step in your own workflow.

Send results to your other tools

Use n8n, Make or Zapier to connect this scraper to the rest of your workflow. For example, you could pass its results to an AI assistant or add records to a spreadsheet. Follow the Apify integration guides for your chosen tool.

For a custom connection, an Apify webhook can notify your app when a run finishes or fails. Your app can then fetch the results or handle the failure.

API usage

Want to collect this data from your own app or automation? The examples below send input to the scraper and show how to collect its results.

The Node.js and Python examples wait for the run to finish before reading its results. The cURL example starts the run and returns its details. Wait for that run to finish, then use its defaultDatasetId to fetch the results.

For setup instructions, see Apify's JavaScript client guide, Python client guide and Actor runs API reference.

cURL

curl -X POST "https://api.apify.com/v2/acts/fetch_cat~yandex-maps-scraper/runs?token=$APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"queries":["coffee"],"cityUrl":"https://yandex.com/maps/213/moscow","maxItems":5,"includeDetails":true,"includeReviews":false}'

Node.js

import { ApifyClient } from 'apify-client';
const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('fetch_cat/yandex-maps-scraper').call({
  "queries": [
    "coffee"
  ],
  "cityUrl": "https://yandex.com/maps/213/moscow",
  "maxItems": 5,
  "includeDetails": true,
  "includeReviews": false
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

Python

import os
from apify_client import ApifyClient
client = ApifyClient(os.environ['APIFY_TOKEN'])
run = client.actor('fetch_cat/yandex-maps-scraper').call(run_input={
  "queries": [
    "coffee"
  ],
  "cityUrl": "https://yandex.com/maps/213/moscow",
  "maxItems": 5,
  "includeDetails": True,
  "includeReviews": False
})
print(client.dataset(run['defaultDatasetId']).list_items().items)

MCP and AI agents

You can ask your AI assistant to collect data with Yandex Maps Scraper and help you work with the results. The scraper returns the data, and your assistant can then summarize it, compare records or prepare notes.

Connect your assistant through the Apify MCP server. MCP gives your assistant a way to find this scraper, run it and read the results. Follow the official setup and sign-in guide for your app.

Easier setup with an Apify plugin

If you use a supported coding assistant, the official Apify plugin can set up the connection for you. It connects your assistant to Apify and includes instructions for common tasks. Follow the guide for your particular app.

Use Apify AI in Console

Prefer to keep everything in Apify? Open Apify AI in Console and ask it to find Fetch Cat's Yandex Maps Scraper. You can describe the data you want and ask questions about the results.

Apify AI is currently in beta. It asks for confirmation before starting an Actor, and normal run charges apply.

Choose your assistant

• Claude and Claude Code (Anthropic): Apify setup guide.
• ChatGPT and Codex (OpenAI): Apify setup guides.
• Grok Bot (xAI): Apify plugin guide.
• Gemini CLI (Google): MCP server setup guide. Use the server URL below with the HTTP configuration supported by Gemini CLI.

Connect just this scraper

To keep your setup focused on this scraper, add this server configuration to a compatible MCP client:

{
  "mcpServers": {
    "apify": {
      "url": "https://mcp.apify.com?tools=fetch_cat/yandex-maps-scraper"
    }
  }
}

Sign in to Apify when your client asks. If your client uses a Bearer token instead, follow its setup guide and keep the token in its secure configuration. Configuration formats vary by app, so use the linked guide if your client needs a different format.

Use Apify's general server

Already connected to the general Apify MCP server at https://mcp.apify.com? You can use it to find this scraper without adding another server. Ask your assistant to use Yandex Maps Scraper by Fetch Cat, or give it the identifier fetch_cat/yandex-maps-scraper.

Your assistant can check the available settings and retrieve the results from the returned run. If the run is still working, it should follow that run rather than start it again. Both connection options use Apify's hosted service.

Example requests

• “Use Fetch Cat’s Yandex Maps Scraper to collect up to 5 coffee places from https://yandex.com/maps/213/moscow with embedded details enabled and review collection off. Keep place IDs, source URLs and missing contact fields without verifying business status.”
• “Collect up to 5 plumber place records from that Moscow city URL with embedded details on. Keep observed ratings, addresses and website references without treating the sample as every provider or contacting anyone.”
• “Retrieve up to 5 hotel places in Moscow and keep their names, ratings and source links. Group the returned places by category for my research notes.”

Normal Apify charges apply. Check the live Pricing tab before asking your assistant to run a larger batch.

Pay with x402

If your AI agent has a funded wallet, it can pay for Apify usage through x402. This experimental option lets an agent use Apify without a conventional account.

Apify AGI provides a prepaid API token with a spending cap after payment. Your agent can use that token to run this scraper through the Apify API or an authenticated MCP connection.

Some MCP setups also support paying for each request directly. That is a different payment option, so check the official guide for its availability.

Follow the official guide for wallet setup, supported payment options and current terms. Apify handles the payments. Keep wallet keys and payment tokens in your agent's secure configuration.

Other ways for agents to pay

Apify also supports MPP for prepaid access through AGI and Skyfire for eligible Actors. If your agent already uses one of these, see the agentic payment guide to choose the right setup.

FAQ

Does it scrape individual Yandex reviews?

No. The current version returns place records plus rating and review counts, not individual review text.

Can I scrape phones and websites?

Yes, when those public fields are available in Yandex Maps results. Embedded detail fields are always returned. includeDetails is retained for compatibility and does not change the output.

Can I schedule it?

Yes. Save the input as an Apify task and schedule repeat runs for the same query and city.

Can I export to Excel?

Yes. Apify datasets support Excel, CSV, JSON, XML, RSS, and API access.

Related Actors

• Yandex Maps Reviews Scraper — Export individual public place reviews when you need review text rather than listing counts.
• Bing Rank Tracker & SERP Scraper — Collect Bing web-search result titles, snippets and links.
• Website Contact Finder for public contact enrichment from business websites.
• Google News Scraper for local business or competitor news monitoring.
• Google Maps Places Scraper — Collect public Google Maps business listings and available place details.

Support and feedback

For custom additions or integrations, email hello@fetchcat.dev.

Found an error or have a feature request? Open an issue with the run URL, a non-sensitive input example and what you expected.

Need help sharing it? See Apify’s guide to sharing a run when reporting an issue. Sharing a run can give the developer access to its input, logs and results, so use a run that contains no sensitive data. Please leave out API tokens, passwords, cookies, private documents and personal data. Use a public sample URL or a redacted example instead.

Tried this scraper? We'd love to hear how it worked for you. Leave a review to help others choose the right tool and help us improve it. Your feedback means a lot to us.

Made with care for curious people, AI agents and the possibilities in data. ♥