Give it an origin and a destination and it returns the route: step-by-step directions with coordinates, distances and travel times. Pick a travel mode, set a departure or arrival time, and get the journey as data instead of a screenshot of a blue line.
The name is ambiguous, so before anything else - here is exactly which sense applies.
This tool deals with road traffic: the conditions between an origin and a destination that determine how long a journey takes. You supply two points; you get the route, the distance and the travel time.
It is not footfall. If you want to know how busy a place is by hour, that's the popular_times field the Google Maps Scraper already returns on every place row - no separate tool needed.
And it is not website traffic. Visits, rank and audience data for a domain are a different category entirely, covered elsewhere in the catalogue.
We'd rather spend the first section of the page on this than have you buy the wrong thing. If it's journey time you're after, read on.
Origin and destination can each be given as a plain address or as coordinates, so it works with whatever your data already looks like.
Because time is a parameter rather than "now", the same pair of points can be measured at rush hour and at midnight in the same run.
Mode changes the route, not just the duration - a cycling route and a driving route often share very little road.
A run returns the journey rather than a single number: step-by-step directions with coordinates, along with distances and travel times. That means you can use the total for a drive-time calculation, or walk the individual legs if you need the actual path.
We don't print a fixed column list on this page - the header row of a real run is the authoritative answer, and the free tier exists partly so you can read it before modelling anything. Worth calibrating early here, since a route with many turns produces more detail than a short hop.
A few examples of how teams use route and travel-time data.
Catchment isn't a radius - it's a drive time, and the two diverge badly wherever there's a river, a motorway or a one-way system. Measuring real journey times from candidate sites to the places customers come from gives you a defensible catchment instead of a circle on a map.
If you promise a 30-minute response, the boundary of that promise moves with the clock. Measuring the same routes at peak and off-peak shows where the commitment is realistic and where it quietly isn't.
For access studies and transport work, the interesting number is the gap: how much longer the journey takes by transit or bike than by car. Running both modes over the same pairs produces that comparison directly.
No subscription, no minimum. Your first 500 rows are on us - after that, pay-as-you-go.
Every new account, one-time. No credit card required. All scrapers unlocked, full feature set - enough to test a handful of routes and calibrate before scaling.
Roughly $2 per 1,000 rows. The pre-flight estimator shows the count and credit cost before a run starts - useful here, since origin-destination matrices grow multiplicatively.
Volume pricing, SLAs, dedicated workers and bespoke onboarding for recurring catchment or service-area modelling. Tell us your numbers and we'll quote.
LIVESCRAPER10 at checkout.Journey data is most useful once you have a list of real places at both ends.
Where your origins and destinations come from - every business in a category and city, with latitude and longitude on each row, ready to route between. It also carries popular_times, the footfall figure this tool doesn't cover.
Assessing candidate sites remotely? Drive time tells you who can reach a location; photos show you what they'll find when they get there.
Short answer: yes - and of everything in the catalogue, this is the least sensitive data we handle.
A route between two public places contains no personal data at all. There's no author, no reviewer, no name - just distances, durations and coordinates on public roads. Nothing here identifies a person, which puts it in a different category from review or profile data entirely.
The usual platform caveat still applies: Google's terms restrict automated access, so this is a terms question as much as a legal one. If you have an agreement with Google covering Maps usage, check it - that call is yours to make.
We touch nothing behind a login, collect no location history and no user data, run no third-party trackers on the data layer, and your exports auto-delete after 30 days.
The questions we hear most. Anything else? Talk to us - humans, not bots, write the answers.
popular_times, which the Google Maps Scraper already returns on every place row. And if you meant visits to a website, that's a different category again.latitude and longitude columns feed straight in.500 one-time free rows on every new account - no expiry. After that it's $0.002 per row, pay-as-you-go - no card on file until you say so.
Livescraper's Google Maps Traffic Scraper returns the journey between two points. You set an origin and a destination - each as a plain address or a latitude/longitude pair - choose a travel mode, optionally fix a departure or arrival time, and download step-by-step directions with coordinates, distances and travel times as CSV, JSON or Excel.
One clarification first, because the name is ambiguous. This is road traffic in the sense of journey time: how long it takes to get from A to B, with conditions reflected in the duration. It is not footfall - if you want to know how busy a place is by hour, that is the popular_times field the Google Maps Scraper already returns on every place row. And it is not website traffic, which is a different category of tool entirely.
Seven travel modes are available: Best, driving, two-wheeler, transit, walking, cycling and flight. Mode matters more than people expect, because it changes the route and not merely the duration - a cycling path and a driving route between the same points frequently share very little road. And because time is a parameter rather than always "now", the same pair can be measured at peak and off-peak in one run.
Retail and property teams score candidate sites by real drive time rather than a radius, since catchment circles fall apart wherever a river, motorway or one-way system sits in the way. Field-service and delivery teams test whether a response-time promise survives rush hour. Transport researchers compare modes across the same origin-destination pairs to quantify the access gap. Start free - your first 500 rows cost nothing and need no credit card.