How to Add Schema Markup to a Local Business Website (Step-by-Step)

Table of Contents

• What Local Business Schema Markup Actually Tells Google
• Why Schema Markup Still Matters for Local SEO in 2026
• Step 1: Pick the Right Schema Type for Your Business
• Step 2: Build Your LocalBusiness JSON-LD Code
• Step 3: Place the Schema Code on Your Website's Pages
• Step 4: Validate the Markup with Google's Rich Results Test
• Step 5: Keep NAP Data Consistent Everywhere It Appears
• Common Local Business Schema Mistakes That Waste the Effort
• Should You Use a Plugin or Hand-Code the Schema
• FAQ

A customer searches for your business by name, and Google shows a competitor's hours instead of yours, or no rich result at all even though your site clearly lists your address and phone number. That's usually not a content problem; it's a code problem. Search engines and AI answer tools can't reliably parse the visible text on your page the way a human can, so if your business facts aren't marked up in a machine-readable format, they get guessed at, or skipped entirely. This guide walks through exactly how to add LocalBusiness schema markup to your website, step by step, and how to validate it before it costs you visibility.

What Local Business Schema Markup Actually Tells Google

Schema markup is structured code, usually written in JSON-LD format, that labels your business name, address, phone number, hours, and category explicitly, so search engines don't have to infer them from surrounding text. Instead of Google reading your footer and hoping it correctly identifies "123 Main St" as your address, schema tells it directly: this is the address, this is the phone number, this is the business type.

Google's own Local Business structured data documentation lists the required and recommended properties for the LocalBusiness type, including name, address, and telephone. Following that spec matters more than guessing at what "good" schema looks like from a random blog post.

Structured data doesn't guarantee a ranking boost by itself. What it does is make eligible content easier to surface in rich results, knowledge panels, and AI Overviews. Think of it as translation, not persuasion.

Why Schema Markup Still Matters for Local SEO in 2026

AI-driven search surfaces, including Google's AI Overviews, ChatGPT, and Perplexity, lean on structured, machine-readable facts more than unstructured prose when they assemble an answer. A paragraph buried in your "About Us" page might mention your hours in passing; a schema block states them in a format the AI can pull without interpretation.

Here's the practical gap this creates: a Las Vegas HVAC company and a Henderson dentist can have nearly identical page copy, similar word counts, similar keyword targeting, and very different visibility in local results if only one of them has clean LocalBusiness markup in place. The content quality is a tie. The machine-readability isn't.

It's worth being clear about what schema is not. It's one input among several, working alongside solid on-page content and a complete Google Business Profile, not replacing either one. If your profile is unclaimed or your page copy is thin, no amount of JSON-LD will fix that on its own.

Step 1: Pick the Right Schema Type for Your Business

Start with LocalBusiness as the base type, then narrow to a more specific subtype when one applies, like Restaurant, Dentist, HomeAndConstructionBusiness, or ProfessionalService. Schema.org defines this type hierarchy, and the more specific subtype you use, the more precise a signal you're sending, compared to leaving everything at the generic LocalBusiness level.

A few things to check before you start writing code:

• Multi-location businesses need one schema block per physical location, not a single sitewide block listing every address you operate out of.
• Check the schema.org type hierarchy first; it's a short lookup and it prevents you from defaulting to the generic type when a closer match exists.
• If your business genuinely spans categories (a med spa that's also a retail storefront, for example), pick the type that reflects the primary customer-facing service.

Step 2: Build Your LocalBusiness JSON-LD Code

At minimum, your JSON-LD needs four fields: name, address (as a nested PostalAddress object, not a flat string), telephone, and url. These are the fields Google's documentation treats as foundational for the type.

Beyond the minimum, a handful of recommended fields meaningfully improve your odds of rich-result eligibility:

Field	What it does
openingHoursSpecification	Lists structured hours instead of freeform text
priceRange	Signals cost tier ($ to $$$$) for comparison shopping
image	Associates a representative photo with the listing
geo	Provides latitude/longitude for map-based results
sameAs	Links to your social profiles and directory listings for entity confirmation

You can write the JSON-LD by hand, generate it through a schema plugin, or export it from your CMS. The output format matters less than one thing: every value in the code has to match what's actually visible on the page. A phone number in the schema that doesn't match the one in your footer is worse than no schema at all.

Step 3: Place the Schema Code on Your Website's Pages

Once the code is built, drop the <script type="application/ld+json"> block in the <head> or just before the closing </body> tag, on your homepage, contact page, and any dedicated location pages.

Don't bury schema on a page users never visit. Google's Local Business documentation recommends placing the markup on the pages that actually represent that business location, meaning the pages a customer would land on to confirm you're real and find you.

On WordPress or Shopify sites, a schema plugin (AIOSEO, Schema Pro, WPSchema) can automate this placement and keep it synced with your CMS fields. On custom-built sites, especially owner-editable web builds on frameworks like Next.js, hand-coded JSON-LD gives you tighter control and avoids depending on a plugin ecosystem that may not exist for your stack.

Step 4: Validate the Markup with Google's Rich Results Test

Before anything goes live, run the finished code through Google's Rich Results Test and the Schema Markup Validator. This step gets skipped more often than it should, and it's the fastest way to catch a typo that silently breaks the whole block.

• Fix every critical error the tool flags. Warnings are optional cleanup; critical errors mean the block may be ignored entirely by search engines.
• Re-test after any redesign, CMS migration, or theme update. Third-party scripts and page builders frequently strip or duplicate <script> tags without any warning in your CMS dashboard.

A schema block that validated cleanly six months ago isn't guaranteed to still be intact today, especially after a platform update. Treat validation as a recurring check, not a one-time task.

Step 5: Keep NAP Data Consistent Everywhere It Appears

NAP stands for name, address, and phone, and it needs to match, character for character, across your schema markup, your Google Business Profile, your website footer, and any citation directories you're listed on.

Small inconsistencies cause outsized trust problems. An abbreviated street name in one place and a spelled-out version in another, an outdated phone number left in the schema after a provider switch, a missing suite number, these all create the same doubt for search engines that inconsistent citations across the web do.

Field	Where to check it	Common mistake
Name	Schema, GBP, footer	Adding "LLC" in one place, not another
Address	Schema, GBP, directories	Abbreviating "Suite" as "Ste" inconsistently
Phone	Schema, GBP, footer	Leaving an old number live after a provider change

Review NAP consistency any time you move offices, open a second Las Vegas or Henderson location, or change phone providers. It takes ten minutes and prevents months of quiet confusion in local rankings.

Common Local Business Schema Mistakes That Waste the Effort

A few mistakes come up often enough to call out directly:

1. Marking up information that isn't visible anywhere on the page. Google's guidelines treat this as markup that misrepresents page content, and it's a documented policy risk, not just a best-practice suggestion.
2. Using the generic LocalBusiness type when a more specific subtype exists. If you run a dental practice, Dentist gives search engines more to work with than the generic parent type.
3. Copy-pasting a schema template across every service page without updating the address or areaServed fields, which produces duplicate, contradictory location signals instead of a clean single source of truth.
4. Never validating after a site migration, so broken markup sits unnoticed for months while nobody realizes the rich results quietly disappeared.

Each of these is easy to avoid once you know to check for it, which is exactly why they're worth listing out before you start building.

Should You Use a Plugin or Hand-Code the Schema

The honest answer depends on your platform, not on which approach is objectively "better."

A plugin is the faster path on WordPress or Shopify sites where you're not touching raw code regularly. It also auto-updates the schema when opening hours or address fields change elsewhere in the CMS, so you're not manually syncing two places.

Hand-coded JSON-LD gives more control on custom builds, like a headless Next.js site, where a plugin ecosystem doesn't really exist. It also avoids the extra script weight that some SEO plugins add to page load, which matters if you're already tracking Core Web Vitals closely.

If you're already working with a developer on a custom build, it's worth asking them to wire schema generation directly into the CMS fields, the same way we approach owner-editable web builds, so the schema updates itself the moment business info changes instead of going stale. This pairs well with other structured-data work, like setting up an llms.txt file for AI crawlers, if you're trying to cover both traditional search and AI answer engines with the same underlying data.

If you're budgeting a full site rebuild rather than a patch job, it's also worth reviewing what a custom business website actually costs in 2026 before deciding whether to retrofit schema onto an existing platform or build it in from the start.

FAQ

How do I add schema markup to my website? Write or generate LocalBusiness JSON-LD code that includes your name, address, phone, and hours, then place it in the page's HTML head or body. Validate it with Google's Rich Results Test before publishing, and re-check it after any site redesign or CMS update.

Is schema markup still relevant for local SEO? Yes. Google's own structured data documentation continues to define required and recommended properties for LocalBusiness markup, and AI-driven search tools lean on structured facts when assembling answers. It's a supporting signal, not a replacement for content and a complete Google Business Profile.

Does LocalBusiness schema need to go on every page? No. It belongs on pages that represent the business location itself, typically the homepage, contact page, and any dedicated location pages for multi-location businesses. Service or blog pages don't need a duplicate LocalBusiness block.

What's the difference between LocalBusiness and Organization schema? Organization schema fits companies without a physical customer-facing address, like a fully remote agency. LocalBusiness schema (and its subtypes like Restaurant or Dentist) fits businesses with a physical location customers visit or a defined service area, and supports address, hours, and geo fields Organization doesn't emphasize.

Can I add schema markup without a plugin? Yes. You can hand-code a JSON-LD script block and paste it directly into your site's HTML, which works on any platform including custom-built sites. Plugins just automate that process and keep it synced with CMS fields on platforms like WordPress or Shopify.

If you're rebuilding a booking flow or client intake process alongside your schema cleanup, our guide to building a booking website with online payments and our framework for automating client onboarding cover the pieces that usually come up next. Start with the JSON-LD code for your homepage and contact page today, run it through Google's Rich Results Test before you publish, and put a recurring reminder on your calendar to re-validate after your next site update.