Chrome Web Store Extension Scraper avatar

Chrome Web Store Extension Scraper

Pricing

Pay per event

Go to Apify Store
Chrome Web Store Extension Scraper

Chrome Web Store Extension Scraper

🧩 Scrape Chrome Web Store extension metadata from public search, category, and detail pages for market research and prospecting.

Pricing

Pay per event

Rating

0.0

(0)

Developer

Stas Persiianenko

Stas Persiianenko

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

2 days ago

Last modified

Categories

Share

Scrape public Chrome Web Store extension metadata from search pages, category pages, and extension detail pages.

Use it to collect extension titles, IDs, URLs, publishers, ratings, user counts, categories, descriptions, images, website links, version information, and update dates.

What does Chrome Web Store Extension Scraper do?

This actor extracts public extension records from chromewebstore.google.com.

It supports three discovery paths:

  • 🔎 Chrome Web Store search terms
  • 📂 Chrome Web Store category URLs
  • 🧩 Direct extension detail URLs or extension IDs

The scraper saves one dataset row per extension.

It can run in a fast search-only mode or open each detail page for richer metadata.

Who is it for?

SaaS marketers can find browser-extension companies in a niche.

Extension founders can benchmark competing extensions.

Security researchers can inventory extensions in a category.

Growth teams can build prospecting lists from publisher websites.

Product managers can monitor rating, user, and update signals.

Investors and analysts can track browser-extension markets.

Why use this actor?

Chrome Web Store pages are public but inconvenient to copy at scale.

This actor turns those pages into structured JSON, CSV, Excel, XML, or API-ready data.

It also preserves source URLs so every record can be verified.

What data can I extract?

FieldDescription
extensionIdChrome extension ID
urlChrome Web Store detail URL
titleExtension name
publisherPublic publisher or offered-by name
publisherUrlPublic publisher website when visible
ratingNumeric rating
ratingsCountNumber of public ratings when visible
usersCountPublic user/install count when visible
categoryChrome Web Store category
shortDescriptionSearch-card or meta description
descriptionDetail-page description when available
iconUrlExtension icon URL
screenshotUrlsPublic screenshot/image URLs
websiteUrlWebsite link when public
supportUrlSupport link when public
versionVersion shown on the detail page
updatedDateLast updated date shown on the detail page
sizeExtension package size
languagesLanguages field
sourceTypeSearch, category, detail, or extension ID
sourceUrlInput URL that produced the record
scrapedAtISO timestamp

How much does it cost to scrape Chrome Web Store extensions?

This Actor uses pay-per-event pricing.

There is a $0.005 start event per run.

Per-result prices use Apify tier discounts:

TierPrice per extension1,000 extensions
FREE$0.000048725$0.0487
BRONZE$0.00004237$0.0424
SILVER$0.000033048$0.0330
GOLD$0.000025422$0.0254
PLATINUM$0.000016948$0.0169
DIAMOND$0.000011863$0.0119

A 100-result realistic cloud test cost about $0.006 in gross PPE charges including the start event.

How to scrape Chrome Web Store search results

  1. Open the actor input.
  2. Add one or more searchQueries such as adblock, seo, or crm.
  3. Set maxItems to the number of extensions you need.
  4. Keep includeDetails enabled for richer detail fields.
  5. Run the actor.
  6. Export the dataset in your preferred format.

How to scrape a Chrome Web Store category

  1. Copy a category URL from Chrome Web Store.
  2. Paste it into startUrls.
  3. Set a result limit.
  4. Run the actor.
  5. Review the dataset for extension metadata.

How to scrape specific extensions

Use extensionIds when you already know the Chrome extension IDs.

You can also paste full detail URLs into startUrls.

Example extension ID:

cjpalhdlnbpafiamejdnhcphjbkeiagm

Input example

{
"searchQueries": ["adblock"],
"startUrls": [
{ "url": "https://chromewebstore.google.com/detail/ublock-origin/cjpalhdlnbpafiamejdnhcphjbkeiagm" }
],
"extensionIds": ["cjpalhdlnbpafiamejdnhcphjbkeiagm"],
"maxItems": 25,
"includeDetails": true
}

Output example

{
"extensionId": "cjpalhdlnbpafiamejdnhcphjbkeiagm",
"url": "https://chromewebstore.google.com/detail/ublock-origin/cjpalhdlnbpafiamejdnhcphjbkeiagm",
"title": "uBlock Origin",
"publisher": "Raymond Hill (gorhill)",
"rating": 4.7,
"ratingsCount": 35500,
"usersCount": 14000000,
"category": "Privacy & Security",
"shortDescription": "Finally, an efficient blocker. Easy on CPU and memory.",
"sourceType": "detail"
}

Tips for better results

Use specific search queries for focused markets.

Use category URLs for broader market maps.

Enable detail pages when you need user counts, versions, update dates, or screenshots.

Disable detail pages when you only need fast discovery from search cards.

Set a small maxItems for the first run to validate your input.

Integrations

Send the dataset to Google Sheets for lead review.

Export CSV for CRM upload.

Use the Apify API to refresh extension lists daily or weekly.

Connect the dataset to enrichment tools that visit publisher websites.

Feed extension URLs into monitoring workflows.

API usage with Node.js

import { ApifyClient } from 'apify-client';
const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('automation-lab/chrome-web-store-extension-scraper').call({
searchQueries: ['adblock'],
maxItems: 25,
includeDetails: true
});
console.log(run.defaultDatasetId);

API usage with Python

from apify_client import ApifyClient
client = ApifyClient('YOUR_APIFY_TOKEN')
run = client.actor('automation-lab/chrome-web-store-extension-scraper').call(run_input={
'searchQueries': ['adblock'],
'maxItems': 25,
'includeDetails': True,
})
print(run['defaultDatasetId'])

API usage with cURL

curl -X POST 'https://api.apify.com/v2/acts/automation-lab~chrome-web-store-extension-scraper/runs?token=YOUR_APIFY_TOKEN' \
-H 'Content-Type: application/json' \
-d '{"searchQueries":["adblock"],"maxItems":25,"includeDetails":true}'

MCP usage

Use the actor from Claude Code or other MCP-compatible tools through Apify MCP.

MCP URL:

https://mcp.apify.com/?tools=automation-lab/chrome-web-store-extension-scraper

Claude Code setup:

$claude mcp add apify-chrome-web-store --url "https://mcp.apify.com/?tools=automation-lab/chrome-web-store-extension-scraper"

Generic MCP JSON config:

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

Example prompts:

  • "Find the top Chrome Web Store extensions for ad blocking and summarize publishers."
  • "Scrape Chrome Web Store SEO extensions and export user counts."
  • "Monitor these extension IDs and compare ratings week over week."

Data quality notes

All fields depend on what Chrome Web Store publicly displays.

Some search cards expose fewer fields than detail pages.

Some publishers do not show a public website or support link.

Counts can be rounded by the source site.

FAQ

Why did I get fewer records than maxItems?

Chrome Web Store search pages expose a limited initial result set per query. Add more queries or category URLs to collect more records.

Why are version or updated-date fields empty?

Enable includeDetails so the actor opens extension detail pages and extracts richer metadata.

Can this actor extract emails?

Not directly in this MVP. It returns public publisher and website links that you can use in a downstream enrichment workflow.

Troubleshooting

If you get fewer records than expected, increase maxItems or use a broader query.

If fields like version or updated date are empty, enable includeDetails.

If a query returns no records, test the same query in Chrome Web Store and try a simpler phrase.

Legality

This actor extracts publicly available Chrome Web Store information.

Do not use the data for spam, harassment, credential attacks, or policy-violating automation.

Check the source site's terms and your local laws before using scraped data commercially.

Explore other actors from Automation Lab for app intelligence, reviews, product research, and lead generation.

Use Chrome Web Store data together with company websites, app reviews, and social profiles for richer analysis.

Changelog

Initial version supports search URLs, category URLs, extension detail URLs, extension IDs, optional detail enrichment, and public extension metadata extraction.

Support

If the output looks wrong, provide the run ID and the input you used.

We can inspect whether Chrome Web Store changed markup or whether a specific extension hides the field you expected.

Limits

The actor does not log in.

The actor does not scrape private or account-only data.

The actor does not guarantee email extraction.

The actor does not scrape reviews in this MVP.

Summary

Chrome Web Store Extension Scraper turns public extension discovery pages into structured datasets.

It is built for repeatable browser-extension market research and prospecting workflows.