LocalBusiness Schema
The LocalBusiness schema is a format from the Schema.org vocabulary that lets you store structured data about a local business on your website in a machine-readable way. Details such as name, address, opening hours, phone number and location are marked up so unambiguously that search engines and AI systems can reliably recognize, understand and reuse them in answers or recommendations.
Why it matters for AI visibility
Search engines and AI assistants like ChatGPT, Perplexity or Google AI Overviews have to extract facts from your website in order to use them in answers. Plain running text leaves room for misinterpretation: is "Sonnenweg 12" an address or a hiking trail? With the LocalBusiness schema you supply the answer unambiguously. You turn your core data – location, availability, category – into robust, citable facts. That increases the chance of an AI system naming your business correctly instead of skipping it or presenting it with wrong details. Especially with local questions like "a good dentist near me," data quality decides whether you show up as an option at all.
How it works technically
You usually embed the data as JSON-LD, a small script in the source code of your page. In it you define the type (for example "Restaurant", "Dentist" or the general "LocalBusiness") and fill in properties such as name, address, geo, openingHours and telephone. Consistency is key: the marked-up details should match the visible page content and external sources like your Google Business Profile. The more precise the chosen subtype, the better a machine understands your industry. An en dash as a separator or a clean postal code sounds trivial, but exactly this tidiness decides whether a parser takes the data over without error or discards it.
Common mistakes
The most common mistake is inconsistency: the website lists a different phone number than the schema or the business directory. Such contradictions undermine trust and can cause systems to ignore your data entirely. Equally problematic is marking up information that isn't visible to users at all – that counts as manipulation. Other pitfalls: a type that is too general instead of the fitting category, missing mandatory details like the full address, or outdated opening hours. Check your markup with a validation tool before you go live, and update it as soon as your address, hours or offering change.
Relation to AI recommendations
In the context of Generative Engine Optimization it's no longer just about rankings, but about being actively recommended and cited by AI systems. Structured data is a foundation for this: it lowers the risk of hallucinations, because the model doesn't have to guess but takes over documented facts. When a user asks an assistant for a local provider, many systems fall back on clearly marked-up entities. A clean LocalBusiness schema increases your chance of appearing in such answers with correct contact details. It doesn't replace good content, but it makes your existing information reliably usable for machines – and that is exactly the ticket into AI answers.
Example
Imagine a small bike repair shop in Regensburg. On its contact page it visibly shows name, street, opening hours and phone number. In addition, the shop stores these details as a LocalBusiness schema in the source code, with the fitting type "BikeStore" and exact geo-coordinates. If someone asks an AI assistant "Where can I get my bike repaired in Regensburg on a Saturday?", the system finds the clearly marked-up opening hours and the address. The shop is named with correct data – while a competitor without markup is easily overlooked or shown with outdated hours.
Common questions
Do I need programming skills for the LocalBusiness schema?
Not necessarily. Many content management systems and plugins generate the JSON-LD automatically from your inputs. For custom pages, a schema generator helps: you enter your data and copy the finished code. Afterwards, check the result with a validation tool.
Does the schema affect my AI visibility immediately?
No, it's a foundation, not a switch. Systems first have to crawl your page and take in the data. What remains decisive is the combination of clean markup, consistent details across all channels, and good, up-to-date content. The schema improves your chances but doesn't guarantee a mention.