Structured data for local businesses: what schema does and does not do for AI visibility
Schema markup makes your pages easier for machines to parse, LocalBusiness markup takes about an hour and is worth having, and its specific effect on whether AI assistants mention your business is mostly unproven. All three of those are true at once. This topic drowns in overclaims, so the restrained version is the useful one.
The honest answer, up front
Schema demonstrably helps machines parse your pages: it labels what your business is, where it is, and what it offers in a format built for software. What nobody has demonstrated is that schema, by itself, changes whether AI assistants name you in answers. Add it because parsing help is cheap and real; don’t buy it as a visibility lever, and be wary of anyone selling it as one.
Schema, in owner terms
Your page says “Summit Plumbing, Fort Collins, open 7 to 6.” A human reads that instantly; software benefits from labels: this string is a business name, this is an address, these are hours. Schema is that labeling, invisible to visitors, embedded in the page. That’s the whole concept, and two paragraphs is what it deserves.
The types worth having
For a local service business: LocalBusiness, or its closer subtype where one exists (Schema.org defines Dentist and MedicalBusiness among dozens of others), with address, telephone, and openingHours filled1. Match the markup to what the page visibly says; markup that contradicts your visible content recreates the consistency problem in a second layer machines can read.
What we could and couldn’t observe
Isolating schema’s effect on AI answers is genuinely hard: sites that add markup are usually improving other things at the same time, and attribution in this field caps out at correlation even for big interventions. We haven’t observed a case where markup alone moved mentions, we haven’t seen anyone else document one to a checkable standard, and the honest position is that the mechanism is plausible and the proof is absent. When our tracking can say something better, it will come with dates.
Where the hour goes, and where it stops
Our opinion: add LocalBusiness markup once, correctly, and then never think about schema again until your business facts change. The recurring “schema optimization” retainer is a product built on this topic’s fog. The readable-content work (structure machines can parse, answers machines can quote) outranks markup every time the two compete for an afternoon, because content is what answers are made from and markup is only how it’s labeled.