Search results as a local searcher sees them, at scale
Run your own SERP collector on residential IPs in the exact city, or send us the query and get structured JSON back. Either way: real local results, no CAPTCHAs stopping the job, no monthly minimum.
MilanDesktopMilanMobile
New YorkDesktopNew YorkMobileFour pages, four rankings. The exit IP and the device decide which one your customers see.
Datafuel supports SERP scraping two ways: residential and mobile proxies that put your own collector on a local IP in the city you choose, or the Search API that returns organic results, local packs and People also ask as structured JSON. Both charge only for successful queries.
Why there is no single search result page
There is no single search result page. Google returns different results by country, by city, by device, and by what it knows about the searcher. A ranking checked from your office is your ranking in your office.
Automated queries are the thing search engines defend against most. Rate limits and CAPTCHAs arrive within a few requests from any IP that looks like a tool, and datacenter IPs are recognised immediately.
The page itself has changed. AI Overviews now appear on close to half of searches, above the organic results, and being cited in one matters more than ranking third below it. A tracker that only reads the ten blue links is measuring less and less of the page.
Most Google searches happen on a phone, and the mobile page is not the desktop page: different ads, a different local pack, often a different order. A desktop-only tracker measures the minority.
best pizza deliveryMilan · DesktopThree blocks sit above the first organic result. A tracker that reads only organic misses most of the page.
Two ways to scrape search results from local IPs
The proxies run on the residential and mobile network, the Search API on Datafuel's own pool, and both return local results. The difference is who does the parsing.
Keep your collector and fix the network, or hand us the query. Same IPs, same local results, same billing rule.
| Residential proxies | Search API | |
|---|---|---|
| You bring | your own collector and parser | a query and a location |
| You get | the raw results page from a local IP | organic, local pack and questions as JSON |
| Targeting | country · region · city · ASN · OS · device: desktop or mobile | country · language · city (location, uule or GPS) |
| CAPTCHAs | handled by your collector | handled inside the request |
| Billing | per GB, traffic never expires | per successful query, credits never expire |
| Best when | you already have a working tracker | you want results without maintaining a parser |
Many teams use both: the Search API for tracking, residential proxies for the collectors they already run.
Products for SERP scraping
Same price on every use case. Failed requests are free and purchased traffic never expires.
- Country, region, city, ASN and OS targeting
- Rotating or sticky sessions, up to 24 hours
- Traffic never expires, no monthly minimum
- HTTP(S) and SOCKS5
- Consent-sourced, GDPR-compliant IPs
- Organic, local pack and questions as separate JSON fields
- Country, language and city targeting (location, uule or GPS)
- CAPTCHAs handled inside the request
- Blocked queries refunded, zero credits charged
- Batch hundreds of queries in one job
How it works
- 01Point your collector at the Datafuel gateway with the city and device in the username.
- 02Each query exits from a local residential IP; sticky sessions hold the IP across a multi-step check.
- 03Your collector parses the page as it does today.
- 01Send the query with
country,languageandlocation. - 02Datafuel runs it from its own pool, clearing CAPTCHAs inside the request.
- 03Organic results, local pack and questions return as JSON.
What to watch for
- Track the whole page, not just organic position. Ads and local results are where the page has moved.
- Rotate identities between queries on both paths. Repeated queries from one IP change the results and invite CAPTCHAs.
- Search engines' terms restrict automated querying. Understand your exposure; our compliance documentation sets out how we operate. Collecting public search results has been upheld in US courts in the hiQ and Meta v. Bright Data cases; the remaining exposure is the search engine's own terms of service.
SERP scraping — frequently asked questions
Should I use proxies or the Search API?
Can I get results for a specific city on both paths?
How are CAPTCHAs handled?
Is there a monthly minimum on either?
Do you return AI Overviews?
Ready to build?
Start with the free tier and scale as your project grows. No credit card, no sales call.
Talk to an engineer, not a chatbot.