What is Organization schema?

Organization schema, explained

Google's Organization documentation says the markup helps Google understand your organization's administrative details and disambiguate it in search results, and that some properties can influence how you appear, such as the logo shown in results and details in knowledge panels. It has no required properties: you add the ones that apply.

The recommended ones for a startup are name, url, logo, sameAs (links to your profiles on LinkedIn, X, GitHub, Crunchbase and similar), description, and contact details like email or a contactPoint. A physical address matters if you have one. Google says the logo must be at least 112×112 pixels, crawlable and indexable, in a supported format, and should look right on a white background. Use the most specific subtype that fits, such as OnlineStore or LocalBusiness, where one applies.

Placement is simple. Google recommends putting it on the homepage, or on a single page that describes the organization like an About page. You don't need it on every page. Many sites give it an @id and reference that from Article publisher fields and other markup, which ties the site's entities together.

The sameAs links matter beyond Google. They connect your site to the profiles that describe you elsewhere, which helps any system that tries to work out which company a name refers to. That's especially useful for new brands with generic names.

Why it matters for founders

A new product with a common-word name is easy to confuse with other things. Organization markup is a direct way to tell search engines which entity your site is.

Example

Your homepage adds Organization JSON-LD with your name, a 512×512 logo, your support email and sameAs links to your LinkedIn, X and GitHub pages.

Common mistakes

• A logo smaller than 112×112 or blocked from crawling.
• Different company names across pages and profiles.
• Repeating full Organization markup with different details on every page.
• Leaving sameAs empty.