SEO · Free tool
Organization Schema Generator
Build the Organization JSON-LD block that anchors your Google knowledge panel. Includes sameAs social profile links and a customer contact point.
Paste into <head>
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Organization",
"name": "Example Pvt Ltd",
"url": "https://www.example.in",
"logo": {
"@type": "ImageObject",
"url": "https://www.example.in/logo.png"
},
"foundingDate": "2018-03-15",
"contactPoint": {
"@type": "ContactPoint",
"telephone": "+91-22-26200012",
"contactType": "customer support",
"areaServed": "IN"
},
"sameAs": [
"https://www.linkedin.com/company/example",
"https://twitter.com/example",
"https://www.crunchbase.com/organization/example"
]
}
</script>sameAs is the strongest entity signal
The sameAs array tells Google which external profiles represent the same entity as your site. The richer this list — LinkedIn, X / Twitter, Wikipedia, Crunchbase, Companies House, the GST portal — the faster Google triangulates your identity and the more confidently it builds your knowledge panel.
Place this on every page
Organization schema should sit in a shared layout, not just the homepage. Repeating it across every page reinforces the entity to crawlers without violating any guideline. Pair this with the LocalBusiness schema generator if you have a physical address, and the breadcrumb schema generator to round out site-wide structured data. See Organization schema best practices for Indian sites for the full pattern.
Logo rules to follow
- Absolute URL, publicly fetchable (no auth).
- PNG or JPG (SVG support is patchy).
- Recommended 112–1200 px on the long edge, square or near-square.
- Should match the logo that appears in your Google knowledge panel.
FAQ
What is the sameAs property for?
sameAs links your organization to authoritative external profiles - LinkedIn, Twitter / X, Wikipedia, Crunchbase, GST portal. It is a primary signal Google uses to build your knowledge panel.
Should Organization schema only go on the homepage?
No. Place it in every page via a shared layout. Multiple instances of the same Organization schema across the site reinforce entity recognition without violating any guideline.
What goes in the logo property?
An absolute URL to a square-ish PNG / JPG (recommended 112x112 to 1200x1200, max 12 MB). Avoid SVG - Google still has patchy support. The logo must match what appears in your knowledge panel.