Organization Schema: How to Mark Up Your Brand Correctly

Organization schema is structured data, usually written as JSON-LD, that tells search engines the basic facts about your company: its name, logo, URL, contact details and the official profiles that belong to it. You place it once on your home page (and, if you like, on an about page), keep it identical to what visitors can see, and let machines read your identity without guessing. This guide covers what to include, a working example, how logo, sameAs and site name fit in, and the mistakes that cause trouble.

TL;DR

• Organization schema is a JSON-LD block describing your company. It makes you eligible for features such as logo and knowledge panel details, but structured data never guarantees display.
• No property is strictly required, but Google recommends adding as many relevant properties as apply: name, URL, logo, address, telephone and sameAs links.
• Use the most specific subtype that fits (LocalBusiness, OnlineStore, NGO) instead of generic Organization, and keep the markup in sync with visible page content.
• Site name is a separate job, handled by WebSite markup. Do not confuse the two.
• Treat the markup as a consistency tool: it should match your site, your profiles and your listings.

Table of Contents

• What organization schema is, and what it is not
• Why it matters more in the AI search era
• Decide the goal before you write the code
• The properties that do the work
• A working JSON-LD example
• Logo markup
• sameAs: connecting your official profiles
• Site name: a different markup, a different job
• Choose the most specific type
• Keep markup and page content in sync
• Our perspective: schema is an identity layer, not a trick
• How to validate and monitor
• Common mistakes
• Check your whole brand layer
• FAQ
• Sources

What organization schema is, and what it is not

Schema.org is the shared vocabulary. JSON-LD is one format for writing it. Practitioners often blur the two, and the distinction matters when you pick tools: structured data is the method, Schema.org is the vocabulary of types and properties. Organization is one type in that vocabulary, and it is widely used: Schema.org reports more than 10 million domains using it, based on Google's web index as of August 2026.

In practice, organization schema sits behind the scenes in your code and gives search engines administrative facts about the business. Search engines use those facts to build knowledge graph profiles and to influence elements such as knowledge panels.

It is not a ranking lever. Google keeps discretion over whether to show anything, based on query relevance, site quality and trust. Even markup that validates cleanly in Search Console may be ignored. Think of organization schema as disambiguation: it reduces the chance that a search engine or an AI assistant confuses you with a similarly named company, or states an outdated fact about you.

Why it matters more in the AI search era

Structured data used to be judged by one question: does it trigger a rich result? That is still relevant, but it now also functions as machine-readable fuel for AI engines, which need explicit facts to retrieve and present a business accurately in synthesized answers.

We see this in audits. A brand with a clean, consistent identity layer (same name, same description, same profile links everywhere) is described more reliably than one whose home page, LinkedIn page and directory listings disagree. Schema does not replace that consistency. It states it in a form a machine can parse without interpretation.

If you want to go deeper on how AI systems pick and describe brands, read our pieces on how AI chooses brands to recommend and why strong SEO visibility does not equal strong AI brand presence.

Decide the goal before you write the code

John Mueller's advice on structured data is to start from the outcome. The question is which visual search feature you want, then implement the markup that feature needs, rather than marking up every possible detail.

For organization markup, the realistic goals are:

1. Brand identity clarity. Name, URL, logo and official profiles tied to one entity.
2. Logo eligibility. A logo that search can associate with your organization.
3. Contact and location accuracy. Address, phone and area served, where they are public and true.
4. A stable reference for other markup. Articles, products and people can point back to the organization.

If none of these applies to you, skip the exercise. If one does, the sections below show how.

The properties that do the work

Google states that no properties are required for Organization, yet recommends supplying as many relevant ones as possible. A practical priority list:

Property	What it does	Notes
name	Your legal or public brand name	Match the name on your home page and profiles
url	Canonical home page	Use the exact canonical version, including protocol
logo	Image tied to your brand	See the logo section below
sameAs	Links to official profiles	Only profiles you control
description	Short factual summary	Same wording as your visible about copy
address	Postal address	Only if it is on the page
telephone / contactPoint	Customer contact	Only if public
foundingDate, founder	Company facts	Only if you publish them
@id	A stable identifier for the entity	Lets other markup reference it

Notice what is absent: nothing invented, nothing aspirational. Every value should be something a visitor could verify by reading your site.

A working JSON-LD example

Here is a template for a software company. Replace every value with your own and delete properties you cannot support.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "@id": "https://www.example.com/#organization",
  "name": "Example Co",
  "url": "https://www.example.com/",
  "logo": {
    "@type": "ImageObject",
    "url": "https://www.example.com/images/logo.png",
    "width": 512,
    "height": 512
  },
  "description": "Example Co builds scheduling software for clinics.",
  "sameAs": [
    "https://www.linkedin.com/company/example-co",
    "https://x.com/exampleco",
    "https://www.youtube.com/@exampleco"
  ],
  "contactPoint": {
    "@type": "ContactPoint",
    "contactType": "customer support",
    "email": "support@example.com"
  }
}
</script>

Place it in the <head> or body of your home page. Because the organization is described once, other pages inherit the understanding of the site as an organization in practice, and you generally do not need to repeat the block on every page. Repeating a short reference by @id from article or product markup is cleaner than copying the whole block.

Writing the JSON-LD by hand or with a tool

Hand-editing JSON is where most syntax errors happen: a missing comma, a curly quote pasted from a document, an unescaped character. A JSON-LD schema generator tool can produce the block from a form, which is useful when you want the Schema.org vocabulary rendered correctly as JSON-LD without writing it yourself. Whatever you use, read the output before publishing and remove anything your visible pages do not support.

Logo markup

The logo is the property people ask about most. Three rules:

• Format. Google accepts the logo as a plain URL or as an ImageObject. ImageObject gives more flexibility, since you can add attributes such as width, height and a caption.
• Size. The documented minimum is 112 by 112 pixels, and the image must be crawlable, indexable and supported in Google Images. A blocked image or a file behind a login will not work.
• Choice of file. Use a square or near-square version with a clear background, not a banner lockup with a tagline, so it stays legible when scaled down.

If your logo changes after a rebrand, update the file at the same stable URL or update the markup the same day. Old logos persist in search surfaces and in third-party databases for a long time, and a mismatch between your site and your markup is the sort of inconsistency we flag in brand audits.

sameAs: connecting your official profiles

sameAs lists URLs that represent the same entity elsewhere: LinkedIn company page, YouTube channel, a Crunchbase or Wikipedia entry if one genuinely exists for you, and other verified profiles. It is the clearest way to say "these accounts are all us."

Good practice:

1. List only profiles you own or that formally describe your company.
2. Use the exact profile URL, without tracking parameters.
3. Make sure each profile links back to your home page, so the connection runs in both directions.
4. Remove dead or abandoned accounts. A link to a profile with an old name or logo undermines the consistency you are trying to show.

Corroboration from independent sources strengthens the picture further. We explain how in third-party corroboration in GEO.

Site name: a different markup, a different job

Searchers who look for "site name schema" are usually after the name that appears above your result. That is not set with Organization markup. According to Google, you indicate a site name preference by adding WebSite structured data to your home page. The system also considers other signals such as og:site_name, heading elements and other home page text, so those should agree.

To choose a name, Google advises avoiding generic names, using the name consistently across the home page, and providing an alternative name where one exists, such as an abbreviation. A minimal block looks like this:

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

The two blocks can live side by side on the home page. Use the same name string in both.

Choose the most specific type

Google's documentation encourages using the most specific Schema.org subtype rather than generic Organization. Practical mapping:

• A company with a physical location customers visit: LocalBusiness or a subtype such as Dentist or Restaurant.
• An e-commerce brand: OnlineStore.
• A charity or nonprofit: NGO.
• A software or services company without a public storefront: Organization (or Corporation) is fine.

If you run a multi-location business, the location pages carry their own LocalBusiness markup, while the home page carries the parent organization. Our local presence audit checks that name, address and phone details match across the Google Business Profile, location pages and listings.

Keep markup and page content in sync

This is the rule people break most. Google's general guidelines require structured data not to violate content and spam policies to be eligible for rich results. A typical violation is an address present in JSON-LD but nowhere on the visible page. Mismatched data can lead to manual actions, and it also gives AI engines contradictory facts to extract.

A short pre-publish check:

1. Does every value in the markup appear on a page a visitor can reach?
2. Does the name match your home page title, footer and social bios?
3. Is the logo file crawlable and not blocked by robots.txt?
4. Are all sameAs URLs live and owned by you?
5. Is the JSON valid, with straight quotes and no trailing commas?

Our perspective: schema is an identity layer, not a trick

We score public brand presence against a fixed checklist, and structured data is one of the observable signals. What we see repeatedly is that schema problems are rarely technical. They are consistency problems. A company describes itself one way in its markup, another on its home page, a third in a directory listing, and a fourth on LinkedIn. The markup is then accurate to none of them.

So our advice has an order. Settle the facts first: the legal name, the one-sentence description, the official profile list. Publish them on the page. Then encode them in JSON-LD. Doing it in reverse produces valid code describing a brand nobody can identify.

We also separate three things that teams tend to merge: whether markup exists, whether it is accurate, and whether it changes any outcome. The first two can be checked in minutes. The third cannot be promised, which is why we report score, data coverage and confidence separately instead of presenting one number as certainty. For a broader view of where schema fits in a B2B brand, see our guide to schema markup for B2B brands.

— Quincy

How to validate and monitor

1. Test before publishing. Run the page through Google's Rich Results Test and the Schema Markup Validator to catch syntax and type errors.
2. Publish and request indexing. After deployment, inspect the home page URL in Search Console.
3. Watch the enhancement reports. Search Console reports on detected structured data and flags errors.
4. Recheck after changes. Rebrands, new addresses, new social handles and site migrations all invalidate parts of the block.
5. Check the AI side. Ask several AI assistants who you are and what you do, and compare the answers with your markup. Our 30 to 50 prompt test describes a repeatable way to do it.

Expect delay. Even correct markup may show no visible change, because display is at Google's discretion.

Common mistakes

• Marking up every page with a full Organization block. One authoritative block on the home page, referenced elsewhere by @id, is cleaner.
• Using the logo of a partner or a product. The logo should be yours.
• Listing social profiles you no longer use.
• Adding ratings or review markup to the organization itself to chase stars. This invites a spam-policy problem.
• Copying a competitor's block and changing a few fields, leaving stale properties behind.
• Treating a green validator result as success. It says the syntax is fine, not that the facts are right.

Check your whole brand layer

Organization schema is one signal among many. If you want to see how your markup compares with your messaging, search visibility and AI presence, our free scan reads your public data with no sales call and no credit card. The full twelve-category audit is $99 one-off and scores categories including SEO, AEO, GEO and reputation, with recommendations tied to observable evidence. If answer-engine readiness is your focus, start with the AEO audit. Plans are on the pricing page, and the Starter plan is $79 per month.

FAQ

Is organization schema still worth adding?

Yes, if you value a clear, machine-readable identity. It does not guarantee a rich result or a ranking gain, and Google may choose not to display it. The cost is low and it supports consistent brand facts for search and AI systems.

What is the difference between schema and structured data?

Structured data is the method of labeling information so machines can read it. Schema.org is the shared vocabulary of types and properties, and JSON-LD is a common format for writing it. The distinction is often conflated, but knowing it helps you choose the right markup.

Do I need Organization markup on every page?

No. Describe the organization once, usually on the home page, and reference it from other markup where needed. Repeating a full block everywhere adds maintenance work and more chances for contradictions.

Which properties are required?

None are strictly required, according to Google's documentation. Google recommends including as many relevant properties as you can support, such as name, address, telephone and logo.

Does organization markup set my site name in search results?

Not by itself. Site names are driven mainly by WebSite structured data on the home page, together with other signals such as headings and og:site_name.

Sources

• Organization structured data, Google Search Central
• General Structured Data Guidelines, Google Search Central
• Site names in Google Search
• Organization Schema Explained, Search Engine Land
• Google logo schema gains ImageObject type support, Search Engine Land
• What Structured Data To Use And Where To Use It, Search Engine Journal
• Structured Data in the AI Search Era, BrightEdge
• Organization, Schema.org
• Structured data and rich snippet display, SEO Declarations
• How to Structure Content for Machine-Readability and AI Extraction

Recommended

• B2B Schema Markup: Structured Data for Brand Health
• Entity SEO for Marketing Teams: Turn Brand Signals Into Audi
• Brand Audit Checklist & Template (Free, 40 Checks)