In short. Place Organization structured data on the home page or one page that describes the organization.
Definition: Organization structured data describes an organization on the page that represents it. Google recommends placing it on the home page or on one page that describes the organization, such as an About Us page, rather than repeating the same markup across the site.
Key facts
- Google's Organization structured data documentation names the home page or a single organization-description page as the recommended location.
- Google says the markup describes the content of the page where the information applies, according to its introduction to structured data.
- The Organization guide has no required properties. It recommends properties that apply to the organization, including name, address or telephone, url, and logo.
- Google recommends JSON-LD when the site setup permits it. JSON-LD can be placed in an HTML head or body script element.
- Schema.org defines Organization as a type covering an organization such as a school, NGO, corporation, or club.
Which page should carry Organization markup?
Google's technical guidance recommends the home page or a single page that describes the organization, with an About Us page as its example. The same guidance says that the markup does not need to appear on every page. For a site with a clear organization-description page, that page is the documented alternative to the home page.
The choice is about the page's subject. Google's introduction to structured data describes structured data as in-page markup on the page to which the information applies, and says that the structured data describes that page's content. The Organization type itself is broad: Schema.org defines it as an organization such as a school, NGO, corporation, or club.
What should the markup describe?
The Organization node should describe the organization represented by the selected page. Google's general structured data guidelines say that structured data about information hidden from users or absent from the page's visible content is unsuitable, even when the information is accurate. The same guidelines say to include the main structured-data type that reflects the main focus of the page and to make structured-data items complete enough to represent the content visible to users.
Google's Organization guide says there are no required properties. It recommends adding properties that apply to the organization and focusing on useful details: name or alternateName for the business name, address or telephone for real-world presence, and url or logo for online presence. The guide also recommends the most specific Schema.org subtype that matches the organization, such as OnlineStore for an ecommerce site or a suitable LocalBusiness subtype for a local business.
Where does the code go in the HTML?
JSON-LD is a JavaScript notation inside a script tag. Google's format guide places it in the head or body of the HTML page, and says that Google can read it when JavaScript injects it into the page. Google recommends JSON-LD when it is the easiest format for the site's owners to implement and maintain. A minimal version matching Google's Organization example looks like this:
<head>
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Organization",
"url": "https://www.example.com",
"name": "Example Corporation"
}
</script>
</head>
Microdata is usually placed in the body, although Google documents that it can also be used in the head. RDFa is commonly used in both the head and body. These are HTML placement options; the page-selection rule remains the same.
How should the placement be checked?
Google's Organization documentation recommends validating the code with the Rich Results Test and fixing critical errors. It also recommends using URL Inspection after deploying a few pages with the markup. The selected page must be accessible to Google and free of restrictions from robots.txt, a noindex tag, or login requirements.
Google also says that finding and crawling a newly published page may take several days. The Organization guide recommends submitting a sitemap to keep Google informed of future changes.
Related terms
FAQ
Should you add Organization markup to every page?
No. Google recommends the home page or one page that describes the organization, such as an About Us page, and says the markup does not need to be on every page.
Can you put JSON-LD in the head of an About Us page?
Yes. Google documents JSON-LD inside a script element in the HTML head or body, and its Organization example uses an About Us page title with the script in the head.
Should you create a separate page only for the markup?
No. Google says structured data belongs on the page to which the information applies and advises against blank or empty pages created only to hold structured data.
Sources
- Google Search Central, "Organization Schema Markup", 8 September 2026
- Google Search Central, "Intro to How Structured Data Markup Works", 10 December 2025
- Google Search Central, "General Structured Data Guidelines", 10 July 2026
- Schema.org, "Organization", date not stated
Check how a page reads to answer engines. Open the GEO score analyzer