The Closest Place Is Rarely the Best One

Search "coffee near me" and you get a map covered in pins, with the nearest one practically glowing. So you go there. Most of us do this several times a week without thinking about it.

The thing is, nobody ever decided that place was good. It just happens to be close.

Distance is a lazy filter

Sorting by distance answers a question you didn't ask. You wanted to know where to eat. It told you what's geographically nearest, which is a completely different thing.

The gap between those two answers is often bigger than people realize. Walk one extra block in a city and you might go from a 3.8 to a 4.6. Drive four more minutes in the suburbs and the same thing happens. You're trading a couple of minutes for a genuinely better hour.

And here's what makes it worse: the closest place gets picked constantly for exactly this reason, which means mediocre businesses in good locations survive on convenience alone. Being near a busy intersection is not a sign of quality. Sometimes it's the reason a place never had to get good.

How much wider should you look?

A useful rule: search a radius that matches how you're traveling.

• Walking — half a mile to a mile. Ten to twenty minutes on foot, and in most downtowns that covers dozens of options.
• Driving in a city — two to three miles. Feels far on a map, usually under ten minutes in practice.
• Driving in the suburbs — five miles is nothing. You'll pass three strip malls getting there.
• Something worth planning around — a proper dinner, a mechanic you'll trust with your car — go ten miles or more. You're not doing this every day.

Most people search a radius far smaller than they'd actually be willing to travel. Widening it costs you nothing and changes the list completely.

When distance genuinely should win

Not always, though. There are real cases where nearest is the right call:

• You're on a clock. A 45-minute lunch break makes a 20-minute drive absurd, regardless of ratings.
• The quality gap is small. A 4.5 next door beats a 4.6 across town. That 0.1 is noise, not a difference.
• It's a commodity. Gas, a gallon of milk, an ATM. There's not much quality to optimize for.
• You'll go often. The coffee shop you visit daily needs to be convenient or you'll stop going. Weigh distance heavily for habits.
• Weather, kids, tired. Perfectly good reasons. The best restaurant is the one you actually get to.

The point isn't that distance doesn't matter. It's that distance shouldn't be doing the deciding all by itself, which is what happens by default.

A better way to run the search

Try this instead of taking the first pin:

1. Search a radius a bit wider than feels necessary.
2. Sort by rating first, so you see what's actually good in that whole area.
3. Then look at how far the top few are. Often the best option is barely farther than the nearest one.
4. Only fall back to sorting by distance if the good options really are inconvenient.

You'll be surprised how often the highest-rated place in a three-mile radius is six minutes away instead of two. Four minutes is not a real cost. Eating somewhere disappointing is.

One last thing about map apps

It's worth knowing that when a map app shows you "top" results, it isn't purely ranking by quality either. It blends distance, popularity, how complete the business listing is, and how much the business engages with the platform.

That's not a conspiracy, it's just a different goal than yours. Those systems are trying to give a reasonable answer to millions of vague searches. You're trying to have one good dinner. Those aren't the same problem, so it pays to do the last bit of filtering yourself.