NAP consistency. The unsexy foundation that makes everything else work.

What NAP consistency is

NAP stands for Name, Address and Phone: the three details Google uses to identify a business across the web. NAP consistency means those three details appear identically wherever the business is listed: your website footer, your contact page, your Google Business Profile, your schema markup, every directory, every social profile.

The point is simple. When the same NAP appears on twelve different places, Google reads them as twelve corroborating mentions of one business. When the details differ subtly, Google reads them as multiple half-confirmed entities competing for the same business identity. The first scenario produces a strong, single business entity. The second produces a weak, fragmented one.

For the wider context, the Local SEO pillar covers where NAP consistency sits in the trust stack. For the citation-building side of the same work, the Australian citations chapter goes deeper.

Why partial matches kill local rankings

The local-pack algorithm relies on entity consolidation. Google sees a business listed on Yellow Pages, True Local, Hotfrog, the business's own website and a Google Business Profile. If all five list "Acme Plumbing, 3 Loftus St, West Leederville WA 6007, (08) 9123 4567", Google consolidates them into one strong entity with five corroborating citations.

If those five sources list "Acme Plumbing", "Acme Plumbing Perth", "Acme Plumbing Pty Ltd", "ACME Plumbing" and "Acme Plumbing & Gas", with three different address formats and two phone variants, the consolidation fails. Google ends up with several partial entities, each with weaker support. The local-pack ranking is built on the strongest consolidated entity, and the strongest consolidated entity is now weaker than it should be.

The practical impact: a Perth client we audited last year had thirty-two directory listings with seventeen different name variants and four address formats. After two weeks of cleanup (no other changes), map-pack visibility lifted across the top ten target keywords inside the next month. The links and reviews were already there; the consolidation just needed to happen.

NAP matching also touches Google's broader entity recognition, which feeds the knowledge panel, AI Overview citations and brand-mention signals. See brand mentions as a ranking signal for how NAP-matched mentions feed the entity layer, and link attributes explained for how directory links interact with the citation layer.

The five-step NAP audit

The audit is straightforward but tedious. Spreadsheet, two hours, every listing logged.

1. Search the business name in Google. Check the first three pages. Note every listing that surfaces: directories, social profiles, third-party review sites, supplier mentions. One row per listing in the spreadsheet.
2. Record the exact NAP on each listing. Copy and paste, do not retype. Subtle variations matter (Hwy versus Highway, dashes versus brackets in the phone number, Pty Ltd versus no Pty Ltd in the name).
3. Compare each listing to the canonical NAP. Flag any mismatch in a "needs update" column. Common mismatches: outdated suite numbers after an office move, old phone numbers from a previous business line, trading name variants that drifted over time.
4. Prioritise the cleanup. Google Business Profile and the top ten Australian directories first. Industry-specific directories next. Social profiles and the long tail of low-quality directories last.
5. Update each listing. Two-week deadline. Log the date of each update in the spreadsheet. Some directories require email verification or a wait for the next moderation pass; track those separately.

Re-audit every quarter to catch drift. Drift is real: phone systems change, suite numbers get renumbered, the business adds a Pty Ltd suffix that takes six months to propagate.

Picking the canonical format

Before the audit, lock the canonical NAP format. Three decisions to make:

• The business name. "Acme Plumbing", "Acme Plumbing Perth", "Acme Plumbing Pty Ltd" or "Acme Plumbing & Gas". Pick one. Use it everywhere including legal documents, invoicing, and the website footer. The name on Google Business Profile must match the legally-trading name; do not add suburbs or keywords to game the algorithm. Google strips violations.
• The address. "3 Loftus St, West Leederville WA 6007" or "3 Loftus Street, West Leederville WA 6007" or "Unit 3, 145 Stirling Hwy, Nedlands WA 6009". Pick one format for the street type (St vs Street), one format for the unit prefix (Unit vs Suite vs slash notation), one canonical postcode.
• The phone. "(08) 9123 4567", "08 9123 4567", "+61 8 9123 4567" or "0435 462 205". Pick one format. Pick a number you actually answer; do not list a tracking number that drops calls into voicemail.

The format choice itself does not matter to Google. What matters is that the same format appears on every single property. Write it down. Pin it to the office wall. The format is the canonical reference, and any deviation is a NAP audit failure.

For the schema-markup side of NAP consistency, the LocalBusiness schema fields on your website must use the same canonical format. See the canonical tags chapter for the broader canonicalisation principle (same idea, different layer of the stack).

Tracking numbers and call attribution

Many businesses want to track which marketing channel drives which call. The instinct is to replace the website phone number with a tracking number. That choice creates a permanent NAP mismatch between the website and every directory listing, which costs more in lost rankings than the tracking data is usually worth.

Three better options:

• Dynamic number insertion (DNI). Swap the displayed number only for paid-traffic visitors (Google Ads, Facebook Ads). Organic, direct and referral visitors see the real, consistent number. Most modern call-tracking platforms support DNI by default.
• Channel-specific tracking numbers in ads only. Use tracking numbers in paid ads, billboards, and printed material. Never on the website or directory listings. The data you lose is small; the NAP consistency you keep is large.
• Skip call tracking altogether for small businesses. Ask "how did you hear about us?" at the start of every call. The data is messier but it does not cost you map-pack rankings.

For the broader measurement context, see attribution and SEO in the Measurement pillar (when it ships), and the GA4 glossary entry for the analytics side.

Common mistakes

Perth and WA context

Three things worth knowing about NAP consistency for Perth and WA businesses.

First, postcode confusion is common in WA because some suburb boundaries straddle postcodes. West Leederville (6007), Mount Hawthorn (6016) and Leederville (6007) all share parts of the same precinct. Pick the postcode that Australia Post actually delivers to and stick to it across every listing.

Second, regional WA businesses often have NAP issues caused by FIFO arrangements: a head office in Perth, an operations base in Karratha or Port Hedland, and a P&O box for postal. Pick one canonical address (usually the operations base for service-area businesses) and use it everywhere. See SEO Karratha, SEO Port Hedland and SEO Kalgoorlie for the regional-context service pages, and the multi-location strategy chapter for how to handle this properly.

Third, Perth metro businesses with multiple service areas (south-of-the-river plus north-of-the-river) sometimes try to list two addresses on one Profile. That violates the single-address policy and risks a suspension. The correct setup is one Profile per genuine physical location, or a service-area Profile with hidden address. See SEO Fremantle, SEO Cockburn, SEO Mandurah, SEO Rockingham, SEO Joondalup, SEO Bunbury and Services Perth for the metro-area service patterns, plus the service-area business chapter for hidden-address setup.

For the Perth-specific local service we run for clients, see Local SEO Perth. For industry-specific NAP nuances, the trades SEO and legal SEO guides have category notes.