Ozon Scraper — Russia Marketplace Products, Prices & Reviews

What is Ozon Scraper — Russia Marketplace Products, Prices & Reviews?

Ozon Scraper is an Apify Actor for product-level collection from Ozon.ru. It accepts either search keywords or direct Ozon URLs, and each dataset record represents one product captured from a search result page, category page, seller page, or product page. The most useful fields include title, URL, SKU, price, old price, discount percent, rating, reviews count, seller name, brand, image, breadcrumbs, stock state, mode, and scrape timestamp. The outcome is a structured dataset that you can review in Apify, export, or read from the Dataset API.

Best fit and connected workflows

This Actor fits workflows where Ozon product data needs to be collected in a repeatable, structured way.

Common routing patterns include:

• keyword research, where a search term such as a product name becomes a product list on Ozon
• category monitoring, where a category URL is used to collect products from a specific shelf
• product tracking, where a known Ozon product URL is used for a single canonical record
• seller-oriented collection, where a seller URL is used as the starting point
• price-feed workflows, where compact records are easier to pass into reporting or monitoring systems
• Apify MCP-based agent workflows, where an AI agent calls this Actor and reads the resulting dataset

Input

Provide a residential proxy fallback Russian residential proxy URL and then use either keywords or startUrls.

Field	Type	Description
keywords	array of string	Search terms for Ozon.ru. One row per term. Defaults to ["iphone 15"].
startUrls	array of URLs	Direct Ozon URLs for product, category, seller, or search pages.
maxResults	integer	Hard cap on total products collected across the run. Defaults to 100.
enrichProducts	boolean	Opens each found product page for additional detail-page fields. Defaults to false.
sort	string	Sort for keyword searches: relevance, price, price_desc, rating, or new.
maxPagesPerStart	integer	Hard cap on how many result pages the Actor walks per keyword or category URL. Defaults to 5.

Focused input example

{
  "keywords": ["iphone 15"],
  "maxResults": 30,
  "enrichProducts": false,
  "sort": "relevance",
  "maxPagesPerStart": 3
}

Output

Each dataset item represents one product record.

Field	Type	Description
sku	string	Ozon product SKU from the product URL.
url	string	Canonical Ozon product URL.
title	string or null	Product title from the listing or product page.
brand	string or null	Brand from JSON-LD in detail mode.
price	number or null	Current price in RUB.
oldPrice	number or null	Original price before discount, when shown.
discountPercent	integer or null	Discount percentage derived from price and old price.
currency	string or null	ISO currency code, always RUB on Ozon.
rating	number or null	Average rating from 0 to 5.
reviewsCount	integer or null	Number of reviews shown on the tile or product page.
sellerName	string or null	Seller or merchant name.
image	string or null	Primary product image URL.
images	array of string or null	Full image gallery URLs in detail mode.
breadcrumbs	array of string or null	Category breadcrumb trail in detail mode.
inStock	boolean or null	Stock state inferred from the product page in detail mode.
mode	string	Source mode: search, category, or product.
keyword	string or null	Search keyword that surfaced the product in search mode.
scrapedAt	string	ISO-8601 UTC timestamp for collection time.

Illustrative output record

{
  "sku": "1234567",
  "url": "https://www.ozon.ru/product/iphone-15-pro-128gb-1234567/",
  "title": "iPhone 15 Pro",
  "brand": "Apple",
  "price": 89990,
  "oldPrice": 119990,
  "discountPercent": 25,
  "currency": "RUB",
  "rating": 4.8,
  "reviewsCount": 1432,
  "sellerName": "Apple Official",
  "image": "https://cdn1.ozone.ru/...",
  "images": ["https://cdn1.ozone.ru/..."],
  "breadcrumbs": ["Electronics", "Smartphones", "Apple"],
  "inStock": true,
  "mode": "product",
  "keyword": null,
  "scrapedAt": "2026-06-27T07:00:00.000Z"
}

How it works

This Actor uses an Apify Playwright-based browser setup with a FOSS unlocker stack, including patchright Chromium, humanized warmup, and session rotation. It accepts either keywords or direct URLs and auto-detects the source mode per URL. Keyword and category runs can walk result pages up to the configured page cap. When enrichProducts is enabled, each found product is opened individually to collect detail-page data such as brand, full image gallery, breadcrumbs, and JSON-LD-derived values.

Pricing

Ozon Scraper — Russia Marketplace Products, Prices & Reviews uses Pay per event plus Apify platform usage.

The charged events are:

• apify-actor-start for run start and initialization
• product-found for each Ozon product successfully extracted

Apify platform usage is billed separately according to the platform's live pricing. For the current pricing details, open the Pricing tab on this Actor page.

Example in words: if a execution collects fifty products, the event-based part scales with fifty product events plus one start event, and platform usage is billed separately based on the run's compute and storage usage.

Use with AI agents (MCP)

This Actor is usable through Apify MCP. It is a structured Ozon product extraction tool for agent workflows that need live marketplace records, including product titles, prices, ratings, review counts, sellers, brands, SKUs, images, and URLs.

Actor identity: khadinakbar/ozon-scraper

A realistic MCP prompt:

Collect the top Ozon.ru results for the keyword "iphone 15", return the product dataset, and keep the output focused on title, price, rating, reviews count, seller, brand, SKU, and URL.

Output interpretation for agents:

• results is the clean dataset endpoint for the full JSON record set
• preview is the table-oriented view for quick inspection
• priceFeed is the compact view for pricing workflows
• each row is provenance-linked to the Ozon source mode through the mode field
• scrapedAt indicates when the record was collected
• keyword is present for search-driven records
• pagination is constrained by maxPagesPerStart
• product counts are constrained by maxResults
• each additional product found adds one product-found event, so agents can plan collection size before starting

Apify API example

JavaScript

import { ApifyClient } from "apify-client";

const client = new ApifyClient({
  token: process.env.APIFY_TOKEN,
});

const actorId = "khadinakbar/ozon-scraper";

const run = await client.actor(actorId).call({
  keywords: ["iphone 15"],
  maxResults: 10,
  enrichProducts: false,
  sort: "relevance",
  maxPagesPerStart: 2,
});

const datasetId = run.defaultDatasetId;
const { items } = await client.dataset(datasetId).listItems({ clean: true });

console.log(items);

Best results and outcome guidance

Use the input shape that matches your starting point:

• use keywords when you begin from a product term
• use startUrls when you already have a product, category, seller, or search URL
• use enrichProducts when you need detail-page fields such as brand, images, breadcrumbs, or JSON-LD-derived data
• use maxResults as your run-level collection cap
• use maxPagesPerStart to bound how many pages each keyword or category can traverse
• use sort only for keyword searches

For routing, category URLs are a natural fit when you want a defined shelf of products, and direct product URLs are a natural fit when you want one canonical item record.

Continue the workflow

• Then use Poshmark Listings Scraper for Resale Data to extend Ozon Scraper — Russia Marketplace Products, Prices & Reviews with a neighboring commerce research source when the brief calls for Poshmark data.
• Then use Naver Product Shopping Scraper to extend Ozon Scraper — Russia Marketplace Products, Prices & Reviews with a neighboring commerce research source when the brief calls for Naver Shopping data.

Design note

I found that the output contract includes a compact priceFeed view with only sku, title, price, oldPrice, discountPercent, currency, inStock, url, and scrapedAt, which makes the Actor suitable for lightweight price-tracking workflows.

FAQ

Should I use keywords or start URLs?

Use keywords for discovery from a search term. Use startUrls for direct Ozon product, category, seller, or search pages.

What happens when I use a product URL?

The Actor records a single product-oriented result and can include detail-page fields such as brand, images, breadcrumbs, and stock state.

What if I want compact price monitoring output?

Use the priceFeed dataset view. It presents the minimal fields needed for a price-tracking workflow.

Can I control how much the execution collects?

Yes. maxResults caps the total number of products, and maxPagesPerStart caps page traversal per keyword or category.

Is this Actor useful for agent workflows?

Yes. It is Apify MCP-ready and exposes structured product records that agents can read from the dataset endpoints.

Responsible use

Use this Actor in line with applicable laws, marketplace terms, and your own data governance requirements. Provide a valid Russian residential proxy URL, keep your collection scope aligned with your task, and review the output fields before building downstream automation.