Local business schema: how to earn rich results in Google
Schema markup is one of those SEO topics that sounds far more technical than it is. For a local business it comes down to describing your name, address, hours and services in a format Google can read without guessing. Done well it earns you more space in search results and feeds the data behind Google Maps. Done badly it does nothing, and done dishonestly it can get you a manual penalty.
What schema does and does not do
Schema markup is structured data added to your pages in the background. Visitors never see it, but search engines read it to understand what a page is about with certainty rather than inference.
For a local business the practical payoffs are concrete. Your opening hours can show directly in search, your star rating can appear under the result, your address and phone can populate the knowledge panel, and individual services or FAQs can take extra space on the page.
It also feeds the local ecosystem. The same structured data that helps a normal search result also helps Google connect your website to your Google Business Profile and your Maps listing.
What schema does not do is move you up the rankings on its own. It is a presentation and clarity layer, not a ranking factor in the way that links or content quality are. A page that does not rank will not start ranking because you added markup.
It also cannot rescue a thin page. If the visible content does not answer the query, describing it more precisely to Google does not change the outcome.
Think of it as making a result that already ranks work harder: more space, more trust signals, a higher click rate from the same position.
The schema types a local business needs
Most local businesses need only three or four types, and adding more than you can keep accurate is a mistake rather than an improvement.
- LocalBusiness, or a more specific subtype like Dentist, Plumber, Restaurant or HairSalon. This is the core: name, address, phone, hours, geo coordinates, price range, areas served.
- Service, one per main service page, describing what the service is and who provides it. This is what lets individual service pages qualify for richer display.
- FAQPage, on pages that genuinely contain a question and answer list. Only mark up FAQs that are actually visible on the page.
- BreadcrumbList, so search results show your site structure rather than a raw URL.
If you publish articles, add Article or BlogPosting to those. If you sell products online, that is Product territory and a separate topic.
Put the LocalBusiness markup on a stable page, usually the homepage or the contact page, and keep it in one place. Repeating slightly different versions of it across every page is a common source of conflicting data.
How to add it without touching much code
The format Google prefers is JSON-LD, a small block of structured text placed in the page head. You do not need to understand it line by line, but you do need it to be accurate.
On WordPress, a dedicated SEO plugin generates LocalBusiness and breadcrumb markup from settings you fill in once, and most also handle FAQ markup through a block you add to the page. This covers the majority of small sites with no code at all.
On a custom or headless site, the developer adds a JSON-LD template that pulls from real page data. This is a small job, usually an hour or two, and worth doing properly so the data stays in sync automatically.
Whatever the method, the rule is the same: the markup must match what a visitor sees on the page. Hours in the schema must match hours on the page, the business name must be identical, the address must be the same format.
Do not mark up data that is not visible. Invisible FAQ markup, fake reviews in schema, or a rating that appears nowhere on the page are all against Google guidelines and are the main reason local businesses get structured data penalties.
Keep it boring and truthful and it will quietly work. Try to game it and it becomes a liability.
LocalBusiness: the fields that matter
A few fields do most of the work, and getting these exactly right matters more than adding obscure ones.
Name, address and phone must be byte for byte identical to your Google Business Profile and your other listings. Do not write Street on one and St on another. Inconsistent data across sources weakens the whole local signal.
Opening hours should use the structured format with each day specified, and special hours for public holidays where your plugin or template supports it. Hours are the field most likely to actually appear in search, so keep them current.
Geo coordinates pin you on the map. Get them from Google Maps by right clicking your exact entrance, not the middle of the building or the car park.
areaServed lists the towns or regions you cover. For a business that travels to customers this matters more than the street address.
sameAs links your profiles: Google Business Profile, Facebook, Instagram, industry directories. This is how you tell Google that these accounts are all the same business.
Leave priceRange approximate, using symbols or a short range, and skip aggregateRating entirely unless you have a real, visible review system on the page producing those numbers.
Testing, mistakes and keeping it accurate
After adding markup, test every page type once with Google's Rich Results Test and the Schema.org validator. The first tells you what Google can use, the second catches structural errors.
Then watch Search Console. The Enhancements section reports which structured data types Google detected and flags errors and warnings per URL, which is where real problems show up over time.
The most common mistakes are all avoidable: schema hours that no longer match reality, a business name that drifted from the Google profile, FAQ markup left on a page after the visible FAQ was removed, and rating markup with no review system behind it.
Set a reminder to review the core markup whenever your hours, address, phone or services change. Structured data that silently goes stale is worse than none, because it actively misinforms.
Do not expect instant results. Rich features can take weeks to appear and Google decides case by case whether to show them, so a correct implementation may still not produce stars or an hours panel on every query.
The realistic goal is steady: accurate data everywhere, no errors in Search Console, and a result that gradually takes more space and earns more clicks from the position it already holds.
FAQ
Will adding schema markup improve my Google rankings?+
Not directly, because structured data is a clarity and presentation layer rather than a ranking factor in the way links and content quality are, so a page that does not rank will not start ranking simply because you described it more precisely. What it does is make a result that already ranks work harder: opening hours can appear in the search result, a star rating can show under the link, breadcrumbs can replace a raw URL, and service or FAQ pages can take more vertical space. The effect you actually measure is a higher click through rate from the same position and a stronger connection between your website, your Google Business Profile and your Maps listing, which over time supports local visibility even though the markup itself is not what moves you up the list.
Do I need a developer to add structured data?+
For most small sites, no. On WordPress a dedicated SEO plugin generates LocalBusiness, breadcrumb and FAQ markup from settings you enter once, which covers the majority of local businesses with no code at all. On a custom or headless site you do need a developer, but it is a small job, usually an hour or two, to add a JSON-LD template that pulls from real page data so it stays accurate automatically. The part that matters regardless of method is discipline rather than skill: the markup must match what visitors actually see on the page, you must not mark up data that is invisible or invented, and you need to update it whenever your hours, address or services change.
Why are my rich results not showing even though the markup is valid?+
Valid markup makes a page eligible for rich features, but Google decides case by case whether to actually display them, and it often does not, especially for newer sites or for queries where it judges the extra detail unhelpful. Rich features also take time, sometimes several weeks after Google has recrawled the page, so a correct implementation can sit quietly before anything appears. Check three things: that the visible content genuinely matches the markup, that Search Console shows the structured data type detected with no errors under Enhancements, and that you are not marking up something Google rarely displays for your category. If all of that is clean, the honest answer is to keep the data accurate and wait, because eligibility is in your control and display is not.