QuQi
LOKAL

Map pack grid tracking plan

Use when your map ranking changes depending on where the searcher is standing and you need to measure it properly.

map-pack-grid-tracking-plan.md
.md herunterladen
You are specifying how to measure map results across a service area. You are not running the scans and you hold no ranking data of your own.

Address the grid centres on: {{BUSINESS_ADDRESS}}
Area we serve and how far out it goes: {{SERVICE_RADIUS}}
Terms worth tracking: {{PRIORITY_TERMS}}
What we track today and in which tool: {{CURRENT_TRACKING}}

Produce:

1. A grid specification: number of points, spacing and total span, centred on {{BUSINESS_ADDRESS}} and covering {{SERVICE_RADIUS}}. Justify the spacing in two sentences. Where {{SERVICE_RADIUS}} is too wide to cover at usable spacing, propose two grids rather than one loose one.

2. A term table: Term from {{PRIORITY_TERMS}}, why it is worth the scan cost, the pattern you would expect if things are healthy, scan frequency.

3. A reading guide covering a tight ring around the pin, a lopsided grid, a uniformly weak grid, and a grid that moves week to week. Say what each suggests and which are worth acting on.

4. A gap list against {{CURRENT_TRACKING}}: keep, drop, add, with a reason on each line.

Rules:
- Do not state the distance at which visibility drops away. Say it varies with how many competitors sit between the searcher and the pin.
- Grid position is not a proxy for enquiries. Name two things to report alongside it.
- Never suggest an address change or an extra listing to widen the grid.
- No em dashes.

Vor dem Start ausfüllen

Ersetzen Sie jeden Platzhalter durch Ihre eigenen Angaben. Je genauer Sie sind, desto weniger erfindet das Modell.

  • {{BUSINESS_ADDRESS}}
  • {{SERVICE_RADIUS}}
  • {{PRIORITY_TERMS}}
  • {{CURRENT_TRACKING}}

So wird das Ergebnis besser

  1. Run the same grid on the same weekday. Comparing two different spacings tells you nothing.
  2. Track three or four terms, not thirty. Cost rises with points multiplied by terms multiplied by runs.
  3. Pair the grid with calls and direction requests, or you end up improving a picture nobody buys from.