Development Tips

Structured Data for Local Business Sites: What Actually Helps You Show Up in 2026

By Ken Key Aug 22, 2026 7 min read Updated Oct 16, 2026

Structured Data for Local Business Sites: What Actually Helps You Show Up in 2026
The short answer

Structured data won't raise your rankings by itself. What it does is remove ambiguity, confirm your hours, address, and services, and feed AI answer engines that pull facts instead of guessing. For local businesses, correct LocalBusiness, FAQ, and review markup still earns rich results and panels.

Part of the complete SEO guide.

On this page

Most local business sites either have no structured data at all or they have a plugin dumping the same generic markup on every page. Both are a waste. Here’s what actually matters in 2026, how to write it by hand, and how to check that it’s working.

I’ve been building and maintaining sites for small businesses around Commack and the rest of Long Island for a long time, and structured data is one of those things where a little careful work goes further than a lot of automated work.

What structured data does (and doesn’t do)

Structured data is machine-readable context about your page. It tells search engines and AI assistants what a thing is: this is a business, this is its address, these are its hours, this is a product with this price and this availability.

What it does not do is boost your rankings by existing. That was never true, and it’s less true now. Google has gotten much better at reading plain page content over the years, so schema is no longer a magic key to rich results. What it still does well:

  • Removes ambiguity. If your hours are in a table somewhere and also in a footer, markup tells the engine which one is authoritative.
  • Feeds AI assistants and answer engines that pull structured facts rather than parsing prose.
  • Powers specific rich results: reviews, FAQs, products, events, breadcrumbs, and local business panels.
  • Catches data errors. Google Search Console flags malformed markup, which often surfaces real content problems.

If you’re running a service business with a storefront, a contractor with a service area, or a shop with inventory, the local business and product types are where your effort belongs.

Start with LocalBusiness, done properly

The most common mistake I see is a plugin that outputs a bare LocalBusiness block with a name and nothing else. That’s nearly useless. Use the most specific subtype you can. Plumber, Dentist, Restaurant, AutoRepair, and HairSalon are all real types under LocalBusiness. Specificity helps.

Here’s a realistic example for a service-area business. Note that it’s JSON-LD in a script tag, which is what Google recommends.

<script type="application/ld+json">
{
 "@context": "https://schema.org",
 "@type": "HVACBusiness",
 "@id": "https://example.com/#business",
 "name": "Example Heating and Cooling",
 "url": "https://example.com/",
 "telephone": "+1-631-555-0100",
 "priceRange": "$$",
 "image": "https://example.com/img/storefront.jpg",
 "address": {
 "@type": "PostalAddress",
 "streetAddress": "123 Main St",
 "addressLocality": "Commack",
 "addressRegion": "NY",
 "postalCode": "11725",
 "addressCountry": "US"
 },
 "geo": {
 "@type": "GeoCoordinates",
 "latitude": 40.8429,
 "longitude": -73.2926
 },
 "areaServed": [
 { "@type": "City", "name": "Commack" },
 { "@type": "City", "name": "Smithtown" },
 { "@type": "City", "name": "Huntington" }
 ],
 "openingHoursSpecification": [
 {
 "@type": "OpeningHoursSpecification",
 "dayOfWeek": ["Monday","Tuesday","Wednesday","Thursday","Friday"],
 "opens": "08:00",
 "closes": "17:00"
 }
 ],
 "sameAs": [
 "https://www.facebook.com/examplehvac",
 "https://www.google.com/maps/place/example"
 ]
}
</script>

A few things worth calling out. The @id gives this entity a permanent handle so other pages can reference it instead of repeating it. areaServed is what tells engines you cover a region even if customers don’t visit you. And sameAs links your profiles together, which helps consolidate the entity across the web.

Put this on your homepage or a dedicated contact page, once. Don’t repeat it sitewide with a template tag if you can avoid it. If you must inject it globally, at least keep the @id consistent so you’re not declaring ten different businesses.

Don’t fake reviews

This is the one that gets people in trouble. Google’s guidelines are clear: you cannot mark up reviews you collected yourself and display on your own site as if they were first-party endorsements from a review platform. Self-serving review markup on your own business is against the rules and can trigger a manual action.

What you can do:

  • Mark up reviews on a page where the reviews genuinely came from a third party and are attributed.
  • Use AggregateRating only when the rating is real and verifiable, and be aware Google may simply ignore it for local businesses anyway.
  • Skip it entirely and let your Google Business Profile carry the reviews. That’s where they actually influence local pack placement.

I’ve seen more sites hurt by aggressive review markup than helped. When in doubt, leave it out.

FAQ and HowTo: still useful, just not for the old rich result

Google stopped showing FAQ rich results for most sites back in 2023. A lot of people concluded FAQ schema is dead. It isn’t. It still helps engines and AI systems understand the structure of your content, and it’s cheap to add.

<script type="application/ld+json">
{
 "@context": "https://schema.org",
 "@type": "FAQPage",
 "mainEntity": [
 {
 "@type": "Question",
 "name": "How much does a furnace tune-up cost?",
 "acceptedAnswer": {
 "@type": "Answer",
 "text": "A standard tune-up runs $120 to $180 depending on system type. We waive the fee if you sign up for an annual maintenance plan."
 }
 },
 {
 "@type": "Question",
 "name": "Do you offer emergency service?",
 "acceptedAnswer": {
 "@type": "Answer",
 "text": "Yes. We run 24/7 emergency calls across Commack and surrounding towns, with a $95 after-hours dispatch fee."
 }
 }
 ]
}
</script>

One rule: the FAQ content must be visible on the page. Marking up questions that don’t appear in the rendered HTML is a violation and does nothing useful.

Products, services, and breadcrumbs

If you sell physical goods, Product markup with offers is still the highest-value schema you can add, because merchant listings still show price and availability. Keep price, priceCurrency, and availability accurate. Stale availability data gets ignored fast.

For service businesses, Service markup is underused. It lets you describe what you offer, who it’s for, and the area covered, which pairs well with the LocalBusiness block above.

Breadcrumbs are the easiest win nobody bothers with. One small block on interior pages:

<script type="application/ld+json">
{
 "@context": "https://schema.org",
 "@type": "BreadcrumbList",
 "itemListElement": [
 { "@type": "ListItem", "position": 1, "name": "Home", "item": "https://example.com/" },
 { "@type": "ListItem", "position": 2, "name": "Heating", "item": "https://example.com/heating/" },
 { "@type": "ListItem", "position": 3, "name": "Furnace Tune-Ups" }
 ]
}
</script>

How to add this without a plugin fight

Most WordPress SEO plugins will output some schema for you, and then you’ll try to add your own, and now you have two conflicting blocks. Pick one owner. Either let the plugin handle the basics and extend it, or turn its schema off and hand-roll it.

If you’re comfortable in a theme, a small function in functions.php is clean enough:

add_action('wp_head', function () {
 if (!is_front_page()) return;
 $data = [
 '@context' => 'https://schema.org',
 '@type' => 'HVACBusiness',
 '@id' => home_url('/#business'),
 'name' => 'Example Heating and Cooling',
 'url' => home_url('/'),
 'telephone'=> '+1-631-555-0100',
 'address' => [
 '@type' => 'PostalAddress',
 'streetAddress' => '123 Main St',
 'addressLocality' => 'Commack',
 'addressRegion' => 'NY',
 'postalCode' => '11725',
 'addressCountry' => 'US',
 ],
 ];
 echo '<script type="application/ld+json">'
 . wp_json_encode($data, JSON_UNESCAPED_SLASHES)
 . '</script>';
}, 20);

If you’re on a custom build, whether it’s static HTML or a framework, this is exactly the kind of thing that’s easier to control when the markup is yours. That’s part of why I lean toward custom web development for local businesses instead of stacking plugins on a theme you don’t control. You get one clean JSON-LD block per page and no conflicts.

Test it, then leave it alone

Two tools, both free:

  • Rich Results Test at search.google.com/test/rich-results. Tells you which types Google recognizes on the page and what’s missing.
  • Schema Markup Validator at validator.schema.org. More thorough, checks against the full vocabulary, not just Google’s subset.

Then watch Search Console’s Enhancements reports for a few weeks. If something’s wrong, it’ll show up there with the specific page and error.

Once it validates, stop touching it. I’ve watched people “improve” working schema into a broken state more times than I can count. Add it, verify it, move on to content that actually earns traffic.

FAQ

Do I need structured data to rank locally?

No. Your Google Business Profile, reviews, citations, and on-page content do the heavy lifting for local rankings. Schema helps engines and AI assistants interpret your site correctly, and it can earn rich results, but it won’t move you up the map pack on its own.

Can I just use my SEO plugin’s schema and be done?

Usually not. Plugins tend to output a minimal generic block, and if you add your own on top you get duplicates and conflicts. Check what your plugin is emitting first, then either configure it properly or disable its schema and add your own.

Will adding FAQ schema bring back FAQ rich results?

For most sites, no. Google limited those to authoritative government and health sites in 2023. The markup still helps with content understanding and AI answer engines, so it’s worth keeping, just don’t expect the old dropdown in search results.

Have a project like this?

I do custom web development for Long Island businesses. If you need this done right, let’s talk.