Seerfar Ozon keyword mining: mines Ozon (and Wildberries) related keywords around a seed keyword with multi dimensional filtering by search volume, growth, product count, seller count, competitor c...
Добавьте инструмент одной командой или скачайте проверенный архив версии.
npx skills add nexscope-ai/nexscope-ecommerce-skills --skill ecommerce-ozon-keyword-miningThis skill mines Ozon marketplace keywords around a seed keyword in the Seerfar analytics database and filters the discovered terms by rich performance metrics — search volume, 30-day growth, product/seller/competitor counts, average price, relevancy, title density, cart-add conversion, and more. Each mined keyword carries a full market profile (market space, return/cancellation rate, top products, Chinese translation), making it the starting point for Ozon keyword expansion, long-tail discovery, and seed-term opportunity analysis.
Seed-driven, not market-browse: unlike a market keyword search, this endpoint requires a keyword (the seed) and returns terms related to that seed, each enriched with market metrics. You expand outward from a term you already have in mind.
Relevancy is the mining signal: relevancy scores how closely a mined term relates to the seed (the seed term itself returns at relevancy: 100, related terms rank lower); titleDensity reflects how densely the term appears in product titles. Both are populated on every row — sort by relevancy DESC to keep expansions on-topic.
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.
Match mode: matchType controls how the seed keyword (and includeKeywords) are matched — 0 exact, 1 fuzzy. Choose fuzzy to broaden the expansion, exact to stay tight.
No date or category selectors: this endpoint does not accept searchDate or categories. If you need month-over-month or category-scoped browsing, use the market keyword search skill instead.
| Parameter | Type | Required | Description |
|---|---|---|---|
| keyword | string | yes | Seed keyword; mining expands around it (maxLength 1000). |
| page | object | yes | Pagination {page, pageSize, orders[]}. page from 1 (default 1), pageSize default 20. orders[] = {field, direction} with direction DESC/ASC. |
| matchType | integer | no | Keyword match mode: 0 exact, 1 fuzzy. |
| includeKeywords | array | no | Terms that must appear (max 1000); narrows the expansion. |
| excludeKeywords | array | no | Terms to exclude (max 1000); removes irrelevant expansions. |
| wordCount | {min,max} | no | Keyword word/char count range. |
| searchVolume | {min,max} | no | Monthly search volume range. |
| searchChange30 | {min,max} | no | 30-day search change range. |
| productViews | {min,max} | no | Product view range. |
| products | {min,max} | no | Product count range. |
| sellers | {min,max} | no | Seller count range. |
| price | {min,max} | no | Average price range. |
| marketSpace | {min,max} | no | Market space range. |
| conversionSharing | {min,max} | no | Conversion concentration range. |
| relevancy | {min,max} | no | Relevancy-to-seed range. |
| uniqQueriesWCa | {min,max} | no | Cart-add count range. |
| ca | {min,max} | no | Cart-add conversion rate range. |
| titleDensity | {min,max} | no | Title density range. |
| adRivalCount | {min,max} | no | Ad competitor count 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. keyword and page are both required.
/seerfar/ozon/keywordMining (full parameters/responses/error codes in references/api.md)python scripts/ozon_keyword_mining.py '<JSON params>' [--inline]Output strategy (script default behavior):
<cwd>/nexscope/<YYYY-MM-DD>/<session>/data/ecommerce-ozon-keyword-mining-<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. Expand around a seed term (sort by search volume)
{"keyword": "платье", "page": {"page": 1, "pageSize": 10, "orders": [{"field": "searchVolume", "direction": "DESC"}]}}
2. Blue-ocean expansions — high volume, few sellers
{"keyword": "телефон", "page": {"page": 1, "pageSize": 20, "orders": [{"field": "searchVolume", "direction": "DESC"}]}, "searchVolume": {"min": 10000}, "sellers": {"max": 50}}
3. Keep expansions on-topic with relevancy + title density
{"keyword": "наушники", "page": {"page": 1, "pageSize": 20, "orders": [{"field": "relevancy", "direction": "DESC"}]}, "relevancy": {"min": 50}}
4. Narrow with include / exclude lists
{"keyword": "часы", "page": {"page": 1, "pageSize": 20}, "includeKeywords": ["женские"], "excludeKeywords": ["ремень"], "matchType": 1}
keyword: it is required and defines the expansion center. Pass it in Russian for Ozon.page.orders: sort by the metric you care about (searchVolume DESC for popularity, relevancy DESC for on-topic, sellers ASC for low competition).searchVolume floor with a low sellers ceiling to surface blue-ocean expansions; add relevancy / titleDensity bounds to keep them relevant to the seed.includeKeywords / excludeKeywords to steer the expansion: force in must-have modifiers and strip noise without running a second query.query / queryCn (Chinese translation), then searchVolume, count30GrowthRate, productCount, sellers, avgPrice; show relevancy to convey closeness to the seed (the seed term itself is 100).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 the seed keyword or filters.keyword + page required: a payload missing either is rejected.searchDate; you cannot pick a data month here. Use the market keyword search skill for month-scoped data.categories is not accepted as input; each returned keyword carries a categories ID array you can group or filter client-side.dimension / categoryInfos not returned: both are defined in the schema and appear as columns, but real data[*] rows do not populate them on this endpoint. (categoryInfos IS populated on the sibling market-keyword-search endpoint — don't assume parity.)products[*] (Top Products) is structured and decision-useful — see references/api.md for sub-fields. (categoryInfos[*] is documented there for schema completeness but is not returned on this endpoint; dimension / columns are opaque or partially populated.)Applicable — seed-driven Ozon keyword expansion:
| User Says | Scenario |
|---|---|
| "Mine Ozon related keywords around term XX" | Seed-keyword expansion |
| "Ozon long-tail keyword mining / expansion around a term" | Long-tail mining around a seed |
| "Ozon blue-ocean expansion for a term: low competition, high search" | Blue-ocean expansion (high volume, few sellers) |
| "Ozon keywords related to XX, sorted by relevancy" | Relevancy-ranked expansion |
| "Ozon keyword expansion with include/exclude filters" | Include/exclude steered expansion |
Not applicable — Needs beyond seed-driven keyword mining:
searchDate / categories).Boundary judgment: if the user wants to expand outward from a seed term and rank the related terms by market metrics, start here. If they want to browse the whole market of keywords (no seed) or scope by month/category, route to the market keyword search skill.
| Путь | Размер | SHA256 |
|---|---|---|
| SKILL.md | 11728 | 9d46c9847d6c41c2... |
| manifest.json | 281 | 16c3331083492c10... |
| references/api.md | 11094 | 2c99106204c82c3d... |
| scripts/ozon_keyword_mining.py | 6710 | a8a80b857a18d284... |
npx skills add nexscope-ai/nexscope-ecommerce-skills --skill ecommerce-ozon-keyword-mining или скачайте ZIP-архив.Войдите, чтобы оставить комментарий.
Комментариев пока нет.