Most hunts for a Chrome Stats API alternative start with a spreadsheet that got too big to fill by hand. Somewhere around row 200, copying user counts stops being fun.
The wider research method is in competitor analysis for a Chrome extension.
Four Chrome Stats API alternatives side by side
| Route | Cost | Time to set up | Good for |
|---|---|---|---|
| "Paid data API" | Monthly fee | An afternoon | Dashboards, bulk pulls |
| "MCP server" | Usually part of a plan | Minutes | Asking questions in an AI tool |
| "Your own crawler" | Server plus your hours | Days to weeks | Full control of fields |
| "Manual checks" | Free | None | Under 20 extensions |
| "Store developer dashboard" | Free | None | Only your own extensions |
If you build your own crawler
Read the store's robots.txt first. When we fetched it on 3 Oct 2026 it disallowed paths including /search and /detail/*/reviews. Detail pages themselves were allowed.
Go slowly. Our own crawler runs at about one request per second, with an honest user agent. That pace covered 61,820 extensions by 3 Oct 2026, about 21% of sitemap IDs, so plan for weeks to cover the store.
Once you have the data, automatic competitor tracking keeps it fresh.
The Developer Tools category page has the dated counts if you want to check this yourself.
What to ask any API seller
- Which fields come from the store, and which are estimates?
- When did your history start?
- Are rounded user buckets marked as rounded?
- What are the daily call and row limits?
Where an MCP server fits
An MCP server lets Claude, Cursor or another client call the data directly while you work. You ask "which screenshot tools haven't updated in a year?" and the AI runs the query.
We're biased: Ext Watch is building one for its two top plans. For what such a server should return, see Chrome Web Store MCP.
The same rule applies to ours. Every number should come back with the date it was observed.
Count how many extensions are in your spreadsheet today. That number picks your route.
Questions people ask
Is there an official Chrome Web Store API?
There's a publish API for developers to manage their own items. It doesn't return data about other people's extensions.
Can you scrape the Chrome Web Store?
Allowed detail pages can be fetched politely. Disallowed paths in robots.txt, like reviews, should be left alone.
What is the best way to get Chrome Web Store data?
It depends on scale. Check by hand under 20 extensions, use an MCP server or data API for questions at volume, and build a polite crawler only if you need full control of fields.
Where these numbers come from
- chromewebstore.google.comChrome Web Store robots.txtAccessed 3 Oct 2026
- developer.chrome.comChrome Web Store Program PoliciesAccessed 3 Oct 2026
Part of our guide: Competitor Analysis Chrome Extension: A Step-by-Step Method. More in Tools and comparisons.
1,182 new extensions in the last 30 days in Developer Tools. See them all.
Watch any extension for user, rating, version and owner changes. Updated 3 Oct 2026 from our Chrome Web Store crawl
