Chrome Web Store Scraper — Extensions, Ratings & Developer Leads

Extract complete Chrome Web Store extension data — ratings, install counts, version, size, full description, screenshots, requested permissions, the parsed manifest, and the developer's contact details (email, website, postal address) — straight from the store, with the richest dataset in the category. Search by keyword or pull specific extensions by URL/ID. Optionally turn every developer into a ready-to-contact B2B lead by crawling their own website for extra emails, phone numbers, and social links.

No login, no cookies, no browser — fast HTTP extraction with a clean, server-rendered data path.

Why this Chrome Web Store scraper?

Most extension scrapers return the basics and stop there. This actor parses the store's embedded data record and ships the fields that actually matter for lead generation, competitive intelligence, and security/permission review — in one run:

Data	Typical scrapers	This actor
Name, rating, rating count, install count	✅	✅
Version, size, last-updated & first-published dates	partial	✅
Full description + screenshots	partial	✅
Developer email (publisher contact)	❌	✅
Developer website + postal address + legal name	❌	✅
Requested permissions / host permissions / optional permissions	❌	✅
Parsed manifest (manifest version, content-script count)	❌	✅
Developer phone & socials (from their website)	❌	✅ opt-in
Lead score (0–100) per extension	❌	✅
Monitoring mode — only new extensions	❌	✅
Start fee	$0.005–0.25	none

Use cases

• Lead generation — extension developers are active SaaS buyers and partners. Every record carries the publisher's developerEmail, developerWebsite and developerAddress, scored by reach (userCount) and quality (rating). Filter by leadScore and reach the maker directly.
• Competitive & market intelligence — map a category or keyword: who's winning, install counts, ratings, update cadence (lastUpdated), and which permissions competitors request.
• App-store optimization (ASO) — track your and rivals' ratings, rating counts, descriptions, screenshots and versions over time.
• Security & permission review — audit the permissions, hostPermissions and manifestVersion of any extension or set of extensions for risk assessment, SOC 2 / vendor reviews, and supply-chain monitoring.
• Portfolio & change monitoring — schedule recurring runs to watch a keyword or a list of extensions for new entrants, version bumps and rating shifts.

How to use

1. Sign up for Apify — the free plan is enough to try this actor.
2. Open the Chrome Web Store Scraper, choose a mode, enter search queries or extension URLs/IDs, and click Start.
3. Watch results stream into the dataset table.
4. Export as JSON, CSV, Excel, XML, or RSS — or pull results programmatically via the Apify API.

Input

{
    "mode": "search",
    "searchQueries": ["screenshot", "ad blocker", "crm"],
    "maxResultsPerQuery": 30,
    "includeDeveloperContacts": true,
    "includePermissions": true,
    "enrichDeveloperContacts": true
}

Or pull specific extensions:

{
    "mode": "extensionDetails",
    "extensionUrls": [
        "https://chromewebstore.google.com/detail/grammarly/kbfnbcaeplbcioakkpcpgfkobkghlhen",
        "cjpalhdlnbpafiamejdnhcphjbkeiagm"
    ],
    "enrichDeveloperContacts": true
}

• mode — search (discover by keyword) or extensionDetails (specific extensions).
• searchQueries — keywords to search; each result is enriched to the full record. (Mode: Search.)
• extensionUrls — Chrome Web Store URLs or bare 32-character extension IDs. (Mode: Extension details.)
• startUrls — paste any mix of detail URLs and /search/<query> URLs; each is auto-routed.
• maxResultsPerQuery (default 30) — cap per query. The store returns a curated short list per query (~10), so use several specific queries for breadth.
• includeDeveloperContacts (default true) — email, website, address, support URL, privacy policy + lead score.
• includePermissions (default true) — permissions, host/optional permissions, content-script count, manifest version.
• includeScreenshots (default true) — store screenshot image URLs.
• enrichDeveloperContacts (default false) — crawl the developer's own website (home + contact/about, max 3 pages) for extra emails, phone and socials.
• deduplicateExtensions (default true) — emit each extension at most once per run.
• monitorMode (default false) — emit only extensions not seen in previous runs (pairs with Schedules).

Output

One record per extension (type: "extension"):

{
    "type": "extension",
    "extensionId": "kbfnbcaeplbcioakkpcpgfkobkghlhen",
    "name": "Grammarly: AI Writing Assistant and Grammar Checker App",
    "url": "https://chromewebstore.google.com/detail/grammarly-ai-writing-assi/kbfnbcaeplbcioakkpcpgfkobkghlhen",
    "iconUrl": "https://lh3.googleusercontent.com/...",
    "summary": "Grammarly for Chrome helps you write with confidence.",
    "description": "Grammarly for Chrome is your always-on AI partner…",
    "rating": 4.498,
    "ratingCount": 43084,
    "userCount": 38000000,
    "category": "Communication",
    "categorySlug": "communication",
    "version": "14.1302.0",
    "lastUpdated": "2026-06-12T19:55:51.000Z",
    "published": "2012-03-22T07:34:57.000Z",
    "size": "43.58MiB",
    "sizeBytes": 45696942,
    "languages": ["English"],
    "manifestVersion": 3,
    "permissions": ["scripting", "sidePanel", "tabs", "notifications", "cookies", "identity", "storage"],
    "hostPermissions": ["http://*/*", "https://*/*"],
    "optionalPermissions": [],
    "contentScriptsCount": 8,
    "screenshots": ["https://lh3.googleusercontent.com/..."],
    "developerName": "Grammarly",
    "developerLegalName": "Grammarly, Inc.",
    "developerEmail": "support@grammarly.com",
    "developerWebsite": "http://grammarly.com/",
    "developerAddress": "548 Market St Ste 35410\nSan Francisco, CA 94104-5401\nUS",
    "developerSupportUrl": "https://support.grammarly.com/",
    "privacyPolicyUrl": "https://www.grammarly.com/privacy-policy",
    "contactEmails": ["pr@grammarly.com"],
    "contactPhones": [],
    "contactSocials": { "linkedin": "https://www.linkedin.com/company/grammarly", "twitter": "https://twitter.com/grammarly" },
    "leadScore": 100,
    "source": "extensionDetails",
    "scrapedAt": "2026-06-15T08:00:00.000Z"
}

Automate & schedule

Run this actor on autopilot and pull results into your own stack:

• Apify API — start runs, fetch datasets, and manage schedules over REST.
• apify-client for JavaScript and apify-client for Python — official SDKs.
• Schedules — run it hourly/daily/weekly to monitor new extensions for a keyword, or version/rating changes for a watchlist; perfect for lead pipelines and market dashboards.
• Webhooks — trigger downstream actions (CRM import, Slack alert, email sequence) the moment a run finishes.

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: 'MY_APIFY_TOKEN' });

const run = await client.actor('scrapesage/chrome-web-store-scraper').call({
    mode: 'search',
    searchQueries: ['crm', 'email finder'],
    enrichDeveloperContacts: true,
});

const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(`Got ${items.length} extensions & developer leads`);

Integrate with any app

Connect the dataset to 5,000+ apps — no code required:

• Make — multi-step automation scenarios.
• Zapier — push new developer leads straight into your CRM.
• Slack — get notified when a monitored keyword finds new extensions.
• Google Drive / Sheets — auto-export every run to a spreadsheet.
• Airbyte — pipe results into your data warehouse.
• GitHub — trigger runs from commits or releases.

Use with AI assistants (MCP)

The output is clean, LLM-ready JSON. You can call this actor from Claude, ChatGPT, or any agent framework through the Apify MCP server — ask your assistant to "find the top CRM extensions and list their developers' emails" and let it run this scraper for you.

More scrapers from scrapesage

Build a complete app-market & developer-lead stack across every store:

• Google Play Store Scraper — Android apps, reviews & developer leads.
• Apple App Store Scraper — iOS apps, reviews & charts.
• Steam Scraper — games, prices, reviews & charts.
• Shopify App Store Scraper — Shopify apps, reviews & developer leads.
• Product Hunt Scraper — launches, makers & leads.
• Y Combinator Scraper — startups, founders & jobs.
• YouTube Scraper — channels, videos & creator leads.
• Substack Scraper — newsletters, posts & creator leads.

Tips

• Breadth: the Chrome Web Store's search returns a focused, relevance-ranked short list per query (≈10). To cover a whole niche, run several specific queries (e.g. screenshot, screen recorder, screen capture) rather than one broad term.
• Leads: every extension already carries the developer's contact email and website from the store page — turn on enrichDeveloperContacts to add phone numbers and social profiles from the developer's own site.
• Monitoring: combine Schedules with monitorMode to capture only newly published or newly ranking extensions each run.
• Cost control: enrichment only runs for extensions that expose a developer website, and each extension is emitted once per run.

FAQ

How do I scrape a specific Chrome extension? Use extensionDetails mode and paste the Chrome Web Store URL or the 32-character extension ID into extensionUrls.

Does it need the Chrome Web Store API or a login? No. There is no public Chrome Web Store API — this actor extracts the same data the store renders into its public pages, with no key or login.

Where do the developer emails come from? The Chrome Web Store publishes each developer's contact email, website and (for registered traders) postal address on the listing — this actor reads them directly. With enrichDeveloperContacts on, it also visits the developer's own website for extra emails, phone and socials.

Can I export to Google Sheets, CSV, or Excel? Yes — one click in the dataset view, or automatically on every run via the Google Drive integration.

How do I monitor new extensions automatically? Turn on monitorMode and create a Schedule; optionally add a webhook to push new developer leads into your CRM as they appear.

A field is null — why? Some extensions genuinely don't set a developer website, address, or language list. Fields are null only when the data doesn't exist, not because the scraper skipped them.

Is scraping the Chrome Web Store legal? This actor collects publicly available data only. You are responsible for using the data in compliance with applicable laws (GDPR/CCPA for personal data) and Google's terms.

Need help?

Open an issue on the actor's Issues tab, or visit the Apify help center. Feature requests are welcome — this actor is actively maintained.