All posts
Insights and guides

All cities vs a short city list for Marketplace monitoring

Wider Marketplace coverage sounds better until city slots, triage time, and travel radius catch up. Here is when all-cities helps and when a short list wins.

More cities are not automatically more deals. They are more fetch budget, more alerts to triage, and more listings you will never drive to. The useful question is whether a wide net increases closed inspections, or only increases noise.

This is the choice between an all-cities monitor and a short, deliberate city list.

What "all cities" actually means

In Crawlbench, an active all_cities monitor spends the account's full city-slot budget and rotates that many anchor metros across fan-out cycles. Unlimited city slots can crawl the full anchor set each cycle. A short list pins the monitor to the metros you name.

Neither mode promises that every city is checked every 10-minute fan-out. Coverage rotates. Treat both as scheduled monitoring with different width settings, not as a live map of the whole country.

Details on multi-city workflow without tab chaos: monitoring multiple cities.

When a short city list wins

Pick three to five metros (or fewer) when:

  1. You will only inspect within a known drive time
  2. Your buy box is common enough that local volume already fills the week
  3. You are still tuning excluded terms and year floors (wide coverage multiplies false positives)
  4. Your plan's city slots are tight and you would rather run two sharp monitors than one bloated one

A short list also keeps triage honest. If every alert is inside a radius you actually travel, you can message with a real inspection window instead of "maybe next month if I am nearby."

When all-cities earns its keep

Widen coverage when:

  1. Your segment is thin (specific years, rare trims, odd price bands)
  2. You or a partner can travel, ship, or use transporters for the right car
  3. Filters are already strict (make, model, year floor, price cap, excluded terms)
  4. Missing one listing in an adjacent metro costs more than reviewing extra alerts

All-cities is a density play for scarce inventory. It is a poor substitute for weak filters. If "Camry under $6k" is already noisy in one city, making it national will not fix the buy box.

The real costs people skip

City slots. Caps bind at the owning account. An all-cities monitor consumes the full city-slot budget for that account while it is active. Check pricing before you assume you can also run five other wide monitors.

Triage time. Every extra metro is more alerts that need the two-minute kill ritual. If you cannot process the queue, wider coverage just trains you to ignore pings.

Travel fiction. A $2,000 "deal" four states away is not a deal if you will not go. Either budget transport or keep the map smaller.

Fetch ceiling. Scheduled crawls consume monthly fetch budget. Wider rotation uses more of it. Plans list ceilings explicitly on the pricing page.

A practical decision rule

Start narrow for seven days:

  1. Pick the metros you can inspect this month
  2. Set strict vehicle filters on vehicle monitoring
  3. Measure alerts per day and how many earned a seller message
  4. Widen only if qualified conversations are too few after filters are tight

Move to all-cities only after the short list proves the filters, not before. Width without discipline is just a louder refresh button.

Closing

All-cities is a tool for scarce inventory and real travel range. A short city list is the default for most buyers who still want to stand in front of the car this week. Choose the map that matches your calendar, not the map that looks impressive on a settings screen.

put the guide to work

Never miss a mispriced listing

Crawlbench runs scheduled Marketplace checks and alerts you on Telegram, email, and in-app when a match clears your filters.

Full access for one day, no card · then 7-day free trial