Thomas Lucas You land in Ghent, open your phone, type “travel q tips nearby,” and get 40 results. All of them point to the same castle, the same frites stand, the same canal tour. It feels less like discovery and more like a choreographed cattle route.
I’ve spent enough time wandering Belgium, France, Germany, Ireland, and the Netherlands to know this: the default “nearby” results are rarely the best use of your time. They’re the most optimized, not the most interesting. This is how I filter them.
The Problem With “Nearby” Search Results
Here’s the core issue. When you search for travel tips nearby, the algorithm isn’t asking “what would this specific person love?” It’s asking “what do most tourists click on?” That’s a big difference.
Google Maps and Tripadvisor reward places with high volume. The pancake house with 12,000 reviews in Amsterdam floats to the top. The family-run broodjeszaak two streets away with 87 perfect reviews? Buried. It’s not that the pancake house is bad. It’s that you’re seeing a popularity contest, not a quality ranking.
I’ve tested this in Bruges more times than I can count. Search “best food near me” at noon and you’ll get the tourist traps around the Markt. Walk 10 minutes north toward the Sint-Gillis district and you’ll find better bread, better coffee, and no queue. The algorithm doesn’t reward that walk. You have to force it.
What The Algorithm Actually Rewards
- Review velocity: How many reviews in the last 30 days, not how good they are.
- Photo count: Places with 500 photos of the same latte art rank higher than a better café with 30 photos.
- Proximity to other tourist anchors: If it’s next to a cathedral, it gets a boost regardless of quality.
- SEO-optimized descriptions: Some restaurants literally hire people to manage their Google presence. That’s fine, but it doesn’t make the food better.
None of those factors tell you whether the place is actually good. They tell you whether the place is good at being found.
Filter Out The Noise: A Working Method
I don’t rely on one app anymore. I use a stack, and I use them in a specific order.
First, Google Maps for logistics, not recommendations. I use it to see what’s physically close and when things are open. That’s it. I ignore the star rating unless it’s below 4.0 — that’s the only signal I trust, because if a place in a tourist zone dips below 4.0, something is genuinely wrong.
Second, I check Spotted by Locals. It’s a paid app (€3.99/month, worth every cent for a 10-day trip). The tips come from people who actually live in the city, not influencers passing through. They don’t get paid per click, so there’s no incentive to send you to the same 10 spots. In Antwerp, it sent me to a coffee bar called Caffènation that I’d never have found otherwise. Best flat white of the trip.
Third, I cross-reference with Komoot for walking routes. This is the one I recommend most for “nearby” searches that involve any walking at all. It shows you footpaths, not just roads. In the Ardennes, it found me a trail along the Semois river that Google Maps didn’t even know existed.
My Exact Filtering Sequence
- Open Google Maps. Save anything under 4.0 stars to a “Skip” list. This takes 2 minutes.
- Open Spotted by Locals. Look for spots within 1km of my current location. Save 5-6 options.
- Open Komoot if I’m walking or cycling. Check if there’s a non-road route between the spots I saved.
- Ask one real human. Hotel front desk, barista, the person next to me on the train. One question: “Where do you eat on your day off?”
That last step matters more than any app. Locals in Leuven sent me to a student lunch spot called De Werf where I got a full meal for €9. No app would’ve surfaced that. It’s not optimized for tourists.
When “Nearby” Search Actually Works
I’m not saying the feature is useless. It works well for three specific things.
Pharmacies and emergencies. When you need a pharmacy in rural Ireland at 6pm, Google Maps is unbeatable. It shows hours, phone numbers, and distance accurately. Use it for that.
Public transit connections. In Berlin, the “nearby” search combined with BVG’s live departure data is genuinely excellent. It tells you exactly which U-Bahn entrance to use and when the next train leaves. That’s a solved problem.
Opening hours and closures. In France, a lot of restaurants close between 2pm and 7pm. Google Maps usually has accurate hours. It saves you from showing up hungry at 3pm to a locked door.
For everything else — food, culture, hidden corners — the default search results are a starting point, not a recommendation.
What I Actually Do In A New City (Step By Step)
Here’s my routine now, after years of trial and error. I land, drop my bag, and do this before I look at a single recommendation.
I open Google Maps and search for the nearest public library or university building. Not because I want to visit them. Because those anchors tell me where the non-tourist neighborhoods are. The area around a university always has better cheap food, better coffee, and fewer souvenir shops. In Utrecht, this trick led me to the entire Lombok district. Kanaalstraat has a Turkish bakery called Bakers Best that sells simit for €1.20. I went back three times.
Then I do the opposite of what the algorithm wants. I zoom out. Way out. I look for green spaces and water. In Dublin, this got me to the Poolbeg Lighthouse walk instead of another Temple Bar pub. It was a 7km walk along the Great South Wall, completely free, and I saw maybe 12 other people the entire time. That’s the kind of “nearby tip” no app hands you.
Here’s a comparison of what the default search gives you versus what a filtered search gives you:
| Factor | Default “Nearby” Results | Filtered Results (My Method) |
|---|---|---|
| Food quality | Volume-driven, tourist-adjusted menus | Local favorites, authentic pricing |
| Crowd level | High, especially 12-2pm and 6-8pm | Low to moderate |
| Price | 10-30% tourist markup | Local prices, often €5-10 cheaper per meal |
| Uniqueness | Same 15 places in every blog post | Places you won’t see on Instagram |
| Time to find | 30 seconds | 15-20 minutes of filtering |
That 20 minutes of filtering saves you hours of standing in lines and eating mediocre food. Worth it every time.
Failure Modes: When You Should Ignore This Entire Approach
There’s a real failure mode here, and I’ve fallen into it. Over-filtering. You can spend so much time trying to find the “authentic” spot that you waste half your trip staring at your phone. That’s worse than going to a tourist trap.
Some situations call for just going to the obvious thing. The Eiffel Tower is popular because it’s actually worth seeing. The Rijksmuseum has 47,000 reviews because it holds Rembrandt’s Night Watch. Don’t skip something genuinely great just because it’s popular. The goal isn’t to be contrarian. The goal is to avoid the places that are popular only because they’re popular.
If you’re tired, hungry, or short on time, just go to the nearest well-reviewed place and eat. The filtering method is for when you have energy and want something better than the default. Know the difference.
Also, Rick Steves Audio Europe is still the best free resource for walking tours in Belgium, the Netherlands, and Germany. His audio guides are free, downloadable, and genuinely informative. I use them as a baseline and then wander off-script when something catches my eye. The combination of a structured audio guide plus my own filtering is the sweet spot.
One last thing: don’t trust any “nearby” result that has more photos than reviews. That ratio usually means the place is aggressively managing its online presence. Not always a red flag, but it’s a signal that you’re seeing marketing, not reality.
If you only take one thing from this: spend 15 minutes filtering on day one, and you’ll eat better, walk more interesting streets, and come home with stories that aren’t on the first page of Google. That’s the whole game.
