Organization Schema for Korean Businesses: A Practical Guide

TL;DR

Organization schema is the most fundamental markup for getting search engines and AI to recognize your company or brand as a single entity. For a Korean business, doing it right means handling the schema.org standard plus Korea-specific information together.

1. Organization vs LocalBusiness — which one?

Decide this first.

Site type	Use
Online service, software, media	Organization
Physical storefront (restaurant, cafe, clinic, salon, retail)	LocalBusiness (subtype of Organization)
Both physical and online	One LocalBusiness covers it

Using LocalBusiness automatically includes all the Organization information. Don't use both — pick one.

This article uses Organization as the base, with LocalBusiness-only properties at the end.

2. The three required properties

{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "E:LAB Studio",
  "url": "https://elab-studio.xyz",
  "logo": "https://elab-studio.xyz/logo.png"
}

These three are non-negotiable.

• name — the official company name. Displayed verbatim on the brand card in search results.
• url — official website URL, at the domain level (not a page URL).
• logo — a square or rectangular PNG/SVG. Must be at least 112x112px and an absolute, externally accessible URL for Google to use it.

3. Korea-specific: address format

The standard way to map a Korean address to schema.org's PostalAddress:

{
  "address": {
    "@type": "PostalAddress",
    "streetAddress": "13 Banpo-daero 27-gil",
    "addressLocality": "Seocho-gu",
    "addressRegion": "Seoul",
    "postalCode": "06000",
    "addressCountry": "KR"
  }
}

Mappings to watch:

• streetAddress — road name address only (no city/district). You can include floor/unit, e.g. "13 Banpo-daero 27-gil, 3F."
• addressLocality — city or district (e.g. Seocho-gu, Gangnam-gu).
• addressRegion — metropolitan-level region (e.g. Seoul, Gyeonggi-do, Busan).
• addressCountry — must be the ISO 3166-1 alpha-2 code KR. Don't write "한국" or "Korea."

4. Korea-specific: phone numbers and business registration

{
  "telephone": "+82-2-1234-5678",
  "taxID": "608-29-62679"
}

• telephone — international (E.164) format. For Korean numbers: +82- followed by the number with the leading 0 dropped. Not "02-1234-5678" but "+82-2-1234-5678."
• taxID — Korean business registration number. There's no Korea-specific field in schema.org, so use taxID. Not displayed in search results directly, but used as an entity identifier and trust signal.

5. Connecting official channels with sameAs

sameAs is one of the most important signals for declaring "other official sources for this brand." It helps search engines and AI tie everything together into a single brand entity.

{
  "sameAs": [
    "https://www.instagram.com/your_brand",
    "https://www.youtube.com/@your_channel",
    "https://blog.naver.com/your_blog",
    "https://pf.kakao.com/_your_channel",
    "https://www.linkedin.com/company/your-company"
  ]
}

For a Korean business, always include the Naver blog and Kakao channel. Both carry weight in the Korean search market. There's no cap on how many channels you list — include every official one you operate.

6. contactPoint (customer support)

Spell out the official channels where customers can reach you.

{
  "contactPoint": {
    "@type": "ContactPoint",
    "telephone": "+82-2-1234-5678",
    "email": "support@example.com",
    "contactType": "customer support",
    "areaServed": "KR",
    "availableLanguage": ["ko", "en"]
  }
}

Use standard values for contactType: "customer support", "billing support", "technical support", "sales". If you have multiple channels, list them as an array.

7. Korean timezone and business hours (LocalBusiness only)

For physical storefronts (LocalBusiness), specify opening hours. Korea Standard Time (KST, +09:00) doesn't need to be declared separately — just use 24-hour format.

{
  "@type": "Restaurant",
  "openingHoursSpecification": [
    {
      "@type": "OpeningHoursSpecification",
      "dayOfWeek": ["Monday", "Tuesday", "Wednesday", "Thursday", "Friday"],
      "opens": "09:00",
      "closes": "21:00"
    },
    {
      "@type": "OpeningHoursSpecification",
      "dayOfWeek": ["Saturday", "Sunday"],
      "opens": "10:00",
      "closes": "22:00"
    }
  ]
}

For closed days, leave them out of OpeningHoursSpecification.

8. Full example (production-ready)

A complete Organization JSON-LD for a Korean company combining everything above.

{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "E:LAB Studio",
  "alternateName": "이랩스튜디오",
  "url": "https://elab-studio.xyz",
  "logo": "https://elab-studio.xyz/logo.png",
  "image": "https://elab-studio.xyz/og-image.png",
  "description": "Brand structure studio for the AI search era.",
  "address": {
    "@type": "PostalAddress",
    "streetAddress": "13 Banpo-daero 27-gil",
    "addressLocality": "Seocho-gu",
    "addressRegion": "Seoul",
    "postalCode": "06000",
    "addressCountry": "KR"
  },
  "telephone": "+82-2-1234-5678",
  "taxID": "608-29-62679",
  "email": "contact@elab-studio.xyz",
  "founder": { "@type": "Person", "name": "Kyungchan Yang" },
  "foundingDate": "2024-01-01",
  "contactPoint": {
    "@type": "ContactPoint",
    "telephone": "+82-2-1234-5678",
    "email": "contact@elab-studio.xyz",
    "contactType": "customer support",
    "areaServed": "KR",
    "availableLanguage": ["ko", "en"]
  },
  "sameAs": [
    "https://www.instagram.com/elab_studio",
    "https://blog.naver.com/elab_studio",
    "https://pf.kakao.com/_elab"
  ]
}

9. Common mistakes

Build it yourself