Local Business Schema is structured data that labels the key facts about a real business location on your website, such as the business name, address, phone number, opening hours, and page URL. In practice, it belongs on a page that represents an actual office, store, clinic, or branch, so search engines can read those details as defined business data instead of piecing them together from scattered page elements.
That sounds technical, but the use case is ordinary. A customer wants to know where you are, whether you are open, and which number to call. Local Business Schema supports that kind of location information. It does not replace a Google Business Profile, and it does not turn a generic service page into a local landing page. It works best when the page already does a clear job of representing a real location.
What it actually does
Most business websites already contain local details somewhere. The trouble is that those details are often messy in practice. The main number sits in the header, an old branch number still appears in the footer, and opening hours are mentioned on a contact page that no longer matches the latest update.
Local Business Schema gives those details a fixed structure. It tells search engines, in plain terms, “this is the business name,” “this is the address,” and “this is the phone number for this location.”
That does not make schema a magic local SEO feature. It makes it a clarity feature. On a well-built location page, that clarity helps. On a weak page, it simply labels weak information more neatly.
Where it belongs
Use Local Business Schema on pages that represent a real, customer-facing location.
That usually means:
- a contact page for a single-location business
- a branch page for a retailer
- an office page for a law, accounting, or consulting firm
- a clinic page for a medical or dental practice
- a store page for a franchise location
- a location page for a gym, salon, or restaurant
These pages exist to answer practical questions: where is this branch, how do I contact it, and when is it open?
That is different from a service page. A service page explains what you do. A location page explains where that branch exists and how customers reach it. Once that distinction is clear, most markup decisions become much easier.
What people commonly confuse it with
Google Business Profile
Your Google Business Profile lives on Google. Local Business Schema lives on your website.
They should support the same core details, but they are not the same asset. If your profile shows 5pm closing time and your website says 6pm, schema does not solve the mismatch. The fix is to correct the business details, not to add more markup.
Organization Schema
Organization Schema usually describes the business at brand level. Local Business Schema describes a specific local entity or location.
A business with one brand and several branches may use Organization Schema on the main company page, then use Local Business Schema on each branch page. That keeps the structure clean: one markup type for the organisation, another for the locations people actually visit or call.
Service Schema
Service Schema describes the service. Local Business Schema describes the business location.
A tax consultancy might have a page about outsourced accounting services and a separate Johannesburg office page. Those are two different page roles. One is about what the company offers. The other is about where that office is and how to contact it.
When to use it, and when not to
Use Local Business Schema when a page genuinely represents a real business location with its own local details. Good signs include a physical address, branch phone number, opening hours, directions, or branch-specific contact information.
Avoid using it as the main markup on:
- broad service pages
- pricing pages
- blog posts
- comparison pages
- generic home pages with no clear location focus
- city landing pages for places where you do not have a real office or branch
That last point matters more than most businesses realise. Many companies build city pages for places they serve, then treat those pages as if they were real branch pages. If there is no actual location there, Local Business Schema is usually the wrong fit. The issue is not missing markup. The issue is pretending a service-area page is a physical location page.
The fields that matter most
A lot of articles list the fields, then move on. That misses the practical point. The value is not in having a checklist. It is in having the right details, on the right page, in a form that matches reality.
Business name
The name should match the real business name customers see elsewhere. If the contact page says one thing, the footer uses another variation, and external listings use a third, the page becomes less trustworthy.
This happens more often than people think. A business rebrands slightly, shortens its name in one place, keeps the old legal version in another, and suddenly the web presence looks fragmented.
Address
The address tells search engines and users that the page represents a real location. It also tends to be where avoidable errors creep in.
An outdated suite number, a previous office address, or a vague “serving all of Gauteng” line in place of a proper branch address can weaken the page. For a multi-location business, putting the head-office address on every branch page is another common mistake. It saves time in the short term and creates confusion everywhere else.
Phone number
For many local searches, the phone number is the conversion point. It is not a background detail.
If a Cape Town office page uses the national call-centre number while the Google Business Profile shows a direct branch number, that branch page becomes less useful. The customer does not know which number is correct, and the location page loses some of its credibility.
Opening hours
Hours affect real decisions. People check them before they call, visit, or compare local options.
This is especially important for retail, medical, hospitality, and any business with branch-specific trading times. If your website still shows Saturday hours for a branch that stopped opening on weekends months ago, that is not a small formatting issue. It is a trust problem.
URL
The page URL ties the structured data to the page representing that business location. On a multi-location site, that matters. Each branch should have a page that clearly belongs to that branch, rather than one broad page trying to cover every office at once.
Geographic coordinates
Coordinates add location precision. They are not always the first field a business thinks about, but they can help reinforce exactly where the branch is, especially when map-level accuracy matters.
Business type
This is where many implementations become too generic. “LocalBusiness” is broad. A dental practice, restaurant, store, legal office, or hotel is better described with a more specific type where one exists.
Specificity helps the markup describe the page more accurately. Vague markup is not always wrong, but it is often lazy.
What this looks like on a real website
The best way to understand Local Business Schema is to look at page-level decisions.
Single-location plumber
A plumbing company has one office in Sandton and a /contact/ page with its address, office number, opening hours, and service-area notes.
That contact page is the right place for Local Business Schema.
The main /emergency-plumbing/ page is not. That page targets service intent. It should explain the service, response process, and coverage areas. It is not the page that represents the physical office.
If the business also creates pages for nearby suburbs it serves, those pages should not be marked up like branch pages unless the company genuinely has premises there.
Multi-branch law firm
A law firm runs a single brand site with three real office pages:
/cape-town-office//durban-office//johannesburg-office/
Each office page includes its own address, contact number, office hours, and practical location details. Each office page should carry its own Local Business Schema.
The general “Commercial Law Services” page should not. Neither should the main “About the Firm” page. Those pages have different jobs. Once the site structure respects those roles, the markup becomes obvious.
Retailer with store pages
A retailer has eight stores. The weak setup is one “Our Stores” page with every address and number dumped into a long block of text.
The stronger setup is a store finder page linking to eight dedicated store pages. Each store page carries its own local details and its own Local Business Schema. The store finder page acts as a hub. The branch pages carry the location-level markup.
That approach handles branch-specific hours, click-and-collect details, and direct store numbers much more cleanly than a single catch-all page.
Mistakes that waste the markup
The biggest problems usually start before the schema is added.
Using it on the wrong page
If the page does not represent a real location, the markup is probably misapplied.
Marking up fake locations
A city page for a place you serve is not automatically a branch page. If there is no office there, do not mark it up as though customers can visit one.
Reusing the same details everywhere
Multi-location sites often copy the head-office number, address, and hours across all branch pages. That makes the site easier to build and harder to trust.
Leaving outdated details live
Schema only helps when the information is current. Old hours, old addresses, and replaced phone numbers turn it into another source of inconsistency.
Treating schema as the strategy
Schema supports local SEO. It does not replace proper location pages, internal linking, Google Business Profile management, or local trust signals.
A quick test before you add it
Ask one plain question:
Is this the page a customer should land on if they want to find, call, or visit this specific business location?
If the answer is yes, Local Business Schema is probably relevant.
If the page is mainly about services, pricing, or general brand information, you are probably looking at the wrong page type.
Final takeaway
Local Business Schema is most useful when the site has earned the right to use it well. That means a real location, a clear page for that location, and business details that are accurate enough to trust.
Used that way, it sharpens a local page that already makes sense. Used carelessly, it only exposes structural problems faster. The real decision is not whether to add schema everywhere. It is whether your site has genuine location pages that deserve it.