Chrome Web Store Scraper

Scrape public Chrome Web Store search results and extension detail pages for market research, competitive monitoring, security review, and product intelligence.

What does Chrome Web Store Scraper do?

Chrome Web Store Scraper collects structured data from public Chrome Web Store pages.

It can start from search terms, search result URLs, category URLs, or individual extension detail URLs.

The actor returns extension names, IDs, URLs, publishers, categories, ratings, user counts, descriptions, versions, update dates, sizes, icons, screenshots, and source ranking data when available.

Use it to monitor competitors, discover fast-growing extensions, enrich internal software catalogs, and track metadata changes over time.

Who is it for?

• 🧩 Extension marketers comparing competitors in crowded Chrome Web Store categories.
• 🔐 Security researchers reviewing popular extensions and publisher metadata.
• 📈 SaaS growth teams tracking partner, integration, and adjacent-product ecosystems.
• 🛒 Marketplace analysts measuring user counts, ratings, and category positioning.
• 🧪 Product managers validating extension ideas before investing engineering time.
• 🗂️ Data teams building recurring Chrome extension intelligence datasets.

Why use this actor?

• 🚀 Scrape search results and detail pages in one run.
• 📊 Export clean dataset rows instead of copying extension pages manually.
• 🔎 Preserve source query and rank for keyword-position monitoring.
• 🧾 Capture detail fields such as version, last update, size, and long overview.
• 🌍 Use optional language and country parameters for localized Chrome Web Store views.
• 🔁 Run on a schedule to detect rating, user count, or version changes.

Input settings

How to scrape Chrome Web Store search results

1. Open the actor on Apify.
2. Add one or more search queries, such as ad blocker or password manager.
3. Set the maximum number of extensions to save.
4. Keep Fetch extension details enabled if you need version, update date, users, and long descriptions.
5. Click Start.
6. Download the dataset as JSON, CSV, Excel, XML, or HTML.

How to scrape specific extension detail pages

1. Copy Chrome Web Store extension URLs.
2. Paste them into Start URLs.
3. Set maxItems to the number of extensions you want.
4. Run the actor.
5. Review detail fields such as version, lastUpdated, userCount, and description.

Input options

Search queries

Use searchQueries for keyword monitoring and discovery.

Examples:

• ad blocker
• password manager
• coupon finder
• screen recorder
• ai assistant

Start URLs

Use startUrls for Chrome Web Store URLs you already know.

Supported URL types include:

• Extension detail URLs.
• Search result URLs.
• Category or listing URLs that contain extension cards.

Maximum extensions

Use maxItems to control run size and cost.

For first tests, keep this value low.

For production monitoring, increase it to match your keyword list and reporting needs.

Fetch extension details

When includeDetails is enabled, the actor enriches search results by opening each extension detail page.

This gives you more fields, including users, version, update date, size, overview, and screenshots.

Disable it for faster lightweight ranking checks when search card data is enough.

Locale settings

Use language and country to request localized Chrome Web Store pages.

Examples:

• language: en-US, de, fr, ja
• country: US, GB, DE, JP

Example input

{
  "searchQueries": [
    "ad blocker"
  ],
  "startUrls": [
    {
      "url": "https://chromewebstore.google.com/detail/ublock-origin/cjpalhdlnbpafiamejdnhcphjbkeiagm"
    }
  ],
  "maxItems": 10,
  "includeDetails": true,
  "language": "en-US",
  "country": "US"
}

Example output

{
  "query": "ad blocker",
  "rank": 1,
  "extensionId": "gighmmpiobklfepjocnamgkkbiglidom",
  "name": "AdBlock — block ads across the web",
  "url": "https://chromewebstore.google.com/detail/adblock/gighmmpiobklfepjocnamgkkbiglidom",
  "developerName": "getadblock.com/",
  "category": "Extension > Privacy & Security",
  "rating": 4.5,
  "ratingCount": 296000,
  "userCount": 20000000,
  "shortDescription": "Block ads on YouTube and your favorite sites for free",
  "version": "6.0.0",
  "lastUpdated": "June 20, 2026",
  "size": "12MiB",
  "sourceUrl": "https://chromewebstore.google.com/search/ad%20blocker",
  "scrapedAt": "2026-07-03T00:00:00.000Z"
}

Tips for better results

• Start with one or two queries before scaling to a large monitoring list.
• Use specific keywords such as linkedin automation instead of only broad terms like marketing.
• Keep detail enrichment on when you need user counts and version data.
• Turn detail enrichment off for quick rank-only checks.
• Schedule runs weekly or daily for trend monitoring.
• Store historical datasets if you want to detect rating or user-count changes.

Common use cases

Competitor tracking

Track extensions competing for the same Chrome Web Store keywords.

Monitor rank, ratings, user counts, descriptions, and update cadence.

Category research

Collect extension records from category pages and compare categories by popularity.

Use this for market sizing and product idea validation.

Publisher intelligence

Create a dataset of extensions from known publishers or partner categories.

Use developer names and URLs to enrich internal account lists.

Security review

Build a watchlist of high-install extensions and review publisher, update, category, and description changes.

SEO and listing optimization

Compare titles, descriptions, ratings, and screenshots for extensions ranking above your product.

Integrations

Google Sheets

Export the dataset as CSV and import it into Google Sheets for lightweight dashboards.

BigQuery or Snowflake

Use Apify integrations or API exports to load extension records into your warehouse.

Slack alerts

Schedule the actor and trigger alerts when a tracked extension changes version or passes a user-count threshold.

CRM enrichment

Use developer/publisher fields to enrich partner or competitor account lists.

BI dashboards

Combine repeated runs into a trend table for ratings, users, and rank by keyword.

API usage

Run Chrome Web Store Scraper from your own code with the Apify API.

Node.js

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const input = {
  "searchQueries": [
    "ad blocker"
  ],
  "startUrls": [
    {
      "url": "https://chromewebstore.google.com/detail/ublock-origin/cjpalhdlnbpafiamejdnhcphjbkeiagm"
    }
  ],
  "maxItems": 10,
  "includeDetails": true,
  "language": "en-US"
};

const run = await client.actor('fetch_cat/chrome-web-store-scraper').call(input);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

Python

from apify_client import ApifyClient
import os

client = ApifyClient(os.environ["APIFY_TOKEN"])
run = client.actor("fetch_cat/chrome-web-store-scraper").call(run_input={
  "searchQueries": [
    "ad blocker"
  ],
  "startUrls": [
    {
      "url": "https://chromewebstore.google.com/detail/ublock-origin/cjpalhdlnbpafiamejdnhcphjbkeiagm"
    }
  ],
  "maxItems": 10,
  "includeDetails": true,
  "language": "en-US"
})
items = client.dataset(run["defaultDatasetId"]).list_items().items
print(items)

cURL

curl -X POST "https://api.apify.com/v2/acts/fetch_cat~chrome-web-store-scraper/runs?token=$APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"searchQueries":["ad blocker"],"startUrls":[{"url":"https://chromewebstore.google.com/detail/ublock-origin/cjpalhdlnbpafiamejdnhcphjbkeiagm"}],"maxItems":10,"includeDetails":true,"language":"en-US"}'

Use with AI agents via MCP

Chrome Web Store Scraper can be used by AI assistants through the hosted Apify MCP server.

Claude Code setup

claude mcp add --transport http apify "https://mcp.apify.com?tools=fetch_cat/chrome-web-store-scraper"

Claude Desktop, Cursor, or VS Code JSON config

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

Example prompts

• "Run Chrome Web Store Scraper with this input JSON and summarize the dataset."
• "Export the latest Chrome Web Store Scraper results to a table I can review."
• "Schedule this Actor for monitoring and tell me what changed between runs."

Data freshness

Chrome Web Store pages can change frequently.

Run the actor on a schedule if you need fresh market intelligence.

Use scrapedAt to distinguish historical snapshots.

Limits and caveats

• Only public Chrome Web Store data is collected.
• Some fields may be missing when Chrome Web Store does not display them.
• User counts and rating counts are public rounded values.
• Markup and labels can vary by locale.
• Very broad searches may not expose every matching extension.
• The actor does not log in to Google accounts.

Legality

This actor collects publicly available data from Chrome Web Store pages.

You are responsible for using the data in a lawful way, respecting applicable laws, platform terms, privacy rules, and internal compliance policies.

Do not use scraped data for spam, harassment, credential attacks, or other abusive activity.

Support

Report bugs, wrong output, blocked runs, or missing fields from the Actor page. Include the Apify run ID or run URL, your input JSON, what you expected, what the Actor returned, and one reproducible public URL so the issue can be tested quickly.