JSON-LD Organization Schema Builder

Organization structured data, built in seconds

The Organization type from schema.org is the canonical way to describe the company, brand, or institution behind a website. Search engines read it to associate your domain with a verified entity — name, logo, contact details, and the official social profiles you control. This builder produces ready-to-paste JSON-LD with only the fields you fill in.

How it works

JSON-LD (“JSON for Linking Data”) embeds machine-readable structured data inside a <script type="application/ld+json"> tag. The builder constructs an object whose @context is https://schema.org and @type is Organization, then adds your name, url, and logo. Contact details become a nested contactPoint object (@type: ContactPoint) with telephone and contactType. Each non-empty line in the social box is added to the sameAs array. Empty fields are dropped entirely so the schema never carries blank or null values.

Tips and example

A minimal valid block needs at least name and url. The output for a fully filled form looks like this:

{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Gera Systems Ltd",
  "url": "https://gera.services",
  "logo": "https://gera.services/logo.png",
  "foundingDate": "2024-01-01",
  "contactPoint": {
    "@type": "ContactPoint",
    "telephone": "+44-20-1234-5678",
    "contactType": "customer support"
  },
  "sameAs": [
    "https://www.linkedin.com/company/gera",
    "https://x.com/gera"
  ]
}

Use foundingDate in ISO YYYY-MM-DD form. Place exactly one Organization block per site, normally on the homepage, and validate it with Google’s Rich Results Test before shipping.

What Organization schema actually influences

Organization structured data does not directly produce a rich result in the same way that Article or Product schema does. What it does instead is feed the knowledge graph — the entity model that search engines maintain about the world. Once your site is associated with a confirmed Organization entity, several things can follow:

• Knowledge panel: Google may display a branded panel in the right column of search results showing your logo, name, and social links. This is more likely for established brands with consistent sameAs signals.
• Brand SERP improvements: Searches for your company name are more likely to return your own site first, with your social profiles listed below, because the engine has high confidence in the entity.
• Author and publisher attribution: Article and ReviewAction schemas that reference your organization by name can be linked back to the Organization entity, strengthening author authority.

None of these are guaranteed, but they follow naturally from a well-formed, consistent organization graph presence.

The sameAs field — your most important entity signal

The sameAs array is where you list the URLs of your organization’s official profiles on authoritative third-party platforms. These links serve as corroborating evidence that the entity described in your schema is the same as the one that appears elsewhere on the web.

High-value sameAs targets include:

• Your LinkedIn company page (https://www.linkedin.com/company/...)
• Your X (Twitter) profile (https://x.com/...)
• A Crunchbase or Companies House listing, if public
• A Wikipedia article about your company, if one exists
• Your GitHub organization page (https://github.com/...)

Enter one URL per line. The generated schema emits them as an array of strings. Do not include personal social profiles here — only official, organization-level accounts.

Logo requirements for search features

For your logo to appear in search features, Google specifies it should be:

• An image served over HTTPS
• At least 112 × 112 pixels; 600 × 60 pixels is a common alternative for wide logos
• Crawlable (not blocked by robots.txt or X-Robots-Tag)

Use a permanent, direct URL to the image rather than a redirect chain. A broken logo URL is a common reason Organization schema fails validation.