Organization Schema Generator

Build a complete Organization JSON-LD block — name, logo, URL, postal address, contact points, and sameAs social profile links — in seconds. Supports Organization, Corporation, and EducationalOrganization subtypes. The output is a ready-to-paste <script type="application/ld+json"> tag that helps Google identify and display your brand entity in knowledge panels.

Postal address
Contact points

How to use the Organization Schema Generator

Select the organization subtype (Organization, Corporation, or EducationalOrganization). Fill in name and URL at minimum — those are required for Google to resolve the entity. Add a logo (PNG or SVG, at least 112×112 px, max 1 MB) to populate the knowledge panel. Under Postal address, enter the full mailing address — Google uses this to match the entity in Maps. Under Contact points, click "+ Add contact point" for each department: telephone (+1-800-000-0000 format), contact type, area served, and available language. In sameAs, list every official social profile and Wikipedia/Wikidata URL — one per line. Click Generate, then copy the output into your site's <head> or a JSON-LD <script> block. Validate in Google's Rich Results Test before deploying.

What Organization schema does

Organization schema (schema.org/Organization) is a JSON-LD vocabulary entry that tells search engines who you are as an entity — not just what a particular page is about. Google uses it to build and confirm knowledge-panel cards, surfacing your name, logo, website, contact details, and social profiles directly in search results without the user clicking through.

The sameAs array is especially powerful: linking your schema to Wikipedia, Wikidata, official social media accounts, and Google Business Profile accelerates entity disambiguation — the process by which Google matches your brand name to a canonical entity in its Knowledge Graph. Without it, Google must infer your entity from co-citation signals, which can take months.

Use Corporation when the entity is a for-profit legal person; EducationalOrganization for universities, schools, and training providers (which unlock additional rich-result eligibility). The contactPoint array maps customer-service, sales, and technical-support telephone numbers — Google may surface these in knowledge panels and local service ads. Omit any field you don't fill; the generator strips empty values automatically.

Common use cases

  • Knowledge panel verification — Supply name, url, logo, and sameAs to give Google all it needs to show a branded knowledge panel in search results.
  • Corporation entity registration — For-profit companies use the Corporation subtype; the contactPoint array surfaces customer-service numbers directly in SERPs.
  • University or school pages — EducationalOrganization schema unlocks course-rich-result eligibility and links academic profiles in knowledge panels.
  • Multi-department contact routing — List separate contactPoints for sales, support, and billing — Google may show a "Call" shortcut for each in mobile search results.
  • Social-profile consolidation — Declaring all official profiles in sameAs prevents Google from attributing unofficial fan pages or imposters to your brand entity.

Frequently asked questions

Do I need Organization schema on every page?
No. Put it once in your site-wide layout (usually the footer or the homepage <head>). Repeating it on every page is harmless but wasteful.

What logo size does Google require?
Google recommends at least 112×112 px for the knowledge-panel logo and prefers a square or near-square image. The file must be reachable by Googlebot and served over HTTPS.

Is Organization schema the same as LocalBusiness schema?
No. LocalBusiness (a subtype of Organization) adds physical location properties like openingHours and geo coordinates and is used for brick-and-mortar businesses. Pure Organization is better for companies without a public storefront.

How many sameAs URLs should I list?
Include every authoritative profile: Wikipedia, Wikidata, major social networks (Twitter/X, LinkedIn, Facebook), GitHub, Crunchbase, etc. More is better — each co-reference strengthens entity confidence. Remove any that you don't control.

Why does the contactType need a specific value?
Google's parser recognizes a fixed vocabulary: customer service, technical support, billing support, bill payment, sales, reservations, credit card support, emergency. Use these exact phrases (lowercase).