Checking stable entity identifiers across service pages

Build an identifier map across service pages before changing entity identifiers. The purpose is to see whether references that intend to describe the same organization actually do so, while preserving real distinctions between businesses, locations, and pages.

Define the entities first

List the real things the site intends to represent. An organization, a location, and an individual service page may need to remain distinct in the implementation. Do not decide identity from similar spelling alone. Ask for the approved business relationship when two names or addresses appear to conflict. This review method is a practical way to organize evidence, not a claim that Google mandates a particular identifier pattern.

Collect references from several pages

Inspect a small, purposeful selection of service pages and record the identifiers used for the organization and related references. Include the component or publishing source if known. Compare the associated names and details, not just the identifier strings. Google requires structured data to be accurate and represent visible content, so a consistent identifier attached to conflicting facts still needs investigation.

  • Page URL and page version.
  • Entity identifier and represented organization or location.
  • Names and contact details attached to that identifier.
  • Other identifiers the block references.

Separate accidental drift from real distinction

A changed spelling in an identifier may reflect a template edit rather than a new business. Conversely, two actual locations should not be collapsed simply to reduce the number of identifiers. Write the intended relationship beside each mismatch. Choose a correction only after that relationship is understood, then identify the source that must change so future service pages follow the same decision.

Verify the reference map again

After an edit, revisit the affected pages and confirm their representations agree with the documented identity map. Check that a consolidation did not leave unrelated details attached to the surviving entity. Keep a list of pages not reviewed rather than implying whole-site coverage. Stable, accurate references are the maintenance outcome; rich-result display remains unguaranteed. Use /website-analyzer/ to continue the wider audit.

Source guidance

Use the website analyzer to collect a starting set of observations, then verify the specific evidence described above.

Frequently Asked Questions

Should every page use one identifier for everything?

No. First establish what each reference represents. Shared organization references and distinct page or location identities serve different purposes.

Does an identifier mismatch prove search harm?

No. It identifies a representation to investigate. Record the inconsistency and its correction without inventing a ranking or display consequence.

Want to be found and recommended in AI search?

Start with a free scan of where you stand, then book a call and we'll map the highest-ROI AI plays for your business.

Book a Free Call →