ParseForge
Chrome Web Store Scraper
parseforge/chrome-web-store-scraper
Developer toolsOtherAutomation
Scrapes Chrome Web Store extension listings by keyword search or extension ID. Returns each extension as a flat row with title, description, rating, user count, category, and developer details.
- Total users
- 35
- Monthly active
- 4
- Total runs
- 534
- Bookmarked
- 0
- Rating
- 1.0 (1)
- Last modified
- 9 days ago
Overview
Chrome Web Store Scraper
Scrape Chrome Web Store extensions by keyword search or extension ID, up to a million per run. Every extension comes with its title, description, rating, user count, category, and developer details. No API key required. Export to CSV, JSON, Excel, or XML.
The Chrome Web Store has no official API for bulk extension data, making market research and competitive analysis a manual chore. This Chrome Web Store scraper reads the public storefront directly, collecting extension listings by search query or a list of specific extension IDs. It returns structured data ready for analysis, without browser extensions or complex setup.
| Who uses it | What they scrape Chrome Web Store for |
|---|---|
| Market researchers | Analyze which extension categories are growing fastest and what features competitors offer. |
| Extension developers | Track ratings, review volumes, and user counts for their own extensions and competitors. |
| SEO and content teams | Build a dataset of Chrome extensions for directory sites, blog posts, or tool roundups. |
| Lead generation specialists | Find extension publishers to contact for partnerships, sponsorships, or acquisition targets. |
What it does
This Actor collects Chrome Web Store extension listings by keyword search or extension ID and returns each one as a flat row.
- 🔍 Keyword search: enter any term and the Actor returns matching extensions from the Chrome Web Store, ranked by relevance.
- 🆔 Extension ID lookup: provide a list of 32-character Chrome Web Store IDs and get full detail data for each one.
- 📊 Structured output: every extension row includes title, description, rating, user count, category, and developer information in a consistent schema.
- ⚡ High throughput: collect up to a million extensions per run, limited only by the maxItems setting you choose.
Results export to CSV, JSON, Excel, or XML, or straight from the API.
What you can do with Chrome Web Store data
📈 Monitor competitor extensions.
A product manager enters a competitor's extension ID each week to track rating changes, user growth, and description updates over time.
🔎 Discover extensions in a niche.
A content writer searches for 'grammar checker' and collects the top 200 results to build a comparison article for their blog.
📋 Audit your own extension portfolio.
A developer provides a list of their published extension IDs and scrapes current metadata to check for consistency across listings.
🤝 Find partnership leads.
A business development manager searches for extensions in the productivity category and exports a list of publishers to contact.
Why choose this scraper
| What you get | |
|---|---|
| No API key needed | Scrapes the public Chrome Web Store pages directly, with no registration or authentication. |
| Two collection modes | Search by keyword to discover extensions, or fetch detail data for specific extension IDs you already know. |
| Scalable volume | Collect anywhere from a single extension to a million per run, controlled by one number input. |
| Fixed output schema | Every extension returns the same fields, so your dataset is clean and ready for analysis. |
How it compares
This Actor is purpose-built for the Chrome Web Store with a fixed schema and no coding required, while the general-purpose scrapers below need custom code to extract the same data.
| Feature | ParseForge | Puppeteer Scraper | Playwright Scraper |
|---|---|---|---|
| Pre-built Chrome Web Store schema | Yes, fixed schema for extension listings | Not listed | Not listed |
| Keyword search on Chrome Web Store | Yes, built-in search mode | Not listed | Not listed |
| Extension ID lookup mode | Yes, fetch by 32-character ID list | Not listed | Not listed |
| No coding required | Yes, configure with input fields only | Not listed | Not listed |
| Automatic pagination handling | Yes, follows search result pages | Not listed | Not listed |
Configure the run
Drive the Actor from a keyword search or a list of extension IDs, and set a maximum number of extensions to collect per run. The Input tab lists every parameter.
A first run with the defaults:
{
"maxItems": 10,
"mode": "search",
"searchQuery": "translation"
}
A larger pull:
{
"maxItems": 200,
"mode": "search",
"searchQuery": "translation"
}
Pricing
Pay-per-result: $0.011 per result collected. You pay only for the results written to your dataset.
| Results collected | Approximate cost |
|---|---|
| 100 results | $1.10 |
| 1,000 results | $11.00 |
| 10,000 results | $110.00 |
New Apify accounts start with $5 in free credit.
Free users
Free-plan runs return up to 10 results as a preview. Upgrade your Apify plan to collect up to 1,000,000 results per run.
Run it
- Create a free Apify account with $5 in credit.
- Open the Chrome Web Store Scraper.
- Set your inputs and any filters, then click Start.
- Export the results as CSV, Excel, JSON, or XML from the Dataset tab.
Run it programmatically through the Apify API (run-sync-get-dataset-items) or the ApifyClient for JavaScript and Python.
Use with AI agents (MCP)
Give an AI agent live access to Chrome Web Store through the Model Context Protocol. Add the Actor to Claude, Cursor, or any MCP client:
claude mcp add --transport http apify "https://mcp.apify.com?tools=parseforge/chrome-web-store-scraper"
Then prompt it in plain language to run the scraper and read back the results.
Troubleshooting
Why am I getting no results from my keyword search?
Try a broader or different search term. The Chrome Web Store search can be sensitive to exact phrasing. Also check that your maxItems is set high enough to capture results beyond the first page.
Why did my run fail with an error?
Check that your extension IDs are valid 32-character strings. Invalid IDs or network issues can cause failures. Retry the run, and if the problem persists, check the run log for details.
Why are some extension fields empty in my dataset?
Some extensions may not populate every field on their store listing. Missing data in the output reflects missing data on the Chrome Web Store page itself.
Why is the scraper returning fewer results than my maxItems setting?
The Chrome Web Store search may return fewer total results than your maxItems value. The Actor collects all available results up to your limit, but cannot create results that do not exist.
Can I scrape reviews or user comments with this Actor?
This Actor collects extension listing data, not individual user reviews. For review data, you would need a different scraper configured to target the review pages.
FAQ
| Question | Answer |
|---|---|
| Does this scraper need a Chrome Web Store API key? | No. It reads the public Chrome Web Store pages directly, so no API key, OAuth, or Google developer registration is required. |
| What data fields does the scraper return for each extension? | Each extension row includes the title, description, rating, number of users, category, developer name, and other metadata visible on the public store listing. |
| Can I scrape extensions by category or filter by rating? | The Actor searches by keyword or fetches by extension ID. Category and rating filters are not built into the input, but you can filter the output dataset after the run completes. |
| How many extensions can I scrape in one run? | You set the maximum with the maxItems input. The upper limit is one million extensions per run. |
| What is an extension ID and where do I find it? | The extension ID is the 32-character string in the Chrome Web Store URL. For example, in the URL for Google Translate, 'aapbdbdomjkkjkaonfhkkikfgjllcleb' is the ID. |
| Does this scraper handle pagination automatically? | Yes. When searching by keyword, the Actor follows pagination through the search results until it reaches your maxItems limit or the end of the results. |
| Can I export the scraped data to Google Sheets? | You can export the dataset to CSV, JSON, Excel, or XML from the Apify platform, then import any of those formats into Google Sheets. |
| Is this scraper legal to use? | The Actor scrapes publicly available data from the Chrome Web Store. You are responsible for complying with Google's terms of service and any applicable laws in your jurisdiction. |
| Can I schedule this scraper to run daily or weekly? | Yes. Apify supports scheduled runs, so you can set this Actor to collect Chrome Web Store data on a recurring interval. |
| What happens if a search returns no results? | The run completes with an empty dataset. Check your search query for typos or try a broader keyword. |
Related actors
Browse the full ParseForge collection for more scrapers.
🆘 Need help? Email parseforge@protonmail.com with your run ID, your input, and what you expected.
⚠️ Disclaimer. This Actor is unofficial and is not affiliated with, endorsed by, or sponsored by Google LLC. It collects only publicly available data. You are responsible for using the collected data in compliance with the source's terms of service and applicable data-protection laws, including GDPR, CCPA, and PIPL. Do not use it to collect personal data unlawfully.
Input
| Field | Type | What it does | Default |
|---|---|---|---|
| maxItems | integer | How many extensions to collect per run. | 10 |
| mode | string (2 options) | Search by keyword OR scrape specific extension IDs. | search |
| searchQuery | string | Used when mode=search. Free-text search on the Chrome Web Store. | translation |
| extensionIds | array | Used when mode=ids. The 32-char ID from the URL. Example: aapbdbdomjkkjkaonfhkkikfgjllcleb | not set |
Pricing
from $8.25 per 1,000 results
| Charged for | What it is | Price each |
|---|---|---|
| Item | One row in the default dataset. | $0.00825 to $0.011 |
Tiered: the lower figure is the price on a higher Apify plan. Billing and the free credit live on Apify.
API
One POST returns the dataset directly. Same shape for every scraper in the library, so swapping the slug is the only change.
curl -X POST "https://api.apify.com/v2/acts/parseforge~chrome-web-store-scraper/run-sync-get-dataset-items?token=$APIFY_TOKEN" \
-H "Content-Type: application/json" \
-d '{
"helloWorld": 123
}' Examples
Input that runs as-is.
{
"helloWorld": 123
} Reviews
Rated 1.0 out of 5 across 1 review. Read them on Apify.
Issues
We build and maintain this scraper, so a problem with it comes to us. Report it on the Apify listing and the thread stays attached to the scraper where the next person can find it: open an issue.
Broken and urgent, or you would rather not post in public? Write to parseforge@protonmail.com and it reaches the people who wrote it.