NAP Consistency Checker
Extracts the business name, phone number and street address from the pages you list and compares them. In local SEO, inconsistent NAP data pushes you down the map pack.
- Sign-in requiredMembership is free
- Open on the Pro plan100 runs a day
- Saved to your historyReachable from your account
What does this tool look at?
The business-data consistency and local markup you need to show up on maps and in “near me” searches.
- Phone and address details pulled from each page
- Format differences normalised before comparing
- LocalBusiness schema consistency verified
- Inconsistent pages listed one by one
What this tool measures
NAP stands for name, address and phone. When Google ranks a business on maps, it checks whether those three match across sources. If the contact page shows one number, the footer another and a directory listing an old one, the signal weakens and the ranking follows.
The tool fetches up to five pages, extracts phone numbers from visible text and tel: links, then reads the business name, phone and street address out of JSON-LD. Numbers are normalised before comparison, so 0546 215 34 72 and +90 546 215 34 72 count as the same line.
Ignoring formatting differences matters, because the real problem is not how a number is typed but genuinely different numbers. One page holding the retired line while another holds the new one leaves Google unable to decide which is right.
How to use it
- 1
Choose the pages to compare
Contact, about, branch pages and the homepage. Five addresses are processed per run, so pick the pages that actually carry the information, not blog posts.
- 2
Enter the correct number
The phone field is optional. Filling it compares every number found against yours and names each page that disagrees.
- 3
Find and fix the inconsistent page
The table lines up each page's detected number, schema name and schema address. Once you find the odd cell, fix the template or component that produces it rather than the single page.
- 4
Match your Google Business Profile
Even when the site agrees with itself, it must agree letter for letter with the profile listing. Even an abbreviation versus its full form makes matching harder.
- 5
Review external sources too
Directories, social profiles and map listings should carry the same NAP. This tool audits your own pages; external sources still need a manual pass.
When to use it
- After changing a phone number or moving office, to find where the old details survive.
- When map results underperform, to rule out the technical causes first.
- In a multi-branch business, to confirm each branch page carries its own details.
- After a site launch, to check the contact details migrated correctly.
Reading the result
Two different numbers found
This warns. Often one is a landline and one a mobile, which can be legitimate. Even so, picking a single primary number and using it everywhere beats spreading two.
Three or more numbers
This fails. At that point an old number has almost certainly survived somewhere, or department numbers are being presented as the business number. Trace and consolidate them.
A page with no phone number
Pages where no number appears raise a warning. Putting the number only inside an image, or in a component rendered later by JavaScript, hides it from crawlers and from this audit alike.
Differing street addresses
Different streetAddress values across schemas fail the check. For a multi-branch business that is expected; for a single location it is a copy-paste error.
No LocalBusiness schema
Finding no business schema anywhere fails. Visible text satisfies humans, not machines. Generate the block with the LocalBusiness Schema Generator and add it to your contact page.
Questions about the NAP Consistency Checker
Five per run. Run it again for more. Five covers most businesses: contact, about, homepage and two branch pages already hold all the details.
Not for matching. The tool normalises formats before comparing and Google does the same. Still, one consistent format serves the user copying it and the visitor tapping it on a phone.
Visible addresses are often split across design elements, and a machine cannot tell which fragment is the street and which the district. JSON-LD states that explicitly, so the comparison is made there.
In local results, yes. Google confirms a business exists by seeing the same details across sources. Contradictory records weaken that confirmation and make the map pack harder to reach.
Use it alongside these
The other tools in the same category. Run them together and you see the whole picture.
The tool found the problem. Now for the fix
We run technical SEO, content and AI visibility work end to end. Let us review your site and come back with a clear list of what to do.
Monday – Saturday 09:00 – 18:00