Skip to content
SEO

Organization Schema Generator

Generate Organization JSON-LD with address and social profiles.

organizationschemajson-ldbusinessseo
Loading tool…

About the Organization Schema Generator

The Organization Schema Generator creates Organization JSON-LD that feeds knowledge panels and reinforces your brand's entity identity in search. The form covers the full business profile: name and legal name, website and logo URLs, founding date, founder, email and phone, a complete postal address (street, city, region, postal code, and ISO country code), plus a list of sameAs social profile URLs that you can grow up to twenty entries. It ships prefilled with a Fernandes Labs example so you can see a complete, realistic output immediately, and every field is optional — the emitted JSON contains only the properties you actually filled, so a minimal name-plus-URL submission produces a clean, valid object instead of a pile of empty values. The founder becomes a nested Person type, the address compiles into a PostalAddress object whenever any address field is set, and phone maps to the schema.org telephone property. A stats row confirms whether a name is set, whether an address exists, and how many social URLs are included. Consistent Organization markup across your homepage and about page helps Google merge signals about who you are — and identical entity data is a prerequisite for strong brand SERPs.

Organization Schema Generator examples

Input
The prefilled Fernandes Labs defaults: Name "Fernandes Labs" · Legal name "Fernandes Labs, Inc." · URL "https://fernandeslabs.com" · Logo "https://fernandeslabs.com/logo.png" · Description "We build polished developer tools and open-source utilities." · Founding date "2021-04-01" · Founder "Alex Fernandes" · Email "hello@fernandeslabs.com" · Phone "+1-555-0100" · Street "100 Market Street" · City "San Francisco" · Region "CA" · Postal "94105" · Country "US" · sameAs: twitter.com/fernandeslabs, github.com/FernandesLabs
Output
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Fernandes Labs",
  "legalName": "Fernandes Labs, Inc.",
  "url": "https://fernandeslabs.com",
  "logo": "https://fernandeslabs.com/logo.png",
  "description": "We build polished developer tools and open-source utilities.",
  "foundingDate": "2021-04-01",
  "founder": {
    "@type": "Person",
    "name": "Alex Fernandes"
  },
  "email": "hello@fernandeslabs.com",
  "telephone": "+1-555-0100",
  "address": {
    "@type": "PostalAddress",
    "streetAddress": "100 Market Street",
    "addressLocality": "San Francisco",
    "addressRegion": "CA",
    "postalCode": "94105",
    "addressCountry": "US"
  },
  "sameAs": [
    "https://twitter.com/fernandeslabs",
    "https://github.com/FernandesLabs"
  ]
}
Note: The founder is nested as a Person, the address as a PostalAddress, and phone maps to the telephone property. Stats show Name set: Yes, Has address: Yes, Social URLs: 2.
Input
Clear every field, then fill only Name: "Bean & Brew" and URL: "https://beanandbrew.example"
Output
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Bean & Brew",
  "url": "https://beanandbrew.example"
}
Note: Because all fields are optional, only the two filled properties are emitted. The JSON stays minimal and valid rather than carrying a pile of empty strings.
Input
Add a third social URL via Add URL: "https://linkedin.com/company/fernandeslabs"
Output
  "sameAs": [
    "https://twitter.com/fernandeslabs",
    "https://github.com/FernandesLabs",
    "https://linkedin.com/company/fernandeslabs"
  ]
Note: The sameAs array grows with each added URL, up to 20 entries. Empty social URL inputs are filtered out of the emitted array, and badges list the trimmed hostnames below the result box.

How to use the Organization Schema Generator

  1. 1

    Start from the prefilled Fernandes Labs example and replace Name, Legal name, URL, and Logo URL with your company's details.

  2. 2

    Fill in Founding date (YYYY-MM-DD), Founder, Email, and Phone — phone is emitted as the schema.org telephone property.

  3. 3

    Complete the Postal address fields; the address object appears in the JSON-LD as soon as any one of them is filled.

  4. 4

    Manage social profiles in the Same-as social URLs section: click Add URL to append entries (up to 20) and the trash icon to remove them.

  5. 5

    Review the Organization JSON-LD in the result box — only filled fields are emitted — then copy or download organization.json.

Common use cases

  • Knowledge panel groundwork — publish consistent Organization markup on the homepage and about page.
  • Local business profiles — extend the same schema with address details for regional landing pages.
  • Brand entity consolidation — list all official social profiles in sameAs so platforms agree on your entity.
  • Press and career pages — reuse the schema with slight variations while keeping the identity fields identical.
  • Schema migrations — regenerate the Organization block after rebranding, domain changes, or address moves.
  • E-A-T signals — document founders, founding date, and contact data in machine-readable form for quality evaluators.

Technical SEO best practices

  • Use the legal name for legalName and the public brand name for name — Google cross-references both when building knowledge panels.
  • Link every official profile in sameAs and nothing else; mismatched or unofficial profiles dilute entity confidence.
  • Keep the schema identical across the homepage, about page, and social bios so entity signals merge instead of fragmenting.
  • Format foundingDate as YYYY-MM-DD and country as the two-letter ISO 3166-1 code, exactly as the field hints suggest.
  • Only include a logo URL that serves a real image (112×112px minimum is recommended for Google); broken logos fail rich result checks.
  • Re-emit the schema after rebrands, domain changes, or address moves — stale Organization data is worse than none.

Tips

  • Run a knowledge panel check on your brand before and after publishing the schema to see the entity signals strengthen.
  • Use the sameAs list to include only profiles you actively maintain.
  • Keep the description under a paragraph — search engines truncate long entity descriptions.
  • Fill the country code for every address you use; mixed formats break PostalAddress parsing.

Frequently asked questions

Name is the public brand — "Fernandes Labs" — while legal name is the registered corporate entity — "Fernandes Labs, Inc.". Google's knowledge panel system cross-references both when merging signals about your organization, and having them as separate properties is more precise than cramming the legal suffix into the brand name. Both fields are optional; fill legalName only if a distinct registered name exists.

Only official profiles you control: your X, GitHub, LinkedIn, YouTube, Instagram, and similar pages. Each entry becomes a verification signal that links the profile to your entity, and Google discourages listing unofficial or fan-created accounts. Add up to twenty URLs with the Add URL button, and keep the list identical across every page that carries your Organization schema.

Because telephone is the schema.org property name for a contact phone number — the generator maps the friendly label to the correct vocabulary automatically. Use the format your business lists publicly, including the country code, such as +1-555-0100, since consistent formatting across your schema, website footer, and directory listings helps search engines merge the entity data.

As soon as any one of the five address fields — street, city, region, postal code, or country — contains text, the generator emits a PostalAddress object with exactly the fields you filled. If all five are empty, no address property is emitted at all, keeping the JSON clean. Partial addresses are valid JSON-LD, but complete addresses strengthen local and knowledge panel signals.

No — knowledge panels are assembled from many sources (Wikipedia, Wikidata, Google Business Profile, news, and your own markup) and require Google to be confident the entity is notable. Organization schema is one input that makes your pages unambiguous about the entity they describe, especially when the same block appears on the homepage and about page. Think of it as groundwork, not a guarantee.

The generator emits the Organization type specifically. If you operate a single physical location, Google recommends LocalBusiness or one of its subtypes (such as Store or Restaurant) for local results, though Organization is still valid for the corporate entity behind the business. Generate the Organization block for brand-level pages and pair it with location-specific markup elsewhere.

Explore more seo tools

Browse the full collection of seo tools on the hub, or jump back to all categories.

Related tools

Did this tool help?

Anonymous — one tap, no sign-up.