Local Business Schema Markup: What to Add and What to Skip
Schema markup gets treated like a magic switch. Add it, rank better. That is not how it works. Google uses structured data to understand your site more clearly, and for local businesses, the right schema can earn you richer search results. But half the properties people add do nothing, and the wrong setup can quietly confuse rather than help. Here is what is actually worth your time.
On this page
What Schema Markup Actually Does for a Local Business
Structured data gives search engines a machine-readable version of information already on your page. For a local business, that means your address, phone number, opening hours, and business category. Google does not need schema to find this information. It reads your page either way.
What schema does is remove ambiguity. Instead of Google inferring that a string of digits is probably a phone number, you tell it directly. That confidence powers features like the business panel in local search results and rich snippets showing your hours inside Google Maps.
The Schema.org LocalBusiness type is the starting point. Everything branches from there.
Which Properties to Include
Keep the core tight. These are the fields Google consistently reads and uses for local results.
- @type , be specific. Use Plumber, Restaurant or LegalService rather than the generic LocalBusiness where a more precise type exists.
- name , your business name exactly as it appears across every other platform online. Consistency matters here.
- address , use PostalAddress with street, town, postcode and country. Match it to your Google Business Profile precisely.
- telephone , the number customers actually call. One number is enough.
- openingHoursSpecification , structured hours rather than a plain text string. This is what drives the open or closed display in search results.
- url , your canonical homepage URL.
- geo , latitude and longitude if you want to reinforce your precise location.
If you host genuine customer reviews directly on your own site, aggregateRating is worth including. Google is strict on this. You can only mark up ratings you host yourself. Do not pull your Google or Trustpilot score and present it as your own data.
What to Leave Out
This is where most implementations go wrong. Properties get added because they exist, not because they serve a purpose.
Avoid marking up description with a keyword-heavy paragraph. Google does not use it for rich results, and it reads as an attempt to game something that schema simply cannot game.
Skip sameAs unless your social profiles are well-maintained and consistent. Pointing Google at an abandoned Facebook page does not help. It creates a conflicting signal.
Leave hasMap out entirely. Once your address and geo coordinates are in place, it adds nothing useful.
Do not add schema for anything that is not on the page. If your contact details only appear in the footer, adding full service-area markup to a page that says nothing about those services is technically invalid. Google’s own guidance is clear on this. Structured data should describe content the user can actually see.
Why Content Has to Come First
When you add local business schema to your website, it sits on top of your content, not beneath it. It cannot rescue a weak page. We have seen this play out on a local company site where an outside SEO firm produced hundreds of poorly targeted pages chasing fast rankings. The schema on those pages was fine. The content was not. Rankings dropped, and the site picked up a quality signal problem that took months to clear.
Bad content is bad content. Marking it up with structured data only gives Google a clearer map to something it would rather not rank.
Adding It Without Breaking Things
JSON-LD is the format Google recommends, and it is the most straightforward to work with. Drop it into the <head> of the relevant page, or use a plugin that handles the output cleanly. On WordPress, choose a lightweight plugin that generates valid JSON-LD without bloating the page. Avoid plugins that inject dozens of schema types you never asked for.
Validate everything with Google’s Rich Results Test before you publish. Errors are not always fatal, but warnings about missing recommended fields are worth addressing if the field genuinely applies to your business.
Check your Google Search Console for schema errors a few weeks after implementing. The Enhancements section shows whether Google has processed your markup and whether anything has been flagged. That feedback loop tells you far more than a one-time validation check ever will.
What to Expect
Done properly, choosing to add local business schema to your website takes a few careful hours for a single location. That is a modest investment for a meaningful return. It is not a ranking shortcut, and it will not rescue a slow site or thin content. Think of it as tidying up the information Google already holds about your business. A clean signal beats a muddled one, and combined with solid fundamentals, it closes a gap that repays the effort.