Matching Business Listings Can Still Be Wrong

By Melinda Starbird — October 12, 2026

Imagine a contractor changes phone numbers. The website is updated, but an older directory keeps the previous number. Other sites import that directory’s records. Months later, several listings agree with each other, and all of them send the customer to the wrong place.

Agreement looks reassuring until you ask where it came from.

Small businesses hear a great deal about keeping their name, address, and phone number consistent. Often shortened to NAP, those details matter. But an identity record needs more than matching text, and consistency needs more than a count of websites repeating it.

Follow the information back to its source

Corroboration means looking for supporting evidence with enough independence to add confidence. Several directories copying one supplier should not be treated as several independent confirmations.

The W3C’s work on provenance provides a useful foundation. It describes recording the people, activities, and entities involved in producing information so that its quality and reliability can be assessed. In ordinary business terms, that means keeping track of where a fact came from and what happened to it along the way. [1]

My recommendation for a business record is to retain the source, the date checked, and the scope of the check. A business owner should be able to see why a phone number was accepted and which conflicting record still needs attention.

A disagreement can be useful. The older listing may be obsolete. It may also describe a branch, a booking office, or a service that has a separate number. Automatically forcing everything to match can erase information customers need.

The email and the service description count too

Picture a customer who finds the right business name and address, then receives a booking instruction from an unfamiliar email address. Perhaps it is a legitimate booking provider. Perhaps it is an old account. The record should explain that relationship rather than leaving the customer to guess.

Services create another kind of conflict. A homepage might advertise residential and commercial work while a recently updated service page says the company now accepts commercial projects only. Matching contact details will not resolve that contradiction.

Schema.org includes a property called sameAs for linking to a reference page that unambiguously identifies the same entity. That is a way to express an identity relationship; the presence of the link does not independently prove the relationship is true. [2]

This is why the checking has to happen before the label becomes reassuring.

Be precise about what verified means

Checking that a website and public contact details belong together does not establish who is authorized to edit a profile. Confirming control of a domain does not certify workmanship, licensing, or every statement on the site.

A useful verification label should tell a business owner what was checked. A useful ownership process should establish authority to manage the record. Those checks serve different purposes and may require different evidence.

For a business owner, the first pass can be fairly modest. Choose the records that customers actually use. Compare the contact information, website links, service descriptions, and booking destination. Keep a note of each conflict and the source that supports the correction. Give someone responsibility for following through.

That last step matters. A spreadsheet of discrepancies is helpful only if the corrections reach the places where customers encounter them.

MiddleVerse’s business identity approach puts that evidence behind the record. The standard I want us to work toward is simple to describe: an owner should be able to understand the accepted facts, the unresolved questions, and the reason for each distinction.

If several websites agree about your business, check whether they have several reasons to agree.

Sources [1] W3C, PROV Overview https://www.w3.org/TR/prov-overview/

[2] Schema.org, LocalBusiness and sameAs https://schema.org/LocalBusiness