Complete Guide to LocalBusiness Schema — Local Search Optimization for Korean SMBs

What Is LocalBusiness Schema

LocalBusiness schema reports information about physical stores or service businesses as structured data. It provides location, hours, phone number, and price range in a machine-readable form to help accurate information appear in Google local packs, knowledge panels, and AI answers.

It is one of the schemas where Korean SMBs can expect the most immediate ROI. It especially increases local pack visibility for geo-targeted queries such as "Gangnam dermatology" or "Hongdae cafe."

TL;DR

LocalBusiness schema: ① Required: name + address ② Use industry-specific subtypes (cafe → CafeOrCoffeeShop, dermatology → Dermatologist) ③ Write openingHoursSpecification accurately ④ Include geo coordinates with 5+ decimal places ⑤ Information must match Google Business Profile.

Industry Subtype Selection Guide

LocalBusiness is abstract. Schema.org has dozens of subtypes, and using the most specific subtype is recommended.

If no matching subtype exists, using LocalBusiness directly is acceptable.

Property Reference

Based on Google official documentation (verified June 2026).

Minimal Example

{
  "@context": "https://schema.org",
  "@type": "BeautySalon",
  "name": "Kroffle Beauty",
  "address": {
    "@type": "PostalAddress",
    "addressCountry": "KR",
    "addressRegion": "Seoul",
    "addressLocality": "Mapo-gu",
    "streetAddress": "15 Hongik-ro"
  },
  "telephone": "+82-2-1234-5678",
  "url": "https://kroffle-beauty.co.kr"
}

Recommended Example (Hours, Coordinates, Rating Included)

{
  "@context": "https://schema.org",
  "@type": "BeautySalon",
  "@id": "https://kroffle-beauty.co.kr/#localbusiness",
  "name": "Kroffle Beauty",
  "description": "A hair and nail salon located 3 minutes from Hongdae Station.",
  "url": "https://kroffle-beauty.co.kr",
  "telephone": "+82-2-1234-5678",
  "email": "hello@kroffle-beauty.co.kr",
  "image": "https://kroffle-beauty.co.kr/images/salon-main.jpg",
  "priceRange": "₩₩",
  "address": {
    "@type": "PostalAddress",
    "addressCountry": "KR",
    "addressRegion": "Seoul",
    "addressLocality": "Mapo-gu",
    "streetAddress": "15 Hongik-ro",
    "postalCode": "04066"
  },
  "geo": {
    "@type": "GeoCoordinates",
    "latitude": 37.55263,
    "longitude": 126.92354
  },
  "openingHoursSpecification": [
    {
      "@type": "OpeningHoursSpecification",
      "dayOfWeek": ["Monday", "Tuesday", "Wednesday", "Thursday", "Friday"],
      "opens": "10:00",
      "closes": "20:00"
    },
    {
      "@type": "OpeningHoursSpecification",
      "dayOfWeek": ["Saturday"],
      "opens": "10:00",
      "closes": "18:00"
    },
    {
      "@type": "OpeningHoursSpecification",
      "dayOfWeek": ["Sunday"],
      "opens": "00:00",
      "closes": "00:00"
    }
  ],
  "aggregateRating": {
    "@type": "AggregateRating",
    "ratingValue": "4.8",
    "reviewCount": "127",
    "bestRating": "5",
    "worstRating": "1"
  },
  "acceptsReservations": true
}

For closed days (Sunday closed), use opens: "00:00", closes: "00:00" or omit that element.

Adaptation for the Korean Market

Address format: Use the following structure for Korean addresses within PostalAddress:

• addressCountry: "KR"
• addressRegion: Province/city (e.g., "Seoul", "Gyeonggi-do")
• addressLocality: City/district (e.g., "Gangnam-gu", "Yeongtong-gu, Suwon")
• streetAddress: Road name address (e.g., "123 Teheran-ro")
• postalCode: 5-digit postal code

Phone number: Include international code (+82) and area code (drop leading 0) in format +82-2-1234-5678.

Price range: Use priceRange in format ₩, ₩₩, ₩₩₩, ₩₩₩₩.

Google Business Profile integration: LocalBusiness schema information must match information registered in Google Business Profile (name, address, phone). Mismatches can lower trust scores.

Common Mistakes

Wrong example: Using only openingHours string without openingHoursSpecification

"openingHours": "Mo-Fr 10:00-20:00"

Correct example: Use specific OpeningHoursSpecification array

"openingHoursSpecification": [
  {
    "@type": "OpeningHoursSpecification",
    "dayOfWeek": ["Monday", "Tuesday", "Wednesday", "Thursday", "Friday"],
    "opens": "10:00",
    "closes": "20:00"
  }
]

Wrong example: Approximate coordinates in geo

"geo": { "latitude": 37.5, "longitude": 127.0 }

Correct example: Accurate coordinates with 5+ decimal places

"geo": {
  "@type": "GeoCoordinates",
  "latitude": 37.55263,
  "longitude": 126.92354
}

Validation Methods

1. Google Rich Results Test: https://search.google.com/test/rich-results
2. Schema Markup Validator: https://validator.schema.org
3. Google Search Console: Monitor "Enhancements → Business" tab after implementation

Frequently Asked Questions

Q. Which is more important: LocalBusiness schema or Google Business Profile?
A. They are separate and both are needed. Google Business Profile is the direct channel for Google Maps and local pack visibility. LocalBusiness schema strengthens site trust and structural understanding. Best results come when both are maintained with consistent information.

Q. What if I have multiple locations?
A. Insert separate LocalBusiness schema on each location page. Connect locations to headquarters (Organization) via department or subOrganization.

Q. Can aggregateRating be composed only of on-site reviews?
A. Yes. Google allows using reviews collected on your own site in aggregateRating. However, if the site directly evaluates its own business (self-serving), it may be excluded from rich results.

References

• Google official LocalBusiness documentation: https://developers.google.com/search/docs/appearance/structured-data/local-business (verified June 2026)
• Schema.org LocalBusiness: https://schema.org/LocalBusiness