Short answer: a local business can have a consistent name, address and profiles and still not appear in certain AI responses. Identity is only one of the conditions of the information system. Google documents LocalBusiness structured data and Search mechanisms, but does not publish a universal entity salience score for local businesses. In the diagnosis, identity, relevance, location fit, freshness, crawlability and external evidence must be separated.

Cause 1: The location is ambiguous

The brand can have several offices, and the query does not specify the city or area. If profiles and pages do not clearly differentiate locations, the problem is local identity resolution.

Check the location name, URL, address and specific services.

Cause 2: Local page is almost duplicated

A page that only changes the name of the city does not bring information gain. Multiple repetitive URLs do not make the brand a more relevant entity.

Localization must change real data: program, team, access, services or coverage area.

Cause 3: the service is not described first-party

Reviews may mention the service, but the site doesn't explain it. Before "salience", check for a clear and current canonical page.

Cause 4: the program is stale

An entity may be correctly identified, but the program or phone may be old in an external directory. This is freshness, not lack of entity salience.

Cause 5: The category is wrong

External profiles may use different categories than the actual service. This conflict can change the relevance for local queries.

Prioritize profiles actually used by customers.

Cause 6: the query does not have a geographic fit

A business can be very clearly identified and yet not relevant for a user located in another area or for a query with a different geographic intent.

Do not diagnose identity when the problem is location relevance.

Cause 7: The page is hard to crawl

Noindex, wrong canonical, status code or weak links can prevent discovery. Solve the technical before interpretations about authority.

Reason 8: reviews are about the experience, not the offer

A good rating for friendliness does not prove that the business offers a specific service. Facts and opinions must be separated.

Cause 9: third-party sources contradict each other

One directory may list an old address, another an old schedule. Identity quality should be evaluated on critical profiles, not by the total number of mentions.

Cause 10: the site does not have intent ownership

Multiple pages can answer the same service question. Consolidation and internal linking can be more important than entity work.

Cause 11: AI response is volatile

A single output is not diagnostic. Repeats a query set and measures factual accuracy, naming consistency and displayed sources.

Cause 12: The tool uses a proprietary score

If a vendor says "salience 36," ask for the formula, sources, period, and denominator. Do not present proprietary metrics such as Google or AI provider metrics.

Decision tree

  1. Does the location have canonical URL and stable data?
  2. Does the local page have information gain?
  3. Are the services described first-party?
  4. Are the schedule/contact current?
  5. Is the category consistent across critical profiles?
  6. Is the query geographically appropriate?
  7. Is the page crawlable/indexable?
  8. Are reviews mapped to the correct location?
  9. Are critical external profiles consistent?
  10. Intent ownership is clear?
  11. Does the problem appear repeatedly in the query set?
  12. Does the score used have a transparent methodology?

If the top ten have findings, you don't need an abstract explanation of salience.

The more useful metrics

Watch:

  • location identity conflict rate;
  • freshness profiles;
  • service coverage;
  • wrong-category count;
  • factual accuracy;
  • location-specific citation rate;
  • time-to-resolution.

Each can produce a specific task.

Prioritization

P0: Wrong address, phone or critical service. P1: important category/profiles and canonical conflict. P2: subdirectories. P3: cosmetic differences.

Do not repair P3 while P0 remains open.

How to check progress

After the fixes, it runs the same array on the same locations and the same query set. If first-party quality increases, you have a direct result. If the external outputs also change, treat the change as additional evidence, not as automatic evidence of causality.

How do you tell a real local conflict from a legitimate variance

A business may use a central call center but different physical locations. May have seasonal hours or services not available in all areas. The audit should record these differences as rules, not as automatic errors.

Build a registry per location with public name, address, phone, schedule, services, and canonical URL. It then only compares sources that should reflect the same location.

Prioritization of findings

A wrong address or an old program takes precedence over a minor name variation. Use decision impact and remediation capability as severity, not number of occurrences.

If an external source cannot be fixed, mark `external unresolved' and keep first-party clear.

Stop condition

If the first-party data is consistent, the critical profiles have an owner and the monitored responses no longer repeat the identified conflicts, move the case to monitoring. Don't keep auditing just to increase a proprietary score.

Claim ledger

  • FACT/EVIDENCE: Google documents LocalBusiness structured data for local business information.
  • PRACTITIONER GUIDANCE: identity, geography, freshness and relevance must be diagnosed separately.
  • INFERENCE: local consistency can reduce ambiguity in automatically consumed sources.
  • NOT PROVEN: a universal entity salience score for local search or AI answers.

Conclusion

Entity salience is rarely the only explanation for local visibility. A good diagnosis shows whether the problem is location identity, geographic relevance, stale data, reviews, crawlability or ownership. The "salience" tag should disappear from the backlog after the concrete cause is known.

Sources reviewed

Related insights