LocalBusiness is a core Schema.org type that defines a specific, physical place of business. It acts as a parent class for more granular business types such as Restaurant, Dentist, Store, or ChildCare. By implementing this markup, organizations provide search engines and AI crawlers with explicit, machine-readable entity identity, including the business name, geographic coordinates, and operating hours.
Glossary
LocalBusiness

What is LocalBusiness?
A Schema.org structured data type representing a physical business location or a branch of an organization that serves customers at a specific address.
This type is critical for entity salience in local search and AI-generated overviews. It establishes a canonical node for a physical location within a knowledge graph, often linked to an Organization via the parentOrganization property. Proper implementation ensures that generative engines associate the correct address, phone number, and service area with the brand, directly influencing visibility in map packs and voice search results.
Key Properties of LocalBusiness Schema
Essential Schema.org properties that define a physical business location for AI-driven search engines, enabling rich local results and accurate entity disambiguation.
Core Identity: name, description, and image
The foundational properties that establish the business's identity within a knowledge graph.
- name: The canonical business name as it appears in the real world. Avoid keyword stuffing; use the exact legal or operating name.
- description: A concise, factual summary of what the business offers. This text is frequently used by AI models for summarization and contextual relevance.
- image: A URL pointing to a representative photo or logo. Multiple ImageObject nodes can be specified for different contexts.
Example: A bakery named "Flour Power" should use exactly that string, not "Flour Power - Best Cakes Downtown."
Physical Location: address and geo
Properties that anchor the business to a precise geographic point, critical for local search and map-based AI interfaces.
- address: Uses the PostalAddress type to define streetAddress, addressLocality, addressRegion, postalCode, and addressCountry. This structured format is preferred over a single string.
- geo: Uses the GeoCoordinates type to specify exact latitude and longitude. This removes ambiguity for businesses in dense urban areas or strip malls.
Why it matters: AI models use these coordinates for proximity calculations and to verify the business physically exists at the claimed location.
Contact & Communication: telephone and url
Properties that define how customers and AI agents can reach or verify the business.
- telephone: The primary contact number in E.164 international format (e.g., +1-415-555-0132). This format is machine-readable and globally unambiguous.
- url: The canonical homepage URL for the specific location. For multi-location businesses, each branch should point to its unique store page, not the corporate homepage.
- email: While less common, can be specified for direct contact.
Best practice: Ensure the telephone and url exactly match the information on the corresponding Google Business Profile and other citations to reinforce entity alignment.
Operational Context: openingHours and priceRange
Properties that provide temporal and economic context, helping AI answer specific user queries about availability and cost.
- openingHours: Uses OpeningHoursSpecification to define structured day-of-week and time ranges. This is far more precise than a free-text string like "Mon-Fri 9-5." It enables AI to answer "Is it open now?" accurately.
- priceRange: A qualitative signal using symbols like
$,$$,$$$to indicate the relative cost of goods or services. - paymentAccepted: Specifies accepted payment methods (e.g., Cash, CreditCard, Cryptocurrency).
Example: A fine-dining restaurant would use $$$ while a food truck might use $.
Categorization: @type and additionalType
Properties that define the specific business category, enabling AI to understand the services offered without parsing unstructured text.
- @type: The primary Schema.org type. While LocalBusiness is the parent, using a more specific type like Restaurant, Dentist, AutoRepair, or DaySpa provides immediate semantic clarity.
- additionalType: A URL referencing an external taxonomy entry, such as a NAICS code or a Wikidata Q-ID, to further refine the business category.
Strategic value: A specific @type allows AI models to infer attributes. A Restaurant type implies the existence of a menu, while a Dentist type implies medical services.
Social Proof & Identity: sameAs and aggregateRating
Properties that link the business to external authoritative sources and aggregate customer sentiment.
- sameAs: An array of URLs pointing to the business's canonical profiles on other platforms (e.g., Wikipedia, LinkedIn, Crunchbase, official social media). This is the primary mechanism for entity reconciliation across knowledge graphs.
- aggregateRating: Uses the AggregateRating type to display the average review score and total review count. This data is often surfaced directly in AI-generated summaries.
- review: Can link to individual Review items for deeper sentiment analysis.
Critical note: The sameAs property is not for marketing links; it must point to definitive, authoritative pages that confirm the entity's identity.
Frequently Asked Questions
Concise answers to the most common technical questions about implementing and optimizing the Schema.org LocalBusiness type for AI-driven search visibility.
LocalBusiness is a Schema.org structured data type representing a physical business location or a branch of an organization. It acts as a parent class for more specific types like Restaurant, Dentist, Store, or ChildCare. Implementing this markup involves embedding a JSON-LD script in the <head> of your webpage that explicitly defines the entity's name, address, telephone, openingHours, and geo coordinates. This structured data allows search engines and AI models to disambiguate your business as a distinct entity, rather than just a string of text, enabling rich results like Knowledge Panels and accurate local pack listings. For AI-driven search, it provides the factual grounding necessary for an agent to confidently cite your location, hours, and contact details in a generative overview without hallucinating incorrect information.
Enabling Efficiency, Speed & Accuracy
Intelligent Analysis, Decision & Execution
We build AI systems for teams that need search across company data, workflow automation across tools, or AI features inside products and internal software.
Talk to Us
Search across company data
Give teams answers from docs, tickets, runbooks, and product data with sources and permissions.
Useful when people spend too long searching or get different answers from different systems.

Automate internal workflows
Use AI to route work, draft outputs, trigger actions, and keep approvals and logs in place.
Useful when repetitive work moves across multiple tools and teams.

Add AI to products and internal tools
Build assistants, guided actions, or decision support into the software your team or customers already use.
Useful when AI needs to be part of the product, not a separate tool.
Related Terms
Master the interconnected vocabulary of structured data. These terms form the technical foundation for defining a LocalBusiness entity and its relationships within a machine-readable knowledge graph.

About the author
Prasad Kumkar
CEO & MD, Inference Systems
Prasad Kumkar is the CEO & MD of Inference Systems and writes about AI systems architecture, LLM infrastructure, model serving, evaluation, and production deployment. Over 5+ years, he has worked across computer vision models, L5 autonomous vehicle systems, and LLM research, with a focus on taking complex AI ideas into real-world engineering systems.
His work and writing cover AI systems, large language models, AI agents, multimodal systems, autonomous systems, inference optimization, RAG, evaluation, and production AI engineering.
Partnered with leading AI, data, and software stack.
How We Work
Custom AI workflows for your Business
One-fit-all AI don't work for modern businesses. At Inferensys, we aim to understand your business & custom requirements; which we use to define most efficient agentic workflows, the data, and the tools for your business.
01
Review the use case
We understand the task, the users, and where AI can actually help.
Read more02
Pick the right approach
We define what needs search, automation, or product integration.
Read more03
Build the first useful version
We implement the part that proves the value first.
Read more04
Improve from there
We add the checks and visibility needed to keep it useful.
Read moreThe first call is a practical review of your use case and the right next step.
Talk to Us