DEV Community

ScraperWatch
ScraperWatch

Posted on

What changed in the Google Maps scraper niche on Apify, October 17–23, 2026

If you sell an actor on the Apify Store, the Store page shows you your own numbers. It does not show how your competitors moved this week, or whether someone changed their price for the same billed event. We record the public Store statistics every day, so here is one week in one niche: Google Maps, from the October 17 to the October 23, 2026 snapshot.

The niche at a glance

In the October 23 snapshot, 452 listed actors matched our Google Maps pattern (names and titles mentioning Google Maps, Google Places or gmaps, excluding contact- and lead-extraction tools). 109 of them had nonzero 30-day users in both the October 17 and October 23 snapshots, so all week-over-week comparisons below use those 109 actors.

Their combined 30-day users went from 57,305 to 59,391 (+3.6%). That is a sum of per-actor counts: one account using two actors counts twice. 34 of the 109 actors gained users, 21 lost users and 54 were unchanged.

Usage is concentrated, and stayed that way

The three Compass actors held 93.1% of the cohort's summed 30-day users on October 17 and 93.1% on October 23. Inside that total, the movement was uneven:

Actor 30-day users, Oct 17 30-day users, Oct 23 Change Share of cohort, Oct 17 → Oct 23
compass/crawler-google-places 42,906 44,561 +3.9% 74.87% → 75.03%
compass/Google-Maps-Reviews-Scraper 7,935 8,386 +5.7% 13.85% → 14.12%
compass/google-maps-extractor 2,522 2,375 −5.8% 4.40% → 4.00%
scraperlink/google-maps-scraper 783 805 +2.8% 1.37% → 1.36%
vortex_data/google-maps 818 787 −3.8% 1.43% → 1.33%

The two largest actors added 1,655 and 451 users. The extractor moved the other way, down 147. Between them, scraperlink/google-maps-scraper overtook vortex_data/google-maps for fourth place.

Smaller actors that grew faster

Below the top five, several actors grew faster than the niche as a whole:

  • memo23/google-maps-reviews-scraper: 150 → 187 (+24.7%), higher in every daily snapshot of the week.
  • kaix/google-maps-places-scraper: 245 → 277 (+13.1%).
  • solidcode/google-maps-photos-scraper: 83 → 93 (+12.0%).
  • kaix/google-maps-reviews-scraper: 316 → 341 (+7.9%).

Three of those four are reviews or photos actors rather than general place scrapers. One week is too short to call that a trend, but it is the kind of signal worth watching if you are deciding what to build next.

Success rates barely moved at the top

The public-run success rate is succeeded runs divided by all public runs in the Store's rolling 30-day window:

  • compass/crawler-google-places: 96.85% → 96.54% (about 4.15 million runs on Oct 23)
  • compass/Google-Maps-Reviews-Scraper: 99.72% → 99.71%
  • compass/google-maps-extractor: 96.60% → 96.75%
  • kaix/google-maps-places-scraper: 98.59% → 98.97%
  • memo23/google-maps-reviews-scraper: 94.87% → 96.86%

These are platform counters of run outcomes. They do not check whether a run returned the data its user needed, and they depend on what inputs users send.

Price changes: none at the top

None of the 12 most-used actors in the cohort changed the price of an existing event this week. The listed primary-event rates on October 23 (free tier, per 1,000 events) were $4.00 per place for compass/crawler-google-places, $5.00 per place for compass/google-maps-extractor, $0.60 per review for compass/Google-Maps-Reviews-Scraper, $0.50 per dataset item for memo23/google-maps-reviews-scraper and $0.08 per dataset item for kaix/google-maps-places-scraper. The billed events differ, so these rates are not directly comparable, and add-on events and run-start charges come on top.

The change among larger actors was an addition, not a repricing. Between the October 21 and October 22 snapshots, memo23/google-maps-reviews-scraper added two events: "Author details" at $0.0005 per event and "Count all reviews" at $0.08 per event. Its dataset-item and run-start prices stayed the same. Seven other price or event changes between consecutive daily snapshots were on actors with two or fewer 30-day users.

How this was measured

We download the public Apify Store listing (api.apify.com/v2/store) once a day and keep a dated copy. The figures come from the October 17 and October 23, 2026 snapshots, plus the daily snapshots in between for the price-change dates. "30-day users" is the Store's totalUsers30Days, so it is a rolling count. A weekly change is the difference between two 30-day windows that overlap by 24 days, not a count of new users. Success rates come from publicActorRunStats30Days. Prices are the listed free-tier event prices; paid-plan discounts are not included. Our October 17 snapshot covered fewer listed actors than later ones, which is why comparisons use only actors present on both dates. Actors are named by their public Store identifiers.

You can check any actor yourself:

import json, urllib.request

url = "https://api.apify.com/v2/store?search=google%20maps&limit=10"
with urllib.request.urlopen(url, timeout=30) as r:
    items = json.load(r)["data"]["items"]

for a in items:
    s = a["stats"]
    runs = s.get("publicActorRunStats30Days") or {}
    rate = runs.get("SUCCEEDED", 0) / runs["TOTAL"] if runs.get("TOTAL") else None
    print(f'{a["username"]}/{a["name"]}: {s.get("totalUsers30Days")} users/30d, success {rate}')
Enter fullscreen mode Exit fullscreen mode

A single call gives you today's numbers. The week-over-week view needs the history, which is the part that cannot be filled in later.

Get this for your own actor

If you publish an actor on the Store, we can send you a free weekly report like this one for your actor and the competitors you choose: your rank and share, competitor price changes with dates, and where demand is growing. Request it at scraperwatch.com/for-developers/.

Written with AI assistance. Every number comes from code over public data.

Top comments (0)