Organization Schema Markup Generator
Strengthen your Google Knowledge Panel and E-E-A-T signals — generate valid Organization schema markup instantly.
Company or brand pages — contributes to Google Knowledge Panel and E-E-A-T signals.
Should match the name used across the site.
The organization's main website.
Min 112×112 px
Photo of the organization or office
Detailed description of the organization.
Primary contact email.
Include country and area code.
LinkedIn, Twitter, Facebook…
JSON-LD output
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Organization"
}
</script>Google Rich Results eligible
How to use the Organization Schema Markup Generator
- Enter your organization name exactly as it appears across your site and official profiles — consistency helps Google connect the entity.
- Add the website URL and logo URL. The logo must be crawlable by Google (min 112×112 px) — it appears in the Knowledge Panel.
- Add an image URL — a photo of your office, team, or headquarters. This is separate from the logo and fills the Knowledge Panel visual.
- Fill in the description — write a factual, neutral summary of what the organization does. Avoid marketing language.
- Add social and profile URLs in the sameAs field — LinkedIn, Twitter/X, Facebook, Wikipedia, Crunchbase, GitHub. These are the most important signals for Google's Knowledge Panel.
- Expand Legal & Details to add founding date, legal name, or alternate names if relevant.
- Copy the generated JSON-LD and paste it into the <head> of your homepage or About page.
How the Organization Schema Markup Generator works
Organization schema markup is a JSON-LD script block placed in your page's <head> that gives Google a machine-readable description of your company or brand — its name, website, logo, contact details, and links to official profiles. The generator builds this block locally in your browser with no server calls. You fill in the fields, the JSON-LD output updates in real time, and you copy the result into your HTML.
Organization schema is typically added to the homepage or About page — the pages Google associates most strongly with the organization entity. Unlike Product or Article schema which are page-specific, a single well-filled Organization schema on your homepage can influence how Google understands your brand across the entire site and across all its content.
Minimal Organization schema
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Organization",
"name": "Abect",
"url": "https://devtools.abect.com",
"logo": "https://devtools.abect.com/logo.png",
"sameAs": [
"https://linkedin.com/company/abect",
"https://twitter.com/abect",
"https://github.com/abect"
]
}
</script>What Organization Schema unlocks in Google
Organization schema does not directly produce a SERP Rich Result in the same visual way as Product or FAQ schema. Its value is more foundational — it tells Google who you are, where to verify that identity, and how to represent your brand across multiple surfaces and features.
- Knowledge Panel — the information box that appears on the right side of Google Search results for branded queries. Organization schema, especially combined with strong sameAs signals, is the primary structured data input for triggering and populating the Knowledge Panel.
- Brand disambiguation — if your company name is shared with other entities, Organization schema helps Google associate the correct entity with your site and distinguish your brand in search results.
- E-E-A-T signals — Google's quality raters evaluate Experience, Expertise, Authoritativeness, and Trustworthiness. A named, verifiable organization with linked social profiles and a clear description strengthens your site's E-E-A-T score, which influences ranking potential for competitive queries.
- Branded search results — for searches of your exact brand name, a well-structured Organization schema can trigger an enhanced brand result with logo, description, and sitelinks displayed more prominently.
- Sitelinks Searchbox — when combined with WebSite schema, Organization schema supports the Sitelinks Searchbox feature that shows a search field directly in Google Search results for your brand.
- Publisher identity for content — when your site also publishes articles, Organization schema on the homepage establishes the publisher entity that Article schema on individual posts references via the publisher field.
Organization Schema fields — what each one does for Google
Organization schema has no technically required fields — the schema is valid with just a name. But the practical impact varies enormously depending on which fields you fill in. The table below maps each field to its contribution to Google's understanding of your brand.
| Field | Impact level | What Google uses it for |
|---|---|---|
| name | Critical | Primary entity label — must match all other mentions of the brand |
| url | Critical | Confirms the canonical web presence of the organization |
| logo | Critical | Displayed in Knowledge Panel and used in Article publisher markup |
| image | High | Visual representation in Knowledge Panel — distinct from logo |
| sameAs | Very high | Cross-references brand identity across authoritative external sources |
| description | High | May appear in Knowledge Panel and informs entity classification |
| Medium | Contact signal — used in local and entity verification | |
| telephone | Medium | Contact signal — especially valuable for local business hybrid setups |
| legalName | Medium | Helps disambiguate from similarly named entities |
| foundingDate | Low–medium | Adds credibility and age signals to the entity |
| address | Medium | Required if the organization also functions as a local business |
| alternateName | Low | Helps Google recognize abbreviations and former brand names |
sameAs — the most important field in Organization Schema
The sameAs field is a list of URLs that all refer to the same entity as your organization. Google uses these links to cross-reference your brand across the web and build confidence in the entity's identity. A strong set of sameAs URLs is the difference between a brand that gets a Knowledge Panel and one that does not. Think of each sameAs URL as a vote of identity from an authoritative external source.
High-value URLs to include in sameAs
- Wikipedia — if a Wikipedia article about your organization exists, this is the single most powerful sameAs URL. Google treats Wikipedia as the highest-authority external source for entity verification.
- Wikidata — even without a Wikipedia article, a Wikidata entry (wikidata.org/wiki/Q...) carries significant weight. Creating a Wikidata item for your organization is worthwhile if Wikipedia is not yet an option.
- LinkedIn Company Page — essential for B2B organizations. LinkedIn is one of Google's most trusted identity verification sources for companies.
- Crunchbase — highly valued for startups, tech companies, and investors. Crunchbase profiles are crawled regularly and treated as authoritative business data.
- Twitter/X official account — social verification signal, especially valuable for media brands and public figures.
- Facebook Business Page — important for consumer brands, especially in markets where Facebook presence is expected.
- GitHub organization — relevant for developer tools, open-source projects, and software companies. Google recognizes GitHub as authoritative for tech organizations.
- Official government or trade registry — for regulated industries, a link to your registration in an official business registry adds a strong authenticity signal.
What not to include in sameAs
- Pages where you are listed but not the owner — directories, review sites, or aggregators where your brand appears but the page is not your official profile.
- Broken or redirecting URLs — Google follows the sameAs links when verifying identity. A 404 or a redirect chain weakens the signal.
- URLs of similarly named competitors — even accidentally including a URL that leads to a different entity can confuse Google's entity graph.
- Social profile URLs that are inactive or abandoned — a profile with no activity for years sends a weaker signal than an active one.
Technical deep dive: Organization vs LocalBusiness, and WebSite schema
Organization vs LocalBusiness: LocalBusiness is a subtype of Organization — it inherits all Organization fields and adds location-specific ones: `openingHours`, `geo`, `hasMap`, `priceRange`. If your organization has a physical location where customers visit, use LocalBusiness (or one of its subtypes like Restaurant, MedicalClinic, or Store) instead of plain Organization. You can also combine both types in a single schema using an array: `"@type": ["Organization", "LocalBusiness"]` — this tells Google the entity is both a company and a physical place.
WebSite schema and Sitelinks Searchbox: adding a WebSite schema block alongside Organization on the homepage is a low-effort, high-value addition. The WebSite schema with a `potentialAction` of type `SearchAction` enables the Sitelinks Searchbox — a search field that appears directly in Google's branded SERP for your site. Google decides whether to show it, but having the schema is a prerequisite for eligibility.
Full Organization schema with WebSite schema
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Organization",
"name": "Abect",
"url": "https://devtools.abect.com",
"logo": {
"@type": "ImageObject",
"url": "https://devtools.abect.com/logo.png",
"width": 300,
"height": 60
},
"image": "https://devtools.abect.com/img/office.jpg",
"description": "Free browser-based developer tools — image converters, SEO tools, and schema markup generators.",
"foundingDate": "2024",
"email": "hello@abect.com",
"sameAs": [
"https://linkedin.com/company/abect",
"https://twitter.com/abect",
"https://github.com/abect",
"https://crunchbase.com/organization/abect"
]
}
</script>
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "WebSite",
"url": "https://devtools.abect.com",
"potentialAction": {
"@type": "SearchAction",
"target": {
"@type": "EntryPoint",
"urlTemplate": "https://devtools.abect.com/?q={search_term_string}"
},
"query-input": "required name=search_term_string"
}
}
</script>Frequently Asked Questions
Does Organization schema need to be on every page, or just the homepage?
Organization schema is most effective on the homepage or About page — the pages Google most strongly associates with the organization entity. You do not need it on every page. Some sites add it sitewide via a shared layout component, which is acceptable but provides diminishing returns. If you add it sitewide, ensure the schema is identical on every page — inconsistent data across pages can confuse Google's entity graph.
How many sameAs links should I include?
Add every official profile URL where your organization has a genuine, active presence — there is no maximum. Quality matters more than quantity. A Wikipedia page, Wikidata entry, LinkedIn Company Page, and one or two social profiles typically provide a strong signal. Avoid adding URLs to pages where you are listed but do not control the content, and never add broken or redirecting links.
Does Organization schema help with branded search results?
Yes — Organization schema is one of the key inputs Google uses when generating enhanced branded search results. For queries matching your exact organization name, strong schema combined with sameAs signals increases the likelihood of a Knowledge Panel appearing, your logo showing in the SERP, and sitelinks being displayed. The effect is most noticeable for organizations that have consistent brand mentions across authoritative external sources.
What is the difference between logo and image in Organization schema?
The logo field specifies your brand's official logo — typically a simple text-and-symbol lockup on a transparent or solid background. Google uses it in the Knowledge Panel header and in Article publisher markup. The image field is for a broader visual representation of the organization — a photo of your office, headquarters, team, or product. Both can appear in Knowledge Panel but serve different visual roles. Google recommends including both when available.
Do I need a Wikipedia page for Organization schema to work?
No — a Wikipedia page is not required. Organization schema works without any Wikipedia entry. However, a Wikipedia article in sameAs is the strongest possible entity verification signal and significantly increases the probability of a Knowledge Panel being generated. If you do not have Wikipedia, prioritize Wikidata (where you can create an item yourself), LinkedIn, and Crunchbase as the next most authoritative sources.
Can I use Organization schema for a personal brand or freelancer?
For a personal brand, Person schema is more appropriate than Organization. Person schema includes fields for jobTitle, alumniOf, and worksFor that are not available in Organization. If you run a one-person company with a distinct brand name, you can use Organization — but if the brand is primarily associated with you as an individual, Person schema will give Google clearer signals about the entity type.
How does Organization schema interact with Article schema on the same site?
Article schema on individual articles references a publisher field that should point to the same Organization entity defined on the homepage. When both are in place, Google can connect the author content to the publisher organization, strengthening E-E-A-T signals for the entire site. The publisher name and logo in Article schema should exactly match the name and logo in the homepage Organization schema.
What is the Sitelinks Searchbox and how does Organization schema relate to it?
The Sitelinks Searchbox is a search field that appears directly in Google's branded search results for your site, allowing users to search your site without clicking through first. It requires WebSite schema with a SearchAction potentialAction — not Organization schema directly. However, having Organization schema on the homepage establishes the entity context that supports other Knowledge Panel features alongside the Searchbox.
Should the Organization schema foundingDate be a full date or just a year?
Either is acceptable. Schema.org supports Date values as YYYY (just year), YYYY-MM (year and month), or YYYY-MM-DD (full date). For most organizations, the founding year alone is sufficient and avoids the need to pin down an exact date. If you use a full date, the date input in the generator will format it correctly. Do not guess or approximate the founding date — accuracy matters for entity verification.
Can Organization schema have multiple contact points for different departments?
Yes — you can add a contactPoint array with multiple ContactPoint objects, each specifying a contactType (customer support, sales, technical support, billing, reservations, credit card support). This is useful for larger organizations with distinct departments. For smaller organizations, including email and telephone directly on the Organization object is simpler and equally effective.
How long does it take for Organization schema to affect the Knowledge Panel?
Organization schema alone rarely triggers a Knowledge Panel immediately. The Knowledge Panel is a result of Google's overall entity understanding — schema is one input among many, including external references, Wikipedia mentions, press coverage, and site authority. Schema helps but is not a guarantee. After adding schema, allow several weeks for Google to recrawl and reprocess the entity data. Monitor changes in how your brand appears in branded search results.
What happens if the name in Organization schema does not match my page title or logo alt text?
Consistency is critical for entity signals. If the name in your Organization schema differs from the name in your logo alt text, your Twitter bio, your LinkedIn page, and your Crunchbase profile — Google's confidence in the entity identity drops. Use the exact same name string everywhere. If your brand has a common abbreviation, add it to alternateName rather than using it as the primary name.