Collision local visibility and inquiry review
Keep search observations separate from accepted website inquiry outcomes.
Use the interactive tool without signing up. It runs in your browser: enter your numbers, save a comparison, download results or print a working copy. Your numbers are not sent to BlueFinch.
Illustrative example inputs
These starting values show how the math works. They are not industry averages, customer results or a quote.
| Input | Example value |
|---|---|
Planned geographic locations One service query, business and coordinate set. | 25 |
Locations with usable observations Exclude failed and unmeasured collection gaps. | 20 |
Usable observations in the top three Only observations from the entered usable set. | 8 |
Unique website inquiries in a separate cohort Document the source period, unit and observation date. | 30 |
Cohort inquiries with an accepted order Actual decision evidence, not assumed map-derived sales. | 12 |
Example results
| Measure | Result |
|---|---|
Map measurement coverage Usable observations among planned locations. | 80% |
Observed top-three share Top-three observations among usable results. | 40% |
Separate inquiry-to-order share Accepted orders in the defined inquiry cohort. | 40% |
Calculation detail
| Measure | Result |
|---|---|
| Planned locations without a usable result | 5 |
| Usable locations outside top three | 12 |
| Inquiries without accepted-order evidence | 18 |
Model assumptions
- Map query/date and inquiry source/window are distinct records.
- Outside-depth evidence needs a depth including the first three positions.
- Missing observations are collection gaps, not inferred rankings.
- No personal search-to-order match or causal attribution is established.
Read alongside these results
- No live scan, website edit or CRM change occurs.
- Visibility and order rates are not causally linked by this worksheet.
- Empty groups retain unavailable rates.
Download this worked example (CSV). Use the interactive version to export your own inputs and results.
Your body shop might appear near the top of a map scan while few website inquiries reach accepted repair orders. Review the usable search observations and the actual inquiry outcomes separately. A ranking is an observation from a location and query, not evidence of a customer's decision to book.
The worksheet's starting figures are fictional. Keep the map query, locations and collection date in one source record. Keep the inquiry cohort and observation date in another. This calculator runs no live scan and identifies no searcher. It compares entered totals without attributing accepted jobs to the measured map positions.
Use with this guide
Review map scan setup and limits
Check stored sources rather than assuming a live measurement.
Answer a supported intake question
Use the actual shop policy and next step.
Review the actual inquiry cohort
Keep contacts, estimates and accepted orders distinct.
Browse the complete auto body guides and worksheets.
Use the query for the service you actually provide
Record the business identity, exact search phrase, coordinates, observation date and collection settings for the scan. Collision repair and paint work are different queries. Use services the shop provides and accurate location information. A nearby place name in a listing does not replace a measurement from the actual coordinate being reviewed.
Google explains local ranking through relevance, distance and prominence. Keep the business information accurate and complete so the listing describes the real service and location. Do not invent addresses or imply the shop serves a place through a physical location it does not have. Accurate information does not guarantee a particular position or appointment count.
Sources for this section: Google: Local relevance, distance and prominence
Separate usable observations from collection gaps
Use the provider's documented meaning for a successful observation outside the measured depth. For a top-three measure, the searched depth must include those positions. A usable outside-depth result shows no top-three position within that observation. A failed or unmeasured point supplies no evidence of the shop's rank.
Keep failed and unmeasured locations in the coverage-gap count. For a later comparison, match the query, coordinates and relevant settings, then inspect which points supply usable observations in both scans. One scan does not show a before-and-after change. A missing observation is not proof of a poor position.
Read visibility and inquiry outcomes separately
The fictional scan has 20 usable observations from 25 planned locations. Measurement coverage is 80 percent, leaving five coverage gaps. Eight usable observations are in the top three, giving a 40 percent share of usable points. The other 12 usable points are outside the top three under the stated measurement rule.
A separate fictional website cohort has 30 unique inquiries and 12 accepted orders, giving 40 percent inquiry acceptance. Eighteen inquiries lack an accepted order at the observation date. Some are pending. The matching 40 percent figures are coincidental. They do not connect individual inquiries or customer decisions to map positions.
Choose a supported website or intake task
Review supported service descriptions, location details and hours before changing every price. BlueFinch's website audit organizes findings available from the configured analysis. The audit does not automatically fix another site or prove revenue loss. Assign a specific supported issue to the person responsible for the website.
Inspect unresolved estimate questions in the actual inquiry records. Identify the source, missing information and next customer decision. Keep claim details out of public URLs. Use the authorized reporting process to record outcomes. Map visibility alone does not establish who called, where they searched or which page caused their decision.
Sources for this section: BlueFinch: Evidence-backed website audit scope
Review scan settings before planning another comparison
BlueFinch's maps workspace supports configured location and keyword scans, available saved results and history within the account's collection limits. Opening a stored result does not collect a fresh scan. Check the collection date and usable coverage before calling a report current. Setup and source availability still matter.
Download the report for the next visibility and intake review. Start with a missing observation or supported intake gap. Compare a later measurement under matching settings if you need to assess change. Empty denominators stay unavailable. Report visibility observations and accepted repair orders as separate evidence, rather than combining them into a sales claim.
Sources for this section: BlueFinch: Geographic ranking observations and scan limits
Primary sources
BlueFinch last reviewed these sources on October 4, 2026. Payment rules and state requirements can change.
- Google: Local relevance, distance and prominence
- BlueFinch: Evidence-backed website audit scope
- BlueFinch: Geographic ranking observations and scan limits
Use this page for general business information. It is not legal, tax, or accounting advice.
Related resources
- 2026 Credit Card Processing Cost Report
- Auto Body Shop Payment Guide
- Auto Repair Shop Credit Card Processing Calculator
- Build a body-shop customer update queue from recorded repair milestones
- Separate the collision customer, insurer and rental contact in your CRM
- Keep body-shop estimate follow-up separate from insurer authorization