Skip to content

Local SERP results as structured JSON

Instead of maintaining browsers, proxy rotation, and block-handling yourself, you send a local-results URL in one request and receive parsed business data back.

OUTPUT FORMATSHTMLJSONMarkdown

Rendering, IP rotation, and anti-bot handling are done for you.

What the data is used for

Teams typically pull local results for three distinct jobs, and the right request options depend on which one you are doing:

  • Business discovery: collect names, addresses, phone numbers, hours, ratings, review counts, categories, and map-pack position to build lead lists or competitor maps.
  • Foot-traffic and trend monitoring: repeat the same queries daily and compare which businesses appear and where, to spot demand shifts and plan layout or marketing changes.
  • Local-SEO visibility tracking: record local-pack and map-pack presence across queries and geographies, then watch for visibility gains or losses over time.

A quick decision check before you code: if the page needs scripts to show results, enable JavaScript rendering; if results change by country, set geo-targeting; if you only need a few fields, use selector-based extraction; if the layout changes often, use natural-language extraction instead.

How it works

Four steps cover the whole workflow:

  1. Create an account to receive an API key and a starting credit balance.
  2. Install the SDK for your stack — Python, Node, Go, PHP, or Ruby — so each page fetch is a single function call, with no proxy or headless-browser management on your side.
  3. Send the local-results URL with your API key. The page is executed in a real browser, the IP is rotated, and the response is returned for parsing.
  4. Add advanced parameters only when needed: render_js for JavaScript, stealth_proxy for CAPTCHA-heavy pages, country_code for geo-targeting, and ai_extract_rules for natural-language extraction.

Each returned page can include business name, address, phone, hours, rating, review count, category, and map-pack position, parsed in one call across geographies. Optional outputs include full-page screenshots for visual verification and clean Markdown for LLM-based aggregation or SEO research.

Getting structured output

Two extraction paths are available, and choosing between them is the main failure distinction to get right:

  • extract_rules maps CSS selectors to named fields. Use it when the page structure is stable and you want precise, repeatable fields.
  • ai_extract_rules takes a natural-language specification. Use it when markup changes frequently and you would rather describe the fields you need than maintain selectors.

Either way, the response comes back as parsed JSON rather than raw HTML you must clean up. Code samples are available in Python, Node.js, Ruby, PHP, Go, and cURL, plus a dashboard request builder for testing without writing code. Automation tools such as n8n can also drive local-SEO monitoring workflows without scraper code.

Reliability and compliance notes

Proxy rotation is intended to keep IP-based blocking from halting a run, and headless-browser rendering imitates ordinary browsing to reduce the likelihood of being blocked. The design is meant to scale across large numbers of headless browsers and rotating proxies, so throughput should hold up during traffic spikes, and typical responses are described as arriving in 1–5 seconds with high accuracy on most sites, including JavaScript-heavy ones. Whether personal data from scraped sites is collected or stored depends on the operator's policy and on whether the user explicitly requests it — a compliance review should confirm the applicable data-handling terms before you rely on them.

Pricing

Plan details and current rates should be confirmed against the provider's published pricing before you commit. The pricing structure distinguishes plans by API credits, concurrent requests, and whether JavaScript rendering, rotating and premium proxies, geotargeting, screenshots and extraction rules, priority email support, a dedicated account manager, and team management are included. Credits are valid for one month and do not roll over; requests start at 1 credit each, with JS rendering at 5 credits, premium proxies at 10 or 25 credits depending on JS rendering, and stealth options higher. All prices are exclusive of VAT. A starting free allowance and cancellation terms should both be verified before budgeting.

Parameter decision map
SituationOption to setWhy
Results only appear after scripts runrender_js=trueExecutes JavaScript server-side and returns post-render HTML
CAPTCHA or bot challenges block the pagestealth_proxyRoutes through stealth infrastructure for harder anti-bot stacks
Results differ by countrycountry_codeRoutes through a residential IP in the chosen country
Need named fields as JSONextract_rules or ai_extract_rulesSelector mapping for stable layouts; natural-language spec for changing layouts

Options and credit costs are as captured; confirm current owner terms before use.

Frequently asked questions

How do I handle JavaScript when scraping local search results?

Set render_js=true. The page is executed in a real headless browser on the server side, and the HTML returned is the version after scripts have run.

Can I scrape local search results from a specific country?

Yes. Supply country_code to route the request through a residential IP in that country, which helps when results differ by geography.

What's the rate limit for scraping local search results?

Limits are concurrency limits per plan rather than per-target rate limits. If a target throttles aggressive patterns, space requests out or use multiple sessions.

How do I get structured JSON from local search results?

Use extract_rules to map CSS selectors to field names, or ai_extract_rules with a natural-language specification. The response is returned as parsed JSON.

Which programming languages can I use to scrape local search results?

Any common stack works. SDKs are published for Python, Node.js, Go, PHP, Ruby, and Java, and plain cURL works too.

How much does it cost to scrape local search results?

A free-credit allowance is offered on signup without a card, and paid plans start at a lower monthly tier for higher volume and concurrency. Per-request credit cost varies by option: 5 credits for JS rendering, 25 for premium_proxy with JS, and 75 for stealth_proxy. Confirm current owner pricing and allowances before budgeting, as these figures are volatile.