Chrome Web Store Scraper & Extension Intelligence API

Scrape public Chrome Web Store extension profiles and keyword search rankings. Use this actor for extension competitor tracking, Chrome Web Store ASO research, permission audits, market mapping, and weekly ranking snapshots.

The actor opens rendered Chrome Web Store pages with Playwright because the useful profile data is JavaScript-rendered. It extracts extension metadata, ranking context, privacy text, and manifest permissions into a CSV/API-ready Apify dataset.

What You Can Track

• Chrome Web Store extension profiles by URL or raw extension ID.
• Search rankings for keywords such as screenshot, dark mode, coupon, or productivity.
• Users, ratings, rating counts, versions, and update dates.
• Extension category, offered-by/developer text, and public privacy disclosure text.
• Manifest permissions, optional permissions, and host permissions from the hydrated page payload.
• Competitor movement by repeating the same keyword run over time.

Fast First Run

Start with one extension URL and one keyword. Keep browser concurrency low for more reliable Chrome Web Store rendering.

{
  "extensionUrls": [
    {
      "url": "https://chromewebstore.google.com/detail/dark-reader/eimadpbcbfnmbkopoojfekhnkhdbieeh"
    }
  ],
  "searchKeywords": ["screenshot"],
  "maxSearchResultsPerKeyword": 3,
  "includeSearchResultDetails": true,
  "pushSearchSnapshots": false,
  "language": "en-US",
  "timeoutSeconds": 25,
  "maxConcurrency": 1
}

Output

Each extension profile row includes:

• extensionId and extensionUrl
• extensionTitle and category
• rating and ratingsCount
• users
• version and updated
• offeredBy and developer when visible
• privacy disclosure text
• permissions, optionalPermissions, and hostPermissions
• searchKeyword and searchRank when the profile came from keyword search
• status, blockMarkers, error, checkedAt, and runtimeSeconds

Example dataset row:

{
  "recordType": "extension_profile",
  "sourceType": "search",
  "searchKeyword": "screenshot",
  "searchRank": 1,
  "extensionId": "fdpohaocaechififmbbbbbknoalclacl",
  "extensionUrl": "https://chromewebstore.google.com/detail/gofullpage-full-page-scre/fdpohaocaechififmbbbbbknoalclacl",
  "extensionTitle": "GoFullPage - Full Page Screen Capture",
  "category": "Workflow & Planning",
  "rating": "4.9",
  "ratingsCount": "83.7K",
  "users": "11,000,000",
  "version": "8.6",
  "updated": "January 21, 2026",
  "permissions": ["activeTab", "scripting", "storage"],
  "hostPermissions": [],
  "status": "ok",
  "runtimeSeconds": 0.6
}

Use Cases

• Extension competitor monitoring: track competing extensions by URL and compare users, ratings, update cadence, and permissions.
• Chrome Web Store ASO: monitor keyword ranking positions and which extensions appear for target terms.
• Permission and privacy audits: review declared permissions and public privacy disclosures across a competitor set.
• Market mapping: collect category, rating, install/user, and update signals before building or acquiring an extension.
• Weekly rank snapshots: run the same keyword list on a schedule and export the dataset to Sheets, BI, or a database.

Pricing

This actor uses pay-per-event pricing. The primary event is one extracted extension profile. Search keyword checks have a smaller supporting event charge because they load Chrome Web Store search pages before optional profile extraction.

See the Pricing tab for the exact tiered price shown for your Apify plan. Start with the default input first, check the run cost, then scale keyword lists or competitor URL lists.

Notes and Limits

• This is not an HTTP-only scraper. Chrome Web Store profile and permission data requires browser rendering.
• Keep maxConcurrency between 1 and 3; slow browser runs are more reliable than aggressive parallel scraping.
• Public Chrome Web Store pages can change layout, show consent interstitials, or reject individual proxy connections. The actor retries transient browser/proxy failures and skips failed search-derived detail rows instead of failing the entire run.
• Use only legitimate public-data workflows and review your own compliance requirements before storing or processing scraped data.