Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
linkfox-ai avatar

Linkfox Sellersprite Traffic Keyword

  • 247 installs
  • 64 repo stars
  • Updated August 3, 2026
  • linkfox-ai/linkfox-skills

Pull SellerSprite keyword traffic, search volume, and relevancy for Amazon listings to build backend terms, PPC seeds, and title keyword maps.

About

Uses SellerSprite traffic and keyword APIs to rank Amazon search terms by volume, competition, and listing fit. Enables agents to assemble title bullets, backend keywords, and ad group seeds while monitoring lifecycle performance and refresh opportunities post-launch.

  • Search volume and traffic estimates
  • Keyword relevancy scoring
  • PPC and organic seed lists
  • Competitor keyword gaps
  • Listing backend term suggestions

Linkfox Sellersprite Traffic Keyword by the numbers

  • 247 all-time installs (skills.sh)
  • +39 installs in the week ending Aug 2, 2026 (Skillselion tracking)
  • Ranked #903 of 1,879 Marketing & SEO skills by installs in the Skillselion catalog
  • Data as of Aug 4, 2026 (Skillselion catalog sync)
npx skills add https://github.com/linkfox-ai/linkfox-skills --skill linkfox-sellersprite-traffic-keyword

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs247
repo stars64
Last updatedAugust 3, 2026
Repositorylinkfox-ai/linkfox-skills

What it does

Pull SellerSprite keyword traffic, search volume, and relevancy for Amazon listings to build backend terms, PPC seeds, and title keyword maps.

Files

SKILL.mdMarkdownGitHub ↗

SellerSprite Traffic Keyword

This skill helps query and analyze traffic keyword lists for an Amazon ASIN via SellerSprite.

Core Concepts

  • ASIN 反查词:以商品 ASIN 为输入,查看该商品获得流量的关键词列表。
  • 流量占比类型trafficKeywordTypes):主要流量词、精准流量词、以及 schema 中的 preciseLongTail(工具文案为「转化流失词」)等。
  • 转化类型conversionKeywordTypes):如转化优质词、平稳词、流失词等。
  • 词标签badges):如自然搜索词、Amazon Choice 推荐词等。

API Usage

  • Endpoint: POST https://tool-gateway.linkfox.com/sellersprite/traffic/keyword
  • Auth: Header Authorization: <api_key> (LINKFOXAGENT_API_KEY)
  • 完整说明见 references/api.md:含 marketplace/badges/trafficKeywordTypes/conversionKeywordTypes/orderField 等入参枚举与约束,以及响应顶层、data[] 流量词字段、rankPosition/adPositionstats[]summaryList[] 等。
  • Runnable script: scripts/sellersprite_traffic_keyword.py

Key Parameters

ParameterTypeRequiredDescription
marketplacestringYes市场站点,默认 US
asinstringYes要反查的商品 ASIN
monthstringNo历史月份,格式 yyyyMM;不传默认最近30天
pageintegerNo页码,默认 1
sizeintegerNo每页数量,默认 50,最大 100
keywordstringNo关键词筛选
badgesstringNo词标签,多值逗号分隔
trafficKeywordTypesstringNo流量占比类型,多值逗号分隔
conversionKeywordTypesstringNo转化类型,多值逗号分隔
orderFieldstringNo排序字段,默认 rankPosition
orderDescbooleanNo是否倒序,默认 false

Usage Examples

{
  "marketplace": "US",
  "asin": "B0XXXXXXXXX",
  "size": 50,
  "orderField": "rankPosition",
  "orderDesc": false
}
{
  "marketplace": "US",
  "asin": "B0XXXXXXXXX",
  "month": "202507",
  "trafficKeywordTypes": "primary,precise",
  "conversionKeywordTypes": "excellent,stable",
  "page": 1,
  "size": 100
}

Display Rules

1. 结果优先展示:关键词、自然位、广告位、流量占比类型、转化类型。 2. 明确标注查询周期(最近30天或历史月份)。 3. 当存在分页时,告知总数与当前页。 4. 不输出与接口无关的主观商业建议,除非用户明确要求。

Important Limitations

  • 必填参数:marketplaceasin
  • 单次每页最多 100 条
  • 历史查询需传 yyyyMM

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.

<!-- LF_LARGE_RESPONSE_BLOCK -->

Handling Large Responses

To avoid overflowing the agent context, persist the response to disk and extract only the fields you need:

python scripts/response_io.py run --script scripts/sellersprite_traffic_keyword.py --out-dir <DIR> '<params>'
python scripts/response_io.py read <file> --fields "<paths>"   # or --path "<JMESPath>"
Pick --out-dir outside any git working tree (e.g. /tmp/... on Unix, %TEMP%/... on Windows). Persisted responses may contain PII, pricing, or auth-sensitive data — do not commit them. Files are not auto-deleted; clean up when the task is done.

run writes the full response to a file and emits only a schema preview + file path. read projects specific fields, with --limit/--offset for slicing and --format json|jsonl|csv|table for output.

When to prefer this pattern — apply your judgment based on the response characteristics, e.g.:

  • High field count per record, or fields you don't need
  • Batch/paginated results (multiple items per call)
  • Long-text fields (descriptions, reviews, HTML, time series)
  • Output reused across later steps rather than consumed immediately

For small, single-use responses, calling the main script directly is fine.

⚠️ The preview is a truncated schema + sample, not the full data. Any field-level decision must read from the persisted file via read. <!-- /LF_LARGE_RESPONSE_BLOCK -->

Related skills

Marketing & SEOseocontentlifecycle

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.