How do I choose a local rank tracker without confusing a map grid with a promised position?

What should a local rank tracker record at each map point?

A local rank tracker should preserve the keyword, map point, scan date and settings behind every result. Google says distance is measured from the customer who searches, so a result from one location cannot stand in for every customer. For a practical way to think about this measurement, see the guide to tracking local search rankings.

Local Falcon's Scan Explorer describes each grid-point number as the listing's rank for a search performed at that specific point. Its 20+ display means the listing is not showing there or is so far down that it might as well not be. A buyer should be able to export or inspect the point-level record, not only a single headline number.

How should I choose the scan radius and grid size?

Choose a radius and grid size that describe the area you want to inspect, then keep both settings recorded for later comparisons. Local Falcon says grid size determines the number of data points, radius reaches from the grid center to the outer points, and the combination determines the distance between pins. Its page recommends an 11 × 11 grid for visualization, offers 9 × 9 when budget is a concern, and allows irrelevant points such as points over water to be disabled.

Local Falcon gives 2 miles as a starting radius for urban areas, 5 miles for suburban areas and 10 miles for rural areas. Those figures are configuration starting points from that vendor. They do not define Google's coverage or a ranking boundary. Run one or two baseline scans before choosing recurring settings, as Local Falcon recommends, then record what changed between the baseline and the recurring setup.

A workable scan specification: For an urban business, start with an 11 × 11 grid and a 2-mile radius. Record the exact pin spacing shown by the tracker, and disable water points when they do not represent plausible searches. Run one or two baseline scans first. Save the keyword list, centre, date, time, grid, radius, spacing and disabled points with each report.

Which keywords should I track?

Choose a tracker that accepts the exact keyword set you need to compare and makes that set visible in each scan. Local Falcon allows keywords entered manually, selected from Suggested Keywords, or both. It says a user can scan as few or as many keywords as desired, while around 10 is the most common simultaneous count. Around 10 is a usage pattern, not a limit.

The buyer checklist is simple: confirm whether manual and suggested terms are supported, write down the terms used in the baseline, and check that recurring scans keep or clearly expose the same set. A tracker that silently changes the query set makes a later difference hard to interpret.

How do I keep local rank scans comparable over time?

Keep the location, keyword set, grid, radius, pin spacing and scan schedule visible in every recurring record. Local Falcon Campaigns expose a start date, frequency and run time. The service recommends weekly or every-two-week scans; for a monthly cadence, it says to choose every 4 weeks so scans stay on the same weekday. A campaign can reuse settings across locations or customise them per location, so check which behaviour applies.

Local Falcon also says campaigns should run at a time when all locations in the campaign are open. That instruction belongs to its Campaign setup. It is useful when a buyer compares recurring scans across locations and wants the run conditions recorded rather than assumed.

What should a local rank tracker let me export?

Require a usable record outside the tracker before treating its reporting as practical. Local Falcon says it supports CSV and PDF exports, public shareable URLs for scans or reports, API access, and other integrations. A buyer should test one export and one shareable report link against the way the business actually reviews or sends results.

The comparison of local SEO tools is the next step when you want to compare named products. Keep the comparison fair by carrying each product's keyword set, map points, grid, radius, date and export format beside its reported result.

How can I tell whether a tracker reports an observation instead of promising a rank?

A tracker reports an observation when it ties each number to a named keyword, point, scan and configuration. It promises too much when it presents that number as one position every customer should see. Google's guidance says nobody can request or pay for a better local ranking and that Google keeps its ranking-algorithm details confidential. A tracker can record a check. It cannot sell a Google position.

Treat 20+ as a display condition, not an exact rank. Local Falcon says the value can mean that the listing is absent from that point or so far down that it might as well not be visible. Report the point, keyword, date and display value together, then use the free audit if you want an outside check of the profile and local visibility signals behind the record.