Put your full Organization markup in one place: the home page, or one page that describes the organization, such as an About page. Google's Organization documentation recommends that placement and says the markup does not need to appear on every page.
Every other page can point back to that organization by its @id. An article names it as publisher, and a service page names it as provider, so the whole site describes one organization instead of several slightly different copies.
Start by choosing the page that will hold the full entity, then give it a stable @id and connect your articles and services to it. Before you add anything, check what your theme, SEO plugin or platform already prints, because many of them add an Organization node on their own.
What Google recommends for Organization placement
Google's Organization structured data documentation tells site owners to add the markup to the home page or to a single page that describes the organization. It also says you do not need to include it on every page. That is the rule to build on, and it holds whether your site is a five-page brochure or a store with thousands of product pages.
The same documentation lists no required properties for the general Organization feature. It recommends adding the ones that apply to you: name, url, logo, sameAs, address, telephone, email and description. Google says this markup can help it understand and disambiguate an organization, and that it may influence visual elements such as a logo or a knowledge panel. Eligibility does not guarantee that Google will show any of them.
Two details are worth knowing before you write code. First, Google recommends the most specific applicable subtype, such as LocalBusiness or OnlineStore, where it accurately describes the business. Second, the logo file must be crawlable and indexable, and Google's guidance gives a minimum logo size of 112 by 112 pixels.
Google's general structured data guidelines add the condition that applies to every example below: the markup has to describe information that visitors can see on the page. Google recommends JSON-LD as a supported format, and it says structured data makes a page eligible for a feature without guaranteeing that the feature appears.
If your site represents one individual rather than a company, such as a consultant's personal portfolio, Person is the better type. The Person schema generator builds that markup, and an agency or freelancer presented as a business can use Organization.
When another page should reference the organization
A page needs a link to your organization only when something on it is connected to that organization. The common connections are a publisher on an article, a provider on a service, a brand on a product or service, and an owner relationship. A contact page or a plain legal page that does not describe any such entity can carry no Organization markup at all.
publisher names who published a creative work, and provider names who supplies a service. Schema.org describes these as vocabulary relationships, not Google display requirements: see the definitions of publisher, provider and brand. Each can point to an Organization or a Person, so the relationship stays accurate even when the author of a post is an individual.
Some plugins print the full Organization node on every page. Yoast, for example, prints a connected graph on every page, and the Organization node in it is tied to the rest of the graph with @id references. That is consistent with Google's guidance as long as every copy uses the same @id and the same facts.
If you build by hand, you get to choose. One full definition plus lightweight references is the simplest arrangement to maintain, because a change to your logo or name happens in one file. The Organization schema guide covers which properties belong in that definition.
Define the organization once with a stable @id
An @id is a stable identifier for an entity in JSON-LD, and other entities use it to refer to the same thing. The usual pattern is a URL on your own domain with a fragment, such as https://example.com/#organization. Pick it once and never change it, because every page that points at the organization depends on that exact string.
The block below is displayed teaching code with fictional facts on a reserved example domain. Replace the name, the URLs, the description and the contact details with the facts that appear on your own page, and delete any property you cannot back with visible content. Do not paste the example values into a live page.
{
"@context": "https://schema.org",
"@type": "Organization",
"@id": "https://example.com/#organization",
"name": "Example Technology Group",
"alternateName": "Example Tech",
"url": "https://example.com/",
"logo": "https://example.com/images/logo.png",
"description": "Example Technology Group publishes software education resources.",
"email": "hello@example.com",
"telephone": "+1-555-010-0123",
"sameAs": [
"https://social.example.org/example-technology-group"
]
}If you would rather fill in a form than edit JSON by hand, the Organization schema generator produces the same kind of block, and you can then add the stable @id yourself. For the sameAs property, which lists profiles that belong to the same organization, the entity SEO and sameAs guide explains what to include.
Where a narrower type describes the business, use it in place of plain Organization. A shop with one street address can use the most specific LocalBusiness subtype; the local business schema guide walks through that setup. A business with several locations gives each location its own entity and @id, then connects them to the parent organization, which the multiple locations guide covers. An online store can use OnlineStore.
Point other pages to it with publisher and provider
On an article page, the Article entity refers to the organization instead of repeating it. The example below uses an Article that names the organization as both its author and its publisher. Replace the URLs, the headline and the description with the real values on that page, and set datePublished and dateModified to the real dates shown there.
{
"@context": "https://schema.org",
"@type": "Article",
"@id": "https://example.com/resources/example-guide/#article",
"url": "https://example.com/resources/example-guide/",
"headline": "Example Guide",
"description": "A fictional guide published by Example Technology Group.",
"datePublished": "2026-07-15",
"dateModified": "2026-07-15",
"author": {
"@type": "Organization",
"@id": "https://example.com/#organization"
},
"publisher": {
"@id": "https://example.com/#organization"
}
}Google's Article structured data documentation lists recommended properties for the Article feature rather than required ones, so populate the ones your page really shows. If the author is a named person, point author at a Person instead; the Article schema generator builds the whole entity.
A service page works the same way with provider. Google has no dedicated Service rich-result feature in its list of search appearances, so there are no Google-specific properties to claim here. The code is still valid Schema.org vocabulary when the facts are accurate and visible on the page, and the Service schema generator can build it.
{
"@context": "https://schema.org",
"@type": "Service",
"@id": "https://example.com/services/example-service/#service",
"name": "Example Website Review",
"description": "A fictional website review service.",
"url": "https://example.com/services/example-service/",
"provider": {
"@id": "https://example.com/#organization"
},
"areaServed": "US"
}A reference like "@id": "https://example.com/#organization" carries only the identifier. If you want a page's own markup to state the organization's name as well, add name and url beside the @id, or let your plugin print the full node on that page. Either way, keep the identifier and the facts identical to the definition.
When one page holds several entities, such as an Article, a WebPage and the organization, put them together in a single @graph array so they are one connected document. The Schema graph builder assembles those connections, and the JSON-LD examples guide shows more complete samples. The JSON-LD format itself is specified by the W3C as JSON-LD 1.1.
Pick the placement for your site type
A small brochure site gives the full Organization, or a specific LocalBusiness subtype, to the home page or the About page, and references it from other pages when a relationship exists. A local business with one location does the same with the most specific LocalBusiness subtype on the location page or the home page, keeping the address, phone and opening information accurate.
An online store uses the most specific applicable organization type, such as OnlineStore, on the home page or an organization page. Use brand, seller and product relationships where they describe the page. A publisher or blog defines the publishing organization once and references it as publisher from each Article or BlogPosting.
A service business defines the organization once and references it as provider from each Service entity, adding service markup only on pages that describe that service. A software company defines the organization on the home or About page and connects software, service or article entities with publisher, provider or brand.
A multilingual site keeps one consistent organization identity across its language versions. Translate the visible names and descriptions where it makes sense, but keep the stable identifiers and the relationships the same in every language.
Check what your platform already outputs
Before adding a block, view the rendered page source and look for JSON-LD that is already there.
- Yoast SEO for WordPress: outputs a connected graph on every page that includes an Organization or Person node, WebSite, WebPage and the page's main entity, linked with
@idrelationships, according to the Yoast schema specification. - Rank Math for WordPress: says it adds Organization schema by default when the site represents an organization, in its rich snippets documentation.
- Squarespace: says it automatically generates Organization, Blog post, Event, Local business, Product and WebSite schemas and that these built-in schemas cannot be edited or removed, in its SEO features article.
- Wix: says it creates Local Business markup for the homepage when a business name and location are configured, and offers preset markup and manual JSON-LD controls, in its structured data documentation.
- Webflow: allows schema per page, including Collection pages, and recommends keeping schema in one place to avoid duplicates, in its schema markup help article (updated January 27, 2026).
- HubSpot: enables BlogPosting structured data by default for blogs created after August 4, 2022, and warns against turning its structured data on when custom schema already exists, in its blog template settings.
- Next.js: has no Organization default. Its JSON-LD guide (updated February 27, 2026) shows rendering JSON-LD in a
layout.jsorpage.jscomponent and validating it with Google's Rich Results Test or the Schema Markup Validator. - Shopify: its theme requirements call for Google rich product snippets in themes. Organization output depends on the theme and any apps you have installed, so check the source.
WordPress core itself leaves the defaults to your theme, SEO plugin or schema plugin. If you are working on WordPress, the WordPress schema markup guide covers the installation routes and how to avoid a second block.

Two Organization blocks with different names, logos or URLs can give conflicting descriptions of the same business. Open the page source, search for application/ld+json, and count the blocks that describe your organization. If you find two, keep the one from the source you control, switch the other off in its plugin or theme setting, and make sure the survivor holds your correct facts.
You can also list the Organization nodes from the browser console. This snippet reads every JSON-LD block on the current page, flattens any @graph, and prints the @id of each node whose type is exactly Organization. A node typed as a subtype such as LocalBusiness will not appear in this list, so scan the source for subtype names as well.
const nodes = [...document.querySelectorAll('script[type="application/ld+json"]')]
.flatMap((s) => {
try {
const data = JSON.parse(s.textContent);
return data['@graph'] || [data];
} catch (e) {
return [];
}
});
console.log(nodes
.filter((n) => [].concat(n['@type']).includes('Organization'))
.map((n) => n['@id'] || '(no @id)'));Make the Organization markup readable for Bing and AI search
Bing processes Schema.org in JSON-LD, Microdata and RDFa, so the same block serves both Google and Bing (Bing's structured data guidance). Its Webmaster Guidelines say structured data must accurately reflect visible content. Microsoft documents Copilot web grounding as relying on content indexed by Bing (Copilot web access page), and DuckDuckGo results can draw on Bing, so Bing Webmaster Tools is the validation path for both.
If you want ChatGPT Search to reach the page, allow OAI-SearchBot (OpenAI crawler documentation); Perplexity publishes crawler guidance for its crawler. Google says AI features need no special Schema.org markup (AI features documentation), which is no reason to add or remove Organization markup. Yandex offers a structured data validator. For more, see whether AI systems use schema markup.
Validate and find duplicate Organization markup
Run the checks in this order. First confirm the JSON is valid and the right blocks are in the rendered source, then test the vocabulary and the feature, then test the engines you care about. Google's Rich Results Test checks eligibility for Google's features, and the Schema Markup Validator checks vocabulary rather than Google eligibility, so a clean result from one does not stand in for the other.
For Bing, the URL Inspection tool includes a Markup card that reads JSON-LD and other formats. For Yandex, use its validator linked above. Schema Nova's own schema validator checks pasted JSON-LD syntax and structure, and the schema checker reads a page's retrieved HTML.

Valid markup does not guarantee a rich result, a knowledge panel or an AI citation, and the markup has to describe what the page visibly shows. The guide on whether schema markup helps SEO explains what structured data can and cannot be expected to do.
Check again after any change to your theme, SEO plugin, CMS or page template, because those are the usual places for a second Organization block to appear. A sensible habit is to view the source of your home page, one article and one service page after each such change and confirm there is still exactly one definition of the organization.
Questions people ask
Should article pages repeat the full Organization object?
No. Define the organization once and reference its @id as the Article's publisher. If your SEO plugin prints the full node on every page by design, that is acceptable as long as every copy carries the same @id and the same facts.
What is the difference between Organization and LocalBusiness schema?
LocalBusiness is a narrower subtype of Organization for a business with a physical presence, such as a shop or office. Google recommends the most specific applicable subtype, and its LocalBusiness feature asks for name and address. Use plain Organization when there is no physical location to describe.
Does Organization schema guarantee a knowledge panel?
No. Google says the markup can help it understand and disambiguate an organization and may influence visual elements such as a logo or knowledge panel, and it also says eligibility does not guarantee that a feature will be shown. Keep your facts accurate and consistent and treat any display as a possible outcome.
Does Google require Organization schema for AI Overviews?
Google says AI features need no special Schema.org markup and that structured data should match visible text. Organization markup remains useful for ordinary Search eligibility and for other engines that document their own support. Do not add or remove it solely because one provider says it does or does not use it.
What should a multilingual site do with Organization schema?
Keep one consistent organization identity across language versions. Localize the visible names and descriptions where it makes sense, and keep the stable @id and the relationships the same in every language.
