SuperAPI AI Directory
Partner with us中文AI newsFavorites
Skillslinkfox-seerfar-ozon-keyword-back-search

linkfox-seerfar-ozon-keyword-back-search

Marketing & growth

View repository

Updated 10-15 17:33

About this skill

Seerfar Ozon Keyword Back-Search

This skill reverse-looks-up Ozon search keywords by a list of product SKU IDs in the Seerfar analytics database: pass up to 20 SKUs (your own listing or a competitor's) and it returns the search terms those products appear under — organic and/or ad — each enriched with a full market profile (search volume, 30-day growth, product/seller/competitor counts, average price, conversion concentration, top products, plus per-term organic/ad channel, natural rank, exposure, and conversion in the dimension object). It is the starting point for Ozon keyword reverse lookup, listing-title optimization, and competitor traffic-word discovery.

Core Concepts

SKU-driven, not keyword-driven: unlike keyword mining (expand from a seed term) or market keyword search (browse the whole market), this endpoint takes skuIds and returns the search terms those specific products rank for. The direction is product → keywords (reverse).

hasVariant is required: every request must declare whether to exclude variants — 0 keep variants, 1 exclude variants. Pick 1 when you want de-duplicated keyword coverage for a parent listing.

Natural vs ad terms: type filters the search-term channel — ["0"] organic (organic search terms) only, ["1"] ad (ad search terms) only; omit to get both. Combine with the naturalRank / adRank range filters to qualify positioning.

Back-search metrics live in dimension: each returned term carries a dimension object with the reverse-lookup-specific metrics — type (0 organic / 1 ad), naturalRank (the SKU's natural rank for that term), exposure (exposure share, 0–1), conversion (conversion rate, 0–1), and x (opaque position indicator). The input filters type / naturalRank / adRank / exposure / conversion filter on these same per-term values. Note: relevancy is defined in the schema but is not returned by this endpoint.

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 includeKeywords / excludeKeywords are matched — 0 exact, 1 fuzzy.

Parameters

Parameter Type Required Description
skuIds array yes Reverse-lookup SKU list, max 20.
hasVariant integer yes Variant exclusion: 0 keep variants, 1 exclude variants.
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.
type array no Search-term channel filter: 0 organic, 1 ad; omit for both.
historyDate string no Historical month yyyy-MM (e.g. 2026-02); omit for current period.
includeKeywords array no Terms that must appear (max 1000).
excludeKeywords array no Terms to exclude (max 1000).
searchVolume {min,max} no Monthly search volume range.
searchChange30 {min,max} no 30-day search change range.
wordCount {min,max} no Keyword word/char count range.
productViews {min,max} no Product view range.
products {min,max} no Product count range.
sellers {min,max} no Seller count range.
marketSpace {min,max} no Market space range.
conversionSharing {min,max} no Conversion concentration range.
uniqQueriesWCa {min,max} no Cart-add count range.
ca {min,max} no Cart-add conversion rate range.
conversion {min,max} no Conversion rate range.
titleDensity {min,max} no Title density range.
adRivalCount {min,max} no Ad competitor count range.
adRank {min,max} no Ad rank range.
naturalRank {min,max} no Natural rank range.
exposure {min,max} no Exposure 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. skuIds, hasVariant, and page are all required.

How to call

  • API endpoint：POST /seerfar/ozon/keywordBackSearch(for full parameters/response/error codes see references/api.md）
  • Python script：python scripts/seerfar_ozon_keyword_back_search.py '<JSON 参数>' [--inline]
  • Cost constraints: this tool consumes compute; within the same session the same parameter combination is by default called only once, and the script has a 24h local cache. On failure/empty results, do not automatically try successive probes by changing keywords, paging, or changing the zip code; if you need to continue searching, first explain to the user that additional consumption will be incurred.

Output strategy (script default behavior)：

  • Alwayswrite the full response to <cwd>/linkfox/<YYYY-MM-DD>/<session>/data/linkfox-seerfar-ozon-keyword-back-search-<timestamp>.json（<cwd> is the working directory when the script runs, which in Claude Code is the current project directory;<session> is taken from the environment variable SESSION_ID, automatically aggregated according to the user task;writing to /tmp is prohibited, and if the current directory is not writable, report an error)
  • Response body ≤ 8 KB: after writing to disk, print the full JSON to stdout
  • Response body > 8 KB: after writing to disk, stdout outputs only a summary (top-level fields, common counts such as total/costToken, length of the largest list field + first 3 samples)
  • Add --inline to force full printing to stdout (also written to disk)

Data reading suggestions: first look at the summary to judge whether it is sufficient; when specific fields are needed, prefer to use jqorConvertFrom-Json to extract on demand from the saved json file, avoiding bringing the entire JSON into context.

Resolve authentication and compute issues

When the following abnormal situations occur, use references/onboarding.md to guide resolution:

Abnormal situations

  • API Key not configured: the environment variable is not configured LINKFOX_AGENT_API_KEY, and LINKFOXAGENT_API_KEY。
  • Response 401 or 402 status code
  • Response indicates insufficient compute or balance: the message contains "insufficient compute balance/insufficient billing/insufficient balance/quota exceeded/insufficient balance/package expired/recharge required/please recharge", or content with a similar meaning.

Usage Examples

1. Reverse-lookup a single SKU's traffic keywords (sort by search volume)

{"skuIds": [4380710124], "hasVariant": 0, "page": {"page": 1, "pageSize": 10, "orders": [{"field": "searchVolume", "direction": "DESC"}]}}

2. Organic terms where the SKU ranks near the top

{"skuIds": [4380710124], "hasVariant": 1, "type": ["0"], "naturalRank": {"max": 10}, "page": {"page": 1, "pageSize": 20, "orders": [{"field": "searchVolume", "direction": "DESC"}]}}

3. Ad search words only, with an ad-rank floor

{"skuIds": [4380710124], "hasVariant": 0, "type": ["1"], "adRank": {"max": 50}, "page": {"page": 1, "pageSize": 20, "orders": [{"field": "searchVolume", "direction": "DESC"}]}}

4. Narrow with include / exclude lists

{"skuIds": [4380710124], "hasVariant": 0, "page": {"page": 1, "pageSize": 20}, "includeKeywords": ["платье"], "excludeKeywords": ["ремень"], "matchType": 1}

How to Build Queries

  1. Always lead with skuIds + hasVariant: both are required and define the reverse-lookup target. Use real Ozon SKU IDs (the same IDs returned by Seerfar Ozon product / shop / category skills).
  2. Lead with page.orders: sort by the metric you care about (searchVolume DESC for traffic weight, sellers ASC for low competition, count30GrowthRate DESC for rising terms).
  3. Split organic vs ad with type: pass ["0"] or ["1"] to focus a listing-optimization pass (organic) or an ads pass (ad), then bound naturalRank / adRank to qualify positioning — these filter on the values surfaced in each row's dimension.
  4. Use includeKeywords / excludeKeywords to steer: force in must-have modifiers and strip noise without running a second query.

Display Rules

  1. Present data only: show reverse-looked-up keyword metrics in a clear table without subjective advice.
  2. Lead with keyword columns: query / queryCn (Chinese translation), then searchVolume, count30GrowthRate, productCount, sellers, avgPrice; show dimension.naturalRank and dimension.type (organic/ad) to convey how the SKU ranks for each term.
  3. Russian keywords: preserve the original query; the queryCn field provides a Chinese translation when available.
  4. Channel tag: when type is omitted and both organic and ad rows are present, show dimension.type (0 organic / 1 ad) and dimension.naturalRank so the user can distinguish them.
  5. Large result sets: when 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.
  6. Error handling: when code is not 200 (or errcode is not 200), explain the reason from msg / errmsg and suggest adjusting the SKU list or filters.

Important Limitations

  • skuIds + hasVariant + page required: a payload missing any of these is rejected.
  • skuIds capped at 20: pass more than 20 and the request is rejected or truncated.
  • No keyword seed: this endpoint has no keyword parameter — it is reverse (SKU → keywords), not expansion (keyword → keywords). Use the keyword mining skill to expand from a seed.
  • No searchDate / categories input: only historyDate (historical month) is accepted; there is no category filter. Use the market keyword search skill for month- or category-scoped browsing.
  • Nested fields: products[*] (Top products) and dimension (per-term back-search metrics: type, naturalRank, exposure, conversion, x) are structured and decision-useful — see references/api.md for sub-fields. categoryInfos is defined in the schema/columns but is not returned in data[*] on this endpoint (same as the keyword-mining sibling; the market-keyword-search sibling does return it — don't assume parity). relevancy is likewise defined in the schema but not returned.

User Expression & Scenario Quick Reference

Applicable — SKU-driven Ozon keyword reverse lookup:

User Says Scenario
"reverse-lookup the keywords for this Ozon product / SKU" Reverse keyword lookup for a SKU
"which search terms bring traffic to this Ozon link" Traffic-word discovery for a listing
"order-driving keywords / traffic keywords for Ozon competitor SKUs" Competitor traffic-word mining
"organic keywords / ad keywords for a certain Ozon product" Organic vs ad term breakdown
"Ozon keyword reverse lookup, reverse-lookup keywords by SKU" Generic reverse keyword lookup

Not applicable — Needs beyond SKU-driven reverse lookup:

  • Browse/rank the whole market's hot keywords (no SKU) → use the Seerfar Ozon market keyword search skill.
  • Expand outward from a seed keyword → use the Seerfar Ozon keyword mining skill.
  • A specific SKU's price/sales/stock → use a product-level Seerfar Ozon data source.
  • A specific seller's catalog → use the Seerfar Ozon shop search skill.
  • Category-tree browsing → use the Seerfar Ozon category search skill.

Boundary judgment: if the user has a product/SKU (own or competitor) and wants the search terms it ranks for, start here. If they want to browse the market (no SKU) or expand from a seed keyword, route to the market keyword search or keyword mining skill respectively.

Compute consumption rules

Consumes 23 compute.

Users pay fees due to compute consumption. Please fully assess: when this skill needs to be called frequently, or the user's expectation of compute consumption is insufficient, be sure to remind the user and let the user decide whether to continue.

Feedback:

Auto-detect and report feedback via the Feedback API when any of the following apply:

  1. The functionality or purpose described in this skill does not match actual behavior
  2. The skill's results do not match the user's intent
  3. The user expresses dissatisfaction or praise about this skill
  4. Anything you believe could be improved

Call the feedback API as specified in references/api.md. Do not interrupt the user's flow.

For more high-quality, professional cross-border e-commerce skills, set LinkFox Skills.