Operations
Part of How to fix inconsistent NAP citations for UK local SEO
How to fix inconsistent NAP citations for UK local SEO
Fix inconsistent NAP citations with a UK workflow: build one master record, audit directories, correct listings and recheck them every quarter.
What to take away
- Every listing should carry one agreed version of the business name, address and phone number.
- Mixed versions weaken the signals local search uses to confirm a business, so treat this as repair work.
- The loop is simple: agree a master record, audit what is live, correct the gaps, recheck later.
- Companies House filings are a firm reference for a limited company's registered name and office.
Why UK addresses cause most of the damage
UK address variants are the usual culprit: Road against Rd, Street against St, and a postcode written with or without the space. Unit or floor details often appear on one listing but not another.
Phone numbers add their own variants, including +44, 0044 and a leading zero, and tracked numbers per campaign push the mismatch further.
Individually these look trivial. Together they make it harder for a search engine to match one listing to the next, and harder for a customer to believe the business still trades from that address.
Formatting differences are not the same as a wrong address. A missing suite number is cosmetic; a former office is a substantive error that needs fixing everywhere at once.
Build the master record before you touch a directory
Write the agreed version once and store it where the team can find it. Use the registered name, the full postal address with postcode, one phone number in a single format, and the website URL you actually use.
For a limited company, check the registered name and office against your filings at Companies House. Company names and registered offices are governed by the Companies Act 2006, so that record is the reference point.
Decide the display name too. A trading name that differs from the registered name is fine, provided you use it consistently and customers recognise it.
Start where you have control. This Google Business Profile optimisation guide covers the profile fields that other directories tend to copy.
The master record needs a fixed answer for each field:
| Field | What to record | Common error |
|---|---|---|
| Business name | Registered name, or one consistent trading name | Using a short name on one listing and the full name on another |
| Address | Full postal address, unit details included, postcode with a space | Postcode written as SW1A1AA on some listings |
| Phone | One primary number in a single format | Campaign tracking numbers that change every month |
| Website | The live https URL, with or without www, used everywhere | Mixing the http and https versions |
| Opening hours | Standard hours plus a note on bank holidays | Seasonal hours left live all year |
| Categories | One primary category agreed with the profile | Different primary categories across sources |
Which sources to check first
Not every source deserves the same effort. Work down this order so the listings that carry the most weight are corrected first.
| Source | Why it matters | When to check |
|---|---|---|
| Google Business Profile | Feeds Maps and is often the first result a customer sees | Every quarter |
| Companies House | Confirms the registered name and office for a limited company | After any name or address change |
| Core UK directories | High-traffic sources that customers still use | Every three to six months |
| Trade and sector bodies | Membership listings that carry local authority | At annual renewal |
| Data aggregators | Push corrections on to smaller directories | One month after a change |
Data aggregators feed many smaller directories, so a correction there can ripple out over the following weeks. Check back after a month rather than assuming the change landed immediately.
Run the cleanup in six steps
- Freeze the record. Save a dated copy and stop editing it mid-project, so you can show what changed and when.
- Pull a live list. Search the business name and postcode, then check the main UK directories and any trade bodies that list you.
- Score each listing as correct, cosmetic or wrong. Cosmetic means formatting only; wrong means a different address, a dead number or a closed profile.
- Claim and correct, working from the highest-traffic sources down. Most UK directories let you claim a listing; some ask for proof of trading address.
- Merge duplicates. Two live records for one business are worse than an untidy one, so ask the platform to merge or close them.
- Log the change and set the next check. Three to six months is a sensible cycle for most single-location firms.
Once the first pass is done, a broader look at local citation building will show which UK sources are worth keeping on your list.
Handle personal data and misleading claims
Your log may hold personal data, such as a sole trader's home address or a named contact at a branch. Keep only what you need, store it securely, and follow the ICO's UK GDPR guidance for lawful handling.
A listing with a wrong address or a disconnected number can mislead customers. The CAP code on misleading advertising applies to listings as marketing communications, so accuracy is a compliance point as well as a ranking one.
Common questions
How often should I check NAP consistency?
Review the sources you control every three to six months, and sooner if you move premises, change number or rebrand. Bulk directory edits are the usual trigger for drift.
Can I fix citations myself without an agency?
Yes, for a single location. A spreadsheet, a browser and a few hours per source are enough. Agencies earn their fee when there are many sites or several hundred listings.
Does a virtual office address break NAP consistency?
Not on its own. It breaks when one listing shows the virtual address and another shows a trading address. Pick one and apply it everywhere.
What if a directory will not let me change a listing?
Ask the platform directly, or through the data aggregator that supplies it. Keep the reply in your log so the next check does not repeat the same request.