Organization schema for a Turkish company: legal name, tax ID

Organization schema is a JSON-LD block that tells machines which organization a site belongs to. Put it on the homepage or the about page, with the name, logo, legal name (legalName), official profile links (sameAs) and, if you choose, the tax number (taxID). Google does not require any of these fields.

This article is not legal advice. How a tax number, MERSIS number and trade name are shown on a site is the company's decision and responsibility; if you are unsure, ask your accountant or lawyer.

What is Organization schema and what does it do?

Organization is schema.org's type for an organization. Google writes that adding organization markup to a homepage can help it understand your organization's administrative details and tell it apart from other organizations. According to the same page, some properties work behind the scenes to disambiguate (such as iso6523Code and naics), while others can influence how things look in Search results (such as which logo is shown).

Three points from Google's documentation (last updated 8 September 2026):

• There are no required properties. Add the recommended ones that apply to your organization.
• Google recommends placing this on the homepage or on a single page that describes the organization, such as an about page. It does not need to be on every page.
• Use the most specific subtype that fits. For an online shop, OnlineStore instead of OnlineBusiness; for a physical business, a LocalBusiness subtype.

Google's AI features documentation (last updated 10 December 2025) also says there is no special schema.org structured data you need to add to appear in AI Overviews and AI Mode. So Organization schema is not a condition for entering AI answers; it is a way to describe your organization correctly. We found no evidence that it raises the chance of being picked in AI answers.

Which fields do you fill in?

From Google's recommended properties, the ones that matter for a company site:

A made-up example in JSON-LD (the company, address and numbers are invented; it only shows the format):

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "@id": "https://www.example.com/#organization",
  "name": "Örnek Mutfak",
  "legalName": "Örnek Mutfak Gereçleri Anonim Şirketi",
  "url": "https://www.example.com/",
  "logo": "https://www.example.com/logo-512.png",
  "address": {
    "@type": "PostalAddress",
    "streetAddress": "Örnek Mah. Örnek Sok. No: 1",
    "addressLocality": "Kadıköy",
    "addressRegion": "İstanbul",
    "postalCode": "34000",
    "addressCountry": "TR"
  },
  "telephone": "+90-212-000-00-00",
  "taxID": "TAX-ID-HERE",
  "sameAs": [
    "https://www.linkedin.com/company/example",
    "https://www.instagram.com/example"
  ]
}
</script>

Why @id and the name matter is explained below.

How do you write the legal name (legalName)?

Google describes legalName as the "registered, legal name" and asks for it only when it differs from name. If your brand name and company name are not the same, put them in separate fields: the everyday brand name in name, the company name in legalName.

We suggest writing the trade name exactly as it appears in the trade registry, with no abbreviation (this is our suggestion; Google's page gives no detail on spelling). The name in the schema should match the one on your contact page. Google's AI features documentation also asks that structured data match the visible text.

Should the tax number go into the schema?

First, what we know.

What Google says. taxID is defined as the tax ID associated with your organization, if applicable, and must match the country you give in the address field. For vatID, Google writes that it is an important trust signal because users can look up a business in public VAT registries. On schema.org, taxID is the tax or fiscal ID of an organization or person; vatID is the value-added tax ID with a national prefix (example: IT123456789).

What Turkish rules say. This part rests on legal text but is not advice:

• Article 5 of the Regulation on Electronic Commerce Intermediary Service Providers and Electronic Commerce Service Providers (Official Gazette, 29 December 2022, issue 32058) asks an e-commerce service provider that sells on its own site to keep certain information on the homepage, under a "contact" heading. For a merchant (tacir): trade name, MERSIS number and head-office address. For a tradesperson or craftsperson (esnaf ve sanatkâr): name and surname, tax identification number and head-office address. Other information such as the registered e-mail (KEP) address, e-mail, phone number and, if any, the business name and registered trademark is also required.
• So for a merchant selling online, the number the Regulation wants visible is the MERSIS number; the tax ID is listed for tradespeople and craftspeople. We read the text from the Official Gazette page; we did not check later amendments, so verify the current version before relying on it.
• This Regulation is for those who sell online. We could not verify whether the same duty applies to a corporate presentation site that sells nothing.

The personal data question. The Personal Data Protection Law (6698) defines personal data as "any information relating to an identified or identifiable natural person" (article 3). The tax number of a joint-stock or limited company is not information about a natural person. For a sole proprietorship the information may be tied to a natural person. We could not verify from a primary source how the tax number of a sole proprietorship is formed. If you are a sole proprietor, ask your accountant before publishing the number.

Our suggestion (not a rule):

1. Put only information already visible on the page into the schema. If your contact page shows no tax number, do not add one to the schema.
2. Make publishing the tax number a deliberate decision inside the company, so nobody has to ask later why it was published.
3. If the number belongs to a natural person rather than the company, do not add it.
4. We could not verify whether to write vatID for Turkey: Google's example shows a code with a country prefix, and we have no primary source for the Turkish equivalent. If unsure, leave it out.

Google has no field for the MERSIS number. The general schema.org identifier property accepts a PropertyValue (for example {"@type":"PropertyValue","propertyID":"MERSIS","value":"…"}); Google's documentation does not list it, so we do not claim any effect.

What goes into sameAs?

schema.org describes sameAs as the URL of a reference page that unambiguously indicates the item's identity, with a Wikipedia page, a Wikidata entry or an official website as examples. Google's example is the organization's profile page on a social media or review site.

In practice:

• List only real profiles the company manages: the LinkedIn company page, official social accounts, a Wikipedia or Wikidata entry if one exists, a store or marketplace profile.
• Do not list employees' personal accounts, closed accounts, or profiles opened only to get a link.
• Every address must open and belong to the same organization.

Ruescan's threshold here is at least 3 addresses; that is Ruescan's rule, not Google's.

Why should @id and the name be consistent?

In JSON-LD, @id is the keyword that uniquely identifies the node being described (W3C JSON-LD 1.1). If you give your organization a permanent @id such as https://www.example.com/#organization, other markup (for example the publisher of a blog post) can point to the same @id, and it is clear that the same organization is meant everywhere.

For the name, Google's sentence is clear: in name, use the same name and alternateName you use for your site name. Do not have three different spellings in the title, the share tag and the schema.

What is the picture on Turkish sites?

On 19 October 2026 we measured the homepages of 30 large Turkish sites across 8 sectors: in 13 of them we found no organization schema (Organization) in the first HTML. The sample is not random and the measurement is a pilot; a schema added later with JavaScript may not appear in it. Details: Are Turkey's biggest websites ready for AI? We measured 30.

The structure on our own homepage is a small version of what this article describes: an Organization node, a permanent @id, alternateName and sameAs profiles. We did not add a tax number.

Ruescan is Rueseo's site scanner; three of its 275 signals look at topics in this article: identity schema, permanent ID (@id) and official profiles (sameAs).

How do you test the schema?

Google's steps: validate the code with the Rich Results Test and fix critical errors; deploy on a few pages and use the URL Inspection tool to see how Google sees the page; make sure the page is not blocked by robots.txt, a noindex tag or a login. Re-crawling can take several days.

Frequently asked questions