LOCAL

Premises move and address change plan

Use when the business is changing address and the edits need sequencing across the profile, site and directories.

business-relocation-nap-move.md

Download .md

You are sequencing an address change for a local business. You are not deciding whether to move and you cannot check any listing yourself.

Old address: {{OLD_ADDRESS}}
New address: {{NEW_ADDRESS}}
Date the new premises opens and the old one closes: {{MOVE_DATE}}
Everywhere the address appears that we know of: {{SURFACES_LIST}}
How far the move is and whether the catchment changes: {{DISTANCE_AND_CATCHMENT}}

Produce:

1. An impact read of two paragraphs based on {{DISTANCE_AND_CATCHMENT}}: what changes for people searching near the old pin, and whether our existing area content still describes where we work.

2. A timeline table: Timing relative to {{MOVE_DATE}}, from minus four weeks to plus eight weeks, Surface taken from {{SURFACES_LIST}}, Change to make, Owner, How to confirm it took effect.

3. Site work: which pages carry {{OLD_ADDRESS}}, what happens to a location page for the old area, and when a redirect is right rather than a rewrite. State plainly where {{NEW_ADDRESS}} needs a page of its own.

4. A short do not list.

Rules:
- Never leave {{OLD_ADDRESS}} live on a profile past the closing date, and never run two live profiles to hold both areas.
- Do not promise the move is neutral for visibility. Where {{DISTANCE_AND_CATCHMENT}} shows the catchment barely shifts, say the job is smaller than people expect and why.
- Mark [CHECK] where an edit may need re-verification rather than assuming it goes through.
- No em dashes.

Fill in before running

Replace each placeholder with your own detail. The more specific you are, the less the model invents.

{{OLD_ADDRESS}}
{{NEW_ADDRESS}}
{{MOVE_DATE}}
{{SURFACES_LIST}}
{{DISTANCE_AND_CATCHMENT}}

Getting a better result

Change the profile address on the day the new place opens, not when the lease is signed.
Invoices, vehicle livery, email footers and the booking system are the surfaces people forget, and they are what directories copy.
Expect a wobble in map visibility around the move. Do not stack other changes on top of it in the same fortnight.

Questions about this prompt

When should I run this in the move?

As soon as the date is fixed, not when the boxes are packed. The timeline runs from four weeks before to eight weeks after, so half the value is gone if you start on moving day. Run it for any address change, including a short move that keeps you in the same town.

What do I need to hand?

Both addresses, the date the new premises opens and the old one closes, an honest {{SURFACES_LIST}}, and how far the move is with whether the catchment changes. Invoices, vehicle livery, email footers and the booking system belong on that list, because those are the surfaces directories copy from.

What comes back?

An impact read on the catchment, a dated timeline table by surface with how to confirm each change took effect, the site work including when a redirect beats a rewrite, and a short do not list. The confirmation column is what stops an edit that quietly needed re-verification from going unnoticed for weeks.

What is the mistake?

Changing the profile address when the lease is signed rather than when the new place opens, or running two live profiles to hold both areas. Expect a wobble in map visibility around the move, and do not stack other changes on top of it in the same fortnight or you cannot attribute anything.