Amazon Listing Competitor Analysis

📖 Brief

This skill runs a two-phase workflow on a single competitor Amazon listing. Phase 1 uses the BrowserAct Amazon Listing Extractor for SEO template to pull visible product data from that listing. Phase 2 diagnoses what that competitor does well and where the market shows gaps, then closes with your strategic opportunity points (how you can win next to them). Do not end with instructions that read like editing or rewriting this competitor's listing; the analyzed ASIN is evidence only. Final narrative output should be grounded in extracted data, not generic claims.

✨ Features

1. No hallucinations, ensuring stable and accurate data extraction: Pre-set workflows avoid AI generative hallucinations.
2. No CAPTCHA issues: No need to handle reCAPTCHA or other verification challenges.
3. No IP restrictions or geo-blocking: No need to deal with regional IP restrictions or geofencing.
4. Faster execution: Tasks execute faster compared to purely AI-driven browser automation solutions.
5. Extremely high cost-efficiency: Significantly reduces data acquisition costs compared to AI solutions that consume massive amounts of tokens.

🔑 API Key Guide

Before running, you must check the BROWSERACT_API_KEY environment variable. If it is not set, do not take other actions first; you should ask and wait for the user to provide it. Agent must inform the user:

"Since you haven't configured the BrowserAct API Key yet, please go to the BrowserAct Console to get your Key."

🛠️ Input Parameters

When calling the script, the Agent should flexibly configure the following parameters based on user needs:

1. ASIN

   • Type: string
   • Description: The ASIN (Amazon Standard Identification Number) of the Amazon product to analyze.
   • Example: B0CS62LY6P
   • Required: Yes

2. Marketplace_url

   • Type: string
   • Description: The base URL of the Amazon marketplace. Use the correct regional site for the listing.
   • Example: https://www.amazon.com/, https://www.amazon.de/
   • Default: https://www.amazon.com/

🚀 Invocation Method

Run Phase 1 extraction with the script below. After structured data is returned, the Agent performs Phase 2 analysis using the framework in Competitive Analysis Framework (Phase 2). The closing section must synthesize opportunity points for the user's business, not a checklist of edits applied to the competitor page under review.

python -u ./scripts/amazon_listing_competitor_analysis.py "B0CS62LY6P" "https://www.amazon.com/"

When only the ASIN is needed, the marketplace argument may be omitted; the script defaults to https://www.amazon.com/.

⏳ Running Status Monitoring

Since this task involves automated browser operations, it may take a long time (several minutes). The script will continuously output status logs with timestamps while running (e.g., [14:30:05] Task Status: running). Agent guidelines:

• While waiting for the script to return results, please keep an eye on the terminal output.
• As long as the terminal continues to output new status logs, it means the task is running normally. Do not misjudge it as a deadlock or unresponsiveness.
• If the status remains unchanged for a long time or the script stops outputting without returning a result, only then consider triggering the retry mechanism.

📊 Data Output

Upon successful execution, the script prints the API result string (or full task JSON if no string field is present). Typical fields include:

• asin, title, product_url, brand, price, coupon_text, rating, review_count, best_sellers_rank, availability, prime_eligible
• description, short_description, category, key_features, bullet_points
• main_image_url, additional_image_urls, seller_name, ships_from, sold_by
• specifications, product_details, attributes, and review-related blocks (reviewer, content, date, helpful votes, etc.)

Use this payload as the single source of truth for Phase 2; do not invent listing facts.

⚠️ Error Handling & Retry

During script execution, if errors occur (such as network fluctuations or task failure), the Agent should follow this logic:

1. Check the output content:

   • If the output contains "Invalid authorization", it means the API Key is invalid or expired. At this point, do not retry, but guide the user to recheck and provide the correct API Key.
   • If the output contains "concurrent" or "too many running tasks" or similar concurrency limit messages, it means the concurrent task limit for the current subscription plan has been reached. Do not retry; guide the user to upgrade their plan. Agent must inform the user:

     "The current task cannot be executed because your BrowserAct account has reached the limit of concurrent tasks. Please go to the BrowserAct Plan Upgrade Page to upgrade your subscription plan and enjoy more concurrent task benefits."

   • If the output does not contain the above error keywords but the task fails (e.g., output starts with Error: or returns empty results), the Agent should automatically try to run the script once more.

2. Retry limit:

   • Automatic retry is limited to once. If the second attempt still fails, stop retrying and report the specific error message to the user.

🌟 Typical Use Cases

1. Competitor listing teardown: Analyze one ASIN to see title formula, bullets, and differentiation language.
2. Keyword placement audit: Map where primary and long-tail terms appear across title, bullets, and description or A+ content.
3. Visual strategy review: Infer image narrative, infographic highlights, and video approach from extracted media data.
4. Buyer-validated selling points: Use high-helpful positive reviews to confirm what buyers value versus what the listing emphasizes.
5. Unmet needs mining: Use three-star and mixed reviews to find feature and expectation gaps.
6. Pre-launch gap analysis: Compare a planned positioning against a top competitor's listing structure.
7. Cross-marketplace research: Run the same ASIN on different regional Amazon URLs for localized copy signals.
8. Opportunity backlog from a rival listing: Turn extracted facts and gaps into a prioritized map of positioning, search, creative, and offer opportunities for your side of the market.
9. SEO and conversion benchmarking: Relate BSR, rating volume, and copy patterns without guessing unavailable metrics.
10. Review-driven objection handling: Surface recurring complaints to address in copy or images.

🧠 Competitive Analysis Framework (Phase 2)

After extraction succeeds, work through each dimension below. Every insight must be grounded in the actual extracted data.

Layer 1 — What the Competitor Did Right

1. Content Strategy

• Title formula: Information order, primary keyword placement, brand-first vs feature-first vs use-case-first.
• Bullet priority: What Bullet 1 leads with; selling point order across bullets (signal of tested conversion order).
• Differentiation language: How generic category features are phrased to sound distinct.
• A+ content: Modules implied by extracted content (comparison table, brand story, lifestyle, spec callouts).

2. Keyword Placement Strategy

Map where terms appear (not only which terms exist):

• Title (first 80 chars) → primary ranking bets
• Bullets 1–2 → secondary high-weight terms
• Bullets 3–5 → long-tail and use-case terms
• Description / A+ → supplementary terms and synonyms

3. Visual Content Strategy

• Image narrative arc: Sequence story (hero, lifestyle, pain point, specs, size comparison, social proof, guarantee).
• Infographic data: Numbers or attributes highligh