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
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.
Sustituye cada hueco por tus propios datos. Cuanto más concreto seas, menos se inventa el modelo.