Ecommerce Amazon Asin Keywords

SIF ASIN Keyword Analysis

This skill guides you on how to query and analyze traffic keywords for a specific Amazon ASIN, helping Amazon sellers understand which keywords drive traffic to a product and how that product ranks for each keyword.

Core Concepts

SIF ASIN Keyword data reveals the keywords that bring traffic to a specific Amazon product (ASIN). For each keyword, you can see the product's organic search rank, SP ad rank, search volume, traffic share, display position types, and various performance markers. This is the go-to tool for reverse ASIN keyword lookup.

Single-ASIN limitation: This tool queries one ASIN at a time. If the user wants to compare multiple ASINs, you must make separate queries for each.

Ranking logic: A smaller rank value means a better (higher) position. Rank 1 means the product appears first in search results. When a user says "ranking improved", the numeric value decreased; "ranking dropped" means the value increased.

Data Fields

Per-keyword record (each element of data)

Top-level response fields (alongside data)

Supported Marketplaces

13 marketplaces: US (United States), UK (United Kingdom), DE (Germany), CA (Canada), JP (Japan), FR (France), ES (Spain), IT (Italy), MX (Mexico), AU (Australia), AE (United Arab Emirates), BR (Brazil), SA (Saudi Arabia).

Default marketplace is US. Use US when the user does not specify a marketplace. Codes outside this list will be rejected by the API pattern.

How to Invoke

• API Endpoint: POST /sif/asinKeywords (complete params/response/error codes in references/api.md)
• Python Script: python scripts/amazon_asin_keywords.py '<JSON params>' [--inline]
• Cost constraint: This tool consumes credits; the same session and parameter combination is called only once by default, with a 24h local cache in the script. On failure or empty results, do not automatically retry with different keywords, pagination, or postal codes; inform the user about additional consumption before continuing to search.

Output strategy (script default behavior):

• Always write the full response to <cwd>/nexscope/<YYYY-MM-DD>/<session>/data/nexscope-sif-asin-keywords-<timestamp>.json (<cwd> is the working directory at script execution time, i.e. the current project directory in Claude Code; <session> is taken from the SESSION_ID env var, auto-grouped by user task; do not write to /tmp, error if current directory is not writable)
• Response body <= 8 KB: print full JSON to stdout after saving
• Response body > 8 KB: print only summary to stdout after saving (top-level fields, common counts like total/costToken, length of largest list field + first 3 samples)
• Add --inline to force full output to stdout (still saves to disk)

Data reading tip: Check the summary first to decide if it's enough; when specific fields are needed, prefer using jq or ConvertFrom-Json to extract from the saved json file on demand, avoiding loading the entire JSON into context.

Parameter Guide

Required Parameter

• asin (string, required): The Amazon ASIN to look up. Only one ASIN per request.

Optional Parameters

• country (string, default US): Marketplace code. See Supported Marketplaces above.

• keyword (string): Filter results to keywords containing this text. Translate the keyword into the language of the target marketplace when possible.

• timePieceType (string, default latelyDay): Time window type -- latelyDay (most recent N days), month (specific month), week (specific week).

• timePieceValue (string, default 7): Value paired with timePieceType.

  • When timePieceType=latelyDay -> only 7 or 30 are supported
  • When timePieceType=month -> YYYY-MM (e.g. 2026-04)
  • When timePieceType=week -> the week's start date YYYY-MM-DD (e.g. 2026-04-13)

• conditions (string): Comma-separated condition filters. Flag-style filters:

  • nfPosition -- organic traffic keywords
  • isSpAd -- SP ad keywords
  • isBrandAd -- brand ad keywords
  • isVedioAd -- video ad keywords
  • isAC -- Amazon's Choice keywords
  • isAccurateKw -- precise traffic keywords
  • isAccurateTailKw -- precise long-tail keywords
  • isPurchaseKw -- purchase-converting keywords
  • isQualityKw -- high-quality conversion keywords
  • isStableKw -- stable conversion keywords
  • isLossKw -- conversion-loss keywords
  • isInvalidKw -- invalid-exposure keywords
  • isMultiVariantKw -- keywords ranking organically across multiple variants
  • isSearchVolUpKw -- keywords whose search volume increased year-over-year
  • isSearchVolDownKw -- keywords whose search volume decreased year-over-year

  Period-count filters (all / new-in):

  • totalPeriod.in -- newly-entered traffic keywords this period
  • nfKeywordCnt.total / nfKeywordCnt.in -- keywords with (new) organic exposure
  • adKeywordCnt.total / adKeywordCnt.in -- keywords with (new) ad exposure
  • allSpKeywordCnt.total / allSpKeywordCnt.in -- (new) SP-ad keywords (regular + recommendation)
  • spKeywordCnt.total / spKeywordCnt.in -- (new) SP regular keywords
  • recSpKeywordCnt.total / recSpKeywordCnt.in -- (new) SP recommendation keywords
  • allSbKeywordCnt.total / allSbKeywordCnt.in -- (new) SB-ad keywords
  • sbKeywordCnt.total / sbKeywordCnt.in -- (new) SB regular keywords
  • sbvKeywordCnt.total / sbvKeywordCnt.in -- (new) SBV keywords

• sortBy (string): Sort field. Options: lastRank (organic rank), adLastRank (ad rank), updateTime (update time), searchesRank (search popularity rank), estSearchesNum (monthly search volume).

• desc (boolean, default true): Sort in descending order. Set to false for ascending.

• pageNum (integer, default 1): Page number for pagination.

• pageSize (integer, default 100, range 10-100): Number of results per page.

Building Effective Queries

1. Always specify the marketplace: Set country to one of the 13 supported codes.
2. Pick the right time window: The default is the latest 7 days. Pass timePieceType=month + timePieceValue=YYYY-MM for a specific month, or timePieceType=week + timePieceValue=YYYY-MM-DD for a specific ABA week.
3. Use keyword filtering: When the user is interested in specific keywords, pass the keyword parameter to narrow results.
4. Apply condition filters: Use conditions to focus on specific keyword types (e.g., only organic keywords, only purchase-converting keywords, or newly-entered SP keywords via spKeywordCnt.in).
5. Choose appropriate sorting: Sort by estSearchesNum for highest search volume keywords, or by lastRank for best-ranking keywords.
6. Handle pagination: The API returns at most 100 results per page. Use pageNum to retrieve additional pages if the total exceeds 100.

Usage Examples

1. Find all traffic keywords for an ASIN on the US marketplace

asin: "B0XXXXXXXX", country: "US"

2. Find organic traffic keywords only

asin: "B0XXXXXXXX", country: "US", conditions: "nfPosition"

3. Find keywords containing "charger" sorted by search volume (ascending)

asin: "B0XXXXXXXX", country: "US", keyword: "charger", sortBy: "estSearchesNum", desc: false

4. Find high-converting keywords

asin: "B0XXXXXXXX", country: "US", conditions: "isPurchaseKw,isQualityKw"

5. Find SP ad keywords on the Japan marketplace

asin: "B0XXXXXXXX", country: "JP", conditions: "isSpAd", sortBy: "adLastRank", desc: false

6. Find precise long-tail keywords with stable conversion

asin: "B0XXXXXXXX", country: "US", conditions: "isAccurateTailKw,isStableKw"

7. Find newly-entered SP traffic keywords in April 2026

asin: "B0XXXXXXXX", country: "US", timePieceType: "month", timePieceValue: "2026-04", conditions: "spKeywordCnt.in"

8. Find keywords whose search volume is trending up

asin: "B0XXXXXXXX", country: "US", conditions: "isSearchVolUpKw", sortBy: "estSearchesNum", desc: true

Display Rules

1. Present data only: Show query results in clear tables without subjective business advice.
2. Ranking clarification: When showing ranking data, remind users that lower numeric values mean better (higher) positions.
3. Share formatting: Display trafficShare, naturalTrafficShare, paidTrafficShare, and clickConcentrationShare as percentages (multiply by 100). For example, 0.05 should be shown as 5%.
4. Click concentration wording: clickConcentrationShare measures how concentrated clicks are on top ASINs under the keyword -- it is NOT a conversion rate. Label it clearly so users don't confuse it with clickToPurchaseConversionRate.
5. Period disclosure: When showing counts sourced from *.in/*.total filters or comparing numbers, annotate the period range -- default is last 7 days; if timePieceType=month or week is set, surface the resolved period (periodEndDate / abaCreateDateWeek).
6. Marker translation: Translate marker arrays into human-readable labels. For example, ["isMainKw", "isAccurateKw"] should display as "Main Traffic, Precise Traffic".
7. Display position translation: Translate position type arrays into readable labels: natural = Organic, ac = Amazon's Choice, sp = SP Ad, top = Top Brand Ad, bottom = Bottom Brand Ad, er = Editorial Recommendation, vedio = Video Ad, tr = Top Rated, trfob = Top Rated Frequently Bought.
8. Pagination notice: When results have more pages, inform the user of the total count and suggest fetching additional pages.
9. Error handling: When a query fails, explain the reason based on the msg field and suggest adjusting query parameters.
10. Multi-ASIN requests: If the user asks about multiple ASINs, make separate API calls for each and present the results together.

Important Limitations

• Single ASIN per request: Only one ASIN can be queried at a time.
• Page size cap: Maximum 100 results per page.
• Time window granularity: timePieceType=latelyDay only supports timePieceValue=7 or 30; arbitrary N-day windows are not supported.
• Marketplace coverage: 13 marketplaces only -- IN / NL / SE / PL / TR / SG are no longer available.
• Keyword language: The keyword filter should ideally be in the language of the target marketplace.

User Expression & Scenario Quick Reference

Applicable -- Keyword analysis for specific Amazon products:

Not applicable -- Needs beyond single-ASIN keyword lookup:

• Broad keyword research not tied to a specific ASIN (use ABA data tools instead)
• Product reviews, listing copywriting
• Sales estimation, revenue analysis
• Advertising campaign management (bids, budgets)
• Category-wide keyword trends without a specific ASIN

Authentication

Set the NEXSCOPE_API_KEY environment variable. If credentials are missing or expire, visit https://www.nexscope.ai/help/skills-external-access?co-from=skillNS to top up credits.