Yandex Maps Reviews Scraper

Yandex Maps Reviews Scraper: reviews, ratings and owner replies for any place

Paste a Yandex Maps organisation link and every review comes back as a row: star rating, the full text, who wrote it and their Yandex level, the date, likes, photos, and the owner's reply where there is one. The place itself rides on every row too, so name, address, category, overall rating and total review count are already there. No account, no Yandex API key.

The ceiling first. Yandex serves the first 600 reviews of an organisation and no more. That is Yandex's own limit, not a setting here, so a place with 4,000 reviews gives you 600. They arrive in Yandex's own relevance order, which puts newer and longer reviews first, and Yandex ignores any attempt to reorder them, so the five filters below run here rather than being sent to Yandex.

💬 What Yandex Maps Reviews Scraper does

There are two ways to name the places. Paste links, which can be the organisation page (https://yandex.ru/maps/org/niki_dent/55558183898/), its reviews tab, the bare numeric id 55558183898, or a Yandex Maps search link, which is expanded into the organisations it lists. Or skip links and search: put a name or a category into Search terms, add a City, and each term contributes a few organisations whose reviews are then read.

The filters run on the reviews after they arrive, because Yandex ignores filter parameters on this surface. Anything a filter removes is dropped before it reaches your dataset and is not billed, so setting Maximum star rating to 2 to pull complaints only costs you the complaints, not the praise you threw away.

The place card is flattened onto every review row: organizationName, organizationAddress, organizationCategory, organizationRating and organizationReviewCount. Nothing to join.

📥 What you give it

{
  "startUrls": ["https://yandex.ru/maps/org/niki_dent/55558183898/"],
  "maxReviewsPerOrganization": 100,
  "maxItems": 500,
  "maxRating": 3,
  "onlyWithText": true,
  "newerThan": "2026-01-01"
}

📤 What you get back

A real row from a recent run, with the review and the reply cut short:

{
  "reviewId": "Do3qkCnDnsomk9XhYPTBpIvACtyWNTrH",
  "organizationId": "55558183898",
  "organizationName": "Стоматология на Никитской",
  "organizationAddress": "Москва, Малая Никитская улица, 33",
  "organizationCategory": "Стоматологическая клиника",
  "organizationRating": 5,
  "organizationReviewCount": 82,
  "organizationUrl": "https://yandex.com/maps/org/niki_dent/55558183898/",
  "organizationReviewsUrl": "https://yandex.com/maps/org/niki_dent/55558183898/reviews/",
  "rating": 5,
  "text": "Невероятная клиника, стоматология!! Супер! Врачи настоящие профессионалы!! Очень повезло!...",
  "textLanguage": "ru",
  "hasText": true,
  "publishedAt": "2026-05-14T11:42:41.208Z",
  "publishedAtTimestamp": 1778758961208,
  "authorName": "Сергей К.",
  "authorId": "4w09jt6vf7pee5dq7h36j8aczr",
  "authorLevel": "Знаток города 7 уровня",
  "authorAvatarUrl": "https://avatars.mds.yandex.net/get-yapic/47747/0h-2/islands-200",
  "authorProfileUrl": "https://yandex.com/maps/user/4w09jt6vf7pee5dq7h36j8aczr",
  "likes": 0,
  "dislikes": 0,
  "businessReplyText": "Благодарим вас за такой подробный и эмоциональный отзыв...",
  "businessReplyAt": "2026-05-15T17:39:02.331Z",
  "hasBusinessReply": true,
  "photoUrls": ["https://avatars.mds.yandex.net/get-altay/20218502/2a0000019e26c1d1820a..."],
  "photoCount": 1,
  "videoCount": 0,
  "isPinned": false,
  "position": 1,
  "scrapedAt": "2026-09-21T01:46:12.580Z"
}

🧾 Reading the output

There is no charged field on these rows. Filter on reviewId being present.

If your filters remove every review for an organisation, you get zero rows for it and no diagnostic. That is a filter doing its job, not a failure.

▶️ How to run it

1. Open Yandex Maps Reviews Scraper and click Try for free. 2. Paste organisation links into Yandex Maps organisation URLs, one per line. Or leave that empty, open Find organisations by search, and type a term plus a city. 3. Set Maximum reviews per organisation. Start at 20 to see what the rows look like. 4. Open Filters if you only want a star range, written reviews, replied-to reviews, or reviews after a date. 5. Click Start, then download the dataset as JSON, CSV or Excel, or read it from the Apify API.

💰 How much does it cost?

$0.30 per 1,000 reviews. Flat on every Apify plan, with no volume tiers.

One billed row per review delivered. The sample row is not billed, diagnostic rows are not billed, an organisation with no reviews produces no billed rows, and anything your filters remove is dropped before the dataset and never billed.

💡 What people use it for

• Reputation monitoring for your own locations, on a schedule, with newerThan set to the last run

and reviewId for deduping.

• Pulling complaints only, by setting Maximum star rating to 2 or 3, and reading what actually

goes wrong at a place.

• Checking how responsive a business is, using hasBusinessReply and the gap between

publishedAt and businessReplyAt.

• Surveying a category across a city, by searching стоматология in Moscow and reading every

organisation's reviews in one run.

• Feeding review text into a translation or sentiment step of your own, with textLanguage already

filled in.

🚧 What it does not do

• 600 reviews per organisation is the hard ceiling. Yandex stops serving past that point, so a

place with thousands gives you the first 600 in its own order.

• You cannot reorder them. Yandex ignores sort parameters on this surface, so newest-first is

not available.

• No reviewer contact details. Name, level, avatar and profile link are what Yandex publishes.
• publishedAt follows Yandex's own timestamp, which moves when a review is edited. An edited

old review can look recent and will pass newerThan.

• Nothing is translated. language changes the place name, address and category only.
• A city name has to be a place to Yandex. One it only matches to businesses is refused rather

than searched somewhere else: Springfield came back as shops in Belgrade. A geo id always works.

• Rows are a snapshot. Ratings, reply text and review counts all move.
• A big run can come back short. Yandex rate-limits hard, and a page it will not serve becomes

an uncharged diagnostic rather than a gap passed off as complete. Only delivered review rows are billed.

🧭 Which Yandex scraper do you need?

❓ Questions people ask

Do I need a Yandex API key? No. Nothing to apply for and no quota to watch.

Can I get more than 600 reviews for one place? No. Yandex stops serving them past 600, whatever you set.

Can I get the newest reviews only? Set newerThan to a date. You cannot ask Yandex to sort by date, so the run reads its relevance order and keeps what matches.

Which countries does this cover? Wherever Yandex Maps has an organisation directory, which includes Russia, Kazakhstan, Turkey and the wider CIS.

Can I schedule it? Yes. reviewId is stable, so diffing runs shows what is new.

Is this legal? These are public reviews. They carry personal data, which GDPR and similar laws cover, so have a reason for collecting it. Apify's write-up on scraping and the law is a good starting point, and we are not lawyers.

🆘 If something breaks

Open the Issues tab on the actor page. Send the organisation link or the search term and city you used, plus the run ID. The errorCode on the diagnostic row usually names the problem on its own.