Chrome Web Store & Firefox Add-ons Scraper: Extensions, Reviews & Rankings

Scrape Chrome Web Store, Firefox Add-ons (AMO) and Microsoft Edge Add-ons extension data in one clean schema: user count, rating, rating count, version, last updated, developer and contact email, category, permissions with a permission risk score, reviews, and category / keyword rank snapshots. Schedule it with onlyNewReviews to get only the new reviews since your last run.

Built for security & IT teams auditing browser extensions, extension developers tracking competitors and reviews, and growth / M&A teams sizing extension businesses. HTTP only (no browser), so it is fast and cheap.

What you get

Store	Profile	Reviews	Rank snapshots
Chrome Web Store	✅ users, rating, ratings count, version, updated, size, languages, developer + email, privacy policy, full manifest permissions	✅ newest or most helpful, paged	✅ category (first page, ~32) and search (~10)
Firefox Add-ons	✅ daily users, weekly downloads, rating + 1-5★ histogram, version, created/updated, license, permissions, data-collection permissions, Recommended badge	✅ newest first, paged, developer replies	✅ category (sort by users/rating/updated…) and search, up to 500
Edge Add-ons	✅ active installs, rating, version, updated, permissions, privacy disclosures	–	–

Permission risk score

Every profile carries permissionRiskLevel (low / medium / high), permissionRiskScore (0-100), highRiskPermissions, mediumRiskPermissions and accessesAllSites, computed from the extension's manifest (e.g. <all_urls>, cookies, webRequestBlocking, debugger, nativeMessaging, history). Use it to flag risky extensions across your fleet in one run.

Change monitor (new)

Set monitorChanges (and a monitorId) and every profile gets a changes list versus your last run: new version, permissions added or removed, developer or contact email change, permission risk level change, description rewrite, users down or up 10%+, rating move of 0.1+. Add onlyChanged and you are only returned (and only charged) for extensions that actually changed. The first run saves the baseline (isFirstSnapshot: true). Typical use: a daily schedule over the extensions your company allows, alerting when one quietly asks for <all_urls> or changes owner.

Use cases

• Extension security audit: paste the extension IDs installed in your company and get users, last update, developer and permission risk for each.
• Competitor tracking: users, rating and version for your competitors on Chrome and Firefox, every week.
• Supply-chain watch: schedule daily with monitorChanges + onlyChanged to get an alert-ready record when an installed extension changes owner, version or permissions.
• Review monitoring: schedule daily with onlyNewReviews + reviewRatings: [1,2] to catch new complaints.
• Category & keyword rankings: who ranks for "password manager" or tops productivity/workflow today.
• Market research / lead generation: developer names, websites and support emails for extensions in a niche.

Input examples

Profiles only:

{ "extensions": ["https://chromewebstore.google.com/detail/ublock-origin-lite/ddkjiahejlhfcafbddmgiahcphecmpfh", "firefox:darkreader", "edge:odfafepnkmbhccpbejgmiehpchacaeak"] }

New 1-2★ reviews (daily schedule):

{ "extensions": ["nngceckbapebfimnlniiiahkandclblb"], "includeReviews": true, "reviewRatings": [1, 2], "onlyNewReviews": true, "monitorId": "bitwarden-complaints" }

Daily change watch (only changed extensions are returned and charged):

{ "extensions": ["nngceckbapebfimnlniiiahkandclblb", "firefox:darkreader"], "monitorChanges": true, "onlyChanged": true, "monitorId": "fleet-watch" }

Rank snapshots:

{ "rankStore": "firefox", "rankCategories": ["privacy-security"], "rankSearchKeywords": ["tab manager"], "rankMaxItems": 100 }

Accepted inputs: store URLs (Chrome chromewebstore.google.com/detail/... and old chrome.google.com/webstore/detail/..., addons.mozilla.org/.../addon/<slug>/, microsoftedge.microsoft.com/addons/detail/...), bare 32-letter IDs (Chrome by default, or Edge via defaultStore), Firefox slugs or GUIDs, and chrome: / firefox: / edge: prefixes.

Output

One dataset with recordType = extension, review or rank-snapshot, plus ready-made views: Extension profiles, Reviews, Rank snapshots and Ranked extensions (flat). A RUN_SUMMARY record lists every input with its status (ok / not_found / error).

Example profile (shortened):

{
  "store": "chrome", "extensionId": "ddkjiahejlhfcafbddmgiahcphecmpfh", "name": "uBlock Origin Lite",
  "developerName": "Raymond Hill (gorhill)", "developerEmail": "ubo@raymondhill.net",
  "users": 22000000, "rating": 4.519, "ratingCount": 3739, "category": "make_chrome_yours/privacy",
  "version": "2026.1021.1354", "lastUpdated": "2026-10-21T17:59:52Z", "manifestVersion": 3,
  "permissions": ["activeTab", "declarativeNetRequest", "scripting", "storage"], "hostPermissions": ["<all_urls>"],
  "permissionRiskLevel": "high", "permissionRiskScore": 71, "accessesAllSites": true
}

Pricing (pay per event)

Event	Price	Per 1,000
Actor start	$0.00005	–
Extension profile	$0.003	$3.00
Review	$0.00075	$0.75
Rank snapshot (one whole list)	$0.01	$10 per 1,000 lists

Not-found extensions, filtered-out reviews and empty lists are free. Platform usage is included. Example: 50 extension profiles + 20 reviews each = $0.15 + $0.75 = $0.90.

Notes & limits

• Chrome user counts are as the store shows them (rounded, e.g. 22,000,000). Firefox users = average daily users. Edge users = active installs.
• Chrome reviews come newest first (or most helpful); a date filter stops paging as soon as it reaches older reviews.
• Chrome rank snapshots cover the first results page; Firefox lists page up to 500.
• Edge reviews and change alerts (new version, permission or owner change) are on the roadmap. Request features in the Issues tab.
• Public store pages and APIs only, politely paced. No login, no personal data beyond public reviewer display names.

FAQ

Can I schedule it? Yes. Save a task and add a schedule; use onlyNewReviews with a monitorId so each run returns only new reviews. Integrations? Export to CSV/Excel/JSON, or send results to Google Sheets, Slack, Make, Zapier or n8n through Apify integrations. Do I need a proxy? No for normal volumes. For thousands of Chrome extensions per run you can enable Apify Proxy.