Organization Schema: What Google Uses It For — and What AI Assistants See
Organization markup is useful for Google: it can help Google understand your organization and influence which logo appears in Search results and your knowledge panel. For ChatGPT and Claude, what counts is the visible text on your page. Your company name, address and contact details belong in the HTML where people can read them — the markup should repeat exactly that.
What is Organization Schema?
Schema.org Organization is a structured data type that describes a company, nonprofit, institution, or other organization. You place it as a JSON-LD block on your homepage or on a page that describes your organization, such as your About page.
Subtypes are available for more specific organizations: LocalBusiness, Corporation, EducationalOrganization, NGO, and more. Google recommends using the most specific schema.org subtype of Organization that matches your organization.
Why Organization Schema — and Where It Helps
For Google. According to Google's documentation, Organization markup on your homepage can help Google:
- Understand and disambiguate your organization. Google says the markup can help it understand your organization's administrative details and disambiguate your organization in search results.
- Choose your logo. Some properties can influence visual elements, such as which logo is shown in Search results and your knowledge panel.
- Show merchant details. Merchants can influence more details in their merchant knowledge panel and brand profile, such as return policy, address, and contact information.
Google also states that it does not guarantee that features that consume structured data will show up in search results.
For ChatGPT and Claude. When they fetch your page live, they do not see the JSON-LD (see the box above). Whatever you want them to know about your organization must be in the visible text: name, address, phone, email, what you do.
For Gemini. Via the API, Gemini received the JSON-LD in the study, but treated it like an ordinary sentence. If markup and visible text disagree, a model may pick up the wrong version — so keep both identical.
What we don't know. Whether Perplexity, training crawlers (GPTBot, ClaudeBot) or Google AI Overviews use Organization markup has not been examined. We make no claims about them.
JSON-LD Code Snippet
Add this block to the <head> of your homepage (or of a single page that describes your organization). Google says you don't need to include it on every page of your site. Every value should also appear as visible text on your site, for example in the footer or on your About or contact page.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Organization",
"name": "Your Company Name",
"url": "https://example.com",
"logo": "https://example.com/logo.png",
"description": "A concise description of what your organization does — 1 to 2 sentences, plain text only.",
"foundingDate": "2020",
"contactPoint": {
"@type": "ContactPoint",
"telephone": "+49-123-456789",
"contactType": "customer service",
"availableLanguage": ["English", "German"]
},
"address": {
"@type": "PostalAddress",
"streetAddress": "Musterstraße 1",
"addressLocality": "Berlin",
"postalCode": "10115",
"addressCountry": "DE"
},
"sameAs": [
"https://www.linkedin.com/company/your-company",
"https://twitter.com/yourcompany",
"https://www.facebook.com/yourcompany",
"https://en.wikipedia.org/wiki/Your_Company"
]
}
</script>Google lists no required properties for Organization; it recommends adding as many properties as are relevant to your organization.
The sameAs Property
Google describes sameAs as the URL of a page on another website with additional information about your organization — for example, your profile on a social media or review site. You can provide multiple URLs. Typical candidates:
- LinkedIn company page
- Twitter/X profile
- Facebook page
- Wikipedia article (if one exists)
- Wikidata entity (e.g.
https://www.wikidata.org/wiki/Q12345) - Crunchbase profile (for startups and tech companies)
- GitHub organization (for software companies)
Only list profiles that you actually maintain. If these profiles matter to you, also link them visibly on your site, for example in the footer.
Step-by-Step Implementation
- Prepare your logo. Google's requirements: at least 112×112 px, the image URL must be crawlable and indexable, and the file format must be supported by Google Images. Check that the logo looks right on a plain white background.
- Put the facts on the page. Make sure name, address and contact details are visible on your site (footer, About or contact page). The markup repeats these facts — it does not replace them.
- Collect your sameAs URLs. Use canonical profile URLs (e.g.
https://www.linkedin.com/company/your-company, not a short link). - Write the JSON-LD. Fill in the template above with your actual data. Remove properties (like
address) that do not apply to your organization. Copy values exactly as they appear in your visible text. - Place it on your homepage. Add the script block to the
<head>section. In WordPress: use Yoast SEO's Organization settings or a plugin like Schema Pro. - Validate. Run your homepage URL through the Google Rich Results Test and fix any critical errors; the Schema Markup Validator checks general schema.org syntax.
- Check in Search Console. Use the URL Inspection tool on your homepage to see how Google sees the page.
Common Mistakes
- Information only in the schema, not visible on the page. ChatGPT and Claude do not see the JSON-LD when fetching a page live. An address or phone number that exists only in the markup is invisible to them.
- Markup differs from the visible text. Old phone number in the schema, new one in the footer: that kind of conflict misleads. In the study, Gemini Pro took the outdated answer from the (FAQ) markup 8 out of 20 times when it contradicted the visible text. Keep values identical.
- Logo URL not accessible. If the logo URL returns a 404, redirects, or requires cookies, it is not crawlable. Test the URL directly in a private browser window.
- Logo too small. Google requires at least 112×112 px.
- Short links in sameAs. Use the full, canonical profile URL instead of redirects or short links.
- Placing Organization schema somewhere arbitrary. Google recommends the homepage or a single page that describes your organization, such as the About page.
- Description with HTML markup. The
descriptionfield must be plain text. HTML tags in JSON-LD string values are treated as literal characters, not markup. - Invalid JSON. A missing comma or a trailing comma breaks the whole block. Validate after every change.
- Not updating after rebranding. If you change your name, logo, or social profiles, update the visible text and the markup at the same time.
Official Sources
- Rick Ramos (14 Oct 2026) — Schema markup gives AI assistants nothing plain text doesn't
- Google Search Central — Organization structured data
- Schema.org — Organization type definition
- Google Rich Results Test
- Schema Markup Validator