Fix Facebook Marketplace radius that shows 90-mile cars

Facebook Marketplace's own radius control does not reliably restrict vehicle results. A tight distance setting can return the same cars as a wide one, including listings tens of miles past the town you picked.

That is why a local hunt still fills with cars you will not drive to. The filter chip changes. The feed often does not.

Try Crawlbench free for a day

Prove a local buy box on a no-card Day Pass. One monitor, 24 hours. Pass facts: Facebook Marketplace Day Pass.

Does Facebook Marketplace honor the radius you set?

On the vehicle feeds we checked, Facebook Marketplace did not honor the radius. Setting the control to Facebook's tightest option produced the same result set as the default wide radius.

This was not a saved-search glitch and not a third-party tool. It was facebook.com/marketplace, opened in a normal browser, with no account signed in.

The radius control is easy to trust because it looks exact. Miles or kilometres, a slider, a number. Buyers treat it like a hard fence around the city they can actually visit. On vehicles, that fence did not hold.

What we checked in Telford

In September 2026 we set Facebook Marketplace to Telford in the UK and compared the default 65 km radius with Facebook's tightest option, 1 km, on cars, motorcycles, and the general vehicles feed. The listing set did not change. Distant cars still appeared, some about 90 miles away.

That is a concrete, rerunnable check. Pick the same town, the same vehicle browse, and flip the radius from wide to the smallest mark Facebook offers. If the far towns stay in the first screens, the control is not doing the job the label implies.

We did not test every category or every country. Electronics, rentals, and other markets may behave differently. One UK town is not a worldwide proof. It is enough to stop treating the radius chip as a guarantee on vehicles.

Marketplace search is already a weak filter surface. Radius is one more control that looks strict and still lets distant inventory through.

Why a 40-mile hunt still shows cars 90 miles away

A 40-mile vehicle hunt still shows cars 90 miles away when Facebook's radius does not actually cut the feed. You then spend triage time on listings whose travel cost already killed the deal.

You set a tight radius because you have a workday, a trailer, or a same-evening pickup window. A car two hours away is not a candidate. It is noise that looks like a candidate until you read the town name.

That noise has a cost. You open listings you will never inspect, compare prices from the wrong market, and almost message a seller whose driveway is a wasted Saturday. Then the queue looks thin, so you loosen other filters, when the real problem was geography.

Vehicle filters also miss cars when sellers leave make or model blank. That is a different failure, covered in why Marketplace vehicle filters miss listings. Radius failure is the opposite shape: the car is real, and it is simply too far.

What Facebook's radius actually does

Facebook's radius control changes the label on the search. In the vehicle check above, it did not change which listings appeared.

We do not know Facebook's ranking formula, and Facebook publishes no SLA for how distance is applied. The honest statement is narrower: on those vehicle feeds, at that town, tightening radius to the smallest available setting left the same cars on screen.

A far listing might have a closer pin than the town name suggests, or distance may be a soft signal mixed with engagement. You cannot audit that from the UI. Guessing the mechanism does not help you buy a car this week. Treating the chip as a hard fence does hurt you.

What to do instead of trusting the filter chip

Re-check the listing's town against the distance you will actually drive. Do not let Facebook's radius chip make that decision.

Write the trip you will take this week as a number. Pick cities you can cover, set radius to that number, and read the town before the price. Skip anything past the trip limit, even if Marketplace showed it.

Make, model, and radius is still the right minimal vehicle setup. The radius number is your travel rule. Facebook's own control is not a substitute for that rule.

Crawlbench vehicle monitors re-check distance on their own. If Facebook returned a car outside the radius you set, the row stays in the feed with an Outside radius mark so you can still see what Marketplace showed. It does not fire an alert. You can hide those rows when you want a clean local queue. You still message the seller on Facebook.

We tested vehicles only, so this post makes no claim about the radius gap in other Marketplace categories.

A Monday-morning radius check

Run this once on the vehicle search you already use.

1. Open Facebook Marketplace, pick your usual town, and choose cars or vehicles
2. Note the first screen of towns at the default radius
3. Set radius to the smallest option Facebook offers
4. Compare the towns. If the far ones remain, stop trusting the chip
5. Write your real drive limit and apply it by hand, or with a monitor that re-checks distance

If the tight radius does shrink your local feed, keep using it. The Telford vehicle check is a finding, not a law for every search. The useful habit is the same either way: believe the town name, not the slider.

The takeaway

Facebook Marketplace radius is not a reliable fence on vehicle search. A 1 km setting can still show cars about 90 miles away. Set a travel number you mean, read the town on every candidate, and use a monitor that marks out-of-radius rows instead of alerting you as if they were local.

Crawlbench is not affiliated with Meta.