← All articles

Websites

Structured data for local businesses: the 5 schema types that matter

Copy-ready JSON-LD for LocalBusiness, Organization, Service, BreadcrumbList and Review, plus what Google changed with FAQ rich results in 2026.

7 min read

For most local businesses, five schema types cover everything worth marking up: LocalBusiness (using the most specific subtype), Organization, Service, BreadcrumbList, and Review, the last one only in a narrow case. Add them as JSON-LD, make sure every value matches what's visible on the page, and test before you publish. FAQ markup, which many guides still push, no longer produces anything in Google: the FAQ rich result was retired in May 2026. Below are copy-ready examples and the rules that decide whether they help or get ignored.

What structured data does, and what it doesn't

Structured data is a block of code that describes your page in a vocabulary search engines agree on (schema.org). It doesn't change what visitors see. It tells machines, without guesswork, that "514-555-0100" is your phone number, that you close at 17:00 on Fridays, and that "Commercial floor stripping" is a service you sell.

Three limits to keep in mind:

  • No guarantees. Google's guidelines say plainly that it "does not guarantee that your structured data will show up in search results." Correct markup makes you eligible for a feature; it doesn't force one.
  • It must match the page. Google's rule: "Don't mark up content that is not visible to readers of the page." Hours in your markup that aren't on the page, or that contradict your Google Business Profile, are worse than none.
  • It isn't a ranking shortcut. It helps search engines understand the page. The page still has to be good.

Google recommends JSON-LD "if your site's setup allows it." It's a separate <script type="application/ld+json"> block, which makes it easy to add and maintain. All the examples below use it. Replace the example values with your own.

LocalBusiness: the one every location needs

This is the core. Google requires only name and address, and recommends telephone, url, openingHoursSpecification, geo and priceRange, among others.

Use the most specific subtype schema.org offers: Plumber, Electrician, Dentist, AutoRepair, HealthClub, Restaurant and many more. Google's documentation says you can list several types in an array, for example ["Electrician", "Plumber"]. If nothing specific fits, LocalBusiness itself is fine.

``html <script type="application/ld+json"> { "@context": "https://schema.org", "@type": "Plumber", "@id": "https://www.example.ca/#business", "name": "Example Plumbing Inc.", "url": "https://www.example.ca/", "telephone": "+1-514-555-0100", "email": "info@example.ca", "image": "https://www.example.ca/images/storefront.jpg", "priceRange": "$$", "address": { "@type": "PostalAddress", "streetAddress": "123 Example Street", "addressLocality": "Laval", "addressRegion": "QC", "postalCode": "H7A 0A1", "addressCountry": "CA" }, "geo": { "@type": "GeoCoordinates", "latitude": 45.60000, "longitude": -73.70000 }, "openingHoursSpecification": [ { "@type": "OpeningHoursSpecification", "dayOfWeek": ["Monday", "Tuesday", "Wednesday", "Thursday", "Friday"], "opens": "08:00", "closes": "17:00" } ], "areaServed": ["Laval", "Montréal", "Terrebonne"] } </script> ``

Practical notes:

  • Coordinates: Google asks for at least five decimal places. Take them from your pin in Google Maps.
  • Phone format: include the country code.
  • Multiple locations: put one LocalBusiness block on each location's own page, with that location's address, phone and hours. Don't stack all locations on the homepage.
  • Seasonal hours: openingHoursSpecification accepts validFrom and validThrough, so a landscaping company can mark winter closures.
  • Service-area businesses that hide their address on Google should think twice before publishing a street address in markup that isn't shown on the site. Markup must reflect what's visible.

Organization: who you are as a company

LocalBusiness is a subtype of Organization, so a single-location business can often stop at the block above. Organization markup matters more when you have several locations, or a brand that's separate from any one storefront.

Google says Organization has no required properties and recommends placing it on your homepage or an about page, not on every page.

``html <script type="application/ld+json"> { "@context": "https://schema.org", "@type": "Organization", "@id": "https://www.example.ca/#organization", "name": "Example Plumbing Inc.", "legalName": "9999-9999 Québec Inc.", "url": "https://www.example.ca/", "logo": "https://www.example.ca/images/logo.png", "telephone": "+1-514-555-0100", "email": "info@example.ca", "foundingDate": "1998", "sameAs": [ "https://www.facebook.com/exampleplumbing", "https://www.instagram.com/exampleplumbing", "https://www.linkedin.com/company/exampleplumbing" ] } </script> ``

The sameAs list ties your website to your official profiles elsewhere. Only list profiles you control and keep active.

Service: describing what you actually sell

Google has no rich result for the Service type, so don't expect anything to change visually. It's still worth adding to each service page because it states clearly what the service is, who provides it and where. Schema.org defines provider, areaServed, serviceType, offers and description for it.

``html <script type="application/ld+json"> { "@context": "https://schema.org", "@type": "Service", "name": "Water heater installation", "serviceType": "Water heater installation", "description": "Installation and replacement of electric and gas tank water heaters for homes and small commercial buildings.", "provider": { "@id": "https://www.example.ca/#business" }, "areaServed": [ { "@type": "City", "name": "Laval" }, { "@type": "City", "name": "Montréal" } ], "url": "https://www.example.ca/services/water-heater-installation/" } </script> ``

The "@id" reference points back to the LocalBusiness block, so search engines connect the service to your business instead of treating it as a stray entity. Use the same @id value everywhere.

Only add an offers block with a price if that price is shown on the page and is the real price a customer pays. If you quote case by case, leave it out.

Breadcrumb markup tells Google where a page sits in your site, and Google can show that trail in desktop results. It's one of the few types here with a visible effect, and it's easy.

``html <script type="application/ld+json"> { "@context": "https://schema.org", "@type": "BreadcrumbList", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "Services", "item": "https://www.example.ca/services/" }, { "@type": "ListItem", "position": 2, "name": "Water heater installation" } ] } </script> ``

Google requires at least two items. The last item can skip item, and Google will use the current page's URL. Google also recommends breadcrumbs that follow how a person would browse your site, not necessarily your URL folders.

Review: valid, but rarely on your own site

This is where most local businesses get it wrong. Google's review snippet rules say that if the entity being reviewed controls the reviews about itself, its pages using LocalBusiness or Organization markup are not eligible for star ratings. That includes testimonials you paste into your own markup and reviews pulled in through a third-party widget.

In plain terms: marking up your own Google reviews or testimonials on your own site will not get you stars in search results. Google supports LocalBusiness reviews only for sites that review other businesses, like a directory or a review platform.

What you should do instead:

  • Show real reviews on the page as normal text, with a link to your Google profile.
  • Put your effort into getting more and more recent reviews on your Google Business Profile, where they do affect local visibility.
  • If you sell products with genuine product reviews, Product markup with reviews follows different rules. That's a separate topic.

Never invent ratings or review counts in markup. Google lists fake reviews as an example of misleading markup, and a structured data manual action removes a page's eligibility for rich results.

What happened to FAQ schema

For years, FAQPage markup could make your result taller with expandable questions. Google limited that to "well-known, authoritative government and health websites" in 2023, then deprecated the feature entirely: according to Google's documentation updates, it stopped appearing in Search on May 7, 2026, and the documentation was removed in June 2026.

So:

  • Keep FAQ sections on your pages if they answer real customer questions. They help people, and the text is still indexed like any other content.
  • Don't spend time adding FAQPage markup for Google. If it's already there and valid, removing it isn't urgent.
  • Be wary of any SEO audit in 2026 that lists "missing FAQ schema" as a priority.

Test before and after publishing

  1. Paste the page URL or the code into Google's Rich Results Test. It flags errors and shows which features the page is eligible for.
  2. After launch, check the enhancement reports in Search Console (breadcrumbs, for example) for errors across the whole site.
  3. Re-check whenever you change hours, phone numbers or addresses. Outdated markup is a common, quiet problem after a move or a new phone system.

For a bilingual site, each language version gets its own markup with text in that language and its own URLs. The business name, phone and address stay identical.

Where this fits in a site build

When PNE rebuilt the website for DC Maintenance, a Quebec commercial and industrial cleaning company operating since 1990, the old site had no sitemap and no structured metadata. The rebuild added the first sitemap, structured metadata and per-service pages in the company's history, across 28 pages in French and English. That's the normal approach in our website design work: markup is generated from the same data as the visible page, so the hours on screen and the hours in the code can't drift apart. You can see the project in the DC Maintenance case study. If you're also deciding how to structure location content, our article on city pages for service businesses covers that side.

Sources

Free website review

Want a site that brings in calls?

Tell us about your business and your current site. We’ll reply with what we would change first.

Prefer to talk? Book a free 30-minute call or call +30 694 022 3552.

Keep reading