Make the business behind the pages unambiguous

Create a small identity record

Most inconsistency is accidental. The legal name, the trading name, the short name used in conversation, an old logo and two phone numbers all drift into different places over the years. Fix it at the source with one short document that every other place is copied from. Keep it in a shared location, give it an owner and update it first when anything changes.

Audit the places that describe you

A business is described in more places than its own site. List them, then check each against the identity record. The goal is not a perfect match on every directory. It is to catch the contradictions that would make a person, or a machine summarizing the web, unsure which facts are current.

Google’s rules for business profiles make the same demand in one place: represent the business as it is consistently represented and recognized in the real world, across signage, stationery and other branding. The name must reflect the real-world name as used on the storefront, website and stationery, and adding unnecessary information, such as keywords, can lead to suspension.^[1] Treat that as a general principle, not only a rule for one platform.

Describe the organization accurately

Markup is the machine-readable version of your identity record. Google lists no required properties for Organization structured data, and recommends fields such as name, alternate name, URL, logo and sameAs links to profiles elsewhere, plus identifiers such as vatID and iso6523Code, which help distinguish an organization from others with similar names.^[2] The organization name should match the name you use for your site name.^[2] Place the markup on your home page or an About page.

Google’s site name system is separate. It generates the name shown with your results from your home page and references to it on the web, and it considers WebSite structured data most important if you want to state a preference, alongside og:site_name, the title element and headings. It advises choosing a unique name that accurately reflects the identity of the site.^[3] You can supply an alternative or short name with alternateName.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "WebSite",
  "name": "Northside Physio",
  "alternateName": "Northside",
  "url": "https://example.com/"
}
</script>

Keep the markup honest and boring. It should repeat what the visible page says and nothing more; the structured data chapter covers the validation steps.

Give a reader a verification route

Google’s rater guidelines suggest three places to look when judging whether a business is trustworthy: what the site says about itself, starting with its About page; what others say, such as independent reviews, references and news; and what is visible on the page.^[4] A prospective customer does the same thing. Build an About page that holds up to that check: who runs the business, where it is, how to reach a person, what it is registered as and how long it has operated. Link to the profiles that confirm it, and to the author pages for your writers. Do not invent anything; a short honest page is better than an impressive one that cannot be verified.

Resist shortcuts for the second source. Google’s guide to generative AI search says that seeking inauthentic mentions across the web is not as helpful as it might seem.^[5] Earned, accurate mentions come from doing and publishing work that others reference. You can make them easy to find by linking to your own best evidence from your About page, and by correcting factual errors where they appear.

Observe external summaries without overclaiming

Ask a few AI services plain questions about your business: who are you, what do you offer, where are you based and who runs the company. Record the answers with the date and the service, and compare them with the identity record. Differences have usually one of three causes: an old fact repeated on a directory, a similarly named business or an ambiguity on your own pages. Find where the wrong fact appears, fix it at the source and note the change.

Do not expect a quick or guaranteed update. Systems refresh their data on their own schedules, and some answers come from sources you cannot edit. Do not describe an inconsistency you saw once as a pattern. If a similarly named business is causing confusion, the identifiers in your markup, a clear description and links from authoritative profiles are the tools you have. The citation audit chapter gives a method for repeated observation.

Plan for a rebrand

A rename is the moment when identity drifts. Make a checklist from the identity record. Update the site and its markup, redirect old URLs, change profiles and business listings, ask partners and directories to update, and correct press mentions that are likely to be repeated. Keep the old name as an alternate name for a time, since people and some sources will keep using it, and avoid presenting two names as two organizations. Record the date of the change in your correction log so later discrepancies can be traced.

Apply it to your website

• One identity record holds the names, description, contact details, identifiers, logo and official profiles.
• Your website, markup, business profile and social profiles all match the record.
• Directories and partner pages with old facts are listed, and corrections have been requested.
• Organization and WebSite markup state the same name, with URL, logo and sameAs links to your official profiles.
• An About page explains who runs the business, where it is and how to verify it, with no invented claims.
• You periodically ask AI services what they say about you, and record the differences with their dates.
• A rebrand checklist exists, and the previous name is kept as an alternate for a transition period.