Why Foot Traffic Counts Lie: A Guide for First-Time US Restaurant Owners

A broker tells you a site sees 20,000 vehicles a day, or a shopping center reports 500,000 annual visitors, and it sounds like proof the location works. It isn't. Foot and vehicle traffic counts measure volume passing a point, not whether that volume actually notices, wants, or is able to stop at your specific restaurant.

For a suburban or strip-mall location, the gap between traffic passing on the road and customers actually walking through your door is enormous and depends on factors a traffic count never captures: can drivers see your signage from the speed and lane they're traveling in, is there a safe and easy turn lane into the lot, is parking visible and available right when they'd want to stop. A site with heavy commuter traffic moving at 45 mph past a set-back building with a small sign converts a small fraction of a lower-traffic road where every driver can see the entrance clearly and turn in without stress.

One of the most common site-selection mistakes in car-dependent markets: a location is visible and appealing, but there's no dedicated turn lane, or the turn lane is on the wrong side for the direction most commuters are traveling during peak meal hours. A restaurant that's easy to reach heading home from work but requires a dangerous or inconvenient turn heading to work loses half its potential daypart traffic to nothing more than road geometry.

Customers who can't see available parking as they approach often just keep driving rather than risk circling a full lot. A site with technically adequate parking that's hidden behind the building, or shared with several other businesses in a way that makes availability unpredictable, will underperform a site with visibly available parking directly in view — even at an identical traffic count and an identical number of total parking spaces.

Two suburban strip-mall units sit on the same road, both reporting roughly 18,000 vehicles a day passing. Unit A is set back from the road with parking behind the building, invisible from the street, and its sign is a small tenant panel on a shared pylon. Unit B faces the road directly, has visible parking directly in front, and has its own prominent, well-lit sign. If even 3% of passing traffic notices and considers Unit A while 10% notices and considers Unit B, and both convert a similar share of those who notice, Unit B could see more than three times the daily visits Unit A gets — from the identical traffic count both sites technically share.

A restaurant only needs traffic during meal windows, not all day. A road with high traffic at 8am and 5pm (commuter peaks) but light traffic at lunch is a very different opportunity for a lunch-dependent concept than a road with steady traffic across the whole midday window, even if their 24-hour averages are identical. Ask for traffic counts broken down by hour, not just a daily total.

None of this means traffic counts are useless — they're one input. The mistake is treating a big number as the answer instead of one data point that needs to be checked against visibility, access, turn-lane geometry, and parking before it means anything for your specific concept at your specific site.

A road's traffic count is usually an annual average, which can hide dramatic swings that matter enormously to a restaurant. A road near a seasonal tourist attraction might see triple its average traffic in summer and a fraction of it in winter, while a road near office parks sees the opposite pattern — steady on weekdays, dead on weekends. Ask for a seasonal and day-of-week breakdown, not just a single annual number, especially if your concept's own demand has its own seasonality that might or might not line up with the road's.

You don't have to take a broker's traffic figure on faith. State and city department of transportation websites publish traffic count data for most major roads, often broken down by direction and sometimes by time of day, and it's free to check directly rather than relying on a secondhand number from a listing sheet. Cross-referencing the official count against what a broker quotes you is a five-minute check that occasionally reveals a meaningfully different, and more honest, number.

For a walkable downtown or mixed-use site, pedestrian counts carry a parallel problem to vehicle counts — they measure people passing, not people who'd actually stop for your specific concept. A count taken during a lunch rush of office workers walking briskly to a meeting looks impressive but represents a very different, much lower-intent crowd than a count taken during a weekend afternoon when people are genuinely out browsing and open to stopping somewhere new.

A Viabe.ai Location Intelligence Report evaluates the site-specific factors that determine whether traffic actually converts — visibility, access, competitor context — not just the raw count a broker hands you.