Recently we told a business owner that incomplete business schema was one of the issues holding their website back. The reply came quickly: "But we do have business schema." And they did. We ran their homepage through the official validator and it came back green. Zero errors. Zero warnings.
Then we read what the markup said. A WebPage entry. A WebSite entry. An Organization with a name, a logo, and a link to a social profile. That was the lot. No business type. No address. No phone number. No opening hours. No coordinates. The markup was technically perfect and said nothing about the business as a local entity: not what it does, not where it is, not when it's open, not how to call it. Every one of those facts sat in plain text on the page, where a machine has to scrape and infer them instead of being told.
This pattern is everywhere, and it explains why "we have schema" and "your schema is incomplete" are both true at once. Most schema on local business websites was never written by anyone. It's the default output of an SEO plugin, and plugin defaults describe a website, not a business.
The short answer
Business schema will not lift your Google Maps ranking, and anyone selling it as a ranking lever is overreaching: Google does not list structured data among its local ranking factors, which remain relevance, distance, and prominence, driven by your Business Profile. What complete schema does is state your business facts in a form machines read without guessing, corroborating the details Google finds on your profile and your pages. Valid but generic schema is roughly neutral. Incomplete or contradictory schema can work against you. Complete schema costs about an hour, once.
So the answer to "is some better than none" is: it depends entirely on what the some says. Which is worth unpacking, because the failure modes are specific.
What schema does, per Google
Google's structured data documentation is measured about the benefits. Markup helps Google understand what a page contains, and it makes pages eligible for rich results; Google is also explicit that structured data is no guarantee of any particular treatment (Google Search Central documentation, 2026). Its local ranking documentation, meanwhile, doesn't mention website markup at all: relevance, distance, and prominence, fed by complete and accurate business information (Google Business Profile Help, 2026).
Read together, those two positions define the honest job description. Schema is a corroboration layer. Your Google Business Profile says you're at a certain address, open certain hours, reachable on a certain number. Your website says the same things in prose. A complete LocalBusiness block says them a third time, in the one format built specifically for machines: no scraping, no inference, no ambiguity about whether the number in the footer is a phone or a fax. Consistency across all three is the point. We covered in our AEO research review which machine-readability work the evidence supports and which is retainer theatre; structured data sits firmly in the first group, precisely because it's cheap, permanent, and documented by Google itself.
When some is worse than none
The generic plugin block from the opening is the mild case: it says nothing, so it costs nothing beyond false reassurance. Three failure modes cost more.
- Schema that contradicts the page or the profile. An old address left in a markup block after a move, a phone number that differs from the footer, hours that don't match the profile. Now Google holds two versions of the facts, and the layer meant to remove ambiguity is manufacturing it. This is the strongest sense in which incomplete schema is worse than none.
- Markup that was started and never finished. A second business we audited in July had a LocalBusiness block someone clearly began by hand: name and address present, then no geo coordinates, no hours, no phone, no profile links. Half a corroboration layer corroborates half your facts and stays silent on the rest, and it signals that nobody has looked at the site's technical layer in a long time.
- The wrong type doing the wrong job. An Organization block on a single-location service business, or a bare WebPage graph, describes a brand or a document. It leaves the local entity, the thing with an address customers visit and hours customers check, entirely unstated.
The zero-errors trap: validators check syntax, not substance. A block that says nothing valid about your business passes just as green as a complete one. Never read "0 errors, 0 warnings" as "we're done." Read what the markup says, then ask what it leaves out.
What complete looks like
A complete block for a local business is short. This is an hour of work including checking it twice:
- The most specific type that matches you. Schema.org lists dozens of LocalBusiness subtypes: Dentist, Electrician, Plumber, MovingCompany, LegalService, AutoRepair and so on. Use the one that fits; fall back to LocalBusiness itself only if nothing does.
- Name, address, phone, exactly as they appear on your profile and your page. Same spelling, same formatting, same suburb conventions. The mirror rule from our services list guide applies here in full: consistency strengthens the match, contradiction weakens it.
- Geo coordinates, opening hours, url, and image. The coordinates end any ambiguity about where you are; openingHoursSpecification ends any about when you're open.
- sameAs links to your real profiles. Your Google Business Profile listing, your social accounts. This ties the entity together across the web.
- For service-area businesses, areaServed. Name the suburbs or regions you cover rather than leaving machines to guess your reach.
Place it as JSON-LD in the head of your homepage (and contact page), run it through validator.schema.org, and then, the step everyone skips, put "update the schema" on the same checklist as updating the website whenever your hours, address, or phone change. Stale schema is how the contradiction failure mode is born.
Where it sits in your priorities
Below the profile work, above almost everything sold as technical SEO. Your ranking is driven by what happens on and around your Business Profile: the right category, a complete services list, and the prominence Google reads from real customer behaviour: searches, profile visits, clicks, calls, direction requests, business visitations — real devices, real locations. Schema doesn't compete with any of that and can't substitute for it. What it does is make sure that when Google and, increasingly, AI systems read your website to confirm what your profile claims, they find the same facts stated cleanly instead of scattered through footer text.
That's why it appears as a critical item on our audits despite not being a ranking factor: it's the cheapest fix on the list with the longest life. One hour, once, then maintenance only when your details change. And it's why we'd tell you not to pay anyone a monthly fee for it. Schema is not a campaign. It's a form you fill in correctly one time.
If a provider has been charging you for SEO and your validator shows nothing but plugin defaults, that's worth a conversation. Not because the missing block explains your rankings, it doesn't, but because of what it says about thoroughness. The businesses that win on Maps tend to be the ones where somebody swept every corner, and this is a corner that takes an hour to sweep. For where rankings are won, start with our Top 3 guide.
Frequently asked questions
Does LocalBusiness schema improve Google Maps ranking?
Not directly. Google's documentation describes structured data as helping Google understand page content and qualify it for rich results; it doesn't list schema among local ranking factors, which Google states are relevance, distance, and prominence, driven by your Business Profile. What complete schema does is corroborate your business details in a machine-readable form, removing any need for Google to infer your name, address, phone, hours, and location from page text.
Is some business schema better than none?
It depends what the schema says. A valid but generic block, the kind SEO plugins generate automatically, is roughly neutral: it passes validation while stating nothing local. Incomplete or contradictory schema can be worse than none, because markup that conflicts with your page or your Business Profile sends Google two versions of the facts. A complete, accurate block costs about an hour and settles the question.
My schema validates with zero errors. Doesn't that mean it's fine?
No. Validators check syntax, not substance. A generic WebPage and Organization graph with no address, phone, hours, or location passes with zero errors and zero warnings while telling machines nothing about your business as a local entity. The test that matters: does the validator show a LocalBusiness type (or a specific subtype like Dentist or Electrician) carrying your address, phone, geo coordinates, and opening hours?
Which schema type should a local business use?
The most specific LocalBusiness subtype that matches what you are: Dentist, Plumber, Electrician, MovingCompany, LegalService, and so on. Schema.org lists the full set. If no subtype fits, use LocalBusiness itself. The details inside the block must mirror your website and your Google Business Profile exactly, down to formatting of the name, address, and phone number.
How do I check what schema my website has?
Paste your homepage URL into validator.schema.org or Google's Rich Results Test. Ignore the error count at first and read what's there: look for a LocalBusiness or specific subtype, then check it carries address, telephone, geo coordinates, opening hours, and links to your profiles. If you only see WebPage, WebSite, and Organization entries, you have plugin defaults, not business schema.
Sources: Google Search Central, structured data documentation, 2026; Google Business Profile Help, Tips to improve your local ranking on Google, 2026; Schema.org, LocalBusiness type documentation, 2026; Spotlight Local website and profile audits, July to August 2026 (client details anonymised).
Want our new guides highlighted for you in Google Search and AI Overviews? Add Spotlight Local as a preferred source.