localwebadvisor
WIKI← Wiki home

What Is Organization Schema?

By FayUpdated Jul 9, 2026EVERGREEN
⚡ THE ANSWER

Organization schema is structured data from schema.org that describes a company or brand as an entity to search engines, including its official name, logo, website, contact details, and social profiles. Added as JSON-LD, usually on the homepage, it helps Google build an accurate knowledge panel, associate your logo with your brand in search, and understand who is behind a website. It underpins brand identity across search and is the parent type of LocalBusiness.

Vocabulary
schema.org/Organization, parent of LocalBusiness and Corporation (schema.org)
Common placement
Homepage, describing the site's owning entity (industry-typical)
Key logo effect
logo property can associate a brand logo in Google results (Google Search Central)
Identity links
sameAs connects official social and profile URLs (schema.org)

What is Organization schema and why does it exist? #

Organization schema describes the entity behind a website, the company, firm, or brand, in a way search engines can read and trust. It states the official name, the URL, the logo, contact points, and the sameAs links to your verified social and directory profiles. Its purpose is identity: helping Google understand who you are as a distinct entity, so it can build an accurate knowledge panel, show your logo, and connect the dots between your website, your social accounts, and mentions of you across the web. Organization is the parent type of LocalBusiness, covered in /wiki/what-is-localbusiness-schema; a plumber uses LocalBusiness because it adds physical-place details, while a purely online brand or multi-location company may use Organization directly. It is part of the schema.org vocabulary explained in /wiki/schema-markup-guide. For any business investing in a brand, Organization schema is the foundation layer that tells search engines this is a real, identifiable entity with a name, a face, and official channels.

What properties should Organization schema include? #

A strong Organization block starts with name, the exact legal or brand name, and url, your canonical homepage. logo points to a clear, square-ish image of your logo, which is what Google may associate with your brand in results, so use a high-quality file. contactPoint can describe customer service or sales with a telephone and contactType. sameAs is a powerful array listing your official profiles, your Facebook page, LinkedIn company page, Instagram, YouTube, and any authoritative directory listing, which helps Google confirm these accounts belong to you and consolidates your entity. Additional useful properties include description, foundingDate, address for organizations with a headquarters, and areaServed. The more consistent and complete this information is, the more confidently Google can assemble your knowledge panel. Every value should match what appears across your site and profiles. Generate the structure with /tools/schema-generator, and preview how your brand appears socially with /tools/social-preview to keep logo and identity consistent across surfaces.

What does Organization JSON-LD look like? #

The Organization object typically lives on the homepage and declares the brand identity. The example below shows a company with a logo, a contact point, and sameAs links to its official profiles. Note that logo is an absolute URL to an image, sameAs is an array of profile URLs, and contactPoint nests its own object with a contactType. This block establishes the entity once, and other pages can reference it. Because Organization is about identity rather than a specific offer, it does not usually produce a flashy standalone rich result; its value is in feeding the knowledge panel and logo association, and in giving AI systems a clean statement of who you are. After deploying, validate with /tools/schema-validator and monitor Google Search Console. Keep the sameAs list current, adding new official profiles and removing abandoned ones, so your entity graph stays accurate.

organization.json — Homepage Organization JSON-LD
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Rivertown Plumbing Co.",
  "url": "https://rivertownplumbing.com",
  "logo": "https://rivertownplumbing.com/logo.png",
  "description": "Licensed plumbing services for homes and businesses in Austin, TX.",
  "contactPoint": {
    "@type": "ContactPoint",
    "telephone": "+1-512-555-0142",
    "contactType": "customer service",
    "areaServed": "US"
  },
  "sameAs": [
    "https://www.facebook.com/rivertownplumbing",
    "https://www.instagram.com/rivertownplumbing",
    "https://www.linkedin.com/company/rivertownplumbing"
  ]
}

How does Organization schema differ from LocalBusiness? #

This is the most common question, and the answer is about scope. Organization is the general parent type describing any company or brand as an entity. LocalBusiness is a specialized child type that adds physical-place properties like a street address, opening hours, and geo coordinates, plus service-specific subtypes like Plumber or Dentist. If your business serves customers from a physical location or defined service area, LocalBusiness (or a specific subtype) is usually the right primary choice because it carries the local details Google needs for the Map Pack, as covered in /wiki/what-is-localbusiness-schema. If you are a purely online brand, a multi-location company describing the overarching entity, or a firm without a single storefront, Organization fits. Some businesses use both: Organization on the homepage to establish the brand entity, and LocalBusiness on location pages for each physical site. They are not in conflict; they describe the business at different levels. Choosing correctly keeps your identity signals clean and your local details attached where they belong.

How does the logo property and knowledge panel work? #

One of the most tangible benefits of Organization schema is logo association. When you specify a logo URL in your Organization markup, you give Google an explicit, high-quality image to associate with your brand, which can appear in the knowledge panel and other brand contexts. Without it, Google guesses from your favicon or images, often poorly. The knowledge panel itself, the box of brand information that can appear for a branded search, is assembled from many signals: your Organization schema, your website content, your sameAs profiles, Wikipedia and Wikidata if present, and other authoritative mentions. Organization schema is your direct contribution to that assembly, the one source you fully control. Consistency across all these signals is what builds Google's confidence to display a rich panel. For a growing local brand, this is how you begin to own your branded search results, and it complements the reputation work in /services/local-seo. Preview your logo and social appearance with /tools/social-preview so every surface shows the same identity.

Why does the sameAs property matter so much? #

sameAs is deceptively important. It lists the URLs of your official presences elsewhere, social profiles, a Crunchbase or Yelp page, a LinkedIn company page, telling Google these accounts are the same entity as your website. This does two things. First, it consolidates your entity, so Google understands that your Facebook page, your Instagram, and your site all represent one brand, strengthening the knowledge graph connection. Second, it helps Google verify authenticity, distinguishing your real accounts from impersonators. For AI systems and answer engines described in /wiki/ai-search-optimization, sameAs links provide corroborating sources that increase confidence when they cite or describe your business. Keep the list to official, active profiles you control; do not pad it with irrelevant links. Update it as your presence changes, adding a new YouTube channel or removing a dead account. This maintenance is small but meaningful, and it is part of the ongoing entity hygiene our /services/care-plans provide, ensuring your brand's connected profile stays accurate as it grows across platforms.

As search shifts toward AI Overviews and answer engines, having a clean, machine-readable statement of who you are matters more than ever. When an AI system needs to describe your business, cite it, or decide whether it is a legitimate answer to a query, it looks for authoritative, consistent identity signals. Organization schema provides exactly that: an unambiguous declaration of your name, logo, official channels, and description straight from your own site, corroborated by the sameAs profiles it links to. This is a core part of /wiki/ai-search-optimization and /wiki/what-are-ai-overviews. For branded searches, where someone types your company name, strong Organization signals help Google present you accurately rather than showing competitors or confusing you with a similarly named entity. In an environment where machines increasingly mediate discovery, being clearly identifiable is a competitive advantage. Organization schema is the least glamorous but most foundational piece of that identity, the layer everything else, LocalBusiness, Service, Product, Review, hangs from, which is why we include it on every brand site we build.

How do you implement and maintain Organization schema? #

Place a single Organization block on your homepage to establish the entity, and reference it from other markup where appropriate rather than repeating full details everywhere. On WordPress, an SEO plugin or a snippet added through /services/wordpress-development can output it from fields you set once. On a custom site, put it in the global template so it appears site-wide with consistent values, which our /services/web-design and /services/web-app-development teams do by default. Generate the initial code with /tools/schema-generator, validate with /tools/schema-validator, and confirm in Google Search Console. Maintenance centers on keeping identity current: update the logo if you rebrand, refresh the sameAs list as profiles change, and correct contact details if they move. Because identity is stable, this markup changes rarely, but the changes that do happen, a rebrand, a new social channel, a headquarters move, are exactly the ones that matter most for how Google recognizes you. Folding this into /services/care-plans ensures your entity stays coherent as the brand evolves.

FAQ

Should I use Organization or LocalBusiness schema?

If your business serves customers from a physical location or defined service area, LocalBusiness or a specific subtype like Plumber is usually the primary choice because it carries address, hours, and geo details Google needs for local results. Organization fits online-only brands, multi-location companies describing the overall entity, or firms without a single storefront. Many businesses use both at different levels.

Where should Organization schema go on my site?

The homepage is the natural home, since it represents the brand as a whole. Place a single Organization block there to establish the entity, ideally output from a global template so the values stay consistent site-wide. You do not need to repeat the full block on every page; other markup can reference the entity instead.

What does the logo property actually do?

It gives Google an explicit, high-quality image to associate with your brand, which can appear in the knowledge panel and other brand contexts. Without it, Google guesses from your favicon or page images, often poorly. Use a clear, reasonably square logo file at an absolute URL so your brand shows up correctly in search.

Why is the sameAs property important?

sameAs links your official social and directory profiles to your website, telling Google they all represent one entity. This consolidates your brand in Google's knowledge graph, helps verify authenticity against impersonators, and gives AI systems corroborating sources. Keep it to active, official profiles you control and update it as your presence changes.

Does Organization schema produce a rich result?

Not a flashy standalone one. Its value is behind the scenes: feeding the knowledge panel, associating your logo, and giving AI systems a clean statement of who you are. You will not usually see a badge from it, but it strengthens how accurately Google and answer engines recognize and present your brand.

Does Organization schema help with AI search?

Yes. AI Overviews and answer engines rely on authoritative, consistent identity signals to describe or cite a business. Organization schema provides an unambiguous, machine-readable declaration of your name, logo, channels, and description, corroborated by sameAs links. In an AI-mediated search landscape, being clearly identifiable is a real advantage, and this markup is the foundation of it.

Was this helpful?