🧩 Chrome Web Store Scraper — users, ratings and the publisher's email

Turn the Chrome Web Store into a developer lead list. Search a keyword or browse a category and get one row per extension: user count, rating, review count, category, version, size, last update — and the publisher's name, contact email and website.

Every listing we have scraped carried a contact email. Measured: 100% across 94 extensions in three runs (2026-08-26/27).

What does this actor do?

• 🧩 name, tagline, description, version, size, languages
• 👥 users — the install count (Adobe Acrobat: 320,000,000)
• ⭐ rating and reviewCount
• 📧 publisherEmail — the developer contact shown on the public listing (present on every extension we measured)
• 🏢 publisherName and 🌐 publisherWebsite
• 🗂️ category / categoryGroup
• 📅 lastUpdated, firstPublished
• 🔗 storeUrl, supportUrl, privacyPolicyUrl

Example input

{
  "categories": ["productivity/developer", "productivity/workflow"],
  "searchTerms": ["crm", "email finder"],
  "minUsers": 100000,
  "minRating": 4,
  "maxItems": 200
}

Field coverage — measured

From a real 32-extension category run (2026-08-27) and a 30-extension search run (2026-08-26):

Field	Fill
name, extensionId, rating, reviewCount, category, version, size, lastUpdated, firstPublished, languages, description, tagline, storeUrl	100%
publisherEmail	100%
publisherName	100%
publisherWebsite	83-88%
privacyPolicyUrl	88-90%
supportUrl	63-84% — lower on search-sourced rows than on category rows
users	97% — a handful of Google's own extensions do not publish a count

Honest limits — read this before planning a big run

The store does not paginate. This is the real constraint and it is not a scraper defect:

• a search page returns about 10 extensions and has no next page
• a category page returns 32 and has no next-page token
• all 17 categories resolve, so category browsing addresses roughly 544 extensions

To build a list of thousands you supply many search terms — one per niche you care about — rather than asking for deep pagination that the store does not offer. The actor de-duplicates across every source in a run, so overlapping terms cost you nothing.

Other limits worth stating:

• Data comes from the store's own data blobs, not the rendered DOM. That is why it is fast and needs no browser — but it also means a Google front-end change can require a parser update.
• users is a rounded band (1,000,000 rather than 1,043,912). That is how Google publishes it.
• The publisher email is a support address, not a personal one — which is what makes it usable for B2B outreach.

Who is this for?

Extension monetisation and adtech networks, security and compliance vendors auditing extensions, dev-tool sales teams, and anyone doing competitive research on the extension ecosystem.

Pricing

What	Price
Per extension returned	$0.003

Filtered rows cost nothing — if minUsers drops an extension, you are not charged for it.

FAQ

Does every extension really have a contact email? Every one we have measured did — 100% across the 94 extensions in the three most recent runs. Use requireEmail if you want a hard guarantee.

Can I get more than 32 extensions from a category? Not from one category page — the store does not paginate. Use more categories and more search terms.

How do I find an extension's ID? It is the 32-letter string in the store URL. Pass any number of them in extensionIds.

Is the user count exact? No — Google publishes it rounded (e.g. "1,000,000+"). The actor returns the rounded number as-is.

Do I need a proxy? No. The data comes back from ordinary HTTP requests — no browser and no anti-bot to defeat.

Can I filter to popular extensions only? Set minUsers and minRating. Both are applied before you are charged.

What are the category slugs? Three groups — make_chrome_yours/*, productivity/* and lifestyle/*. The input schema lists all 17 valid values.

Does it return the full description? It returns the listing description truncated to 1,000 characters — on a typical run about two thirds of rows hit that limit and are cut off.

Is scraping this allowed? The store is a public catalogue with no login and no paywall; this actor reads only publicly served listing data and backs off automatically if the store ever rate-limits it. You are responsible for how you use publisher contact details — CAN-SPAM and GDPR apply to your outreach.

Data source and fair use

Data comes from public Chrome Web Store listing pages. No login is used and no private API is touched. Publisher emails are the contact addresses those publishers chose to display on their own public listings.