What is sameAs actually used for?

sameAs is a list of URLs that unambiguously identify the same real-world entity elsewhere on the web - your official social profiles, Wikipedia page, or Crunchbase entry - and it's one of the signals Google uses to build (or verify) a Knowledge Panel for your organization, by cross-referencing that these other profiles describe the same entity.

Where should Organization schema go on my site?

Typically on the homepage, since that's the page most representative of the organization as a whole; some sites also repeat it on an About page. It's usually added once per site, not per page, unlike Article or Product schema which is per-content-item.

Do I need a contact point?

Only if you want it - it's optional and mainly useful if you want the contactType (like "customer service") and telephone number to be machine-readable for search engines or AI systems that surface contact information, rather than requiring someone to find it in your page's text.

What's the difference between this and LocalBusiness schema?

Organization is the general type for any company or entity, online or offline. LocalBusiness (available as its own generator in this category) is more specific: it adds a physical address and opening hours, and is meant for businesses with a real-world storefront or office customers visit. If you have a physical location, use LocalBusiness instead; if you're a purely online business or want to describe the parent company, use Organization.

Organization Schema Generator - Organization JSON-LD with sameAs

Overview

Introduction

Organization schema is how a site tells search engines "this is the company behind this website," complete with an official name, logo, and links to verified social profiles. It's a small piece of markup, but it's one of the inputs Google can use when deciding whether to build a Knowledge Panel for a brand.

This generator builds the object from a simple form, including a dynamic add/remove list for the sameAs array of social profile URLs, which is normally the most tedious part to type by hand correctly.

What Is Organization Schema Generator?

A form-driven generator for Organization JSON-LD: a name, URL, logo, description, a list of sameAs social/reference profile URLs, and an optional nested ContactPoint.

It's typically added once per website (on the homepage), rather than once per page like Article or Product schema.

How Organization Schema Generator Works

Name, URL, logo, and description map directly to their JSON-LD properties; the sameAs list is built from a dynamic add/remove set of URL inputs and only included in the output once at least one URL is entered.

The optional contact point (telephone plus a contact type like "customer service") is nested as a ContactPoint object only when at least one of those two fields is filled in, keeping the output minimal when they're left blank.

When To Use Organization Schema Generator

Setting up baseline structured data on a new site's homepage so search engines can identify the organization behind it.

Consolidating a brand's official social profiles into machine-readable form to support Knowledge Panel eligibility.

Often used alongside Structured Data Validator, Local Business Schema Generator and Article Schema Generator.

Features

Advantages

Builds the sameAs array with a proper add/remove list instead of requiring manual comma-separated URL editing inside raw JSON.
Keeps the contact point out of the output entirely when it's not needed, rather than emitting an empty or placeholder object.
Produces valid Organization JSON-LD from just a name, with every other field optional, so you can start minimal and expand later.

Limitations

Doesn't verify that sameAs URLs actually point to profiles that identify the same organization; that's a manual accuracy check.
Only exposes the commonly-used Organization fields, not the full schema.org property set (like founder, foundingDate, or numberOfEmployees).

Examples

A company homepage entry with social profiles

Input

Name: Acme Devtools
URL: https://acmedevtools.com
Logo: https://acmedevtools.com/logo.png
Description: Developer tools for web teams.
sameAs: https://twitter.com/acmedevtools, https://github.com/acmedevtools
Contact: telephone +1-555-0100, type customer service

Output

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Acme Devtools",
  "url": "https://acmedevtools.com",
  "logo": "https://acmedevtools.com/logo.png",
  "description": "Developer tools for web teams.",
  "sameAs": [
    "https://twitter.com/acmedevtools",
    "https://github.com/acmedevtools"
  ],
  "contactPoint": {
    "@type": "ContactPoint",
    "telephone": "+1-555-0100",
    "contactType": "customer service"
  }
}
</script>

Every optional field is filled in, producing a fully fleshed-out Organization entry suitable for a homepage.

Best Practices & Notes

Best Practices

Only list sameAs URLs for profiles you actually control and that clearly identify your organization, not general mentions of your brand on other sites.
Use a logo that's a clear, square-ish image; Google's logo guidelines recommend it be at least 112x112px.
Keep the name field consistent with your organization's legal or clearly-established brand name, since mismatches can undermine entity recognition.
Place Organization schema on your homepage rather than scattering slightly different copies of it across many pages.

Developer Notes

logo and url are emitted as bare string values rather than nested ImageObject/WebSite objects, matching the simplest valid form Google's own examples use; ContactPoint is only added to the output when at least one of telephone/contactType is present, avoiding an empty object in the JSON.

Organization Schema Generator Use Cases

Adding baseline Organization schema to a new company website's homepage
Consolidating official social profile links into sameAs for Knowledge Panel signals
Publishing a machine-readable customer service contact point alongside general company info

Common Mistakes

Adding sameAs links to unofficial mentions (news articles, review sites) instead of profiles the organization directly controls and maintains.
Duplicating slightly different Organization schema across multiple pages instead of keeping one canonical version on the homepage.

Tips

If you also have LocalBusiness schema for a physical location, keep the name and url consistent between the two so they read as the same entity.
Revisit the sameAs list whenever a social profile is renamed or replaced, since a stale URL can point to a defunct or unrelated account.

Organization Schema Generator