Schema for Local Businesses, Minus the Cargo Cult

Schema markup gets sold two ways, and both are wrong. The hype version says schema will boost your rankings — add the code, watch positions climb. The dismissive version says schema is snake oil that does nothing. The truth sits between them and is more interesting than either: schema doesn't rank you, and it isn't nothing. It makes what's already true about your business legible to machines. In a search world increasingly mediated by machines, that's a bigger deal than it sounds — but only if you understand exactly what it does and refuse to cargo-cult the rest.

What schema does not do

Let's kill the hype first, because it's what makes people waste money. Schema is not a ranking factor you can spike. Bolting LocalBusiness markup onto a thin page does not move it up the results. Adding more schema types than you need — stacking Product, Review, Organization, Service, and six others onto a page that only warrants one — does not compound into more visibility. That's the cargo cult: builders and plugins that spray every schema type they can find onto every page, on the theory that if some structured data is good, all of it must be better. It isn't. Irrelevant or false schema is at best ignored and at worst a trust problem. More markup is not more magic.

What schema actually does

Now the real value. Schema is a translation layer. Your page says, in prose, "This is an HVAC company serving Baldwin County, open weekdays, located here, offering these services." A human reads that fine. A machine has to infer it — and inference is lossy. Schema states the same facts in a format the machine doesn't have to guess at: this is a LocalBusiness, these are its service areas, this is its address, these are the services, this is how the locations relate to each other. You're not persuading the machine of anything. You're removing ambiguity about what's true.

Two facts about the modern SERP make this matter more every year. First, structured data is what powers the rich features and the knowledge connections search engines build — the machine can only present what it can confidently parse. Second, and bigger: search is increasingly answered by AI systems that read the web and summarize it back to the user. The local-SEO data shows a fast-rising share of consumers now using AI tools for local recommendations, and shows that the businesses leading Google's results don't automatically appear in those AI answers — surfacing there is a separate, harder game. When an AI is deciding whether to recommend you, machine-legible facts about who you are and what you do are not decoration. They're the difference between being correctly represented and being guessed at or skipped. That's the same argument as being citable in AI answers: the machine can only repeat what it can parse. It's also why the death of FAQ rich results didn't kill FAQs — losing the visual widget didn't change the underlying value of stating your facts in a form a machine can read.

The part that takes real skill: fencing multi-location schema

Here's where schema stops being copy-paste and starts being craft. If a business has more than one location, or serves distinct areas, the schema has to fence those correctly — each location as its own entity, with its own address and service area, connected in an identity graph that says how they relate without blurring into one ambiguous blob. Done wrong, you tell the machine a confusing story about who's where, and confusion is the one thing structured data exists to eliminate. When I did the schema for Revitalize's build, the multi-location fencing was the hard part — not stamping LocalBusiness on every page, but drawing the entity boundaries so the identity graph was true and unambiguous. That's the work. The plugin can't do it because the plugin doesn't know your locations are distinct entities; only a person modeling the truth can.

So: schema, minus the cargo cult. Don't buy the ranking-boost pitch. Don't let a plugin spray every type onto every page. Do treat structured data as the layer that makes your real facts machine-legible, and get the multi-location fencing right, because that's where truth and skill actually meet.

A schema audit — including the fencing — is part of every build I ship. See the studio approach →