You can check NAP consistency without a large software budget by comparing your business's name, address and phone number across your website, public listings and existing citations. Keep the evidence in a simple spreadsheet, investigate differences, and confirm that corrections appear where customers can actually see them.
The eight checks below separate wrong business facts from harmless presentation differences, private-address policies and intentional phone routing. A manual audit takes your time and covers only the sources you inspect; it cannot certify that every mention on the web is correct. It also cannot promise higher rankings. Google's local ranking guidance describes several considerations, including relevance, distance and prominence.
Before checking, define the right record for each location
Write down the facts you intend customers to use. Verify them with the business owner or location manager instead of copying a listing that may already be wrong.
| Field | What the reference record should establish |
|---|---|
| Business name | The name customers know from the real business, without invented keywords or location additions. |
| Location | The correct branch address and unit, or the appropriate public service-area information. |
| Phone | The current business-controlled number and the location or team it should reach. |
| Website | The correct business or branch page. |
| Exceptions | Approved address hiding, alternate phone routing and platform-specific presentation. |
Google's business representation guidelines require the real-world business name. That does not mean automatically adding a corporate legal suffix to every public listing.
Keep one reference per genuine branch. A Washington branch and a Alexandria branch can correctly have different addresses and phone numbers; comparing both against head-office details would manufacture errors.
For a business that visits customers and does not receive them at its address, Google's service-area guidance says to remove the address from the Business Profile. Record that exception without putting a private home address in a publicly shared audit sheet. Consistency should preserve accurate, appropriate disclosure.
1. Inspect the NAP visitors can read on your website
Open your homepage, contact page and each real location page. Compare their visible business details with the reference record. Include repeated areas such as the header, footer, appointment panel and mobile navigation.
Look for stale content outside the main contact block. An old telephone number may survive in a service page, a downloadable brochure or an image even after the footer changes. Record the specific page and field so the person making the correction can find it.
A useful evidence row says “Alexandria service page still shows Washington phone,” rather than “website NAP inconsistent.” For a multi-location business, the correct number depends on the page's purpose.
Check the mobile version too: it may use a separate contact panel or hide the full address behind a menu. Inspect what customers can read without assuming that a desktop footer proves every view is current. The local website SEO guide covers the broader location-page work.
Record page URL, observed text, intended location, mismatch and date checked. Capture the visible facts here; the next check examines structured data, and check seven examines what contact links actually do.
2. Compare structured data with the visible business facts
A page can display the right number while its structured data still describes an old office. Inspect the business data separately from the visible contact block.
In page source, search for LocalBusiness, a relevant subtype such as Dentist, and properties including name, address and telephone. JSON-LD commonly appears in a script marked application/ld+json. If a plugin inserts markup after the page loads, inspect the rendered page's elements or ask the person maintaining the site to identify the generated business record.
Compare the relevant entity with the same branch's visible information. On a page with multiple entities, do not mistake a publisher's organization details for the local branch being audited. Note the script or plugin responsible when you can identify it.
Google's LocalBusiness documentation explains the supported properties and examples. A validator can help find syntax or eligibility issues, but it cannot establish whether the phone reaches your business or the address is current.
Do not publish a hidden residential address just to fill a field or make a checker pass. Record the privacy and service-area exception, and review the implementation against the applicable requirements.
Record page URL, entity or branch, property, current value and required factual correction.
3. Compare public listings with your managed profiles
Open the public Google Search or Maps listing for the correct business. Read the name, address or service area, phone and website destination. Then compare that view with the information and edit status in the account you use to manage it.
This checks a different problem from an incorrect form entry: a saved correction may not yet be public. Google's edit-status guidance distinguishes accepted, pending and not-approved changes. Keep those states separate in your audit.
Repeat the public-versus-managed comparison for relevant listings you already maintain, such as Apple Maps, Bing Places, Yelp or a business social profile. This is a targeted check of known records, not a requirement to create an account everywhere.
For each source, save the listing's direct URL and the date you checked it. A screenshot helps when a displayed value differs from the editor, but keep customer or account information out of shared evidence.
An omitted address is not automatically an error for a service-area business. Similarly, a platform may display an address in its own layout. Check the underlying location before requesting cosmetic changes. Use the Business Profile optimization guide if eligibility or profile setup needs attention.
Record public value, managed value, current edit status and the action still needed. “Submitted” is not the same as “publicly verified.”
4. Search current and retired business details
Use search to discover references you did not know about. Search the current business name with its city, then search an old name, retired telephone number and former street address separately. Old identifiers are useful because a stale listing may not mention the current name at all.
These are fictional examples; replace every business detail with your own:
"Example Bicycle Repair" "Washington"
"Example Cycle Workshop" "Washington"
"202-555-0147"
"2025550147"
"12 Example Road" "Example Bicycle Repair"
site:yelp.com "Example Bicycle Repair"
Google documents quoted phrases and site-specific searches. Try the number's common display variations rather than assuming one quoted format will find every occurrence.
Open each relevant result and inspect the actual page. A snippet can contain old text or refer to a different business. Record the current page value, its URL and whether the source is under your control. If a result mixes two businesses, investigate the identity before requesting an edit.
Treat the search results as leads. Google's site-operator documentation says the returned list is not necessarily exhaustive. No results for a query does not prove that an old listing has disappeared.
Record the discovery query, live source URL, observed fact and the current or retired identifier that found it.
5. Look for duplicate records of the same business
Search Maps and relevant directories for the business name, address and former name. Compare the actual records, not just the number of search results: two results may point to one listing, while two different listing URLs may represent separate records.
For each suspected pair, ask:
- Do both represent the same real business and location?
- Is one an outdated record from a move or rebrand?
- Is the second an eligible branch, department or individual practitioner?
- Which record is managed by the business, and which needs an ownership request?
Record the two URLs and the evidence supporting your answer. Do not remove another legitimate business just because it shares your street address or building.
Google's duplicate-profile guidance distinguishes ownership problems, genuine duplicates and separate eligible businesses at the same address. It also says to update the existing profile when a business moves rather than create a new one for the new address.
A wrong phone number on a duplicate is more than a formatting issue: correcting your main profile may leave the other record unchanged. Use the platform's ownership or duplicate-resolution route for the specific record, and verify the outcome afterward. Do not treat removing a profile from an account as proof that every public reference is gone.
Record suspected duplicate URL, matching business identity, ownership status and the resolution route.
6. Read local and industry publications directly
Some business details live in a chamber member directory, trade-association profile, supplier locator, local event program or downloadable PDF. These publications may be maintained by somebody outside your business, and a profile-management dashboard will not prove they are accurate.
Start with organizations you already belong to and partners that already refer customers. Follow their member, partner or stockist links directly. If you have a record of referral sources, use it to identify pages worth checking rather than buying a large list of unrelated directories.
On each page or document, inspect the business name, location, phone and linked destination. Confirm that you are reading the current edition. An archived event brochure is a different correction problem from the active member profile customers use today.
A targeted search can help locate documents:
site:association.example "Example Bicycle Repair"
"Example Bicycle Repair" filetype:pdf
The domain and business are placeholders. Open the organization's live site as well, because search discovery is incomplete.
Record who controls the source: your account, an association administrator or a supplier's listing team. Request a correction to the precise page or file rather than asking for a new listing. The local link-building guide covers relevant partnerships; this check is about repairing facts in existing references.
Record publication URL or file edition, wrong field, source owner and correction contact.
7. Check where phone numbers and contact links lead
Matching digits do not establish that a customer can reach the correct business. Check the contact path as well as the text.
| Check | What to confirm |
|---|---|
| Displayed phone | The number belongs to the intended business or branch. |
| Tap-to-call link | The link's tel: destination agrees with the intended call route. |
| Approved test call | The call reaches the expected location or team. |
| Website or booking link | The destination serves the business or branch named in the listing. |
For example, a mobile button can display the current phone number while retaining an old number in its link. Inspect the link destination or ask the site maintainer to check it, then make an agreed test call during suitable business hours. Avoid unnecessary calls to a retired number that may now belong to somebody else.
Google's phone guidelines require a number under the business's direct control and contact information that represents the actual business. Do not turn that into a blanket ban on every tracking number. If intentional routing exists, confirm its purpose and destination with the person responsible before changing it.
Check a phone mismatch at the branch level: a central reception line may be deliberate, while a disconnected line or a different company's voicemail needs urgent attention.
Record displayed number, link target, confirmed destination, intentional exception and any failed contact path.
8. Flag differences in a field-level audit sheet
Put one source, location and field on each row. This lets you compare many observations without hiding a wrong phone number behind a general “listing complete” status.
Copy this CSV into a spreadsheet. The business and URLs are fictional; the blank observed values mean the checks have not been done.
location_id,source_url,field,expected_value,observed_value,text_check,decision,action,last_checked
branch_01,https://example.com/contact/,phone,+12025550147,,not_checked,unreviewed,,
branch_01,https://directory.example/business/example/,name,Example Bicycle Repair,,not_checked,unreviewed,,
branch_01,https://example.com/contact/,public_address,[hidden by policy],,not_checked,unreviewed,,
Keep the expected and observed value columns, D and E, formatted as plain text so phone numbers retain leading zeros and country-code plus signs. Check the imported values against your original record. After entering your own values, put this formula in F2 and fill it down:
=IF(OR(D2="",E2=""),"not_checked",IF(EXACT(D2,E2),"text_match","review"))
In Google Sheets, EXACT checks identical characters, including case and spaces. The formula uses English function names and comma separators; adjust separators if your spreadsheet locale requires them.
Keep the formula result separate from the decision. A text_match proves only that the two entered strings agree. It does not prove that either value is correct, that a phone call works, or that a private address should be public. A review flag is not a Google ranking penalty.
| Difference | Human review |
|---|---|
| “Street” versus “St” | Check that both identify the same real address; record an accepted presentation difference if appropriate. |
| Unit 4 versus Unit 9 | Verify the correct premises; do not normalize away a meaningful difference. |
| Different phone numbers | Establish whether this is wrong routing or an approved business-controlled alternative. |
| Hidden public address | Confirm the business model and platform policy; record the exception without exposing the private address. |
Leave unavailable observations blank and retain not_checked. For policy-based omission, use an explicit marker such as [hidden by policy] only after confirming the public state. Record dates as observations are made, then assign a decision such as confirmed correct, correction needed or accepted exception.
Prioritize corrections and verify the public result
Start with errors that can send a customer to the wrong business or prevent contact. Use this as an operational priority order, not a ranking formula:
| Priority | Typical finding | Next action |
|---|---|---|
| Urgent | Wrong business, disconnected phone, incorrect customer-facing location | Confirm the intended facts and correct the relevant source or request ownership. |
| Important | Conflicting branch details, stale schema, duplicate record | Identify the record owner and fix the specific entity or field. |
| Lower urgency | Equivalent address formatting or cosmetic spacing | Confirm that the meaning is unchanged and document the accepted difference. |
For sources you manage, update the verified facts. For third-party publications, send the source owner the exact page, wrong value and replacement. Keep the request or submission date in the action log. If a record cannot be changed immediately, preserve its evidence and unresolved state.
Reopen the actual public page after a correction. Check the relevant field and contact destination again; do not close the issue solely because an editor accepted the form submission. On Google, distinguish pending, accepted and not-approved edits, and investigate unexpected updates rather than repeatedly resubmitting the same change.
Repeat the affected checks after a move, rebrand, phone change or website-template update. Set a review interval that fits how often your business details change; no universal monthly or quarterly schedule proves accuracy.
Your finished record should identify what was checked, what is still unavailable, which differences are legitimate and which corrections are publicly verified. That is a useful low-budget NAP audit even when it cannot discover every citation or attribute a ranking change to the work.