Parsing Reviews from External Platforms for 1C-Bitrix
Reviews on a product card improve conversion, but building up organic reviews from scratch takes time. A quick start: parsing reviews from Yandex Market, OZON, Wildberries, Google Maps, and other platforms where ratings about your products or business have already accumulated. It is important to distinguish between product reviews and company reviews — these are two different scenarios with different architectures.
Two review parsing scenarios
Scenario 1: product reviews — for online stores. Link reviews from Yandex Market/OZON to specific SKUs in the 1C-Bitrix catalog.
Scenario 2: company reviews — for service businesses. Aggregate reviews from Google Maps, 2GIS, Yandex Maps, and display them on the site.
Storing reviews in 1C-Bitrix
1C-Bitrix has a built-in reviews module (vote), but a Highload block is more convenient for imported reviews:
Table ExternalReviews:
UF_PRODUCT_ID — link to the infoblock element (or 0 for company reviews)
UF_SOURCE — 'yandex_market' | 'ozon' | 'google' | '2gis'
UF_AUTHOR — author name
UF_RATING — rating (1–5)
UF_TEXT — review text
UF_DATE — review date on the platform
UF_SOURCE_ID — unique review ID on the source
UF_ACTIVE — moderation status (Y/N)
UF_SOURCE_ID prevents duplicates on repeated parser runs.
Parsing Yandex Market
Yandex Market actively protects against scraping. Working approaches in 2025:
Official Partner API — if you are a seller on Yandex Market, reviews are available via the API. The most reliable path.
Headless parsing — Playwright with proxy rotation. The review page loads via AJAX; you need to wait for the [data-zone-name="reviews"] component to render.
Mobile version — m.market.yandex.ru is simpler to parse, has less protection, and reviews are in more straightforward HTML.
Parsing OZON and Wildberries
OZON: XHR requests to /api/v1/review/ are visible in Network DevTools — you can call them directly, passing the session cookie. Works until the authorization scheme changes.
Wildberries: public review endpoint — https://feedbacks.wildberries.ru/api/v1/feedbacks?imtId={id}. The imtId parameter is the internal WB product ID, which must be found on the product page.
Moderation and display
Do not display parsed reviews without moderation — they may include negative or irrelevant content. The default UF_ACTIVE = N flag; the manager reviews them in the admin panel.
For display, create a component based on bitrix:main.include or a custom one that reads from the Highload block with a UF_ACTIVE = Y filter. Output ratings with schema.org/Review microdata — this affects search result snippets.
Case study: review aggregation for a restaurant chain
Goal: collect reviews from Google Maps, Yandex Maps, and 2GIS for 12 locations, updated weekly.
Implementation:
- Google Maps: official Places API (free quota of 5 requests/sec)
- Yandex Maps: Playwright + proxy pool (organization API is closed)
- 2GIS: undocumented API
https://public-api.reviews.2gis.com/v1/reviews— works without authentication - Highload block linked to the "Restaurants" infoblock via
UF_BRANCH_ID
Result: 847 reviews aggregated on the first run, 60–80 new ones per week. Average rating and a block of recent reviews displayed on each restaurant page.
Work timeline
| Phase | Duration |
|---|---|
| Analyzing platforms, choosing parsing method | 4–8 hours |
| Developing the parser (1 platform) | 1–2 days |
| Highload block, storage schema | 4–6 hours |
| Frontend component with microdata | 4–8 hours |
| Moderation, admin interface | 4–6 hours |
| Testing, schedule configuration | 4 hours |
Total for 3 platforms: 7–10 working days.