Local Schema Markup: Use Accurate Business Facts.

Start with a real location page

Before writing JSON-LD, confirm the public business name, address, phone, hours, and services. Put accurate information on the visible page. Structured data should describe that information rather than create a second, conflicting version.

For a service-area business, check what information should be published and which Google Business Profile rules apply. Do not invent a storefront address to resemble a local competitor.

Build a minimal example

The following is illustrative markup, not an actual business listing. Replace every example value and check the required and recommended fields for your business type.

{
  "@context": "https://schema.org",
  "@type": "LocalBusiness",
  "name": "Example Repair Shop",
  "url": "https://example.com/location/",
  "telephone": "+1-202-555-0100",
  "address": {
    "@type": "PostalAddress",
    "streetAddress": "123 Example Street",
    "addressLocality": "Washington",
    "addressRegion": "DC",
    "postalCode": "20001",
    "addressCountry": "US"
  }
}

Test what you publish

1. Validate the syntax and supported properties with the appropriate tools.
2. Compare every value with the visible page.
3. Confirm the page is accessible to Google.
4. Inspect the published version rather than relying on a draft preview.
5. Update both the page and markup when business information changes.

Keep expectations realistic

Valid structured data can support eligibility for relevant search features, but their display is not guaranteed. It does not override the local ranking considerations of relevance, distance, and prominence.

Keep your Business Profile information accurate, respond to reviews constructively, and maintain useful location content. Avoid adding fabricated ratings or copying review totals from somewhere else without checking the applicable guidelines. Markup is a description of your business; it is not a shortcut around the work of representing it accurately.