Open, Move, and Close Playbook for Local Listings

Step-by-step local listing playbook for opening, relocating, or closing a location so maps and directories show the correct address, hours, and status.

Open move close playbook for local listings

An open, move, and close playbook for local listings is the step-by-step sequence to create, relocate, or retire public place cards so maps and local directories show the correct status, address, and hours during location lifecycle events. It is a high-risk local listing management workflow. Definition hub: What is local listing management?.

This is an ops playbook — not a definition page and not a platform ranking.

Why lifecycle events need a playbook

Opening, moving, or closing a store creates duplicate pins, old addresses that keep ranking, and "open now" on dead locations. Google's representation guidelines and local ranking tips both stress accurate, real-world information. Lifecycle mistakes spread through aggregators if you only fix Google.

Open (new location)

  1. Freeze the canonical NAP, categories, hours, URL, and open date in the source of truth.
  2. Claim/create Google Business Profile with truthful data; verify ownership.
  3. Claim Apple Maps and Bing Places with the same identity (publisher priority).
  4. Hold marketing announcements until Tier 1 place cards match the approved record.
  5. Store ownership emails and recovery codes in the vault (RACI).
  6. Capture QA evidence on public cards (QA evidence).

Move (address or suite change)

  1. Decide whether the publisher treats this as an edit to the same entity or a new place (follow platform rules; do not invent a second Google pin "for SEO").
  2. Update the source of truth first; then Tier 1 publishers in the same day window when possible.
  3. Watch for duplicate old-address listings; suppress or mark closed per platform tools.
  4. Update hours if the move includes temporary closure (hours change control).
  5. Verify maps pins land on the correct building before running ads to the new address.

Close (temporary vs permanent)

Close typeLocal listing actionCommon mistake
TemporaryTemporary closed + reopen date where supportedLeaving temporary closed forever
PermanentMark permanently closed; stop citations that re-open itOnly removing the website
Relocate brandMove playbook + redirect customersCreating a competing pin

Evidence table

EventMust-verify surfacesPass criteria
OpenGoogle, Apple, Bing public cardsNAP/hours/status match source
MoveSame + old-address searchNo live competing old suite
Permanent closeSame + major aggregatorsStatus closed; no "open now"

Frequently asked questions

Should we create a new Google profile for every move?

Only when platform rules require a new entity. Prefer updating the existing verified profile when it is the same business continuing at a new address.

Does closing Google alone finish the job?

No. Aggregators and secondary maps can keep the old address alive. Local listings management includes the verify loop across priority publishers.