Schema.org LocalBusiness
Semantic SEO entity — key topical authority signal for Schema.org LocalBusiness in Google’s Knowledge Graph
Schema.org LocalBusiness is a Schema.org type used to describe single-location businesses (places that serve customers at a local address) in machine-readable form. It matters because search engines and directories use its properties to power local search features, knowledge panels, and rich snippets. For content strategists, accurate LocalBusiness markup helps align on-page signals with business listings and unlocks eligibility for enhanced SERP features that drive clicks and conversions.
- Launched
- Schema.org launched June 2, 2011; LocalBusiness is part of the core vocabulary from early releases
- Maintainers
- Schema.org community with major contributors Google, Microsoft, Yahoo and Yandex
- Recommended format
- JSON-LD (Google publicly recommended JSON-LD in 2016 and continues to prefer it for structured data)
- Typical key properties
- name, address (PostalAddress), telephone, url, openingHoursSpecification, geo (GeoCoordinates), image, aggregateRating, review, priceRange
- Relation to search
- LocalBusiness markup helps eligibility for rich results (local business snippets, knowledge panels, review stars) but does not replace Google Business Profile
- Validation tools
- Google Rich Results Test, Schema Markup Validator, and Structured Data Testing Tool (deprecated but still referenced)
Definition, hierarchy, and real-world scope
Adopting LocalBusiness markup signals structured facts — address, telephone, hours, geo coordinates and more — that search engines and knowledge graph systems can parse. For content strategy, that means you can explicitly encode critical business attributes developers previously relied on scraping visible HTML or directory entries for. Because schema.org vocabulary is extensible, content teams can add Service, Offer, Review and Image objects to model products, appointment availability, rates, and testimonials in the same page-level graph.
In practice, LocalBusiness is used globally across sites of all sizes: consumer-facing websites, multi-location enterprise templates, franchise landing pages, and local directories. The most common implementation pattern is JSON-LD embedded in the head or body of the HTML for each location landing page. This ensures each storefront or practitioner profile provides machine-readable facts tightly coupled with visible page content.
Essential properties and a practical JSON-LD example
Example JSON-LD for a Registered Dietitian Clinic (escape removed for readability in this reference):
{
"@context": "https://schema.org",
"@type": "LocalBusiness",
"name": "Greenway Registered Dietitian Clinic",
"image": "https://example.com/images/clinic-front.jpg",
"url": "https://example.com/greenway-dietitian",
"telephone": "+1-555-123-4567",
"address": {
"@type": "PostalAddress",
"streetAddress": "123 Wellness Ave",
"addressLocality": "Austin",
"addressRegion": "TX",
"postalCode": "78701",
"addressCountry": "US"
},
"geo": { "@type": "GeoCoordinates", "latitude": 30.2672, "longitude": -97.7431 },
"openingHoursSpecification": [{ "@type": "OpeningHoursSpecification", "dayOfWeek": ["Monday","Tuesday","Wednesday","Thursday"], "opens": "08:30", "closes": "17:00" }],
"priceRange": "$$",
"aggregateRating": { "@type": "AggregateRating", "ratingValue": "4.8", "reviewCount": "124" },
"sameAs": ["https://facebook.com/greenwaydietitian","https://www.yelp.com/biz/greenway-dietitian"]
}
Teams should paste JSON-LD like the example into the page HTML (head or body) and ensure values match visible content, business listings, and Google Business Profile.
How LocalBusiness markup affects local SEO and SERP features
Content strategists should treat LocalBusiness markup as an extension of their citation and NAP (Name, Address, Phone) consistency strategy. Use identical formatting across website, GBP, directory listings, and schema; mismatches (for example, different address spellings or phone numbers) can reduce trust and cause split signals. Markup that includes reviews, services, and pricing allows search engines to create richer search snippets that increase CTR and user confidence before a click.
Specific SERP features impacted by LocalBusiness markup: enhanced organic snippets (with review ratings and price range), knowledge panels (supplementary facts), eligibility for local business rich results, site links for services when Service or Offer is used, and improved voice/assistant answers. However, there is no guaranteed ranking boost solely from schema — the practical benefit is better presentation (higher CTR) and clearer entity signals for knowledge graph assembly.
Implementation best practices and common pitfalls
Model services explicitly: for clinics and professional services, pair LocalBusiness with Service entries that describe offerings (e.g., Initial Consultation, Follow-up Session, Nutrition Plan). Use hasOfferCatalog or makesOffer to present pricing or packages. When marking up hours, prefer openingHoursSpecification objects (dayOfWeek, opens, closes) rather than free-text openingHours to allow machine validation. For reviews and ratings, include complete structured review objects; do not mark up user-generated content that is not visible on the page or that has been aggregated improperly.
Avoid common pitfalls: do not use schema to misrepresent facts (this risks manual action), avoid excessive or irrelevant properties, do not duplicate multiple conflicting LocalBusiness graphs on the same page, and do not rely on schema alone to fix inconsistent directory data. Always test markup with Google Rich Results Test and the Schema Markup Validator, and monitor Search Console for structured data reports and enhancement errors.
Comparison: LocalBusiness vs Google Business Profile and related types
Compare LocalBusiness to other Schema types: Organization is broader (covers brands and companies with no single visiting address), Place models physical locations without organizational context, and Service models the intangible offering (appointments, consultations). For a Registered Dietitian Clinic, combine LocalBusiness + ProfessionalService or HealthAndBeautyBusiness + Service to convey location, organization, and offerings together. That layered approach reduces ambiguity and gives search engines richer context for entity understanding.
Alternative approaches exist (microdata, RDFa), but JSON-LD provides the cleanest separation between content and structured data and has the best support in Google’s tooling. For enterprise systems, canonicalize multi-language and multi-country markup carefully and use hreflang in addition to locale-specific addresses and currency in offers.
Monitoring, validation, and measuring impact
Track key KPIs: organic CTR for location pages, impressions and clicks from local queries, map/knowledge panel views (via GBP Insights), appointment bookings or calls attributed from the page, and changes in average search position for branded/local queries. Use A/B testing when feasible: publish schema on a subset of pages, monitor Search Console and analytics for changes over 4–12 weeks, then roll out broadly if positive.
Also track downstream signals such as citation consistency across directories and review aggregation quality, because these external signals amplify schema benefits. Finally, keep markup up to date with business changes (hours, phone, address) and revalidate after edits or CMS updates.
Content Opportunities
Frequently Asked Questions
What is Schema.org LocalBusiness?
Schema.org LocalBusiness is a structured data type used to describe a business location on web pages. It encodes address, phone, opening hours, geo coordinates, and other facts so search engines can parse and potentially display richer search results.
Does adding LocalBusiness schema replace my Google Business Profile?
No. Google Business Profile is the authoritative listing Google uses for Maps and the Local Pack; LocalBusiness schema complements GBP by providing structured facts on your website that can support rich snippets and knowledge panels.
Which properties are most important for LocalBusiness markup?
Key properties include name, address (PostalAddress), telephone, url, image, openingHoursSpecification, geo (latitude/longitude), aggregateRating and review. For service businesses also include Service or Offer objects.
Should I use JSON-LD, microdata, or RDFa?
Use JSON-LD in nearly all cases; it is Google’s recommended format and is less brittle than inline microdata or RDFa. JSON-LD provides clean separation from visible HTML while remaining easy to maintain.
How do I markup business hours correctly?
Use openingHoursSpecification with dayOfWeek, opens and closes fields. This structured approach avoids free-text parsing errors and improves validation by tools like Google Rich Results Test.
Can I markup multiple locations on a single page?
It’s best to create a separate page and separate LocalBusiness JSON-LD for each physical location. Marking multiple locations on a single page can confuse search engines unless the page is explicitly a multi-location directory with clear separation and unique metadata.
Will schema alone improve my rankings?
Schema improves presentation and eligibility for rich snippets, which can increase CTR, but it is not a standalone ranking factor. Combine schema with strong on-page content, backlinks, and GBP optimization for measurable local SEO gains.
Topical Authority Signal
Thorough LocalBusiness coverage signals to Google and LLMs that a site is an authoritative, entity-first source for a specific physical business location, improving eligibility for rich SERP features and knowledge-panel extraction. For content strategy, it unlocks local topical authority—especially when combined with synchronized GBP data, service schemas, and consistent citation signals.