Chrome Web Store — Extension Metadata Snapshot

Pricing

Rating

Developer

Actor stats

Categories

Share

Snapshot Chrome Web Store extension metadata — rating, user count, version, developer, and screenshots — by extension ID. One row per extension. Public HTML, no authentication required.

How to use

Provide a list of Chrome extension IDs (the 32-character hash from the Web Store URL) as extensionIds.

Input schema:

{
"extensionIds":[
"bfbmjmiodbnnpllbbbfblcplfjjepjdn",
"cfhdojbkjhnklbpkdaibdccddilifddb"
]
}

Extension IDs can be found in the Chrome Web Store URL: https://chromewebstore.google.com/detail/<extension-name>/<extensionId>

Example output row

{
"extensionId":"bfbmjmiodbnnpllbbbfblcplfjjepjdn",
"snapshotAt":"2026-06-04T05:00:00+00:00",
"name":"AdBlock — best ad blocker",
"description":"Block ads, pop-ups and annoying banners...",
"ratingValue":4.6,
"ratingCount":489231,
"developerName":"AdBlock",
"imageUrl":"https://lh3.googleusercontent.com/...",
"userCount":"65,000,000+",
"version":"6.8.0",
"updatedAt":"June 3, 2026",
"storeUrl":"https://chromewebstore.google.com/detail/bfbmjmiodbnnpllbbbfblcplfjjepjdn"
}

Pricing

A run over 100 extension IDs costs $0.05. Only successfully scraped rows are charged.

Buyer

• Market intelligence — track competitor extensions: monitor rating drift, user growth, version cadence.
• Chrome extension directories — bulk-populate a database of extension metadata for catalogues or comparison sites.
• Developer research — find the most popular extensions in a niche before building your own.
• Review aggregation — combine with rating/review scrapers to benchmark extension quality at scale.
• App store analytics — monitor your own extension's public metrics over time for reporting.

Source

Data is scraped from the public Chrome Web Store listing pages at:

https://chromewebstore.google.com/detail/{extensionId}

Metadata is extracted from the application/ld+json structured data block (JSON-LD, SoftwareApplication schema) embedded by Google for SEO purposes, supplemented by targeted regex probes for userCount, version, and updatedAt fields not present in the structured data. No authentication is required. Extensions that have been removed from the store return HTTP 404 and are skipped gracefully.