Reviews · from a YouTube video, Sep 28, 2026 · Added

Competitor Review Mining and Product Improvement Report with Codex

Pull hundreds of reviews for an ASIN and turn them into product improvements for a refresh or new launch

958 unique reviews

“958 unique reviews, 46% of the 2,000 displayed”

Per source Self-reported by the source, not independently verified.

Copy-paste prompt

Copy-paste promptPrompt written by us, based on this case
Open this Amazon listing [URL] in the browser. Go through the written reviews by star rating (1 to 5 stars), clicking 'see more' as needed, and collect review text, rating and date into a table. Report how many you collected out of how many are displayed. Then group the complaints and praise into themes with counts and 2 quoted reviews each, and list product improvement opportunities ranked by how often they come up. Don't log in to any account. Save this process as a skill I can rerun on another ASIN.

The source didn't publish its exact prompt. We wrote this starter so you can try the same workflow. Replace anything in [brackets].

See the original YouTube video

What they did

John Aspinall (Aspi) says Grok Bot and Meta's Muse get blocked on Amazon pages, so he used the Chromium browser built into Codex instead, on GPT-6 Astra Medium. On an Echo Dot listing he had Codex page through the reviews by star rating, then asked it to turn what it did into a reusable skill whose report adds areas of opportunity for making the product better. He then ran the skill on a costume listing with color variations.

How it went

On the Echo Dot it recovered "958 unique reviews, 46% of the 2,000 displayed", and the updated report added six product opportunities, such as software onboarding and connectivity recovery, each with review evidence. On the second listing it was "done under 9 minutes", collecting "196 out of the 246 displayed" written reviews, and it flagged that the product details showed a different ASIN than the URL, likely a variation. It couldn't reach all of the Echo Dot's roughly 19,000 reviews.

We only report what the source says. Results are self-reported unless noted.

Worth knowing

He says Amazon doesn't like scraping, advises against logging into Seller Central in that browser or running agent workflows there, and frames this as research only. Variation listings slow it down, and he notes paid review APIs may suit sellers checking many ASINs.

Original source

YouTube videoJohn Aspinall (Aspi) (John Aspinall)Published Sep 28, 2026 · youtube.com https://www.youtube.com/watch?v=EPTrWROPLW4Open the source

Keep going

Related use cases

Reviews

Review Sentiment Analysis with Jungle Scout (Ask Cobalt / MCP)

Group review text into complaint and praise themes and compare with competitors ToolsJungle ScoutSourceVendor docs · Jungle ScoutSharedAug 27, 2026PromptSeller's own prompt
Show promptHide prompt for Review Sentiment Analysis with Jungle Scout (Ask Cobalt / MCP),Seller's own prompt
What features do customers wish this product had?
Compare review sentiment for our product against the top 3 competitors — what do they praise that we get criticized for?
Has a specific complaint theme increased in frequency since our last listing update, suggesting the change backfired?
Which negative review themes correlate most strongly with declining conversion rate, versus ones that are just noise?

Reviews

Review Gap Analysis vs Competitors with an n8n Template

Compare your review complaints with competitors' praise Toolsn8n, OpenAI API, Bright DataSourceWorkflow template · Daniel Shashko (n8n template)SharedAug 13, 2026PromptWritten by us
Show promptHide prompt for Review Gap Analysis vs Competitors with an n8n Template,Written by us
Here are reviews for my product and for [3] competitors: [paste or attach].
1. For each product, list complaint themes, praise themes and feature requests, with a count and one example quote each.
2. Find gaps: things buyers complain about in my product that they praise in a competitor's.
3. Write a 5-line brief: the top 3 gaps and what to change in the product or the listing for each.
Only use what's in the reviews.

ReviewsShows real results

One-Star Review Pattern Detection with Claude Code

Read a best seller's 1-star reviews before committing to inventory
$0.0477“The run cost $0.0477” self-reported
ToolsClaude CodeSourceX post · Jasper LiSharedAug 10, 2026PromptWritten by us
Show promptHide prompt for One-Star Review Pattern Detection with Claude Code,Written by us
Here are all the 1-star and 2-star reviews for [ASIN] with their dates and any 'used for X days' mentions: [paste]. Find failure patterns, especially WHEN the product fails (days or weeks of use) and HOW. Count how many reviews support each pattern and quote short supporting snippets with review dates. Tell me whether the timing lines up with Amazon's return window.

ReviewsShows real results

Review Requests Ad Check by Ratings, Profit and Returns with Claude

Decide which products, if any, should use Amazon's paid Review Requests ad before you spend on it
$18.57“the product lost $18.57” vendor-affiliated
ToolsClaude, Seller Labs MCPSourceX post · Nhan Dinh (Seller Labs)SharedNov 12, 2026PromptWritten by us
Show promptHide prompt for Review Requests Ad Check by Ratings, Profit and Returns with Claude,Written by us
For every product in my catalog, show: total ratings, last 30 days' units, net profit per unit after fees, ad spend and cost of goods, return count and top return reasons, and the main themes of reviews from the last 60 days. Then mark which products qualify for Amazon's Review Requests ad (under 1,000 ratings) and, of those, which are profitable with few complaints. Don't recommend paying for ratings on any product that lost money in the last 30 days.

Reviews

Return Root Causes and One Listing Fix per ASIN with a Claude Skill

Find why a product gets returned and pick one listing change to test ToolsClaude, Adi (Claude skill)SourceBlog post · Ori FirouzSharedOct 20, 2026PromptWritten by us
Show promptHide prompt for Return Root Causes and One Listing Fix per ASIN with a Claude Skill,Written by us
For my 5 ASINs with the highest return cost, read the FBA customer returns report, the product's reviews and the current listing side by side. For each ASIN give:
- the likely root cause, with return counts, reason-code shares, 2-3 buyer quotes, the gap in the listing, and a confidence level (never 'high' from reason codes alone);
- ONE change to test (title under 75 characters, counted; image brief; size chart; or supplier brief);
- today's return rate as the baseline to check at 30 and 60 days.
Don't change anything and don't contact buyers.

Reviews

Competitor Review Mining with Claude

Classify competitor reviews into patterns and turn them into tested ad angles ToolsClaudeSourceX post · wetracked.ioSharedAug 28, 2026PromptSeller's own prompt
Show promptHide prompt for Competitor Review Mining with Claude,Seller's own prompt
You are a senior ecommerce customer-research and creative strategist.

I am giving you public Amazon reviews from competing products.

Analyze only the supplied reviews. Do not invent facts, product capabilities, customer quotes, frequencies, or conclusions.

First, classify each review as:
1. Product defect
2. Expectation gap
3. Setup or usability friction
4. Missing feature
5. Wrong customer or use case
6. Shipping, seller, or delivery noise
7. Isolated complaint with insufficient evidence

Then create a table showing:
• Complaint pattern
• Number of reviews mentioning it
• Situation in which it happens
• Consequence for the customer
• Outcome the customer wanted
• Objection our advertising must answer
• Proof required before making the claim
• Review IDs supporting the pattern

Do not treat one-star reviewers as representative of the entire market. Identify repeated patterns separately from isolated complaints.

Next, compare the negative reviews with any positive reviews I provide. Find where customers disagree and explain what product type, expectation, or use case may cause the difference.

Finally, create 12 original ad experiments for my product.

For every experiment, provide:
• Hook
• Body copy
• Visual concept
• Customer problem
• Promise
• Proof needed
• Awareness stage
• Hypothesis being tested
• Result we should measure

Do not copy review wording, use a reviewer as a testimonial, attack a named competitor, or claim our product solves a problem unless my product information supports it.