Organization schema is structured data based on the Schema.org Organization type that describes the entity behind a website: its official name, logo, address, contact points, identifiers and links to its profiles elsewhere on the web. In structured data for SEO, it is the markup that tells search engines who publishes a site, as opposed to what a single page is about.
Search engines use Organization schema to disambiguate the entity, connect the website to the same organization mentioned on other sites, and choose details such as the logo shown in search results or facts shown in a knowledge panel. The markup is usually written in JSON-LD and placed on the home page or an about page, not repeated with different values across the site.
How Organization schema describes an entity
Organization schema describes an entity through a set of properties with defined meanings. Each property maps a piece of information, such as a legal name or a telephone number, to a vocabulary that machines interpret the same way on every site, which removes the guesswork of extracting facts from free text.
A key technique is the @id identifier, a stable URL-like value such as the home page address followed by a fragment. Other markup on the site, for example the publisher of an article or the seller of a product, can reference this identifier, so all pages point to one consistent organization node rather than many partial copies.
The sameAs property links the organization to its official profiles, such as social media accounts, a business register entry or an encyclopedia page. These links help search engines confirm that the website and the external profiles refer to the same real-world entity.
Important properties and recommended values
Google currently lists no strictly required properties for Organization markup, but recommends adding every property that applies. The table below summarizes the most useful ones and practical guidance for each.
| Property | Content | Practical guidance |
|---|---|---|
| name | Common name of the organization | Match the name used on the site |
| legalName | Registered legal name | Use the exact form from the register |
| url | Official website address | Use the canonical home page URL |
| logo | Logo image URL | At least 112 by 112 pixels, crawlable |
| sameAs | Official external profiles | List only profiles the organization controls |
| address | PostalAddress object | Main or registered address |
| contactPoint | Contact type, phone, email | Separate entries for sales or support |
| Identifiers | VAT ID, LEI, DUNS, ISO 6523 code | Add those that genuinely exist |
Identifiers such as vatID, leiCode and duns are particularly valuable because they are unique and verifiable. They allow search systems to link the website to the same organization in public registers without relying on name matching, which often fails for common names.
Organization schema compared with related types
Organization is a broad parent type in Schema.org, and several more specific types inherit its properties. Choosing the most specific type that fits gives search engines more context without losing any Organization property.
| Type | Best suited for | Key difference |
|---|---|---|
| Organization | Companies, institutions, associations | General entity description |
| LocalBusiness | Businesses with a physical location | Adds opening hours and geo data |
| OnlineStore | Retailers selling online | Adds policies such as returns |
| NewsMediaOrganization | Publishers and newsrooms | Adds editorial policy properties |
| WebSite | The website itself | Describes the site name, not the entity |
| Person | Individuals behind personal sites | Used instead of Organization |
The distinction between WebSite and Organization is a frequent source of confusion. WebSite markup helps search engines choose the site name shown in results, while Organization markup describes the owner. Both can coexist on the home page, linked through the publisher property.
Implementing Organization schema
Implementation is simplest with a single JSON-LD block on the home page, generated from one central source of company data. Content management systems and SEO plugins often output basic Organization markup automatically, so the first step is to check what already exists and avoid conflicting duplicates.
- Collect verified facts: legal name, logo file, address, identifiers and official profiles.
- Choose the most specific type that accurately describes the organization.
- Assign a stable @id and reference it from article, product and website markup.
- Validate the markup with the Rich Results Test and the Schema Markup Validator.
- Review it after changes such as rebranding, relocation or new official profiles.
The markup must match the visible content and real facts. Claiming awards, ratings or profiles that do not belong to the organization violates structured data guidelines and can lead to a manual action that removes eligibility for rich results.
Limitations and common mistakes
Organization schema provides signals, not guarantees. Search engines decide independently whether to show a logo, which facts appear in a knowledge panel and whether to trust the stated profiles, and they weigh the markup against other sources.
| Mistake | Consequence | Correction |
|---|---|---|
| Several conflicting organization blocks | Ambiguous entity signals | Keep one node and reference it by @id |
| Logo blocked or too small | Logo not eligible in results | Use a crawlable image of sufficient size |
| sameAs to unofficial pages | Wrong entity associations | Link only controlled profiles |
| Outdated address or name | Inconsistent information | Update markup with business changes |
Another misconception is that Organization markup improves rankings directly. Its value lies in clarity and consistency of entity information, which supports trust and correct presentation rather than position for a given query.
A non-technical view
Organization schema is a small, hidden description of a company that a website gives to search engines. It says, in a format machines understand, who the company is: its name, logo, address, phone number and official social media pages.
It works like a business card handed directly to the search engine. Instead of guessing from the text on the page, the search engine reads the card and can show the right logo and details when people look for the company.
A concrete example
A mid-sized engineering firm shares its name with a clothing brand in another country. Searches for the firm sometimes show the wrong logo, and a knowledge panel mixes in social profiles of the other company.
The firm adds one Organization block to its home page with its legal name, registered address, VAT and LEI identifiers, a square logo of 512 by 512 pixels and sameAs links to its own professional profiles. Articles and job postings on the site reference the same @id as publisher and hiring organization. After the pages are recrawled, search results begin to show the correct logo, and the panel stops mixing in the unrelated brand.