Chrome Web Store Scraper avatar

Chrome Web Store Scraper

Pricing

from $5.00 / 1,000 extensions

Go to Apify Store
Chrome Web Store Scraper

Chrome Web Store Scraper

Extract Chrome Web Store extension data: name, rating, users, category, developer email, version, reviews. By URL, keyword search, or the entire catalogue.

Pricing

from $5.00 / 1,000 extensions

Rating

0.0

(0)

Developer

Gio

Gio

Maintained by Community

Actor stats

0

Bookmarked

3

Total users

1

Monthly active users

4 days ago

Last modified

Share

Extract structured data for any Chrome Web Store extension: ratings, user counts, category, developer name and email, version, size, last-updated date, supported languages, description, and user reviews. Scrape specific extensions, search by keyword, or crawl the entire catalogue (~320,000 extensions).

Perfect for market intelligence, competitor tracking, and developer-lead generation.

Four ways to use it

ModeInputNotes
Specific extensionsextensionUrlsDetail URLs or raw 32-char IDs. Fastest.
Keyword searchqueriesDiscovers and scrapes every matching extension.
Full cataloguescrapeAllApps: trueCrawls the whole store via its sitemap (cap with maxItems).
ReviewsincludeReviews: trueAdds user reviews to each extension. Works with any mode.

Output

One dataset item per extension:

FieldDescription
id32-char extension ID
nameExtension name
urlDetail page URL
iconUrlIcon image URL
ratingAverage rating (e.g. 4.7)
ratingCountNumber of ratings
usersWeekly user count
categoryCategory (e.g. Privacy & Security)
versionCurrent version
sizePackage size
lastUpdatedLast update date (ISO)
developerDeveloper name
developerEmailDeveloper contact email (when published)
taglineShort summary
descriptionFull description
languagesSupported languages
websiteUrl, privacyPolicyUrlDeveloper links (when present)
reviewsArray of { author, rating, text, postedAt, version, language } (when includeReviews)

Example input

{
"queries": ["ad blocker"],
"maxItems": 50,
"includeReviews": true,
"maxReviewsPerExtension": 20
}

Notes

  • Extension data, the catalogue, and reviews are read directly over HTTP; keyword search uses a real browser because the store's search results are rendered client-side.
  • developerEmail is only present when the developer chose to publish a contact address.
  • Review collection is paged in batches of 10 up to maxReviewsPerExtension.