Aizii Learn · AI Search

[← Back to Learn](https://aizii.ai/learn)

# How to add Organization schema for brand clarity

Organization schema is a block of JSON-LD on your homepage or About page that states, in a machine-readable form, who your brand is: its name, its web address, its logo, its contact details, and the profiles elsewhere on the web that belong to it. It does not change what visitors see. It gives search engines and AI systems one declared version of your identity to match against every other place your name appears.

Google puts the purpose in one sentence in its Organization structured data docs: adding this markup to your home page can help Google better understand your organization's administrative details and disambiguate your organization in search results. Disambiguate is the key word. There are many brands with similar names, and many spellings of one brand. This block says which one is yours.

It is not a ranking factor, and it does not guarantee a knowledge panel. Google says some properties are used behind the scenes to tell your organization apart from others, while others can influence visual elements such as which logo is shown and your knowledge panel. Treat it as identity paperwork, not as a lever that pushes you up a list.

## Where it goes, and how often

Google recommends placing this information on your home page, or on a single page that describes your organization, such as the About page. You do not need to include it on every page of your site. One copy, in one place, kept current, beats a copy on every page that drifts out of sync.

That single-copy rule matters because the most common failure is not a missing block. It is two blocks that disagree. A theme emits one Organization block, an SEO app emits another, and the names, logos, or profile links differ. A machine reading both has to guess which one is right, and the whole point of the block was to remove that guess. Before you add anything, view the source of your homepage and search for application/ld+json. If an Organization block is already there, fix that block.

Google also recommends using the most specific schema.org subtype that matches your organization. If you run an ecommerce site, use OnlineStore instead of the plain Organization type. If your site is about a local business, such as a restaurant or a physical store, use the most specific LocalBusiness subtype and follow the fields for LocalBusiness as well. The rest of this guide uses the plain Organization type, and the same fields carry over to the subtypes.

There are no required properties for Organization markup in Google's docs. Google recommends adding as many properties that are relevant to your organization. A short block with true values beats a long block padded with guesses.

## The complete Organization block

Here is a full JSON-LD block for a fictional outdoor apparel brand. In the example, \[yourdomain.com\] is a placeholder, replacing yourdomain.com with your actual domain. Every field maps to a schema.org Organization property, and the values match what Google's own Organization example uses.

```
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "@id": "https://[yourdomain.com]/#organization",
  "name": "Northwind Supply Co.",
  "legalName": "Northwind Supply Company LLC",
  "alternateName": "Northwind Supply",
  "url": "https://[yourdomain.com]",
  "logo": "https://[yourdomain.com]/images/logo.png",
  "description": "Northwind Supply Co. makes weatherproof jackets and packs for hiking and backcountry travel.",
  "email": "contact@[yourdomain.com]",
  "telephone": "+1-206-555-0148",
  "address": {
    "@type": "PostalAddress",
    "streetAddress": "1200 Alaskan Way",
    "addressLocality": "Seattle",
    "addressRegion": "WA",
    "postalCode": "98101",
    "addressCountry": "US"
  },
  "sameAs": [
    "https://www.instagram.com/northwindsupply",
    "https://www.linkedin.com/company/northwind-supply",
    "https://www.youtube.com/@northwindsupply"
  ],
  "contactPoint": {
    "@type": "ContactPoint",
    "telephone": "+1-206-555-0148",
    "email": "support@[yourdomain.com]",
    "contactType": "customer service"
  }
}
</script>
```

Field by field:

-   **@id**: a stable identifier for your organization, built from your own domain with a fragment such as #organization. Other markup on your site can point back to this same identifier instead of repeating the whole block, so a Product block and an Article block can both say they belong to this one organization.
-   **name**: the brand name exactly as it appears on your site header and in your product markup. This spelling is the anchor. Keep it identical everywhere.
-   **legalName**: the registered name, only when it differs from the brand name. If the two are the same, leave this field out.
-   **alternateName**: another name your brand commonly goes by, if one exists. Do not invent one. A nickname nobody uses adds confusion, not clarity.
-   **url**: your homepage address. This is the canonical address of the organization.
-   **logo**: a full URL to your logo image. Google's guidelines say the image must be at least 112 by 112 pixels, the image URL must be crawlable and indexable, and the file format must be one Google Images supports. A logo that is mostly white or gray can look wrong on a white background, so check how it renders.
-   **description**: one sentence describing what the organization does, in the same words your About page uses.
-   **email and telephone**: real contact details for the business. Include the country code in the phone number.
-   **address**: the physical or mailing address, with the two-letter country code. Provide all the address parts that apply to your country.
-   **sameAs**: URLs of pages on other sites with more information about your organization, such as your profiles on social media or review sites. Only list profiles you control and keep current. A dead or wrong profile link tells a machine your identity is uncertain.
-   **contactPoint**: the best way for a customer to reach you, with a contactType such as customer service. Keep it to the support methods you actually offer.

## Linking it to the rest of your site

The block earns its keep when the same identity shows up in the other markup on your site. Use the same name in your Product brand field, in your Article publisher field, and in your llms.txt file. When a model reads your product page, your homepage, and your llms.txt file and finds the same name, the same address, and the same logo in all three, it resolves them to one brand. When they differ, it may treat them as separate candidates.

The @id is what makes that linkage cheap. Give the Organization block one @id, and then any other block can reference that identifier instead of restating the name and address. If you change your contact email, you change it in one place.

## Validate before you ship

The Schema Markup Validator checks the JSON-LD against the schema.org vocabulary, and it catches typos in property names and wrong types. Run it on your homepage after you add the block. Google's Rich Results Test is less useful here, because Organization markup does not produce a rich result on its own, so the test may show little or nothing for this type. That is expected, not a failure.

Then check the logo by hand. Open the logo URL in a browser and confirm it loads, confirm it is at least 112 by 112 pixels, and confirm it is not blocked by robots.txt. A validator will not tell you the logo is a broken link.

## Common mistakes

**Different name spellings in different places.** The header says one thing, the markup says another, and the social profiles say a third. Pick one spelling and use it in all three. This is the mistake the block exists to fix, and it is the mistake most often found inside the block itself.

**sameAs links you do not control.** A link to a profile you abandoned, or to a similarly named company, attaches someone else's identity to yours. Audit every sameAs URL by opening it and confirming it is your profile.

**A copy on every page.** The block belongs on the homepage or the About page. Copies scattered across product and blog pages drift apart over time, and then the site contradicts itself.

**Guessed identifiers.** Do not add a tax identifier, a DUNS number, or a legal entity identifier unless you know the real value. A wrong identifier is worse than a missing one, because it confidently points at the wrong organization.

**A logo that cannot be read.** A logo behind a login, blocked by robots.txt, smaller than the minimum size, or in an unsupported format does not help. Google's docs list the minimum size and the crawlable requirement plainly, and both are easy to check.

## Say you share a name with another brand

Say your brand is called Beacon Coffee, and there is another Beacon Coffee in another state that sells beans online too. A shopper asks an assistant about Beacon Coffee, and the assistant has to decide which one the shopper means. Your homepage carries an Organization block with your address, your logo, your profiles, and your @id, and your product pages point their brand field at the same @id. The other Beacon Coffee has no Organization markup and its listings use three different spellings of the name. The assistant can pin your facts to one entity and cannot do the same for the other, so it names you with confidence and describes the other one vaguely, or not at all. That is what brand clarity buys: not a higher rank, but a clearer identity when the question is asked.

## What this guide does not cover

This guide covers the identity block. It does not cover getting crawlers to your pages, which is the robots.txt reference, or writing the About page the block describes, or the transaction layer that turns a recommendation into a sale. And it does not cover knowledge panels as a whole: the block can influence which logo and details appear, but Google does not guarantee a panel for any brand.

## Check your own brand now

Run the free scan. It takes seconds, no signup, and shows whether AI crawlers can read your brand today: aizii.ai/aeo-scan

[Run the free scan](https://aizii.ai/aeo-audit)

## Sources

-   Google Search Central, Organization structured data (specific): [https://developers.google.com/search/docs/appearance/structured-data/organization](https://developers.google.com/search/docs/appearance/structured-data/organization)
-   Schema.org, Organization type (general standard): [https://schema.org/Organization](https://schema.org/Organization)
-   Google Search Central, Optimizing your website for generative AI features on Google Search (specific): [https://developers.google.com/search/docs/fundamentals/ai-optimization-guide](https://developers.google.com/search/docs/fundamentals/ai-optimization-guide)
-   Schema Markup Validator (general docs): [https://validator.schema.org/](https://validator.schema.org/)

Note: links marked specific point to the page that supports the claim in this guide. Links marked general docs point to the vendor's general docs section for that topic, not to a page that proves every step. Check the vendor docs for the current path before relying on a menu name or click path in this guide.
