Your Citation Audit Can Be Green While the Wrong Address Is Everywhere

A citation audit can report perfect consistency while every source repeats the wrong address. It can also flag a legitimate service-area setup because one source hides a private operating base while another displays the same address in a proper legal context. The tool detects differences between strings. The business needs to know whether those differences create incompatible public instructions.

That distinction changes the entire local SEO workflow. The goal is not to make every record look identical. It is to make separate sources agree about the real business while respecting the job each source performs.

Consistent data can be consistently false

Most citation-cleanup tools compare versions of a business name, address and phone number. That can expose useful discrepancies. It cannot decide which version is true. If ten directories copied an old address from one another, their agreement is not independent verification. It is replication. A majority vote among stale sources does not move the business back to its former premises.

The same problem appears with phone numbers, opening hours, categories and trading names. The most common public version may be obsolete. The company website may be wrong. The Google Business Profile may be wrong. The internal spreadsheet may be wrong. No source earns authority by being convenient. Before comparing anything, create an approved fact record from current business evidence:

• exact legal entity and trading brand;
• branch or service-area scope;
• present operating model: storefront, service-area or hybrid;
• approved customer-facing address treatment;
• controlled telephone and website destination;
• current hours, services and status;
• evidence supporting each fact;
• accountable approver;
• observation date and review trigger.

This becomes the reference because somebody can defend it, not because software found it most often.

Agreement does not require identical characters

Different sources can describe the same business differently without creating a material conflict.

That is why phone punctuation is usually cosmetic while a wrong destination is not. It is also why removing Ltd may be harmless on a customer-facing profile while presenting a registered office as a shop can be dangerous.

A hidden service-area address is not missing data

Google defines a service-area business as one that visits or delivers to customers and does not serve them at the business address. Its service-area guidance tells eligible businesses not serving customers at the address to remove that address from their Business Profile. An audit tool may compare the hidden Profile address with a directory that publishes the operating base and call the pair inconsistent. The correct response is not automatically to reveal the address on Google.

First classify the external record. An official register may show a registered office in a legal context without inviting customers to visit. A trade directory may display the same location beside a map, opening hours and “visit us” language. The characters match; the customer instructions do not. The first source may be a harmless contextual variant. The second may create a material visitability conflict.

This is a useful test for any branding or SEO agency tempted to standardise fields in bulk. A private address is not a formatting token. It describes a place and can direct a person. Publishing it everywhere to improve “NAP consistency” can degrade privacy, customer experience and factual accuracy at the same time.

Put one public fact on trial

Use a Public Fact Agreement Test for one fact on one source. Do not average a whole domain into a consistency percentage.

The state returned is one of four, each with its own next action:

The test is deliberately non-scored. Ninety-nine correct fields cannot cancel one listing that marks a private base as open to customers. One hundred formatting differences do not become material through multiplication.

Split differences before deciding what matters

A single directory record can contain both harmless variation and dangerous error. Keep those propositions separate. Suppose the phone number uses international formatting, the legal name includes Ltd, the address is a former branch and the opening status says Open. A generic score may label the profile 50 per cent consistent. That number tells the repair owner almost nothing. The useful analysis is:

• telephone destination verified; formatting variant harmless;
• legal and trading name relationship verified; contextual variant harmless;
• former address presented as current; material conflict;
• operating status attached to a closed branch; material conflict.

This is sentence-level claim discipline applied to public business data. Each disputed fact gets its own evidence and disposition. Correct fields cannot launder an incorrect one, and an incorrect field cannot turn every other variation into a repair. For customer acquisition, that distinction is practical. A space in a telephone number does not normally lose an enquiry. A number answered by the wrong branch can. A missing comma does not send a customer across town. A stale address can.

Moves and rebrands create two believable presents

Moves, closures, rebrands and phone changes expose weak fact ownership because old and new versions may both look plausible. Time decides whether a difference is historical evidence or a live conflict. A dated announcement saying “we moved from X to Y in June” can correctly retain the former address. A current directory still offering directions to X cannot use history as a defence. Record the date the business fact changed, the date the public source was observed, whether the same entity and operation continued, whether the old fact is clearly time-bounded, and whether the source presents an action in the present tense.

Do not update genuine history merely to make a crawler see uniform strings. That destroys useful provenance. Update live instructions that misrepresent the present. Rebrands need similar care. A new logo or trading name does not automatically create a new legal entity. A familiar name does not prove continuity. Establish the relationship before merging records, changing descriptions or claiming that two profiles belong to one business.

Branches complicate this further. The Public Fact Agreement Test can compare one approved branch fact with one public record. It cannot invent the branch model or decide that a location deserves a separate Google Business Profile. If branch identity and eligibility are unresolved, return an evidence hold.

Google uses wider information, but consistency is not a ranking formula

Google says Business Profile information can come from publicly available web content, licensed third-party data, user contributions, business owners and Google’s own interactions with a place or business (how Google sources business information). That supports maintaining a coherent public business record. It does not prove that a named directory supplies Google, that every citation has equal influence or that changing one listing will propagate elsewhere.

Google’s local ranking guidance describes local results through relevance, distance and prominence and recommends complete, accurate Business Profile information. It does not publish a citation-consistency percentage, a directory quota or a guaranteed ranking gain from fixing third-party records. The defensible case for correcting material public conflicts is already strong. Wrong facts can confuse identity, visitability, contact and operating status. Do not weaken that argument by attaching a ranking promise the evidence cannot carry.

This is a wider lesson for digital marketing: operational truth is valuable before it becomes an attribution event. A corrected phone number can protect a customer route even if no dashboard proves a ranking movement.

Diagnose the conflict without smuggling in the repair

A verified conflict earns entry to a repair workflow. It does not give the diagnostic process authority to edit every source immediately. Package the exact public record and observation date, the observed proposition, the approved proposition and evidence, the material customer or entity conflict, the accountable source and business owners, the access or correction route if known, and the uncertainty and review trigger.

Then route by object. An owned webpage goes to its page owner. A Google Business Profile or directory record goes to the relevant listing owner. An official register follows its formal process. A proposed paid profile requires a separate value decision. A duplicate may require platform-specific resolution rather than field editing. This boundary matters because changing a public record can require evidence, access, platform review and later observation. The diagnosis should not claim success when an edit has merely been submitted. Send the repair owner one proved false instruction, not a hundred red cells with no meaning attached.

Make the audit answer a customer question

Take the next red row and complete four lines:

APPROVED FACT: [what the business can evidence now]
PUBLIC VERSION: [what this source says, where and when]
CUSTOMER MEANING: [what identity, place, service or action changes]
DISPOSITION: [harmless variant / evidence hold / material conflict]

If the only difference is formatting, close it. If the source is unclear, hold it. If the record tells customers to visit a private address, call a dead number or trust an obsolete status, hand off the exact conflict. The result may leave your citation dashboard less green than a bulk-cleanup supplier would prefer. That is acceptable. A green dashboard is not the asset. The asset is a public business record that agrees with reality, gives customers the right instruction and can be defended by the person responsible for it.