Does LocalBusiness or Service Schema Help AI Understand Business Details?

What does LocalBusiness markup do?

Google's local business documentation requires two properties, name and address. It recommends others, including:

• geo, with latitude and longitude to at least five decimal places;
• telephone, including the country and area code;
• openingHoursSpecification for hours;
• url, the URL of the specific location's page;
• priceRange, shorter than 100 characters, such as "$$" or "$50–$150";
• menu and servesCuisine for food businesses;
• department for businesses with distinct departments.

Google recommends using the most specific subtype of LocalBusiness, such as Plumber, Dentist or Restaurant. Because LocalBusiness is a kind of Organization, it also recommends the organisation fields, such as logo and sameAs. Review and rating markup is only recommended for sites that collect reviews about other businesses, not for your reviews of yourself.

What does Service markup do?

Schema.org's Service type can describe a service with its name, type, provider, area served and offers. It is valid, and some systems that read markup may use it. But Google's structured data gallery has no Service feature, and there is little evidence that AI assistants rely on it over the visible description of your services. Use it if it fits your platform. The services themselves still need to be described in words on the page. How specific those pages should be is covered in how specific service, location and customer pages should be for AI to understand a business.

Does markup help AI assistants specifically?

In limited ways:

• Google's AI features use Google's index. Google says structured data is not required for them, and that markup should match the visible content.
• Other assistants read the HTML they fetch. Most AI crawlers do not run JavaScript, so markup injected by a script or a tag manager may be invisible to them. Markup placed directly in the HTML is readable, but the visible text usually carries more weight.
• Consistency is the real benefit. A page whose markup, visible text and Business Profile all give the same hours and phone number leaves no conflict to resolve. Conflicting values are a common source of wrong answers.

How to add LocalBusiness JSON-LD schema for local AI visibility

Add one block per location page, in the page's HTML. An illustrative example for a fictional plumbing business:

{
  "@context": "https://schema.org",
  "@type": "Plumber",
  "name": "Harbour Lane Plumbing",
  "url": "https://www.example.com/locations/portside",
  "telephone": "+44 117 496 0000",
  "priceRange": "£60–£250",
  "address": {
    "@type": "PostalAddress",
    "streetAddress": "12 Harbour Lane",
    "addressLocality": "Bristol",
    "postalCode": "BS1 4QA",
    "addressCountry": "GB"
  },
  "geo": {
    "@type": "GeoCoordinates",
    "latitude": 51.44912,
    "longitude": -2.59740
  },
  "openingHoursSpecification": [
    {
      "@type": "OpeningHoursSpecification",
      "dayOfWeek": ["Monday", "Tuesday", "Wednesday", "Thursday", "Friday"],
      "opens": "08:00",
      "closes": "18:00"
    }
  ],
  "sameAs": ["https://www.example.com/company-profile"]
}

Then:

1. Match the visible page: the same name, address, phone and hours in text on the page.
2. Match your Business Profile and main directory listings.
3. Use one block per location, each on that location's own page with its own url.
4. Validate with Google's Rich Results Test and the Schema Markup Validator.
5. Update it with every change to hours or phone numbers, including holiday hours on the page.

How should different kinds of business structure it?

Single-location shops and offices. One block on the main contact or location page, with the most specific type, visible address, hours and phone. The home page can carry organisation markup with sameAs links to your profiles.

Multi-location businesses. A page per location, each with its own block, url, phone and hours. A locations index page links to every location page in plain HTML, so crawlers can reach them all. The organisation markup describes the brand once, and each location page can reference it.

Service-area businesses. If customers never visit you, describe the areas you serve in the page text, city by city where that matters. Keep the markup consistent with how your Business Profile handles the address.

Businesses with departments. A car dealer with sales and service, or a hospital with clinics, can use department for distinct parts with their own hours or phone numbers. Google lists department among its recommended properties.

Practitioners within a practice. Individual practitioners need their own records linked to the practice. For doctors, schema.org's IndividualPhysician type, a LocalBusiness subtype, with practicesAt pointing to the practice fits; lawyers and advisers are usually best described with Person markup on their own profile pages, linked to the practice's location page. Match whatever your Business Profile does: if a practitioner has their own profile, give them their own block.

Whatever the structure, the rule is the same. Every value in the markup should be something a visitor can see on that page, and something your Business Profile says too.

What mistakes should you avoid?

• One block listing every location on the home page. Each location needs its own page and block.
• Generic types such as LocalBusiness when a specific type exists.
• Service areas as addresses. Businesses that visit customers should not present an address customers cannot visit as a place to go, though legally required address details stay in the contact or legal section. Describe areas served in text, and follow Google's Business Profile rules on service areas.
• Self-serving review markup, which Google does not use for your own business.
• Markup copied across pages with the wrong URL or phone number.
• Hours in markup only. Visible hours matter more.

How organisation markup complements local markup is covered in how to add organization schema so AI can identify your business.

How do you tell whether it helped?

Markup rarely moves AI answers on its own, so test the combination of fixes:

• Ask assistants for your hours, phone number, address and price range, several times each.
• Record which answers are right and which sources they cite.
• Fix conflicts in any cited source, including directories and your Business Profile.
• Retest a month later.

If answers were already right, the markup is doing its job quietly as a consistent record. If they were wrong and cite a directory, the directory is the fix, not more markup.

What might an illustrative case look like?

Consider an illustrative dental practice with three locations, whose website had one LocalBusiness block on the home page listing the main surgery's address and hours for all three. Assistants gave the main surgery's Saturday hours for the other two, which were closed on Saturdays. The practice created a page for each location with visible hours and a Dentist block per page. It removed the home page block and updated its three Business Profiles to match. It also added holiday hours to each page. A month later, answers about Saturday opening were correct for all three locations.

What do people ask about local business markup?

Is LocalBusiness markup required for AI visibility?

No. It helps consistency, but visible text and your Business Profile matter more.

Should service-area businesses use LocalBusiness markup?

Yes, with care. Do not present an address customers cannot visit as a place to visit: remove it from your Business Profile, as Google requires, and in the markup give only the town and postcode, describing your service area in the page text. If the law requires your address on your website, such as the geographic address UK and EU rules require from businesses that advertise or take bookings online, or a UK company's registered office, keep it in your contact or legal details.

Can markup include opening hours for holidays?

Yes, with special opening hours entries. Show the same holiday hours visibly on the page.