Chrome Web Store Scraper

Chrome Web Store Scraper exports public extension listings and detail-page metadata for competitor research and software catalogs. Search by keyword or supply Chrome Web Store URLs to collect names, ratings, publisher information and available version details. Coverage depends on the source page, not a complete marketplace index.

Quick start

1. Enter a search query and clear any unwanted prefilled Start URLs.
2. Keep a small maxItems limit and enable details when you need version information.
3. Start the Actor, then export its dataset as JSON, CSV or Excel.

{
  "searchQueries": ["ad blocker"],
  "startUrls": [],
  "maxItems": 10,
  "includeDetails": true,
  "language": "en-US",
  "country": "US"
}

Prefer a video guide? This short Apify walkthrough shows you how to set up and run an Actor. It uses a different Actor, but the setup steps are the same.

Ready-to-run examples

Choose a public example to see its settings before starting a run:

• Compare password manager extensions in Germany
• Research productivity and tab manager extensions
• Scrape Chrome Web Store ad blocker extensions

What you get

One row per saved extension listing or direct detail lookup, with available identity, publisher, description, rating and version fields. Optional metadata can be missing. Listing rank is card order rather than a popularity score, and privacy text fragments are not a security or permissions assessment.

Who is it for?

• Extension product teams reviewing how comparable tools are described in public listings.
• Software-catalog teams collecting available metadata from known extension URLs.
• Market researchers preparing bounded keyword-search samples with source links.
• Data teams comparing separately collected extension records in their own workflow.

How you can use the data

• Review an ad-blocker search sample. Search ad blocker with a small shared cap. Keep extensionId, name, url, available description and rating for a product-research sheet. Card position is not a popularity ranking.
• Inspect a known extension's available details. Clear unwanted search-query prefills and supply its current detail URL. Review available version, lastUpdated and publisher fields without assuming a complete record. Direct detail URLs fetch details even when listing enrichment is off.
• Build a cited software catalog. Retain extension identity, publisher links and sourceUrl with each row. The export is metadata, not review text, a downloadable extension package or a structured security assessment.
• Compare like-for-like snapshots downstream. Keep scrapedAt, source URLs and requested locale with each export. Compare names, descriptions or versions in your own tools. Requested language and country do not prove the source returned a fully localized page, and the Actor does not calculate changes or send alerts.

Input settings

Supply at least one nonblank query or Start URL. Queries are processed before URLs, with one shared result limit. Both alternatives may be supplied together.

Setting	JSON key	Meaning
Search queries	searchQueries	Keyword list. The form prefills ad blocker, not an API default.
Start URLs	startUrls	Chrome Web Store detail, search or listing URLs. Clear unwanted form prefills.
Maximum extensions	maxItems	Shared limit, 1–10,000. Schema default: 10.
Fetch extension details	includeDetails	Default: true. Enrich listing records with available detail fields.
Language code	language	Schema default: en-US. Request a localized page.
Country code	country	Schema default: US. Request a country view, not an exclusive geographic filter.
Maximum run time	maxRunSeconds	Optional 60–270 second budget. See input help for completion limits.

For a detail-only lookup, use an empty searchQueries list and a current extension URL in startUrls. Detail URLs always fetch details, regardless of includeDetails. Disabling details affects listing enrichment only.

Example inputs

Use the Quick start input as a small first run. Adjust the fields described above for your own data.

Output data

The dataset contains extension records, not review text or a structured security audit. The following is a shape-only illustration, not a measured extension or sample run:

{
  "query": "ad blocker",
  "rank": 1,
  "extensionId": null,
  "name": null,
  "url": "https://chromewebstore.google.com/search/ad%20blocker",
  "developerName": null,
  "developerUrl": null,
  "category": null,
  "rating": null,
  "ratingCount": null,
  "userCount": null,
  "description": null,
  "shortDescription": null,
  "version": null,
  "lastUpdated": null,
  "size": null,
  "privacyPractices": [],
  "screenshots": [],
  "iconUrl": null,
  "sourceUrl": "https://chromewebstore.google.com/search/ad%20blocker",
  "scrapedAt": "2026-10-24T00:00:00.000Z",
  "requestedLanguage": "en-US",
  "requestedCountry": "US"
}

Fields	Content
extensionId, name, url	Extension identity and page URL when available.
query, rank, sourceUrl	Source query, listing-card position and originating URL. Query/rank may be absent on detail-only records.
developerName, developerUrl, category	Public publisher and category metadata, where found.
rating, ratingCount, userCount	Source-derived rating and counts. Values may be missing or rounded.
shortDescription, description	Short summary and available detail overview.
version, lastUpdated, size	Available detail values. Update date and size retain source text.
privacyPractices	Matched privacy-related text fragments, not a complete policy assessment.
iconUrl, screenshots	Available image URLs. Screenshots are not guaranteed exhaustive.
requestedLanguage, requestedCountry, scrapedAt	Requested locale and collection timestamp, not proof of source localization.
warnings	Optional messages when detail enrichment fails and listing data is retained.

RUN_SUMMARY in the key-value store reports status, saved count, detail-fetch count and warnings. It is not a resumable checkpoint.

Download your results

Open your run's dataset, choose Export and select JSON, CSV or Excel. JSON keeps nested fields together. CSV and Excel are useful when you want to review the records in a spreadsheet.

See Apify's download and export guide for the available formats and field options.

Pricing

This Actor uses pay-per-event pricing: start is charged once after initial input validation, and item is charged for each extension record saved. A listing record retained after failed detail enrichment still counts as an item. There are no separate status-result rows.

See the live Pricing tab for current rates and discounts. Platform usage may also apply.

Tips for best results

• Start with one query and a small cap. Review available metadata before increasing volume.
• Clear query prefills for a detail-only lookup. Queries run before supplied URLs and share the result limit.
• Choose listing enrichment deliberately. Turning it off limits extra detail visits, while direct detail URLs still fetch their pages.
• Keep source and requested-locale fields for comparisons. Inspect actual returned values rather than assuming language or country coverage.
• Read RUN_SUMMARY after incomplete work. Check saved count, detail-fetch count and warnings before using the export.

Limits and caveats

Only public pages are requested, without Google login or private publisher-console access. Page changes or access challenges can prevent collection, and some failures stop the run.

Caps are maximums rather than guaranteed counts. Listing enrichment is limited to 500 detail attempts per run. Listing rank is card order, with no exhaustive search pagination or sorting control.

Missing metadata is normal. Detail failures can retain useful listing rows. Late requests may be refused before completion, while already saved records remain available. RUN_SUMMARY is not a resumable checkpoint, and no automatic continuation is provided.

Locale parameters request a view rather than an exclusive country filter or localization guarantee. English-label extraction and source variation can limit field coverage. Privacy fragments are not a complete policy or permissions assessment.

Automation and integrations

Save your settings for next time

Once you have an input that works for you, save it as an Apify task. This keeps your settings together so you can use them again without filling in the form from scratch.

Run on a schedule

Need fresh results regularly? You can schedule the Actor or a saved task to run at a time that suits you.

Each scheduled run collects the data again. If you want to compare results or highlight changes, add that step in your own workflow.

Send results to your other tools

Use n8n, Make or Zapier to connect this scraper to the rest of your workflow. For example, you could pass its results to an AI assistant or add records to a spreadsheet. Follow the Apify integration guides for your chosen tool.

For a custom connection, an Apify webhook can notify your app when a run finishes or fails. Your app can then fetch the results or handle the failure.

API usage

Want to collect this data from your own app or automation? The examples below send input to the scraper and show how to collect its results.

The Node.js and Python examples wait for the run to finish before reading its results. The cURL example starts the run and returns its details. Wait for that run to finish, then use its defaultDatasetId to fetch the results.

For setup instructions, see Apify's JavaScript client guide, Python client guide and Actor runs API reference.

cURL

curl -X POST 'https://api.apify.com/v2/acts/fetch_cat~chrome-web-store-scraper/runs' \
  -H "Authorization: Bearer $APIFY_TOKEN" \
  -H 'Content-Type: application/json' \
  --data @- <<'JSON'
{
  "searchQueries": [
    "ad blocker"
  ],
  "startUrls": [],
  "maxItems": 10,
  "includeDetails": true,
  "language": "en-US",
  "country": "US"
}
JSON

Node.js

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('fetch_cat/chrome-web-store-scraper').call({
  "searchQueries": [
    "ad blocker"
  ],
  "startUrls": [],
  "maxItems": 10,
  "includeDetails": true,
  "language": "en-US",
  "country": "US"
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

Python

import os
from apify_client import ApifyClient

client = ApifyClient(os.environ['APIFY_TOKEN'])
run = client.actor('fetch_cat/chrome-web-store-scraper').call(run_input={'searchQueries': ['ad blocker'], 'startUrls': [], 'maxItems': 10, 'includeDetails': True, 'language': 'en-US', 'country': 'US'})
print(client.dataset(run['defaultDatasetId']).list_items().items)

API usage notes

The asynchronous response identifies the run. After completion, retrieve records from its defaultDatasetId using the dataset API.

MCP and AI agents

You can ask your AI assistant to collect data with Chrome Web Store Scraper and help you work with the results. The scraper returns the data, and your assistant can then summarize it, compare records or prepare notes.

Connect your assistant through the Apify MCP server. MCP gives your assistant a way to find this scraper, run it and read the results. Follow the official setup and sign-in guide for your app.

Easier setup with an Apify plugin

If you use a supported coding assistant, the official Apify plugin can set up the connection for you. It connects your assistant to Apify and includes instructions for common tasks. Follow the guide for your particular app.

Use Apify AI in Console

Prefer to keep everything in Apify? Open Apify AI in Console and ask it to find Fetch Cat's Chrome Web Store Scraper. You can describe the data you want and ask questions about the results.

Apify AI is currently in beta. It asks for confirmation before starting an Actor, and normal run charges apply.

Choose your assistant

• Claude and Claude Code (Anthropic): Apify setup guide.
• ChatGPT and Codex (OpenAI): Apify setup guides.
• Grok Bot (xAI): Apify plugin guide.
• Gemini CLI (Google): MCP server setup guide. Use the server URL below with the HTTP configuration supported by Gemini CLI.

Connect just this scraper

To keep your setup focused on this scraper, add this server configuration to a compatible MCP client:

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

Sign in to Apify when your client asks. If your client uses a Bearer token instead, follow its setup guide and keep the token in its secure configuration. Configuration formats vary by app, so use the linked guide if your client needs a different format.

Use Apify's general server

Already connected to the general Apify MCP server at https://mcp.apify.com? You can use it to find this scraper without adding another server. Ask your assistant to use Chrome Web Store Scraper by Fetch Cat, or give it the identifier fetch_cat/chrome-web-store-scraper.

Your assistant can check the available settings and retrieve the results from the returned run. If the run is still working, it should follow that run rather than start it again. Both connection options use Apify's hosted service.

Example requests

• “Use Fetch Cat’s Chrome Web Store Scraper to collect up to 5 extension listings for ad blocker. Show names, extension IDs, source links and available descriptions or ratings without calling card order a popularity rank.”
• “Retrieve one extension’s metadata from the current Chrome Web Store detail URL I provide, with any unwanted query prefills cleared. Show available version, update text and public publisher details, marking missing fields.”
• “Collect a small sample of 5 extension records from this public Chrome Web Store search URL without optional listing-detail enrichment. Keep identifiers, requested locale and collection time so I can compare the export with my earlier catalog snapshot.”

Normal Apify charges apply. Check the live Pricing tab before asking your assistant to run a larger batch.

Pay with x402

If your AI agent has a funded wallet, it can pay for Apify usage through x402. This experimental option lets an agent use Apify without a conventional account.

Apify AGI provides a prepaid API token with a spending cap after payment. Your agent can use that token to run this scraper through the Apify API or an authenticated MCP connection.

Some MCP setups also support paying for each request directly. That is a different payment option, so check the official guide for its availability.

Follow the official guide for wallet setup, supported payment options and current terms. Apify handles the payments. Keep wallet keys and payment tokens in your agent's secure configuration.

Other ways for agents to pay

Apify also supports MPP for prepaid access through AGI and Skyfire for eligible Actors. If your agent already uses one of these, see the agentic payment guide to choose the right setup.

FAQ

Is this a Chrome Web Store API alternative?

It provides structured public-page metadata through Apify's API. It is not an official Google API and does not provide private publisher-console data or guarantee every extension will be found.

Can I export Chrome extensions to CSV or Excel?

Yes. Download the dataset in Apify's export formats or retrieve it through the dataset API. This exports listing metadata, not extension installation packages.

Why are details missing or results fewer than requested?

The source may expose fewer matching cards, repeated extensions may be skipped, or detail enrichment may fail. Review optional row warnings and RUN_SUMMARY. A completed listing extraction can return zero records. An empty result alone does not establish why a target was unavailable.

Does it extract extension reviews or permissions?

No review-text or complete permissions collection is implemented. Ratings/counts and matched privacy text should not be treated as a security assessment.

Related Actors

• Apple App Store Apps Scraper — Research another app marketplace.
• Apple App Store Reviews Scraper — Collect app-review data in a separate workflow.
• Google Play Apps Scraper — Compare mobile-app metadata.
• Google Play Reviews Scraper — Research mobile-app feedback separately.
• Product Hunt Scraper — Explore adjacent product launches.

Support and feedback

For custom additions or integrations, email hello@fetchcat.dev.

Found an error or have a feature request? Open an issue with the run URL, a non-sensitive input example and what you expected.

Need help sharing it? See Apify’s guide to sharing a run when reporting an issue. Sharing a run can give the developer access to its input, logs and results, so use a run that contains no sensitive data. Please leave out API tokens, passwords, cookies, private documents and personal data. Use a public sample URL or a redacted example instead.

Tried this scraper? We'd love to hear how it worked for you. Leave a review to help others choose the right tool and help us improve it. Your feedback means a lot to us.

Made with care for curious people, AI agents and the possibilities in data. ♥