Dokaz Industries DK logo Dokaz Industries
Structured data · October 20, 2026 · By

How to add LocalBusiness schema markup to your website

A copy-and-edit JSON-LD template that tells search engines and AI assistants your name, address, phone, hours and area in a form they do not have to guess at.

What is LocalBusiness schema markup?

It is a short block of code that describes your business to software. The format is called JSON-LD. It lists your name, address, phone number, opening hours and the area you serve. Search engines and AI assistants can read your visible page, but structured data removes the guesswork.

It does not guarantee anything. It does not replace having the same facts written on the page. Think of it as a label on the box, not the contents.

Do I need schema markup if I already have a Google Business Profile?

It is worth adding, but it does a different job. Your profile describes you on Google's own pages. The markup describes you on your website, to any software that reads it. If you have no website, there is nowhere to put it, and the profile matters more. If you do have one, the markup takes under an hour and rarely needs touching.

The template

Copy this, replace every value with your own, and keep the structure. The business below is made up. The number, address and web address are placeholders.

JSON-LD
{
  "@context": "https://schema.org",
  "@type": "Plumber",
  "@id": "https://www.example.com/#business",
  "name": "Example Plumbing",
  "url": "https://www.example.com/",
  "telephone": "+1-555-555-0100",
  "image": "https://www.example.com/images/van.jpg",
  "description": "Residential plumbing repair and water heater installation.",
  "address": {
    "@type": "PostalAddress",
    "streetAddress": "100 Example Street",
    "addressLocality": "Exampleville",
    "addressRegion": "WA",
    "postalCode": "98000",
    "addressCountry": "US"
  },
  "areaServed": ["Exampleville", "Sampletown"],
  "openingHoursSpecification": [
    {
      "@type": "OpeningHoursSpecification",
      "dayOfWeek": ["Monday", "Tuesday", "Wednesday", "Thursday", "Friday"],
      "opens": "08:00",
      "closes": "17:00"
    }
  ],
  "sameAs": [
    "https://www.facebook.com/exampleplumbing"
  ]
}

What each field means

FieldWhat to put there
@typeThe most specific kind of business that fits you. See the next section.
@idYour home page address followed by #business. It names the business so other blocks can point at it.
nameYour business name exactly as it appears on your sign and your Google profile.
urlYour home page address.
telephoneThe number customers call, with the country code.
imageThe full address of a real photo: the storefront, the van or the team.
descriptionOne plain sentence about what you do. No slogans.
addressYour street address, town, state, postcode and country, each in its own line.
areaServedThe towns or areas you work in, if you travel to customers.
openingHoursSpecificationYour regular hours. One entry per group of days that share the same hours.
sameAsLinks to your profiles elsewhere, such as Facebook or a trade directory.

Leave out any field you cannot fill honestly. A missing field is better than a wrong one.

Pick the most specific type

The "@type" line should be the most specific one that fits. schema.org has types for most trades. They include Plumber, Electrician, RoofingContractor, HVACBusiness, Restaurant, CafeOrCoffeeShop, Bakery, Dentist, HairSalon, BeautySalon and AutoRepair. If nothing fits, use LocalBusiness. Browse the list at schema.org/LocalBusiness.

How do I write opening hours that change through the week?

Add one entry for each group of days that share the same hours. Days you are closed are simply left out. Here is a business open weekdays all day and Saturday morning, closed Sunday. It replaces the list after "openingHoursSpecification" in the template:

JSON-LD
[
  {
    "@type": "OpeningHoursSpecification",
    "dayOfWeek": ["Monday", "Tuesday", "Wednesday", "Thursday", "Friday"],
    "opens": "08:00",
    "closes": "17:00"
  },
  {
    "@type": "OpeningHoursSpecification",
    "dayOfWeek": "Saturday",
    "opens": "09:00",
    "closes": "13:00"
  }
]

Times use the 24-hour clock with a leading zero. Write "09:00", not "9am". If you close for lunch, give that day two entries: one for the morning and one for the afternoon. For a one-off holiday closure, set special hours on your Google profile. That is where most people check first.

Edge cases

  • You work from home and do not publish your address. Then do not put it in the markup either. Give your town in addressLocality and list the areas you cover in areaServed. The markup should never reveal more than the page does.
  • You have more than one location. Give each location its own page and its own block, with its own @id, address, phone and hours.
  • You run two businesses from one address. Give each its own block and its own @id. Do not merge them into one.
  • Your site has one page. Put the block on that page. That is enough.

Where do I put schema markup on my website?

In the head of every page it describes, wrapped in a script tag. That is usually your home page and your contact page:

HTML
<script type="application/ld+json">
  { ...the JSON above... }
</script>
  • A site builder or content management system: look for a site-wide custom code or header setting, or an SEO add-on with a local business section that writes this for you.
  • A hand-built site: paste it into the head of the page.

If a plugin already writes a block for you, do not add a second one by hand. Two blocks that describe the same business with different details give the machine two answers.

How do I test schema markup?

Paste your page address into a validator and fix what it flags. Two free ones work:

  • Google's Rich Results Test, which shows what Google reads from the page.
  • The Schema Markup Validator at validator.schema.org, which checks the code against schema.org itself.
  • Fix any error before worrying about warnings. A JSON-LD block with a stray comma is silently ignored, and nothing on the page looks wrong.
  • Test again after every edit. A missing quote mark is the most common cause of a broken block.

Mistakes that make it useless

  • Markup that does not match the page. If the JSON says you open at 8 and the page says 9, you have given the machine two answers.
  • Marking up reviews you wrote or collected yourself. Google's guidelines exclude a business's own reviews of itself, and invented ratings can earn a penalty. Leave aggregateRating out unless it reflects real reviews shown on the page.
  • Several different business names across pages, or the wrong type. Use one "@id" for the business and reuse it.
  • Copying a template and leaving its placeholder values in. Check every line, including the image address.
  • Forgetting to update it. When your hours change, change the JSON too.

Structured data is one of the checks in our free check. If you would rather have it done and kept current, the websites we build ship with it already written from your details; see Techne.

Questions

Will schema markup improve my search ranking?

Do not expect it to on its own. It helps software read your facts correctly. Being read correctly is useful, but it is not the same as being ranked higher.

Can a page have more than one JSON-LD block?

Yes. A page can carry one block for the business and another for something else, such as a breadcrumb trail. Just do not describe the same business twice with different details.

Does it matter if the markup and my Google profile disagree?

Yes. Every source that disagrees makes software guess. Pick one set of facts and copy it everywhere, word for word.

Sources