Organization Markup and sameAs: Brand Identity

Organization markup is structured data that describes who your organization is: its name, site, logo, contact details and official profiles. The sameAs property is the part that points from your site to other pages about the same organization, such as social or review profiles. Google's documentation says the markup helps it understand administrative details about an organization and tell it apart from others, with some properties working behind the scenes and others influencing visible elements such as the logo shown in results and knowledge panels. Developers and brand managers who maintain this markup have to decide which fields to fill, which profiles to link, and how to keep everything accurate over time. Nothing here guarantees a search feature, and Google's own documents say so.

The wider JSON-LD topic, including Breadcrumb and Article markup, has its own article: see the JSON-LD structured data guide. This page stays narrow on purpose. It covers brand identity: what each field says, what belongs in sameAs, and how to avoid contradictory data.

What the markup can promise, and what it cannot

Expectations decide whether this work is useful, so separate the documented effects from the assumed ones.

What the documentation says

Per Google's Organization structured data documentation (Opens in a new tab), the markup helps Google understand your organization and distinguish it from other organizations in results. Properties such as iso6523Code and naics operate behind the scenes for disambiguation, while others affect which logo appears in results and knowledge panels. For merchants, the page also says the markup can shape the merchant knowledge panel and brand profile, including return policy, address and contact details.

What it does not say

There is no statement that Organization markup improves rankings, and no promise of a knowledge panel. The general structured data guidelines add that structured data enables a feature but does not guarantee it will be shown, even when markup passes testing. The Search Essentials page likewise says meeting requirements does not mean Google will crawl, index or serve a page. Treat the markup as an identity-consistency task rather than a ranking tactic.

When it is worth the effort

The work pays off when your brand is easily confused with similarly named organizations, when your logo appears wrongly in results, when your official profiles are scattered, or when the same brand lives on several domains or languages. If your name is consistent everywhere and brand searches already look right, markup is a low-urgency task. To see how brand searches look today, start with how to audit your brand SERP.

Ground rules from the general guidelines

The Organization page requires that markup follow Search Essentials and the general structured data guidelines. These set firm limits.

Visible and truthful

The general structured data guidelines (Opens in a new tab) say not to mark up content that readers cannot see and that markup must be a true representation of the page. If your address is not written anywhere on the site, it should not be in the markup either.

Not misleading

Fake reviews, impersonation and irrelevant data are off limits. Even for your own organization, avoid inflated claims: an invented award, an address you do not use or an identifier you do not hold does not belong.

Not blocked

Pages carrying structured data must not be blocked from Googlebot with robots.txt, noindex or other controls, and the logo URL must be crawlable and indexable.

Manual actions

According to the documentation, a structured data manual action means the page loses eligibility for rich result appearance, and the Organization page adds that Google ignores the structured data on an affected page while the page can still appear in results. Once the problem is fixed you can request reconsideration. The wider framework is on the Search Essentials page (Opens in a new tab).

Which properties to fill

The documentation states that there are no required properties and recommends adding all recommended properties that apply to your organization. Here they are, grouped by the job each does.

Names and URL

name is the organization's name, and the documentation suggests using the same name as your site name. alternateName holds another commonly used name. legalName is for the registered name when it differs. url is the organization's website address and helps Google identify it. Keep these spellings identical across the site, profiles and official documents; otherwise the markup creates a contradiction instead of a consistent picture.

Logo

logo can be a URL or an ImageObject and helps Google choose which image to show in results and knowledge panels. The requirements are a minimum of 112 by 112 pixels, a crawlable and indexable image URL, and a file format supported by Google Images. Check how the logo looks on a white background, since white or gray logos may not display well. An ImageObject needs a valid contentUrl or url meeting the same conditions.

Address and contact

address is a PostalAddress with an ISO two-letter country code, locality, region, postal code and street address, and several addresses are allowed. contactPoint describes how people can reach you, with email and telephone. Separate email and telephone properties exist too. Give phone numbers with country and area codes, and make sure every value also appears on the site.

Identifiers

iso6523Code carries an ISO 6523 identifier written as the scheme code and the identifier separated by a colon; the documentation lists 0060 for DUNS, 0088 for GLN and 0199 for LEI as common codes, and prefers it to the older duns and leiCode properties. vatID is described as a trust signal because people can check it in public VAT registers, and taxID should match the country in your address. Fill identifiers only with values you hold and can verify.

Descriptive details

description is a longer account of the organization, foundingDate uses ISO 8601, and numberOfEmployees takes an exact value or a range. Fast-changing values such as headcount need an owner who updates them, or stale numbers will linger in the markup.

Merchant properties and subtype choice

Return policy, shipping service and member program properties link to separate merchant documentation and apply only to commercial operations. The documentation also advises using the most specific schema.org subtype available, such as OnlineStore instead of OnlineBusiness for ecommerce, and a LocalBusiness subtype for physical locations.

Deciding which profiles go into sameAs

The documentation defines sameAs as URLs of other pages with information about the organization, such as social or review profiles, and allows several. It does not list approved platforms or say how many profiles to include, so the selection rule is yours to set.

A selection test for each candidate profile

The following test is an editorial judgment based on the property's definition and the accuracy principle in the general guidelines, not a documented requirement. A profile qualifies if you control it, if it is about the organization itself and not a product, person or campaign, if it is publicly visible without login, if it is active and current, if its name and branding match your markup, and if it has a stable address instead of a redirect chain or temporary campaign URL.

What typically passes and what does not

An official social account, a company registry page, a review-platform profile you manage and the organization's app store listing can pass the test. A third-party article that mentions you, a competitor comparison, an employee's personal account and an empty, abandoned profile do not. Press coverage is evidence about how others describe you; it is not your identity, so do not present it as one.

Never borrow someone else's identity

The structured data guidelines forbid misleading markup and markup that impersonates a person or organization. Listing the profile of a similarly named company as your own is exactly the kind of thing that can fall under that rule. If your brand has separate legal entities in different countries, think carefully about which entity each page describes, and keep that clear.

Link the profile back

The documentation does not require it, but putting your site address in each profile's bio makes the relationship easy for readers to confirm in both directions.

How many is enough?

There is no number in the documentation. Fewer well-maintained profiles beat a long list that drifts. Each addition adds upkeep, because a renamed, closed or transferred account turns into a contradiction.

A single home for the markup

Identity data should be defined once and rendered from that definition. Several hand-edited blocks scattered across templates end up disagreeing.

Where to place the markup

The documentation says the markup belongs on the home page or on a single page describing the organization, such as an About page, and that it is not needed on every page. The home page is the usual choice because it represents the site as a whole. If you use the About page, make sure the values in the markup are visible there.

Generate it from settings

Store the name, logo, address and profile links in site settings and let one template fragment produce the markup. Then a logo change or a new profile is a single edit. Do not let a plugin, a theme and a hand-pasted snippet all output Organization data; choose one producer and disable the others.

Duplicates and languages

The general guidelines say duplicate pages should carry the same structured data. On bilingual sites, identity fields such as name, legalName and url should match across language versions, while description should read naturally in each language. If the versions need different logos or names, make sure the reason is deliberate.

Reference, do not repeat

Article or product markup can reference the organization as publisher, but the full identity set does not have to be repeated on every page. Keep detail in one place and use references elsewhere. For a broader view of how your listing appears in results, see how to control your appearance in Google results.

Edge cases: multiple brands, migrations and branches

The basic setup suits a single brand on a single domain. A few common situations need extra thought, and in each the documentation gives no special rule, so the guidance below is editorial judgment.

A parent company with several brands

Decide which entity each site represents. A brand site describes the brand organization; the parent company can have its own page and its own markup. Avoid listing the parent's profiles on a brand site as though they were the brand's own, and avoid the reverse. Each site's markup should answer the question "who runs this site?" for that site only.

A domain migration or rebrand

Update the url, name and logo together, retire profiles that still carry the old name, and make sure the new home page produces the markup before the old one stops. During the transition, keep the identity statements on old and new pages consistent so that visitors and search systems do not meet two different answers.

Franchises and multiple branches

When separate legal entities operate under one brand, give each location its own accurate address and contact point instead of merging them into one record. Use the documented LocalBusiness subtypes for physical locations and keep each branch page consistent with what visitors see there.

A tiny organization with no official profiles yet

You do not have to create profiles just to fill sameAs. An empty property is better than a list of hastily opened, unmaintained accounts. Add profiles when they reflect real activity and when you can look after them.

Validation and maintenance

The documented sequence

The Organization documentation suggests this order: add the recommended properties that apply; test with the Rich Results Test and fix critical errors; deploy on a few pages and check with the URL Inspection tool how Google sees them, confirming the page is not blocked by robots.txt, noindex or a login; request recrawling if everything looks right; allow several days for crawling and indexing; and submit a sitemap to keep Google updated. Tool names are shown in English; if you use the interface in another language, menu labels may look different.

Your own checklist

• Does every marked-up value have a visible counterpart?
• Do name, url and logo match the site and the profiles?
• Does every sameAs URL open, belong to the organization and stay current?
• Is only one Organization block produced per page?
• Is the logo URL open to crawling?
• Is the page free of noindex and robots.txt blocks?

Monitoring

The effect of markup is hard to isolate, but you can log how your brand results look, including logo, description and sitelinks, before and after changes. To separate branded queries in Search Console, the branded queries filter guide shows the approach. Record dates, and avoid attributing any change to one cause.

Reading the results sensibly

After a change, give crawling and indexing time, since the documentation itself mentions several days. Compare like with like: the same brand queries, the same device type and a note of the date. If the logo or description in results changes, that is a useful observation; if nothing changes, that does not prove the markup is wrong, because the documentation guarantees no appearance. Keep a baseline screenshot so that later comparisons rest on records instead of memory.

Change log

Keep a simple table with the date, editor, old and new value and a short reason for every markup change. A year later, it is the only record that explains why a logo changed or a profile was removed.

Update triggers

Revisit the markup after a rename or logo change, an address or contact change, a closed or taken-over social account, a newly opened official profile, or a domain or language change. Also review the whole block every quarter.

Mistakes worth catching early

Filling sameAs with everything

Padding the list with stale or loosely related profiles lowers accuracy. Apply the selection test and keep only profiles that represent the organization.

Marking up what is not on the page

Adding a phone number or address that appears nowhere visible breaks the guidelines. Publish it first, then mark it up.

Logo problems

Typical failures are images that are too small, blocked from crawling, in an unsupported format or unreadable on a white background. Turn the documented conditions into a pre-release check.

Competing blocks

A plugin, a theme and a custom snippet all emitting Organization data produce conflicting values. Choose one producer.

Treating a passing test as a promise

The general guidelines list reasons a feature may not appear even when the Rich Results Test passes, including errors the tool cannot detect. Keep expectations at the level of consistency and maintenance.

Keyword stuffing the description

Search Essentials advises using the words people search for in places such as titles, link text and alt text, naturally. In markup, an accurate and plain description is enough.

Who does what: a shared workflow

What the brand manager prepares

One table with the official name, registered name, alternate names, logo file URL, address, contact details, each official profile and its owner. Include profiles deliberately left out, with the reason, so the next person does not add them back by accident.

What the developer implements

A single template fragment that reads from settings, a test pass for every release that touches templates, and a note recording which setting feeds which field. The brand manager then checks brand results visually over the following weeks.

Example scenario: a rebranded publisher

Example scenario: a publisher renamed its site last year. Some social accounts still carry the old name, two logo files circulate and the footer shows an old address. The sequence is to confirm the official name and domain, rename or drop the legacy accounts from the list, settle on one logo file used both on the site and in the markup, correct the footer address, render the block from one template fragment on the home page, and watch brand results for a while. No step promises a visible change; the goal is for identity to read the same everywhere.

Before you start: three questions

Which name is official, and how do the brand name, registered name and domain relate? Which facts are already visible on the site? And who will update each field when it changes? A field without an owner will go stale.

Frequently Asked Questions

What is sameAs?

According to Google's Organization documentation, sameAs is a set of URLs of other pages with information about the organization, such as social or review profiles. Several URLs are allowed. The documentation does not list which platforms are accepted.

Are any Organization properties required?

No. Google states there are no required properties and recommends adding all recommended properties that apply to your organization. That does not make accuracy optional; misleading markup breaks the general structured data guidelines.

Where should Organization markup go?

Google says it can go on the home page or on a single page describing the organization, such as an About page, and it is not needed on every page. Use one source that matches the visible content.

Will Organization markup improve rankings or guarantee a knowledge panel?

The documentation makes no such claim. It says the markup can influence which logo appears and helps distinguish organizations, and the general guidelines say structured data features are not guaranteed to appear.

What are the logo requirements?

The image should be at least 112 by 112 pixels, its URL must be crawlable and indexable, and it must be in a format Google Images supports. Also check that it looks right on a white background.

How many sameAs profiles should I list?

The documentation gives no number. Limit the list to profiles that represent the organization, that you control, and that are public and current, and add each one to your upkeep schedule.

How do I test the markup?

The documentation recommends the Rich Results Test, the URL Inspection tool to see how Google views the page, making sure the page is not blocked, requesting a recrawl, allowing several days, and submitting a sitemap.

Related guides: E-E-A-T Implementation Checklist by Page Type, Wikidata and Brand Entity Records: Eligibility and Approach, How to Write an About Page That Supports SEO.

Conclusion

Organization markup and sameAs describe your brand's identity from one consistent source: name, logo, contact details and a small set of official, current profiles you control. Generate the markup from site settings, keep it identical to the visible content, test it, and review it every quarter. It carries no ranking or display guarantee; its value lies in making your identity read the same everywhere.

If you are looking for clearly labeled placements that introduce your organization to new readers, you can browse the guest post listings on Akua Adforce; scope and terms are on that page.