Sign in Start free
LOCAL

NAP consistency audit

Use when name, address and phone details have drifted across directories and you need a fix list.

nap-consistency-audit.md
Download .md
You are auditing name, address and phone consistency for a local business.

Canonical details as they should appear everywhere:
Name: {{CANONICAL_NAME}}
Address: {{CANONICAL_ADDRESS}}
Phone: {{CANONICAL_PHONE}}
Website: {{CANONICAL_URL}}
Opening hours: {{CANONICAL_HOURS}}

Listings found, one per line as platform, then the details as they currently appear:
{{LISTINGS_FOUND}}

Output a table with columns: Platform, Field with a mismatch, Current value, Correct value, Severity, Action.

Severity rules, apply strictly:
- High: a different phone number, a different street address or postcode, a name that a customer would not recognize as the same business, or a duplicate live listing.
- Medium: suite or unit number missing, abbreviation differences that change the address string, a redirecting or wrong website URL, hours that contradict the canonical set.
- Low: punctuation, capitalisation, trading name suffix such as Ltd present or absent, formatting of the phone number.

Then give me:
1. A fix order: the listings to correct first and why, ranked by severity then by likely traffic.
2. Any listing where the fix needs claiming or verification rather than a simple edit, flagged separately because those take longer.
3. Any suspected duplicate listings and what to do with each.

Do not invent platforms I did not list. Do not guess at what a listing says. If a line I gave you is incomplete, put [INCOMPLETE] in the row and say what to check.

Fill in before running

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

  • {{CANONICAL_NAME}}
  • {{CANONICAL_ADDRESS}}
  • {{CANONICAL_PHONE}}
  • {{CANONICAL_URL}}
  • {{CANONICAL_HOURS}}
  • {{LISTINGS_FOUND}}

Getting a better result

  1. Decide the canonical format once, including whether Ltd and the unit number are included, before you start editing anything.
  2. Duplicates hurt more than formatting inconsistencies, so clear those first even though they take longer.
  3. Keep the finished table as the reference document - the next audit is a diff against it rather than a fresh start.

Questions about this prompt

When do I need an audit rather than just fixing what looks wrong?

When details have drifted across several directories and you need an order of work. Any tool can tell you fourteen listings disagree. This assigns severity and a fix order, which is what stops you spending an afternoon on punctuation and capitalisation while a wrong phone number stays live somewhere that gets traffic.

What do I need to prepare?

A canonical set decided first, down to whether Ltd and the unit number are included, covering name, address, phone, website and hours. Settle that before you open a single dashboard. Then paste {{LISTINGS_FOUND}} one per line as platform plus current details. Incomplete lines come back marked [INCOMPLETE] rather than guessed at.

What comes back, and what do I act on first?

A mismatch table with severity and action, a fix order, and two separate lists: listings that need claiming or verification rather than an edit, and suspected duplicates. Act on the duplicates first even though they take longest. A second live listing does more damage than every formatting difference put together.

What is the mistake that wastes the most time?

Starting the edits before the canonical format is settled, which means editing the same listings twice. Keep the finished table afterwards so the next audit is a diff rather than a fresh start, and schedule the claiming and verification list as its own piece of work, because it will not fit in the same afternoon.