Chrome Web Store Reviews Scraper

Extract public Chrome Web Store extension reviews with ratings, text, dates, helpful votes, reviewer names, and extension metadata.

Data fields

FieldTypeDescription
extensionIdstringValue exported as extensionId.
extensionUrlstringValue exported as extensionUrl.
extensionNamestring | nullValue exported as extensionName.
extensionAverageRatingnumber | nullValue exported as extensionAverageRating.
extensionRatingCountinteger | nullValue exported as extensionRatingCount.
reviewIdstringValue exported as reviewId.
ratinginteger | nullValue exported as rating.
reviewTextstring | nullValue exported as reviewText.

Input preview

startUrlsChrome Web Store URLs
extensionIdsExtension IDs
maxReviewsPerExtensionMaximum reviews per extension
sortReview order
languageLanguage
countryCountry code

API and agents

This actor can be run through Apify API, datasets, webhooks, schedules, and the official Apify MCP server.

Ready-to-run examples

Open a saved Apify example, adjust the input, and run the actor in your own Apify account.

View all examples

How this actor works

See example inputs, outputs, API usage, and practical limits before running this actor on Apify.

Open Apify page

Scrape Chrome Web Store extension reviews for browser extension reputation monitoring, competitor analysis, and product feedback research. Export structured review output with ratings, review text, reviewer names, dates, helpful votes, and extension metadata.

What data does it extract?

Chrome Web Store Reviews Scraper extracts public Chrome Web Store review data from browser extension pages for browser extension reputation monitoring and product feedback analysis. The Chrome Web Store reviews output includes extensionId, extensionUrl, extensionName, reviewId, rating, reviewText, reviewerName, reviewDate, and helpfulCount fields.

Use it to monitor your own extension reviews, analyze competitor extension feedback, collect user complaints for product research, or feed public review data into BI, support, and reputation workflows.

Use cases

Common use cases include Chrome Web Store review monitoring, browser extension reputation tracking, competitor review analysis, and product feedback research.

Who is this scraper for?

  • Extension publishers tracking new ratings, complaints, and version-specific feedback.
  • SaaS product teams researching browser-extension competitors and user pain points.
  • Support and reputation teams collecting public review text for triage or recurring reports.
  • Market researchers comparing ratings, review volume, and sentiment across related extensions.

Example input

{
  "extensionIds": ["cjpalhdlnbpafiamejdnhcphjbkeiagm"],
  "maxReviewsPerExtension": 25,
  "sort": "newest",
  "language": "en-US",
  "proxyConfiguration": { "useApifyProxy": false }
}

Example output

{
  "extensionId": "cjpalhdlnbpafiamejdnhcphjbkeiagm",
  "extensionUrl": "https://chromewebstore.google.com/detail/cjpalhdlnbpafiamejdnhcphjbkeiagm",
  "extensionName": "uBlock Origin",
  "extensionAverageRating": 4.697772137619854,
  "extensionRatingCount": 35460,
  "reviewId": "c05ba4d6-b816-49c4-80f6-ab1fcfdb1454",
  "rating": 5,
  "reviewText": "so good, chrome wants it gone",
  "reviewerName": "delta",
  "reviewerProfileUrl": "https://lh3.googleusercontent.com/a/...=s32-mo",
  "reviewDate": "2026-07-07T01:11:50.576Z",
  "publishedAt": "2026-07-07T01:11:50.576Z",
  "updatedAt": "2026-07-07T01:11:50.576Z",
  "developerResponse": null,
  "developerResponseDate": null,
  "helpfulCount": 1,
  "version": "1.72.0",
  "language": "en",
  "sourceUrl": "https://chromewebstore.google.com/detail/cjpalhdlnbpafiamejdnhcphjbkeiagm/reviews",
  "scrapedAt": "2026-07-10T10:03:18.675Z"
}

Input recipes

Start from a verified public Example task when you want a ready-made configuration:

Input settings

Setting JSON key Description Example
Chrome Web Store URLs startUrls Extension detail or /reviews URLs. https://chromewebstore.google.com/detail/ublock-origin/cjpalhdlnbpafiamejdnhcphjbkeiagm/reviews
Extension IDs extensionIds Chrome extension IDs when you do not want to paste full URLs. cjpalhdlnbpafiamejdnhcphjbkeiagm
Maximum reviews per extension maxReviewsPerExtension Per-extension review cap. Start small to verify output and cost. 25
Review order sort newest or helpful. newest
Language language Chrome Web Store UI language for requests. en-US
Country code country Optional reserved localization field. US
Proxy configuration proxyConfiguration Optional Apify proxy settings. Direct public requests normally work. { "useApifyProxy": false }

Provide at least one startUrls entry or one extensionIds entry.

Tips for best results

  • Start with maxReviewsPerExtension: 10 or 25 before scaling up.
  • Use extension IDs for clean repeatable monitoring inputs.
  • Use /reviews URLs when handing inputs from a browser or spreadsheet.
  • Schedule repeat runs and compare datasets to catch new negative reviews or support issues.
  • Keep direct requests enabled unless your environment requires Apify Proxy.

Limits and caveats

  • The Actor extracts public Chrome Web Store review data only; it does not log in or access private Google account data.
  • Chrome Web Store can change response shapes. If output becomes empty for a known public extension, contact Support with the run ID.
  • Very high maxReviewsPerExtension values can produce larger responses and longer runs. Split large competitor batches if needed.
  • Some optional fields, such as developer responses or reviewer profile URLs, are only present when Chrome Web Store exposes them publicly.

API usage

Node.js:

import { ApifyClient } from "apify-client";

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor("fetch_cat/chrome-web-store-reviews-scraper").call({
  extensionIds: ["cjpalhdlnbpafiamejdnhcphjbkeiagm"],
  maxReviewsPerExtension: 25,
  sort: "newest"
});
console.log(run.defaultDatasetId);

Python:

from apify_client import ApifyClient

client = ApifyClient("YOUR_APIFY_TOKEN")
run = client.actor("fetch_cat/chrome-web-store-reviews-scraper").call(run_input={
    "extensionIds": ["cjpalhdlnbpafiamejdnhcphjbkeiagm"],
    "maxReviewsPerExtension": 25,
    "sort": "newest",
})
print(run["defaultDatasetId"])

cURL:

curl -X POST "https://api.apify.com/v2/acts/fetch_cat~chrome-web-store-reviews-scraper/runs?token=YOUR_APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"extensionIds":["cjpalhdlnbpafiamejdnhcphjbkeiagm"],"maxReviewsPerExtension":25,"sort":"newest"}'

MCP and AI agents

Use this Actor from MCP-compatible tools through the official Apify MCP Server.

claude mcp add --transport http apify "https://mcp.apify.com?tools=fetch_cat/chrome-web-store-reviews-scraper"

JSON config example:

{
  "mcpServers": {
    "apify": {
      "url": "https://mcp.apify.com?tools=fetch_cat/chrome-web-store-reviews-scraper"
    }
  }
}

Example prompts:

  • "Run Chrome Web Store Reviews Scraper for cjpalhdlnbpafiamejdnhcphjbkeiagm and summarize the newest one-star reviews."
  • "Compare the latest 100 Chrome Web Store reviews for these extension IDs and list recurring support complaints."
  • "Export the review dataset, then group negative reviews by extension version and helpful vote count."

Ask your agent to run the Chrome Web Store Reviews Scraper for extension IDs, then summarize low-rated reviews, compare competitors, or export datasets for product analysis.

Support

If you need help, open an issue from the Actor run page and include the run ID or run URL plus:

  • Input JSON: the extensionIds, startUrls, and maxReviewsPerExtension you used.
  • Expected output: the reviews, ratings, or extension review count you expected to see.
  • Actual output: dataset item count, missing fields, or error message.
  • Reproducible public URL: a Chrome Web Store extension or /reviews URL that can be opened without logging in.

Common questions

Questions and answers reused from the canonical actor README.

Can I scrape reviews without a Google account?

Yes. The Actor uses public Chrome Web Store review pages and does not require source credentials.

Can I scrape multiple extensions in one run?

Yes. Add multiple extensionIds or multiple startUrls. The maxReviewsPerExtension limit applies to each extension.

Does it collect private user data?

No. It saves only public fields that Chrome Web Store exposes on review pages.

Why are some fields null?

Chrome Web Store does not expose every optional field for every review. Developer responses, helpful counts, version, or profile URLs can be missing.