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 that already exists on your page. For a local business, that means things like your address, phone number, opening hours and the type of business you run. 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 is what powers features like the business panel in local search results and rich snippets showing your hours directly in Google Maps.
The Schema.org LocalBusiness type is the starting point. Everything branches from there.
The Properties That Are Actually Worth Adding
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 specific type exists.
- name , your business name exactly as it appears everywhere else online. Consistency matters.
- 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.
- openingHoursSpecification , structured hours, not a text string. This is what powers the open or closed display in search.
- url , your canonical homepage URL.
- geo , latitude and longitude if you want to reinforce your precise location.
If you have genuine customer reviews on your site and you are aggregating them yourself, aggregateRating is worth including. Google is strict here, though. You can only mark up ratings you host. Do not pull in your Google or Trustpilot score and mark it up as your own data.
What to Skip
This is where most implementations go wrong. People add properties because they exist, not because they serve a purpose.
Avoid marking up description with a keyword-stuffed paragraph. Google does not use it for rich results. It reads as an attempt to game something that cannot be gamed through schema.
Skip sameAs unless your social profiles are well-maintained and consistent. Pointing Google at an abandoned Facebook page from four years ago does not help. It creates a signal conflict.
Ignore hasMap entirely. It is redundant when your address and geo coordinates are already present.
And do not add schema for things that are not genuinely on the page. If your contact details only appear in the footer, adding full service-area markup to a page that says nothing about it is technically invalid. Google’s own guidance is clear on this point. Structured data should describe content that a user can actually see.
The Content Problem Nobody Talks About
Schema is a layer on top of content. It does not rescue a weak page. In our experience working on a local company’s site, the owner later brought in an outside SEO firm that produced hundreds of poorly targeted pages to chase rankings fast. The schema on those pages was fine. The content was not. Rankings tanked, and the site picked up a quality signal problem that took a long time to recover from.
Bad content is bad content. Marking it up with structured data does not change that. Schema on a thin or irrelevant page gives Google a clearer map to something it would rather not rank.
How to Implement It Without Breaking Things
JSON-LD is the format Google recommends, and it is the easiest to work with. Drop it into the <head> of the relevant page or use a plugin that handles the output cleanly. On WordPress, a lightweight plugin that generates valid JSON-LD without bloating the page is a reasonable choice. Avoid plugins that inject dozens of additional schema types you did not ask for.
Validate everything with Google’s Rich Results Test before you publish. Errors there are not fatal, but warnings about missing recommended fields are worth addressing if the field is genuinely applicable to your business.
Check your Google Search Console for schema errors a few weeks after implementing. The Enhancements section will show you whether Google has processed your markup and whether anything has been flagged. That feedback loop matters more than any one-time validation tool.
The Honest Trade-Off
Schema markup done properly takes maybe a few hours to get right for a single location. Not a large investment. But it is also not a ranking shortcut. Think of it as tidying up the information Google already has about you. A tidy signal beats a muddled one. It will not rescue a slow site or weak content, but combined with those fundamentals in good shape, it closes a gap that is worth closing.