Pull Google Popular Times Data via API
Popular-times charts are drawn by JavaScript after the page loads, so a plain HTTP fetch usually returns an empty shell.
This page explains how a rendering API handles that step in one request, which request controls change the result, and how the credit cost of each option combination adds up. It is a configuration guide, not a promise of a specific success rate on any location.
What this API does for popular-times collection
The API takes a Google Popular Times URL, loads the page in a real headless browser, and returns the post-render response. Proxy rotation, rate-limiting and bot checks are handled on the service side, so your code sends one HTTP request instead of maintaining a browser fleet. The practical effect is that the hourly bars, day-by-day peak distribution, average visit duration and live busyness indicators are present in the response rather than missing from a static fetch. Whether a given location exposes all of those fields depends on what Google publishes for that place; the API renders the page, it does not invent data that is absent.
Three practical uses for hourly busyness data
The same field set supports different decisions depending on who is asking.
Staffing: compare the hourly curve for each weekday against your shift boundaries. A location that peaks between 12:00 and 14:00 on weekdays needs coverage there, not evenly spread across the day.
Site selection: pull the same weekday for several candidate locations and compare where the curve is flattest versus most concentrated. A concentrated curve means demand is compressed into a short window, which changes how much floor space and queue capacity you need.
Promotion timing: use the troughs, not the peaks, as the slot for a campaign. A discount aimed at an already-busy hour adds load without adding reach.
In all three cases the useful unit is the weekday-by-hour series, not a single average. Averages hide exactly the shape you are trying to act on.
From signup to a rendered page in four steps
- Create an account. The dashboard issues an API key and the signup credit allowance described in the pricing section.
- Install a client. SDKs exist for Python, Node.js, Go, PHP, Ruby and Java; plain cURL works as well. Each scrape becomes a single function call rather than a browser-management project.
- Send the target URL with your API key. The renderer executes the page in a real browser, rotates the IP, and returns the response your scraper acts on.
- Add controls only where the default is not enough: render_js for JavaScript execution, stealth_proxy when bot checks escalate, country_code for geo-targeted routing, and extract_rules or ai_extract_rules when you want parsed JSON instead of raw HTML.
Fields you can expect on a popular-times page
A rendered popular-times page carries four groups of information: peak-hour distribution by day of week, the hourly traffic pattern within each day, an average visit duration, and live busyness indicators where Google shows them. The API returns the page as rendered; turning those groups into named JSON fields is a separate step handled by extraction rules. If you need a stable schema rather than HTML, define the field names yourself and map selectors to them, or describe the fields in natural language and let the AI extraction path produce the JSON.
Request controls and what each one changes
Each control below is optional and each one changes both the response and the credit cost.
render_js=true runs the page in a real headless browser, executes the JavaScript server-side, and returns the post-render HTML. Without it you get the pre-render document, which for popular-times pages usually lacks the hourly bars.
country_code routes the request through a residential IP in the named country. Use it when the page content varies by geography, for example when a location's listing differs between regions.
stealth_proxy is the escalation path when standard rendering is still met by bot checks. It is the most expensive option per request.
extract_rules takes CSS selectors mapped to field names and returns parsed JSON instead of HTML.
ai_extract_rules takes a natural-language description of the fields you want and returns parsed JSON on the same basis.
A useful rule of thumb: start with render_js alone, add country_code only if the content is geo-varied, and move to stealth_proxy only after a plain rendered request fails. Extraction rules are a separate decision from rendering — you can add them at any point without changing how the page is fetched.
How credits are consumed per request
Credit cost is a function of the options enabled on a successful request, not of the target site. A base request costs 1 credit. Enabling JavaScript rendering raises it to 5. A premium proxy without JS rendering costs 10, and with JS rendering 25. stealth_proxy costs 75. The table below records each combination so you can price a batch before running it. Credits are valid for one month and do not roll over, so a monthly volume estimate is more useful than a per-request one. Confirm the current figures with the account owner before budgeting a large run.
Worked example: turning one weekday of bars into a shift plan
Suppose a rendered page returns a Tuesday hourly series and a Tuesday peak marker. Read the series left to right and mark the hours where the bar is at or near its highest point — that is the peak window. Now compare the peak window to your existing shift change times. If the peak falls inside a shift handover, the handover is the bottleneck, not the total headcount. If the peak sits in a trough between two shifts, you have a coverage gap that a small schedule shift closes.
The average visit duration field adds a second check: a long average duration combined with a sharp peak means the queue builds and drains slowly, so the staffing need extends past the peak hour itself. A short average duration with the same peak shape suggests throughput is fine and the constraint is elsewhere.
This is a planning aid built from the published fields, not a forecast. Popular times are relative busyness indicators, so use them to compare hours and days against each other, not as absolute visitor counts.
Telling three failure modes apart
A request that returns something unhelpful is usually one of three cases, and each has a different fix.
Blocked page: the response is a challenge or error page rather than the listing. This is a bot-check problem. Escalate to stealth_proxy and re-test a single URL before changing anything else.
Empty popular-times block: the page renders correctly but the location has no published popular-times data. No control fixes this — the data is not there. Log the location as unsupported rather than retrying.
Unrendered JS shell: the response is the pre-render document with the chart containers present but no bars. This means JavaScript did not execute. Confirm render_js=true is set on the request.
A fourth case is worth separating: a request that succeeds but returns HTML when you expected JSON. That is not a failure of rendering — it means no extraction rule was supplied. Add extract_rules or ai_extract_rules.
Pre-flight checklist before you scale up
Before running a large batch, confirm each of the following on a small sample:
- One URL renders with render_js=true and contains the hourly bars.
- The same URL returns the fields you need when extract_rules or ai_extract_rules is added.
- country_code is set only if the content actually varies by geography for your targets.
- stealth_proxy is enabled only for the subset of URLs that fail without it, so you are not paying 75 credits on every request.
- Your concurrency setting matches your plan tier; the API enforces per-plan concurrency, not per-target rate limits, so a target that throttles aggressive patterns needs spacing or multiple sessions rather than a higher plan alone.
- Your monthly credit estimate accounts for the option mix, not a flat per-request figure.
Plan tiers and concurrency
The plan table below lists monthly price, API credit allowance, concurrent request ceiling, and which support and account features are included at each tier. All tiers include JavaScript rendering, rotating and premium proxies, geotargeting, screenshots and extraction rules; the differences are volume, concurrency, and the support and team features. Prices are exclusive of VAT. Treat the figures as reference values and re-check them with the account owner before purchase.
Commercial terms to confirm with the account owner
Several statements on this page are commercial commitments rather than technical facts, and they must be confirmed by the account owner before you rely on them. These include the signup credit allowance and whether a card is required, the cancellation terms, the credit validity and rollover rule, the per-option credit costs, the support response commitments, and any compliance or performance claims. Treat each as something to verify with the account owner rather than as a guarantee.
| Plan | Monthly price | API credits | Concurrent requests | Priority support | Account manager | Team management |
|---|---|---|---|---|---|---|
| Hobby | $19 /mo | 75,000 | 25 | Not included | Not included | Not included |
| Freelance | $49 /mo | 250,000 | 50 | Not included | Not included | Not included |
| Startup (Recommended) | $99 /mo | 1,000,000 | 100 | Not included | Not included | Not included |
| Business | $249 /mo | 3,000,000 | 200 | Included | Included | Included |
| Business + | $599 /mo | 8,000,000 | 400 | Included | Included | Included |
| Enterprise 14 | $999 /mo | 14,000,000 | 500 | Included | Included | Included |
| Enterprise 24 | $1,599 /mo | 24,000,000 | 600 | Included | Included | Included |
| Enterprise 41 (Recommended) | $2,399 /mo | 41,000,000 | 700 | Included | Included | Included |
| Enterprise 69 | $3,599 /mo | 69,000,000 | 800 | Included | Included | Included |
| Enterprise 120 | $5,799 /mo | 120,000,000 | 900 | Included | Included | Included |
Prices are exclusive of VAT. All tiers include JavaScript rendering, rotating and premium proxies, geotargeting, screenshots and extraction rules. Figures are reference values and should be re-checked with the account owner before purchase.
| Option combination | Credits per successful request |
|---|---|
| Base request (no JS rendering, no premium proxy) | 1 |
| JS rendering enabled | 5 |
| Premium proxy, JS rendering disabled | 10 |
| Premium proxy with JS rendering | 25 |
| stealth_proxy | 75 |
Credit cost depends on the options enabled on the request. Confirm the current per-option figures with the account owner before budgeting a large run. API credits are valid for one month and do not roll over.
Frequently asked questions
How do I handle JavaScript when scraping Google Popular Times?
Set render_js=true on the request. The page is loaded in a real headless browser, the JavaScript runs server-side, and you receive the post-render HTML — which is where the hourly bars live.
Can I scrape Google Popular Times from a specific country?
Yes. Pass country_code on the request to route through a residential IP in that country. This matters when the listing content differs by geography.
What's the rate limit for scraping Google Popular Times?
There is no per-target rate limit. The API enforces concurrency limits per plan tier. If a target throttles aggressive patterns, space out requests or use multiple sessions rather than assuming a higher plan alone will solve it.
How do I get structured JSON from Google Popular Times?
Pass extract_rules with CSS selectors mapped to field names, or use ai_extract_rules with a natural-language description of the fields. Either way the response comes back as parsed JSON rather than HTML.
Which programming languages can I use to scrape Google Popular Times?
Any language that can send an HTTP request. SDKs are published for Python, Node.js, Go, PHP, Ruby and Java, and plain cURL works too.
How much does it cost to scrape Google Popular Times?
Credit cost depends on the options enabled: 1 credit for a base request, 5 with JS rendering, 10 for a premium proxy without JS rendering, 25 for a premium proxy with JS rendering, and 75 for stealth_proxy. Signup includes a free credit allowance and paid plans start at $19/month; confirm the current allowance and prices with the account owner before budgeting.