Organization schema
Organization marks up your company. The payoff is the knowledge panel on the right side of a branded search ("schemapreview.dev"), the favicon next to your listings, and proper attribution in Google's entity graph.
Required fields
- name — exact organisation name.
- url — canonical website URL.
Strongly recommended
- logo —
ImageObjector URL. Must be at least 112×112 pixels, PNG/JPG/GIF, and accessible without redirects. Without this, no favicon in the SERP. - sameAs — array of URLs pointing to your social profiles, Wikipedia, Wikidata, Crunchbase, etc. Critical for Google's entity reconciliation — it's how it knows your Twitter is yours.
- contactPoint —
ContactPointwithtelephoneandcontactType(customer service,sales, etc.). Used in some knowledge panels. - address —
PostalAddressfor your HQ. - description — short one-paragraph description.
Place this in your root layout
Organization schema usually goes in the site-wide template (header, layout, root layout) rather
than per-page, because it applies to the whole site. In Next.js App Router, put it in
app/layout.tsx; in WordPress, into header.php or a global block.
Pick the right subtype
Organization is generic. Use the specific subtype:
Corporation,NGO,EducationalOrganization,GovernmentOrganization,NewsMediaOrganizationLocalBusinessis technically a subtype too — see LocalBusiness for that case.
Common mistakes
- Logo URL behind a redirect. Google's crawler will not follow. Use the final URL directly.
sameAslinking to login-required pages. Use the public profile URL, not the admin URL.- Forgetting
url. Without it, Google can't tie the schema to a website at all. - Multiple Organization blocks on one page. Pick one, usually the most specific subtype.
CMS notes
- WordPress (Yoast, Rank Math): both emit Organization schema in site-wide mode. Don't add a second copy on the homepage.
- Next.js: inline
<script>inapp/layout.tsx. See the JSON-LD Next.js guide. - Webflow: custom code embed in site-wide head settings.
Generate it below
Last verified: 2026-05-15. Found something inaccurate? Email hello@schemapreview.dev.