Why the choice matters
Plenty of sites never make the decision on purpose. They use LocalBusiness because a plugin defaulted to it, or Service because a blog post said to, and nobody checks whether the markup matches how the business operates. The mismatch doesn't throw an error, so nobody notices that the markup describes the business imprecisely to every search engine and AI tool that reads it.
Schema.org's types exist so you can say exactly what kind of thing a page describes. LocalBusiness is built around a place: somewhere customers visit, or a base you travel out from to serve a defined area, while Service describes an offering, whether it's delivered from one location, ten or none.
Two setups go wrong most often. One is a consultancy that serves clients nationally but describes itself as a LocalBusiness because that's what the theme shipped with. The other is a multi-location business that marks up its headquarters and never mentions the other locations in its markup at all. Both are fixable.
What LocalBusiness schema describes
LocalBusiness assumes a physical presence customers can find: an address, hours, a phone number and a location on the map. Google's LocalBusiness documentation asks you to "use the most specific LocalBusiness sub-type possible", so a law firm should use LegalService or Attorney rather than the generic parent, and a plumber should use Plumber.
Google lists address and name as required, with telephone, url, geo, openingHoursSpecification and priceRange among the recommended properties, and if you travel to customers, the schema.org areaServed property is how you describe that reach. Use it. A business that fills in the type and skips areaServed tells every reader of the markup that it works from a single point, which undersells a company that drives to clients across a metro area.
Work With John
If your site isn't bringing in inquiries, that's fixable.
I work with US service businesses and B2B brands on SEO, websites and lead follow-up. On a free strategy call, I'll tell you what's holding your site back, without a sales pitch.
Get a Free AuditWhat Service schema describes
Service describes what's being offered rather than where, connecting to a provider, which can be a LocalBusiness or an Organization, and carrying its own properties such as serviceType, areaServed, offers and a description of that one service.
The point people miss is that Service sits alongside the business entity, describing one thing the business does without replacing the business itself. A tax preparation page on an accounting firm's site works best with a Service entity that names the firm's ProfessionalService entity as its provider. A Service with no provider looks like an orphaned offering with nobody behind it. Connect the two.
The mistake of one schema block for everything
A common pattern looks like this. An HVAC company with installs, repairs, maintenance contracts and duct cleaning marks up its homepage as a single LocalBusiness and stops. Every service page either repeats the same block word for word or has no markup of its own, so the site describes the company once and says nothing about what it sells.
The better structure uses one LocalBusiness entity, in the most specific subtype, plus a Service entity for each core service on its own page, each pointing back to the business through the provider property. That gives search engines a picture that mirrors the site itself: one business with several offerings, each with its own description and, where it differs, its own areaServed. It takes more setup than one block copied everywhere, and it describes the business far more accurately. It's worth the hour.
A location in one city, customers across a region
Many service businesses have one office and do the work across a wider region. Keep LocalBusiness tied to the real address, and never invent a location you don't operate from, then use areaServed, on the business and on each Service where it differs, to name the regions you serve.
Don't overcorrect. Listing every city you've ever worked in, sometimes dozens of place names, doesn't make the markup more accurate. They make it noisier, and they can read as an attempt to rank in places you don't serve. A short, honest list of the regions you work in regularly is the better choice.
Multi-location businesses
With more than one location, the question becomes how to describe each one. Google's guidance is to "define each local business location as a LocalBusiness type". In practice, each location with its own address, phone number and hours gets its own LocalBusiness entity, connected to the parent company through schema.org's parentOrganization property.
Services then attach to the locations that provide them. Copying identical Service blocks onto every location page claims every location offers every service, even when the visible page says a branch only handles two of the six. Markup should describe what's true on that page. Copied templates rarely are.
What schema does and doesn't do
Schema isn't a ranking lever you pull to watch a position move. Google describes structured data as a way to understand a page, and LocalBusiness markup can feed the business details Google shows, such as a knowledge panel when someone searches for a business by name. Google doesn't offer a rich result for the Service type, so Service markup earns its place by describing your offerings clearly to search engines and AI tools, rather than by changing how a result looks.
The map results that appear for "near me" searches are a separate system that draws on your Google Business Profile, and Google ranks them on relevance, distance and prominence. Page markup supports that picture, and the profile is what puts you on the map. Keep the two consistent. Local SEO for service businesses covers that side.
Clear, consistent markup also fits the trust signals covered in what E-E-A-T is and how you build it, because a business that describes itself precisely and consistently, in its markup, on its pages and in its Business Profile, is easier for any search engine or AI tool to understand and repeat accurately.
Where to go next
If you're still deciding whether schema is worth the time, read this alongside does schema markup help SEO, which covers what structured data can and can't do on its own. If your markup already exists, the schema markup mistakes that trip up service sites usually hide in exactly the kind of copied blocks described above. More technical guides live in the Technical SEO archive, and this kind of structural audit is part of my SEO service.
Getting LocalBusiness and Service schema right comes down to answering two questions separately: where the business operates, and what it sells. Most sites answer only the first, and only partly. Answering both accurately turns schema from a checkbox into a description of the business that a machine can use.
