Chrome Web Store Reviews Scraper
Pricing
from $0.06 / 1,000 review extracteds
Chrome Web Store Reviews Scraper
Scrape public Chrome Web Store extension reviews with ratings, reviewer names, dates, versions, locales, helpful votes, and source URLs.
Pricing
from $0.06 / 1,000 review extracteds
Rating
0.0
(0)
Developer
Automation Lab
Maintained by CommunityActor stats
0
Bookmarked
104
Total users
37
Monthly active users
2 days ago
Last modified
Categories
Features
Share
Collect public Chrome Web Store extension reviews, ratings, developer replies, and helpful votes for product, reputation, and competitor analysis. Sort by newest, most helpful, lowest or highest rating, filter by stars and date, and collect several review languages in one run.
This Apify Actor extracts review rows from public Chrome Web Store extension review pages. It is designed for extension teams, agencies, product marketers, support teams, and analysts who need review text and rating signals in a clean dataset.
What does Chrome Web Store Reviews Scraper do?
It turns Chrome Web Store review pages into structured data.
- ⭐ Star rating
- 💬 Review text
- 👤 Reviewer display name
- 🗓️ Review date
- 🌍 Review language
- 🧩 Extension ID, name and URL
- 🔢 Extension version the reviewer used
- 👍 Helpful and 👎 not-helpful vote counts
- 🛠️ Developer reply, its date and who replied
- 🕒 Scrape timestamp
The actor works with public Chrome Web Store extension detail URLs and /reviews URLs.
Who is it for?
Extension founders
Track what users praise, what they dislike, and which bugs appear after releases.
Product managers
Export reviews into spreadsheets, BI tools, or LLM workflows for roadmap planning.
Support teams
Monitor negative feedback and recurring issues without manually opening the Store page.
Marketing teams
Collect testimonials, review snippets, and rating evidence for campaign research.
Agencies
Audit review quality for multiple browser extension clients in one repeatable workflow.
Competitive intelligence teams
Compare review sentiment across competing Chrome extensions.
Why use this actor?
- 🚀 HTTP-first extraction, no browser overhead for the MVP path
- 📦 Clean dataset rows, ready for CSV, JSON, Excel, or API export
- 🔁 Repeatable inputs for scheduled monitoring
- 🔎 Rating and date filters applied before rows are saved and charged
- ↕️ Four sort orders: newest, most helpful, lowest rating, highest rating
- 🌍 Several review languages per run (Chrome Web Store shows each language separately)
- 🛠️ Developer replies included, so you can measure response rate and reply time
- 🧩 Accepts URLs or raw extension IDs
- 🔌 Also callable as a fast HTTP endpoint (Server API) for single lookups
- 🛡️ Uses only public Chrome Web Store review data
- 💸 Pay-per-review pricing keeps small runs inexpensive
Data you can extract
| Field | Description |
|---|---|
extensionId | Chrome Web Store extension ID |
extensionName | Extension name parsed from the public page |
extensionUrl | Extension detail URL |
reviewId | Stable review ID |
reviewerName | Public reviewer display name |
reviewerAvatarUrl | Public avatar URL when available |
rating | Star rating |
reviewBody | Review text |
reviewDate | Review creation date |
updatedDate | Review update date |
helpfulCount | People who marked the review helpful (0 when nobody did) |
unhelpfulCount | People who marked the review not helpful (0 when nobody did) |
developerResponse | Developer reply text, when there is one |
developerResponseDate | Date of the developer reply |
developerResponderName | Name shown on the developer reply |
extensionVersion | Extension version attached to the review |
locale | Review locale |
language | Review language requested for this row |
totalReviewCount | Reviews the store reports for this extension in the requested language |
pageUrl | Review page URL |
sourceUrl | Source URL used for the scrape |
scrapedAt | Actor scrape timestamp |
How much does it cost to scrape Chrome Web Store reviews?
The actor uses pay-per-event pricing.
- A start event of $0.005 is charged once per run. A run with invalid input is not charged.
- A review event is charged for each saved review row:
| Plan | Price per review | Per 1,000 reviews |
|---|---|---|
| Free | $0.000115 | $0.115 |
| Starter | $0.0001 | $0.10 |
| Scale | $0.000078 | $0.078 |
| Business and higher | $0.00006 | $0.06 |
- From 2 December 2026 the review price will be $0.0001 per review on Free and Starter, $0.00009 per review on Scale, and $0.00008 per review on Business and higher. The start fee stays $0.005.
- You control spend with
maxReviewsPerExtensionand the run's maximum charge. - Rating/date filters are applied before dataset writes, so only matching saved reviews incur the per-review event.
Example: set maxReviewsPerExtension to 20 for a quick sample, or set maxRating to 2 to save only negative reviews. The limit counts matching saved reviews per extension, not scanned reviews.
How to scrape Chrome Web Store reviews
- Open the actor on Apify.
- Paste one or more Chrome Web Store extension review URLs.
- Set
maxReviewsPerExtension. - Click Start.
- Download the dataset as CSV, JSON, Excel, or via API.
Input
{"startUrls": [{"url": "https://chromewebstore.google.com/detail/dark-reader/eimadpbcbfnmbkopoojfekhnkhdbieeh/reviews"}],"maxReviewsPerExtension": 20,"sortBy": "newest","minRating": 1,"maxRating": 2,"reviewsSince": "2026-01-01","languages": ["en", "de"]}
Input fields
startUrls
Chrome Web Store extension detail URLs or /reviews URLs.
extensionIds
Optional raw Chrome extension IDs.
maxReviewsPerExtension
Maximum matching reviews to save for each extension in each language (up to 10,000). The actor continues pagination until it saves this many matches, reaches the date cutoff, or exhausts available reviews.
sortBy
Review order: newest (default), helpful (most helpful first), lowestRating or highestRating. These are the Chrome Web Store's own sort options. With newest, the reviewsSince filter stops paging as soon as reviews get older than the cutoff.
minRating and maxRating
Optional inclusive star-rating bounds from 1 to 5. For example, set minRating to 1 and maxRating to 2 for negative-review monitoring. minRating cannot exceed maxRating.
reviewsSince
Optional inclusive creation-date cutoff. Use an ISO date such as 2026-01-01 (interpreted as midnight UTC) or an ISO date-time with a timezone such as 2026-01-01T12:00:00Z. Reviews without a public creation date do not match this filter.
reviewsPerPage
Advanced backend page size. The default is recommended.
language
Review language code such as en, de, fr, es, ja, pt-BR or zh-CN. Chrome Web Store returns only reviews written in this language, so a German review never appears in an English run.
languages
Optional list of language codes. It replaces language, and each language is collected separately up to maxReviewsPerExtension. Use it to see feedback from several markets in one run.
Output example
{"extensionId": "eimadpbcbfnmbkopoojfekhnkhdbieeh","extensionName": "Dark Reader","extensionUrl": "https://chromewebstore.google.com/detail/eimadpbcbfnmbkopoojfekhnkhdbieeh","reviewId": "b0ad8ba7-43cd-4260-a6be-7cc6e391f302","reviewerName": "Nico Andrade","rating": 3,"reviewBody": "It was amazing but have been crashing Salesforce for me, please update","reviewDate": "2026-09-20T09:23:10.000Z","helpfulCount": 2,"unhelpfulCount": 3,"developerResponse": "Please use Filter mode for Salesforce until the problem is fixed: ...","developerResponseDate": "2026-09-23T03:44:18.000Z","developerResponderName": "Alexander Shutau","extensionVersion": "4.9.132","locale": "en","language": "en","totalReviewCount": 5630}
Tips for best results
- Use
/reviewsURLs when possible. - Keep first tests small with 10 to 20 reviews.
- Increase limits after confirming the extension has enough public reviews.
- Schedule daily or weekly runs to monitor new feedback.
- Use
extensionIdswhen chaining from another Chrome Web Store dataset.
Common use cases
- Review monitoring for your own extension
- Competitor feedback analysis
- Rating trend exports
- Bug report discovery
- Customer voice analysis
- LLM sentiment classification
- Agency reporting
- Product launch monitoring
Integrations
Use the dataset with:
- Google Sheets exports
- Make or Zapier workflows
- Apify webhooks
- BI dashboards
- Data warehouses
- LLM summarization pipelines
- Support triage automations
API usage
Node.js
import { ApifyClient } from 'apify-client';const client = new ApifyClient({ token: process.env.APIFY_TOKEN });const run = await client.actor('automation-lab/chrome-web-store-reviews-scraper').call({startUrls: [{ url: 'https://chromewebstore.google.com/detail/dark-reader/eimadpbcbfnmbkopoojfekhnkhdbieeh/reviews' }],maxReviewsPerExtension: 20,});console.log(run.defaultDatasetId);
Python
from apify_client import ApifyClientclient = ApifyClient('MY-APIFY-TOKEN')run = client.actor('automation-lab/chrome-web-store-reviews-scraper').call(run_input={'startUrls': [{'url': 'https://chromewebstore.google.com/detail/dark-reader/eimadpbcbfnmbkopoojfekhnkhdbieeh/reviews'}],'maxReviewsPerExtension': 20,})print(run['defaultDatasetId'])
cURL
curl -X POST 'https://api.apify.com/v2/acts/automation-lab~chrome-web-store-reviews-scraper/runs?token=MY-APIFY-TOKEN' \-H 'Content-Type: application/json' \-d '{"startUrls":[{"url":"https://chromewebstore.google.com/detail/dark-reader/eimadpbcbfnmbkopoojfekhnkhdbieeh/reviews"}],"maxReviewsPerExtension":20}'
MCP usage
Connect through Apify MCP:
https://mcp.apify.com/?tools=automation-lab/chrome-web-store-reviews-scraper
Claude Code
$claude mcp add --transport http apify-chrome-web-store-reviews "https://mcp.apify.com/?tools=automation-lab/chrome-web-store-reviews-scraper"
Claude Desktop
Add this server in Settings → Connectors → Add custom connector:
- Name:
apify-chrome-web-store-reviews - URL:
https://mcp.apify.com/?tools=automation-lab/chrome-web-store-reviews-scraper
Cursor
Open Settings → Cursor Settings → MCP → Add new global MCP server and add:
{"mcpServers": {"apify-chrome-web-store-reviews": {"url": "https://mcp.apify.com/?tools=automation-lab/chrome-web-store-reviews-scraper"}}}
VS Code
Run MCP: Add Server from the Command Palette, select HTTP, enter the MCP URL above, and name it apify-chrome-web-store-reviews. Or add this to .vscode/mcp.json:
{"servers": {"apify-chrome-web-store-reviews": {"type": "http","url": "https://mcp.apify.com/?tools=automation-lab/chrome-web-store-reviews-scraper"}}}
Example prompts:
- "Scrape 50 reviews for this Chrome extension and summarize the main complaints."
- "Compare ratings and review text for these three extension IDs."
- "Find reviews mentioning broken features or recent bugs."
Scheduling
You can schedule this actor to run every day, week, or month.
Suggested monitoring setup:
- Add the extension review URL.
- Set a small review limit.
- Enable a schedule.
- Send dataset results to a webhook or spreadsheet.
Data quality notes
Chrome Web Store may expose different optional fields for different reviews.
Some reviews have no developer reply or version value; those fields are null.
Vote counts are 0 when nobody voted.
A removed or unlisted extension can still have reviews; its extensionName is then null.
Each run ends with a status message such as "Got 100 of 100 reviews" or the reason it stopped early.
Limitations
- The actor only collects public Chrome Web Store review data.
- It does not log in to Google accounts.
- It does not submit, edit, or vote on reviews.
- Each language is a separate review list in the store; reviews are not translated.
- Deleted or hidden reviews cannot be collected.
Legality
This actor is designed for public data extraction.
Is it legal to scrape Chrome Web Store reviews?
This actor is designed for public data extraction. You should still review Chrome Web Store terms, privacy rules, and your use case. Do not use exported data for spam, harassment, or decisions that require user consent.
FAQ
Can I scrape multiple extensions?
Yes. Add multiple URLs or extension IDs and set a per-extension limit.
Why did I get fewer reviews than requested?
The extension may have fewer public reviews in that language, or your filters match fewer. totalReviewCount shows how many reviews the store has in the requested language, and the run's status message says why it stopped.
Do I need a Google login?
No. The actor uses public review pages and public backend payloads.
Can I filter by rating or date?
Yes. Use minRating and maxRating for inclusive 1-to-5-star bounds, and reviewsSince for an inclusive ISO creation-date cutoff. Filtering happens before dataset writes and per-review charging.
What data is sent when a run fails?
Failed operations send sanitized diagnostic input, exceptions and actor/build/run IDs to our private GlitchTip service so we can repair them. Secret fields and URL queries are removed, and reports are kept for 30 days.
Does it use a browser?
No. The actor is HTTP-first for lower cost and faster runs.
Related scrapers
- https://apify.com/automation-lab/chrome-web-store-extension-scraper
- https://apify.com/automation-lab/google-play-reviews-scraper
- https://apify.com/automation-lab/app-store-reviews-scraper
Changelog
2026-11-17
Developer replies, not-helpful votes, sort order, several languages per run, a Server API, clear status messages, and no charge for invalid input.
0.1
Initial build for public Chrome Web Store extension reviews.
Server API
This Actor is also a Server Actor: copy the server URL from the Server tab and send authenticated HTTP requests. It answers in seconds from a warm process. Normal runs keep the full input and dataset.
GET /reviews
Returns reviews of one extension in one language.
| Query parameter | Required | Description |
|---|---|---|
extension | yes | Chrome Web Store URL or 32-letter extension ID |
maxReviews | no | 1 to 200, default 20 |
sortBy | no | newest (default), helpful, lowestRating, highestRating |
language | no | Review language code, default en |
minRating, maxRating | no | Star bounds from 1 to 5 |
reviewsSince | no | ISO date such as 2026-01-01 |
Response: { "ok": true, "count": 20, "results": [ ...review rows as in the dataset... ] }.
Charge: one review event per returned review. There is no start fee per request, and an error answer is free.
Errors use { "ok": false, "error": { "code", "message", "retryable" } }:
| Status | Code | When |
|---|---|---|
| 400 | INVALID_INPUT | Missing or invalid parameter |
| 402 | SPENDING_LIMIT_REACHED | Your spending limit does not allow the request |
| 404 | NOT_FOUND | No reviews match, or the extension has no listing and no reviews |
| 413 | RESPONSE_TOO_LARGE | The answer would be over 1 MB; use a normal run |
| 502 | UPSTREAM_ERROR | Chrome Web Store returned an error; retry |
| 503 | OVERLOADED, SHUTTING_DOWN | Too many requests at once, or the server is restarting; retry |
| 504 | UPSTREAM_TIMEOUT, TIMEOUT | Chrome Web Store or the request did not finish in time; retry |
curl -H "Authorization: Bearer $APIFY_TOKEN" \"<SERVER_URL>/reviews?extension=eimadpbcbfnmbkopoojfekhnkhdbieeh&maxReviews=10&sortBy=lowestRating"