A production-ready organization schema template provides the JSON-LD markup framework Google uses to identify your business entity, brand properties, and connections across the Knowledge Graph. We break down the mandatory fields, optional enrichments, and deployment patterns that turn a basic snippet into a strategic asset.
Google reads organization schema to decide which logo appears in search results, which social profiles to associate with your brand, and how to disambiguate your company from similarly named entities. Without it, Google guesses—pulling random images from your site, linking the wrong LinkedIn profile, or showing no brand panel at all.
The schema acts as a canonical declaration: "This is our legal name, this is our official logo, these are our verified channels." It feeds the Knowledge Graph, powers brand SERP features, and provides the entity anchor that LocalBusiness, Product, and Article schemas reference through the publisher or brand property. In markets like Ottawa, Toronto, or Montreal where multiple firms share similar names, explicit schema markup prevents entity conflation and ensures your branded queries return accurate, visually consistent results across devices.
The organization schema checklist starts with four mandatory fields: @context (always " @type (Organization or a subtype like Corporation), name (legal business name), and url (canonical homepage). Add logo as a fifth essential—Google requires a square or rectangular image URL, minimum 112×112 pixels, hosted on your domain.
From there, layer in contactPoint for customer service phone and type, address (PostalAddress with streetAddress, addressLocality, addressRegion, postalCode, addressCountry), sameAs array for verified social profile URLs, and founder or foundingDate if publicly relevant. Optional but valuable: description (concise brand statement), email, numberOfEmployees (as a QuantitativeValue range), and award array listing recognitions. Each property you add gives Google another signal to cross-reference, strengthening entity confidence and eligibility for rich features.
Below is a download organization schema template in JSON-LD format, annotated with inline comments. Copy the structure, replace placeholder values, and remove any properties that don't apply to your business.
- @context and @type establish schema.org vocabulary and entity class - name must match your registered business name exactly - url points to your canonical homepage (https, no trailing slash) - logo should be a square PNG or JPG, hosted on your domain, minimum 112×112px - contactPoint includes telephone in E.164 format and contactType descriptor - address fields mirror your Google Business Profile data for consistency - sameAs array lists official LinkedIn, Twitter, Facebook URLs (full https paths) - foundingDate uses ISO 8601 (YYYY-MM-DD); founder references a Person schema if detailed
Paste this into a <script type="application/ld+json"> block in your site header or deploy via Google Tag Manager. Validate immediately with schema.org's validator and Google's Rich Results Test.
Most organizations deploy the schema sitewide so every page declares the publisher entity, but homepage-only placement is also valid if other pages carry more specific schema types. Sitewide deployment through a global header partial or tag manager ensures consistency and simplifies updates—change the logo URL once and it propagates everywhere.
If you operate multiple brands or subsidiaries under one domain, use a parent Organization schema on the main site and LocalBusiness or subOrganization schemas on landing pages. For agencies managing client portfolios, each unique domain needs its own organization schema; cross-domain references require explicit sameAs or parentOrganization links. Canadian bilingual sites should duplicate the schema with French name and description variants only if you present fully separate brand identities in Quebec; otherwise, a single English schema with appropriate address and contact details suffices.
After deployment, run your homepage URL through Google's Rich Results Test and the Schema Markup Validator at validator.schema.org. The Rich Results Test confirms Google can parse the JSON-LD and identifies missing recommended fields. The schema.org validator catches syntax errors—trailing commas, unescaped quotes, malformed URLs.
Common errors include logo URLs that redirect or return 404, telephone numbers without country codes, sameAs URLs pointing to personal profiles instead of official brand pages, and mismatched legal names (schema says "ABC Inc." but Google Business Profile says "ABC Incorporated"). Fix these before Google's next crawl. If you're using tag manager, verify the script fires on every page load and doesn't conflict with existing JSON-LD blocks. Duplicate @context declarations or nested organization objects often break parsing, so consolidate into a single clean schema object per entity.
For businesses with physical storefronts, extend the organization schema framework by changing @type from Organization to LocalBusiness or a specific subtype like LegalService, Restaurant, or MedicalBusiness. Add geo coordinates, openingHoursSpecification, and priceRange. The organization properties (name, logo, contactPoint) remain; you're simply adding location-specific signals.
If your site also carries Product or Article schemas, reference the organization schema via the publisher or brand property using an @id pointer. This creates an entity graph: the article declares "published by @id: and Google links the two. Brand schema (a subtype of Organization) works similarly but focuses on trademark, slogan, and brand-specific properties. In practice, most businesses need only one core Organization schema plus LocalBusiness variants for each location, all cross-referenced through consistent @id anchors.
Treat organization schema as living infrastructure. Update immediately when you rebrand, change your legal name, move headquarters, replace your logo file, or hire a new CEO (if you list a founder or employee in the schema). Stale data undermines entity trust—Google sees mismatches between your schema, your Google Business Profile, and public registries, then deprioritizes your Knowledge Graph signals.
Quarterly audits catch drift: verify logo URLs still resolve, social profile links point to active accounts, phone numbers connect to working lines, and address fields match your CRA business registration and provincial corporate filings. If you expand into new provinces or open additional offices, add LocalBusiness schema blocks for each location and link them to the parent organization via parentOrganization or branchOf properties. Schema updates don't require reindexing requests; Google picks them up on the next crawl, typically within days for high-authority homepages.
Organization schema is the generic entity type for any company, nonprofit, or institution. LocalBusiness is a more specific subtype used when you have a physical storefront or service area, adding properties like geo coordinates, opening hours, and price range. If you operate from a specific address and serve walk-in or local customers, use LocalBusiness. If you're a pure online entity or holding company, Organization suffices. You can also nest LocalBusiness instances under a parent Organization schema using the branchOf property.
A single organization schema on your homepage is sufficient to establish your entity in Google's Knowledge Graph. Many sites deploy it sitewide via a header partial or tag manager so every page declares the publisher, which reinforces consistency. If different pages represent different legal entities or brands, use distinct schema blocks. For typical single-brand sites, sitewide or homepage-only both work; the key is that Google can crawl and parse it from at least one authoritative page, usually your homepage.
Yes. Change the @type from Organization to NGO, and optionally use more specific subtypes like EducationalOrganization or PerformingGroup if applicable. Add a foundingDate, mission statement in the description field, and any relevant award or funder properties. Nonprofits should include their CRA charitable registration number in the taxID property (use "CA" as the country prefix). The same validation and deployment steps apply; just ensure the legal name matches your official incorporation documents and any public charity databases.
Google cross-references schema data with your Business Profile automatically by matching the business name, address, and phone number. Ensure these fields are identical in both places—same legal name, same street address format, same phone number with country code. Add your Google Maps URL to the sameAs array if you want an explicit link. Consistent NAP (name, address, phone) across schema, your GBP, and your website footer signals to Google that all three sources refer to the same entity, strengthening local pack and knowledge panel eligibility.
Google recommends a square or rectangular logo, minimum 112×112 pixels, in PNG or JPG format. For best results across search features, use a square 512×512 or 1024×1024 image with transparent or white background. Host the file on your own domain with a stable URL—avoid CDN parameters that change or redirect chains. The logo property accepts only a single URL string, so choose your primary brand mark. If you have both a square icon and a horizontal wordmark, use the square version in organization schema and reference the wordmark separately in your site's header or WebSite schema.
Include founder or key personnel only if that information is publicly relevant and accurate. Startups often list the founder with a nested Person schema (name, jobTitle, sameAs profile URL). Larger corporations typically omit individual employees unless the executive team is a brand differentiator. Listing a CEO or founder adds entity depth but requires maintenance—update the schema if that person leaves. Avoid adding generic employee arrays; focus on roles that Google might surface in knowledge panels or that reinforce your expertise signals in competitive markets like Toronto legal or Vancouver tech.