In short. Organization structured data uses Schema.org properties to describe organizational identity, with Google documenting placement, property and validation guidance.

Definition: Organization structured data is machine-readable markup that describes an organization using Schema.org's Organization type and its properties. It records identity information such as the organization's name, website and logo.

Key facts

Schema.org's Organization definition covers organizations such as schools, corporations and clubs.
As of 17 October 2026, Google's Organization guide describes uses for distinguishing organizations in Search and influencing displayed logos; it specifies no required properties for the general type.
Google's structured data introduction recommends JSON-LD, a notation embedded in an HTML script element, where the site's setup allows it.
Google's AI features guidance says that AI Overviews and AI Mode require no special Schema.org structured data.

Which identity details does the markup describe?

Schema.org's property definitions distinguish name, the item's name, from legalName, the organization's official registered name. The url property identifies the item's web address. The sameAs property points to a reference page that unambiguously identifies the same entity, with Wikipedia and Wikidata given as examples.

Google's Organization example includes the following fields. This shortened version retains its illustrative company name and URLs:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Example Corporation",
  "url": "https://www.example.com",
  "logo": "https://www.example.com/images/logo.png"
}
</script>

The same guide recommends properties relevant to the organization, including an address or telephone number where applicable. Its sameAs guidance gives an organization's social media or review-site profile as an example. These links describe identity relationships between pages and the organization.

Where does the markup belong?

Google's placement guidelines recommend the home page or a single page describing the organization, such as an About page. Repeating the information on every page is unnecessary. The guide recommends the most specific applicable subtype: OnlineStore for an ecommerce site, or an appropriate LocalBusiness subtype for a physical shop or restaurant. A subtype is a more specific category within the broader type.

Google's structured data policies require markup to represent the page's content truthfully. Information must remain current, and content described in the markup must be visible to readers. For example, the policies require a performer described in markup to also appear in the page's HTML body.

How is the implementation checked?

Google's implementation instructions call for validation with the Rich Results Test and correction of critical errors. After deployment, URL Inspection checks how Google sees the page, including whether robots.txt, a noindex directive or login requirements block access.

Google's general policies explain that automated tools catch most technical errors, while quality requirements are harder to test automatically. A review therefore also compares the marked-up identity details with the visible page and checks their accuracy.

FAQ

Is Organization markup required for Google's AI search features?

Google's AI features documentation sets eligibility around an indexed page that can appear in Search with a snippet. It specifies no additional technical requirements and no special Schema.org markup for AI Overviews or AI Mode.

What should I check before adding a logo URL?

Google's logo guidance requires an image at least 112 by 112 pixels and a crawlable, indexable image URL. Check that your logo remains legible on a white background, as the same guidance recommends.

Sources

Check how a page reads to answer engines. Open the GEO score analyzer