linkfox-sellersprite-traffic-keyword

Original：🇨🇳 Chinese

Translated

1 scriptsChecked / no sensitive code detected

Leverage the traffic keyword reverse lookup capability of SellerSprite to query indicators such as keyword traffic sources, traffic proportion types, conversion types, organic positions, and ad positions by ASIN. It supports historical months and multi-dimensional sorting. This skill is triggered when users mention terms like ASIN reverse lookup traffic keywords, traffic keyword lists, keyword traffic structure, organic/ad keyword analysis, keyword conversion types, SellerSprite traffic keyword, Amazon traffic keywords, or reverse ASIN keywords. Even if users do not explicitly mention "SellerSprite", this skill should be triggered as long as the requirement is to view the keyword traffic sources and keyword list of a specific ASIN.

4installs

Sourcelinkfox-ai/linkfox-skills

Added on2026-05-12

NPX Install

npx skill4agent add linkfox-ai/linkfox-skills linkfox-sellersprite-traffic-keyword

SKILL.md Content (Chinese)

View Translation Comparison →

SellerSprite Traffic Keyword

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

Core Concepts

Reverse ASIN Keywords: Input a product ASIN to view the list of keywords that drive traffic to the product.
Traffic Proportion Types (
```
trafficKeywordTypes
```
): Main traffic keywords, precise traffic keywords, and
```
preciseLongTail
```
from the schema (displayed as "Conversion Lost Keywords" in the tool), etc.
Conversion Types (
```
conversionKeywordTypes
```
): Such as high-quality conversion keywords, stable keywords, lost keywords, etc.
Keyword Badges (
```
badges
```
): Such as organic search keywords, Amazon Choice recommended keywords, etc.

API Usage

Endpoint:

POST https://tool-gateway.linkfox.com/sellersprite/traffic/keyword

Auth: Header

Authorization: <api_key>

(

LINKFOXAGENT_API_KEY

)

For complete instructions, refer to
```
references/api.md
```
: It includes input parameter enums and constraints such as
```
marketplace
```
,
```
badges
```
,
```
trafficKeywordTypes
```
,
```
conversionKeywordTypes
```
,
```
orderField
```
, as well as top-level response fields, traffic keyword fields in
```
data[]
```
,
```
rankPosition
```
/
```
adPosition
```
,
```
stats[]
```
,
```
summaryList[]
```
, etc.
Runnable script:
```
scripts/sellersprite_traffic_keyword.py
```

Key Parameters

Parameter	Type	Required	Description
marketplace	string	Yes	Marketplace site, default is `US`
asin	string	Yes	The product ASIN to perform reverse lookup on
month	string	No	Historical month, format `yyyyMM` ; defaults to the last 30 days if not provided
page	integer	No	Page number, default is 1
size	integer	No	Number of items per page, default is 50, maximum is 100
keyword	string	No	Keyword filter
badges	string	No	Keyword badges, multiple values separated by commas
trafficKeywordTypes	string	No	Traffic proportion types, multiple values separated by commas
conversionKeywordTypes	string	No	Conversion types, multiple values separated by commas
orderField	string	No	Sort field, default is `rankPosition`
orderDesc	boolean	No	Whether to sort in descending order, default is `false`

Usage Examples

json

{
  "marketplace": "US",
  "asin": "B0XXXXXXXXX",
  "size": 50,
  "orderField": "rankPosition",
  "orderDesc": false
}

json

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

Display Rules

Priority display in results: Keywords, organic positions, ad positions, traffic proportion types, conversion types.
Clearly mark the query period (last 30 days or historical month).
When pagination exists, inform the total number of items and the current page.
Do not output subjective business suggestions unrelated to the interface unless explicitly requested by the user.

Important Limitations

Required parameters:
```
marketplace
```
,
```
asin
```
Maximum 100 items per page per request
```
yyyyMM
```
must be provided for historical queries

Feedback:

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

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

Call the feedback API as specified in

references/api.md

. Do not interrupt the user's flow.