Organization schema markup is a block of structured JSON-LD code you place in the <head> of your homepage (or a dedicated about page) that explicitly tells Google, Bing, and AI engines who your organization is. It uses the schema.org/Organization vocabulary to label your name, URL, logo, contact details, and social profiles in a machine-readable format. The result: faster entity disambiguation, stronger eligibility for logo display and knowledge panels in Google Search, and a more reliable signal for AI engines that pull your brand details into generated answers.
Unlike most schema types, Organization markup does not unlock a specific “rich result” feature with visual decorations in the SERP. Google is direct about this in its structured data documentation: it helps Google “better understand your organization’s administrative details and disambiguate your organization in search results,” with some properties working behind the scenes. The payoff is less about a flashy search snippet and more about foundational entity clarity that compounds across every other signal you build.
This guide covers what to include, how to write valid JSON-LD, how to test it with Google’s Rich Results Test, and why this 10-minute implementation has become one of the first steps in any AI search visibility strategy.
What Organization schema markup actually does
Organization schema markup gives Google and AI crawlers an unambiguous identity record for your business. Without it, search engines must infer who you are by stitching together clues from your page text, inbound links, and third-party mentions. With it, you hand them a structured declaration: this is the legal name, this is the logo, these are the authoritative social profiles. That explicit signal reduces the risk of your brand being confused with a similarly-named entity or omitted from an AI answer where it should appear.
On the Google side, the schema can influence which logo appears in knowledge panels and search results, support disambiguation across the Knowledge Graph, and contribute to entity recognition in AI Overviews. On the AI engine side, systems like ChatGPT (via Bing) and Perplexity crawl pages for structured signals when building brand profiles. A well-formed Organization block is one of the cleaner signals they can parse reliably.
Importantly, Google specifies that there are no required properties for Organization structured data. Every property you add is incremental signal. That said, there is a practical minimum that makes the markup meaningful.
The properties that matter most
Not every property listed on schema.org carries equal weight. Based on Google’s Organization structured data documentation, these are the ones worth implementing:
Identity properties
@type: Use the most specific subtype that fits.Organizationis the generic fallback; for most businessesLocalBusiness,OnlineStore,Corporation, or a more granular type likeMedicalBusinesswill be more accurate. The more specific the type, the clearer the entity signal.name: Your organization name as it appears publicly. This should match your site name exactly.legalName: The registered legal entity name if it differs from the trading name. Useful for disambiguation.url: Your canonical homepage URL.description: A concise description of what your organization does.
Logo and visual identity
logo: An ImageObject or direct URL pointing to your logo. Google’s specification: the image must be at least 112x112 pixels, crawlable and indexable, and render legibly on a white background. This is the property that controls which logo Google displays in knowledge panels and branded search results.
Contact and location
email: Primary contact email.telephone: Phone number including country and area code.address: APostalAddressobject coveringstreetAddress,addressLocality,addressRegion,postalCode, andaddressCountry.areaServed: The geographic region you serve, especially relevant for local SEO and service-area businesses.
Social and cross-platform presence
sameAs: An array of URLs pointing to your authoritative profiles: LinkedIn, Twitter/X, Facebook, Crunchbase, Wikipedia, Wikidata, and any industry directories. This is the property that most directly connects your Organization entity across the web and supports Knowledge Graph disambiguation.
Business context
foundingDate: Year founded in YYYY or YYYY-MM-DD format.numberOfEmployees: AQuantitativeValueobject. Useful for B2B entities where company size matters.naics: The North American Industry Classification System code for your sector, if applicable. Google includes it as an optional property that supports industry categorization.
How to write Organization schema markup in JSON-LD
Google recommends JSON-LD over Microdata and RDFa because it is easier to maintain and can be injected dynamically without touching HTML structure. Place the script block in the <head> of your homepage or your primary “About” page.
Here is a complete, annotated example for a mid-sized SaaS company:
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Corporation",
"name": "Acme Software",
"legalName": "Acme Software Pty Ltd",
"url": "https://www.acmesoftware.com",
"description": "Acme Software builds project management tools for distributed engineering teams.",
"logo": {
"@type": "ImageObject",
"url": "https://www.acmesoftware.com/images/logo.png",
"width": 300,
"height": 112
},
"foundingDate": "2018",
"email": "hello@acmesoftware.com",
"telephone": "+61-2-1234-5678",
"address": {
"@type": "PostalAddress",
"streetAddress": "Level 5, 123 Collins Street",
"addressLocality": "Melbourne",
"addressRegion": "VIC",
"postalCode": "3000",
"addressCountry": "AU"
},
"sameAs": [
"https://www.linkedin.com/company/acme-software",
"https://twitter.com/acmesoftware",
"https://www.crunchbase.com/organization/acme-software"
]
}
</script>A few implementation notes:
- Use
"@type": "Corporation"for incorporated businesses,"LocalBusiness"for businesses with a physical location serving a local area,"OnlineStore"for ecommerce, and"NGO"for nonprofits. The generic"Organization"type is a fallback when no specific subtype fits. - The
sameAsarray is where the entity-building work happens. Add every platform where your organization has a verified or authoritative profile. Wikidata entries and Wikipedia pages carry the strongest disambiguation weight. - If your business has multiple locations, use a single Organization block on the homepage and separate
LocalBusinessblocks on individual location pages. Do not replicate the same address block across hundreds of pages.
How to test with Google Rich Results Test
Testing Organization schema is a two-minute step that should happen before and after any deployment. The Google Rich Results Test is the official validator. It accepts either a live URL or pasted code, which means you can test in a staging environment before pushing to production.
How to use it
- Navigate to search.google.com/test/rich-results.
- Enter your homepage URL or paste your JSON-LD directly into the code input.
- Click “Test URL” or “Test code.”
- Look for “Organization” in the detected items. If it appears without errors, the markup is valid.
- Errors shown in red need to be fixed before deployment. Warnings in orange are non-blocking but worth addressing.
One important clarification: Organization markup does not produce a visual rich result preview in this tool the way a Recipe or FAQ schema does. The tool will confirm validity and detect the type, but you will not see a rendered SERP preview. That is normal. The value is entity signal, not a visual enhancement.
After your page is live, monitor it in Google Search Console under the “Enhancements” section. If Google can’t crawl your logo image or finds a property value mismatch, it will surface that as a coverage warning.
Organization schema and AI citations
AI engines, including ChatGPT (which uses Bing’s web index), Perplexity, and Google’s AI Overviews, build entity profiles from multiple signals: Wikipedia, Wikidata, authoritative directories, and direct page crawls. Organization schema markup is one of the cleaner machine-readable inputs into that process because it explicitly declares your identity in a format designed for automated parsing.
The sameAs property is the most direct lever here. By linking your Organization entity to Wikidata, Wikipedia, LinkedIn, Crunchbase, and industry databases, you are connecting your on-site declaration to the off-site entity graph that AI systems draw from. A brand that exists in Wikidata with a matching sameAs reference in its Organization schema is significantly harder to confuse or omit than one that relies solely on unstructured text.
The description property also matters. AI engines that crawl pages sometimes pull the schema description directly when constructing brand summaries. Keep it factual, specific, and free of marketing language. A description like “Acme Software builds project management tools for distributed engineering teams” is more useful to an AI system than “Acme Software empowers teams to achieve their full potential.”
For brands working on broader entity SEO strategy, Organization schema is the foundation. It does not replace building real-world citations, earning editorial mentions, or creating topically authoritative content. But without a clean entity declaration, all of that off-page work has to fight through ambiguity before it compounds into visibility.
You can track whether AI engines are picking up your brand accurately, and whether your schema changes are having an effect, using Fokal’s AI visibility monitoring.
Common mistakes to fix
Using generic Organization when a subtype applies. If you are a local business, use LocalBusiness. If you run an online store, use OnlineStore. Specificity improves entity classification and helps search engines serve your listing in the right contexts.
Empty or partial sameAs arrays. Adding only one social profile misses the point. The value of sameAs is the web of cross-references. Aim for five or more authoritative profiles, prioritizing platforms Google and AI engines trust: LinkedIn, Wikidata, Wikipedia (if applicable), Crunchbase for tech companies, and relevant industry directories.
Logo images that fail Googlebot crawl. Your logo URL must be publicly accessible with no authentication or geo-blocking. Check it by fetching the URL in an incognito browser and confirming it resolves. If you are using a CDN that blocks certain crawlers, add Googlebot and Bingbot to the allowlist.
Placing Organization schema on every page. One well-formed block on your homepage is correct. Duplicating it across dozens of pages with slightly different values introduces conflicting signals. If you run a multi-location business, the Organization block on the homepage should describe the parent entity; location-specific pages use LocalBusiness markup with a parentOrganization reference back to the main entity.
Not updating schema after business changes. If you move offices, rebrand, or acquire new companies, the schema needs to reflect reality. Stale markup with old addresses or inactive social profiles actively undermine entity accuracy.
Organization schema as part of a broader AI strategy
Organization schema is a five-to-ten minute implementation that pays dividends for years. It is not a ranking factor in the traditional sense. Google has been explicit: it does not promise rich results for Organization markup, and the primary benefit is disambiguation and entity accuracy rather than a visible SERP decoration.
But in the context of AI search optimization, entity clarity is the foundation everything else is built on. AI engines that confidently know who you are and what you do are more likely to include you in brand comparisons, product recommendations, and category answers. Ambiguity is what keeps brands invisible in AI-generated responses even when they are the right answer.
Pair your Organization schema with a complete schema markup strategy, a strong sameAs entity graph, and ongoing content that builds topical authority. The AI SEO hub covers the full stack. For entity-specific work including knowledge panel optimization and Knowledge Graph signals, the entity SEO guide goes deeper.