Organization Schema: How to Describe Your Business Clearly

What is Organization Schema?

Organization Schema is structured data that uses the Schema.org Organization type, or one of its more specific subtypes, to describe an organisation.

The object can contain information such as:

• the recognised organisation name;
• an alternative or abbreviated name;
• the registered legal name;
• the official website URL;
• a logo and description;
• contact details and postal addresses;
• official profiles on other websites;
• company and tax identifiers;
• relationships with parent or subsidiary organisations.

The exact Schema.org type is written with American spelling and a capital letter:

"@type": "Organization"

That code remains the same on a British website even when the surrounding copy uses “organisation”. Organization Schema should describe a real entity that the website represents. It is not a place to add marketing keywords, every service offered or unsupported claims about authority.

What does Organization Schema help with?

It identifies the entity behind the website

A business name may be shared with another company, product or person. The organisation's URL, logo, address, profiles and identifiers provide additional evidence about which entity the page means.

It connects business details

An Organization object can bring information from different parts of the site into one coherent description. The name may appear in the header, the logo in an image file, the phone number on the contact page and the legal name in the footer. Structured data expresses how those facts belong together.

It can influence search presentation

Google can use Organization structured data to understand administrative details and distinguish an organisation. Some properties may influence visual elements such as the logo used in search results or a knowledge panel.

Markup cannot force Google to create or change a knowledge panel. The visible search presentation remains automated and is not guaranteed.

It supports consistent reuse

The same organisation can be referenced as the publisher of articles, the seller of products or the parent of a local branch. A stable @id gives those objects a consistent internal reference.

It improves machine-readable entity clarity

Search engines and AI-powered systems benefit from unambiguous names, relationships and identifiers. Organization Schema provides a formal statement of those facts, provided the website and external profiles support them.

Organization, WebSite or LocalBusiness?

These types answer different questions and may appear together.

Organization is the business entity

Use Organization when describing the body behind the site. Schema.org also provides more specific subtypes, including Corporation, EducationalOrganization, NGO, GovernmentOrganization and OnlineStore.

Choose a subtype only when it is accurate and useful. A general company does not become a LocalBusiness simply because it has an address.

WebSite is the web property

Google uses WebSite structured data on the homepage as the strongest structured-data signal for a preferred site name. The website and the organisation may share a name, but they are still different entities.

Use distinct @id values when modelling both:

https://example.com/#organization
https://example.com/#website

The WebSite can then reference the organisation as its publisher where appropriate.

LocalBusiness is a local operation

LocalBusiness is a subtype of Organization intended for a physical or local business. It supports type-specific information such as opening hours and location details. Use the most specific accurate local subtype on the relevant business or location page.

Where should Organization Schema be added?

Google recommends placing Organization information on the homepage or a single page that describes the organisation, such as an About page. It does not need to be copied independently onto every page.

A practical model is:

1. Publish the complete Organization object on the homepage or About page.
2. Give it a stable @id, such as https://example.com/#organization.
3. Reference that identifier from related objects where the implementation supports a connected graph.

For example, an article can identify its publisher through the same organisation reference rather than recreating a different name and logo on every page.

Whichever page carries the full object should return a successful response, be crawlable and indexable, use the canonical organisation URL, display or support the important facts in visible content, and remain stable through redesigns and migrations.

Avoid hiding the only complete business description on a login page, JavaScript-only modal or non-canonical duplicate.

Which Organization properties should you include?

Google currently lists no universally required properties for Organization markup. Add the properties that genuinely apply and that the organisation can keep accurate.

name and alternateName

Use the recognised public name of the organisation. It should match the way the company identifies itself prominently on the site.

"name": "Example Analytics",
"alternateName": "EA"

Use alternateName for a common abbreviation, acronym or alternative trading name when one genuinely exists. Do not insert keyword variations or slogans.

legalName

Use the registered legal name when it differs from the public trading name:

"legalName": "Example Analytics Limited"

This avoids replacing a familiar brand with a legal suffix in every public-facing property.

url and logo

Use the official canonical website URL for the organisation. Provide a crawlable and indexable logo URL or an ImageObject. Follow the current image requirements and confirm that the logo remains legible on a light background.

description and sameAs

Write a concise factual description supported by the About page. List authoritative external pages that unambiguously represent the same organisation, such as official social or industry profiles.

Contact details, address and identifiers

Supply public business contact information that users intend to use, with international telephone codes where relevant. Use a PostalAddress for a genuine public, mailing or registered address when appropriate. Applicable organisations may supply recognised identifiers such as VAT, tax, LEI, DUNS or GLN information.

More properties do not automatically create a better object. Accuracy, relevance and consistency matter more than filling every available field.

An Organization Schema JSON-LD example

This example identifies a fictional UK software company:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "@id": "https://example.com/#organization",
  "name": "Example Analytics",
  "alternateName": "EA",
  "legalName": "Example Analytics Limited",
  "url": "https://example.com/",
  "description": "Example Analytics develops website auditing software.",
  "logo": {
    "@type": "ImageObject",
    "url": "https://example.com/images/example-analytics-logo.png",
    "contentUrl": "https://example.com/images/example-analytics-logo.png"
  },
  "email": "support@example.com",
  "telephone": "+44-20-7946-0123",
  "address": {
    "@type": "PostalAddress",
    "streetAddress": "10 Example Street",
    "addressLocality": "London",
    "postalCode": "EC1A 1AA",
    "addressCountry": "GB"
  },
  "sameAs": [
    "https://www.linkedin.com/company/example-analytics",
    "https://github.com/example-analytics"
  ]
}
</script>

Replace every example value with verified information. Do not publish fictional phone numbers, addresses or profiles copied from documentation.

The @id identifies the entity within the structured-data graph. It does not need to load as a separate webpage when the fragment follows #, but it should remain stable and unique to the organisation.

How to add a business logo

The logo property can be a direct URL or an ImageObject. An ImageObject allows the implementation to express the image more explicitly.

Google advises that the logo:

• represents the organisation;
• is at least 112 by 112 pixels;
• uses a supported image format;
• has a crawlable and indexable URL;
• looks appropriate against a plain white background.

Use the main brand mark rather than a campaign image, social banner or tiny favicon. Make sure redirects, access controls and hotlink protection do not prevent search engines from retrieving it.

Check the logo after a media migration. A structurally valid Organization object can still point to an image that returns 404, redirects through several hosts or has been blocked from indexing.

If several brands operate within one corporate group, assign the correct logo to each actual entity. Do not use the parent-company logo to describe a subsidiary that presents a distinct public brand unless that relationship is made clear.

How to use sameAs for official profiles

The sameAs property points to another URL that unambiguously identifies the same organisation.

Suitable examples may include the organisation's official LinkedIn company page, an official GitHub organisation, a recognised industry or regulatory profile, a verified social profile maintained by the business, or a reliable knowledge-base page specifically about the organisation.

Do not add a URL merely because it mentions the brand. A news article, reseller listing, customer review or directory search result is not necessarily the same entity.

Review each profile before including it:

1. Does it represent this exact organisation?
2. Does the name and website link agree?
3. Is the profile current and controlled or recognised?
4. Does it confuse the parent company with a brand or local branch?
5. Is the URL stable and publicly accessible?

More profile links are not inherently better. A short, accurate set is clearer than a long list containing stale or uncertain identities. Keep the parent business identity consistent with location-level business details and validate the implementation with a structured-data testing workflow.

How to handle contact details and identifiers

Keep contact information public and purposeful

Add a telephone number or email address that users can actually use. Avoid private staff details, unmonitored mailboxes and regional numbers that do not represent the organisation described.

When several contact channels exist, a ContactPoint can add context such as customer service, sales or technical support.

Distinguish trading and registered information

The public name, legal name, trading address and registered address may differ. Use the property that matches each fact and keep the visible legal or contact pages consistent.

Use recognised identifiers accurately

Google's Organization guidance supports several administrative identifiers, including vatID, taxID, iso6523Code and leiCode. Do not expose an identifier without considering whether it is intended to be public. Do not guess one from a company name or repurpose an internal CRM number as an official business identifier.

Match other public evidence

The website's footer, contact page, privacy notice, terms, official profiles and Schema markup should not disagree about the organisation's name, URL or address. Minor formatting differences are normal; material conflicts can make it harder for people and machines to determine which details are current.

How to describe parent companies, brands and divisions

One website can represent more than one organisational concept: a corporate group, operating company, consumer brand, regional subsidiary, department or several local branches. Do not merge them into one overloaded object.

Give each real entity its own identity

Use a separate object and stable @id when the entity needs to be referenced independently. Apply the correct type, name, URL, logo and identifiers.

Express the relationship

Schema.org properties such as parentOrganization, subOrganization and brand can describe relationships when they are factually correct.

For example, a product may reference its Brand, while the brand is owned by a parent Organization. A local shop may be represented as a LocalBusiness connected with its parent company.

Avoid circular or contradictory graphs

Do not declare two companies as each other's parent. Do not use one @id for the brand, website and legal company simply because their public names are similar.

Draw the relationship on paper before coding a complex graph. If the team cannot explain which entity owns which property, machines are unlikely to interpret it cleanly.

Organization Schema for LLMs and AI visibility

Organisation information matters to AI visibility because many generated answers depend on identifying the correct entity before summarising its products, services, ownership or contact information.

An LLM-powered search system may encounter several businesses with the same or similar name, a trading name that differs from the legal company, an old logo on one profile and a new one on the website, several addresses without a clear relationship, or a product brand mistaken for its parent company.

Accurate Organization Schema can make the intended identity and relationships explicit. Stable names, URLs, identifiers and sameAs links give machines clearer signals to connect with corroborating public sources.

For stronger AI entity clarity:

• use one recognised public name consistently;
• distinguish name, alternateName and legalName;
• use a stable canonical organisation URL and @id;
• link only genuine official profiles with sameAs;
• keep addresses and contact details aligned with visible pages;
• model parent, brand and local-business relationships accurately;
• ensure the organisation page is crawlable and indexable;
• update old logos and profiles after a rebrand.

Schema markup is supporting evidence, not proof by itself. Organization Schema does not guarantee a knowledge panel, LLM citation, brand mention or recommendation.

How to test Organization Schema

Use the Rich Results Test for Google's interpretation

Google's Organization documentation directs site owners to validate code and fix critical errors. The Rich Results Test can inspect supported organisation information and the rendered page.

Use the Schema Markup Validator for the object graph

Check the wider Schema.org structure, especially @id references, nested addresses, contact points and parent relationships.

Test the live canonical page

After publication, test the homepage or About page carrying the complete object. Confirm that JavaScript, consent tools or caching do not remove or duplicate it.

Check every linked resource

Open the official URL, logo, profiles and other referenced pages. A validator may accept the URL format without proving that the destination is correct or available.

Compare with visible content

Verify the name, description, contact information and address against the page and current business records. Technical validity cannot establish whether a company fact is true.

Test related WebSite markup separately

If the homepage also contains WebSite markup for the site name, make sure the two objects have distinct identities and consistent names. Google advises using the Schema Markup Validator for site-name markup because the Rich Results Test does not support that feature.

How to audit Organization Schema across a website

Locate every organisation object

Crawl the site and find every Organization object and subtype. Identify whether the complete entity appears once, is referenced consistently or has been duplicated by themes and plugins.

Compare names and identifiers

Group the values of @id, name, alternateName, legalName, url and tax or company identifiers. Investigate small variations that create separate entities unintentionally, such as different protocol, hostname or trailing-slash forms in @id values.

Check logos and profile links

Find image or sameAs URLs that return errors, redirect repeatedly or lead to the wrong organisation. Review rebranded domains and retired social profiles.

Review page eligibility

Confirm that the homepage or About page carrying the object is successful, canonical, crawlable and indexable. Check duplicate homepages for consistent information.

Find competing generators

SEO plugins, ecommerce platforms, themes and custom scripts may each add an organisation object. Establish which system owns the entity and remove conflicting output.

Compare public business details

Review the contact page, footer and key legal pages for material differences in name, address, phone number and website ownership.

Audit Organization Schema with Clearcrawl

Clearcrawl helps reveal the organisation information the live website actually publishes. A CMS settings screen may contain the right name while an old plugin still outputs the previous logo or a different company URL across every page.

Use the crawl to find the scope and consistency of the implementation. Use validators and human review to confirm that the final object is structurally correct and factually true.

How to fix and verify Organization Schema

1. 01
   Define the entity

   Agree which organisation the website represents. Record its recognised name, legal name, canonical URL, logo, profiles and public identifiers.

2. 02
   Separate related entities

   Distinguish the organisation from its website, brands, parent company, subsidiaries and physical locations. Give each necessary object a stable identity.

3. 03
   Select the owner page

   Choose the canonical homepage or About page for the full object. Make sure the page is accessible and contains supporting information.

4. 04
   Trace the generator

   Find whether the theme, plugin, CMS or custom code outputs each block. Remove stale duplicates before adding another version.

5. 05
   Correct the source details

   Update the business record, logo asset, contact information and official profile list. Avoid fixing only the final JSON-LD if the site displays outdated information elsewhere.

6. 06
   Validate the graph

   Test the Organization object, linked WebSite object and relevant subtypes. Follow every @id, logo and external profile URL.

7. 07
   Publish and recrawl

   Confirm that the intended object appears on the live canonical page and that conflicting versions have disappeared.

8. 08
   Monitor entity changes

   Recheck the implementation after a rebrand, merger, new domain, office move, logo change or corporate restructuring.

Common mistakes

Frequently asked questions