Seerfar Ozon market hot keyword search: filters Ozon (and Wildberries) market keywords by multi dimensional metrics including search volume, growth, product count, seller count, competitor count, p...
Добавьте инструмент одной командой или скачайте проверенный архив версии.
npx skills add nexscope-ai/nexscope-ecommerce-skills --skill ecommerce-ozon-market-keyword-searchThis skill searches Ozon marketplace keywords in the Seerfar analytics database and filters them by rich performance metrics — search volume, 30-day growth, product/seller/competitor counts, average price, monthly sales/revenue, conversion & view concentration, ratings/reviews, and more. Each returned keyword carries a full market profile (market space, return/cancellation rate, top products, Chinese translation), making it the starting point for Ozon keyword selection, blue-ocean term mining, and market-opportunity analysis.
Unit of data is the keyword, not the SKU: unlike a product search, this endpoint returns marketplace search terms ("hot keywords"), each enriched with market metrics. You discover which search terms are worth targeting on Ozon.
Platform coverage: each keyword record carries a platform field (0 = Ozon, 1 = Wildberries). The dataset is Ozon-centric; Wildberries rows appear where available. There is no input to restrict the platform — filter client-side if needed.
Date semantics: searchDate selects the data month. Pass 2026-04-01 to get March 2026 data; omit it for the last 30 days. Metrics such as searchVolume (monthly search volume) and count30GrowthRate (monthly search growth) are relative to the selected period.
Match mode: matchType controls how the keywords array is matched — 0 exact, 1 fuzzy. Choose the mode that fits your discovery intent when filtering by keyword text.
| Parameter | Type | Required | Description |
|---|---|---|---|
| page | object | yes | Pagination {page, pageSize, orders[]}. page from 1 (default 1), pageSize default 20. orders[] = {field, direction} with direction DESC/ASC. |
| keywords | array | no | Keyword list to filter (max 1000); combined with matchType. |
| matchType | integer | no | Keyword match mode: 0 exact, 1 fuzzy. |
| searchDate | string | no | Data date yyyy-MM-dd; default last 30 days. 2026-04-01 → March 2026 data. |
| categories | array | no | Category ID list (max 1000). |
| searchVolume | {min,max} | no | Monthly search volume range. |
| searchChange30 | {min,max} | no | 30-day search change range. |
| monthlySales | {min,max} | no | Monthly sales range. |
| monthlyRevenue | {min,max} | no | Monthly revenue range. |
| price | {min,max} | no | Average price range. |
| productViews | {min,max} | no | Product view range. |
| products | {min,max} | no | Product count range. |
| volume | {min,max} | no | Volume range. |
| marketSpace | {min,max} | no | Market space range. |
| conversionSharing | {min,max} | no | Conversion concentration range. |
| reviews | {min,max} | no | Review count range. |
| ratings | {min,max} | no | Rating range. |
| sellers | {min,max} | no | Seller count range. |
| weight | {min,max} | no | Weight range. |
| uId | string | no | User ID. |
| memberId | string | no | Member ID (data attribution). |
All range filters are {min, max} objects; supply either or both bounds. Only page is required.
/seerfar/ozon/marketKeywordSearch (full parameters/responses/error codes in references/api.md)python scripts/ozon_market_keyword_search.py '<JSON params>' [--inline]Output strategy (script default behavior):
<cwd>/nexscope/<YYYY-MM-DD>/<session>/data/ecommerce-ozon-market-keyword-search-<timestamp>.json (<cwd> is the working directory when the script executes, which in Claude Code is the current project directory; <session> is taken from the SESSION_ID environment variable, automatically grouped by user task; do not write to /tmp; error if the current directory is not writable)total/costToken, length of the largest list field + first 3 samples)--inline to force full output to stdout (still writes to disk)Reading data: Check the summary first to determine if it is sufficient. When specific fields are needed, use jq or ConvertFrom-Json to extract from the saved JSON file as needed, avoiding loading the entire JSON into context.
If you encounter authentication or credit issues:
NEXSCOPE_API_KEY environment variable is not set.NEXSCOPE_API_KEY environment variable with a valid API key.1. Hottest keywords right now (sort by search volume)
{"page": {"page": 1, "pageSize": 10, "orders": [{"field": "searchVolume", "direction": "DESC"}]}}
2. Blue-ocean terms — high volume, few sellers
{"page": {"page": 1, "pageSize": 20, "orders": [{"field": "searchVolume", "direction": "DESC"}]}, "searchVolume": {"min": 10000}, "sellers": {"max": 50}}
3. Filter by keyword text (fuzzy, Russian)
{"page": {"page": 1, "pageSize": 20}, "keywords": ["телефон"], "matchType": 1}
4. A specific data month with a sales floor
{"page": {"page": 1, "pageSize": 20}, "searchDate": "2026-04-01", "monthlySales": {"min": 1000}}
page.orders: the dataset is large — always sort by the metric you care about (searchVolume DESC for popularity, count30GrowthRate DESC for rising terms, sellers ASC for low competition).searchVolume floor with a low sellers ceiling to surface blue-ocean keywords; add conversionSharing / marketSpace bounds to qualify demand.keywords + matchType to scope a niche: pass seed terms in Russian with matchType: 1 (fuzzy) to enumerate related long-tail terms.searchDate: omit it for current trends (last 30 days); pass an explicit date for month-over-month comparison.query / queryCn (Chinese translation), then searchVolume, count30GrowthRate, productCount, sellers, avgPrice.query; the queryCn field provides a Chinese translation when available.platform (0/1) so the user can distinguish them.total is large, show the top rows and remind the user they can persist the full response via the large-response pattern below, or page further with page.page.code is not 200 (or errcode is not 200), explain the reason from msg / errmsg and suggest adjusting filters.page is required: a payload without page is rejected.platform field.categories requires Seerfar category IDs, not human-readable names.pageSize and page to page; very large pageSize values may be capped server-side.products[*] (Top Products) and categoryInfos[*] (category path and cross-border availability flag) are structured and decision-useful — see references/api.md for sub-fields. dimension / columns are opaque or partially populated; relevancy / titleDensity / wordCount are usually absent.Applicable — Ozon keyword market research:
| User Says | Scenario |
|---|---|
| "What are the Ozon hot / trending keywords" | Hottest keywords by search volume |
| "Ozon blue-ocean terms: low competition, high search volume" | Blue-ocean term mining (high volume, few sellers) |
| "Ozon rising keywords / fast-growing terms" | Rising keywords (growth sort) |
| "Long-tail keywords around a Russian seed term" | Fuzzy keyword expansion |
| "Market space / competitor count / seller count for an Ozon keyword" | Keyword market profile |
Not applicable — Needs beyond keyword market data:
Boundary judgment: if the user wants to discover and rank search terms on Ozon by market metrics, start here. If they already have a SKU / seller / category and want entities under it, route to the corresponding Seerfar Ozon data source.
| Путь | Размер | SHA256 |
|---|---|---|
| SKILL.md | 10710 | 1800688db2340d59... |
| manifest.json | 307 | 4396b690d2fb1fb3... |
| references/api.md | 8841 | 9761a82ac9080af5... |
| scripts/ozon_market_keyword_search.py | 6771 | 39153aad69354b42... |
npx skills add nexscope-ai/nexscope-ecommerce-skills --skill ecommerce-ozon-market-keyword-search или скачайте ZIP-архив.Войдите, чтобы оставить комментарий.
Комментариев пока нет.