LocalBusiness Schema for Law Offices
LocalBusiness schema establishes your firm's physical presence for AI search, voice assistants, and local pack rankings. Without it, AI systems must infer your location data from unstructured content — an unreliable process that reduces citation confidence for local legal queries.
What LocalBusiness Schema Does for Law Firms
LocalBusiness schema provides machine-readable location and contact signals that AI systems use when answering local legal queries. When someone asks Google Assistant “find a personal injury lawyer near me open on weekends,” the AI matches their location against your firm's geo coordinates, checks your service area, and verifies your hours — all using structured data from your LocalBusiness schema.
Without this schema, AI systems rely on inferring your location from your website's unstructured address text, which is less accurate and less confident. The result is lower ranking in local AI responses and voice search results.
Complete LocalBusiness Schema Implementation
The following JSON-LD implementation covers all critical properties for a law office. Place this in the <head> of your homepage and contact page:
{
"@context": "https://schema.org",
"@type": "LocalBusiness",
"@id": "https://example-firm.com/#localbusiness",
"name": "Smith & Associates Law Firm",
"url": "https://example-firm.com",
"telephone": "+1-310-555-0123",
"email": "info@example-firm.com",
"address": {
"@type": "PostalAddress",
"streetAddress": "123 Main Street, Suite 400",
"addressLocality": "Los Angeles",
"addressRegion": "CA",
"postalCode": "90001",
"addressCountry": "US"
},
"geo": {
"@type": "GeoCoordinates",
"latitude": 34.0522,
"longitude": -118.2437
},
"openingHoursSpecification": [
{
"@type": "OpeningHoursSpecification",
"dayOfWeek": ["Monday","Tuesday","Wednesday","Thursday","Friday"],
"opens": "09:00",
"closes": "17:00"
}
],
"serviceArea": {
"@type": "GeoCircle",
"geoMidpoint": {
"@type": "GeoCoordinates",
"latitude": 34.0522,
"longitude": -118.2437
},
"geoRadius": "50000"
},
"priceRange": "$$",
"sameAs": [
"https://www.google.com/maps/place/your-gmb-id",
"https://www.yelp.com/biz/smith-associates-law"
]
}Critical Properties Law Firms Commonly Miss
Voice assistants use coordinate data for 'near me' resolution. Text-only addresses are less precise for geographic matching. This is the most commonly missing high-impact property.
Distinguishes the geographic area you serve from your office location. Critical for firms that serve a wide metro area or multiple counties from a single office.
Structured hours (not just text) allow voice assistants to answer 'open now' queries. Use the structured format with dayOfWeek arrays, not just an hoursAvailable text string.
Specifying contactType: 'customer service' or 'legal consultation' helps AI systems categorize the type of contact your firm accepts, improving relevance matching for service queries.
Links from your LocalBusiness schema to your Google Maps listing and major directories create entity cross-references that reduce location identity ambiguity for AI systems.
Multiple Office Locations
For firms with multiple offices, create a separate LocalBusiness schema block for each location with its own @id, address, phone, and geo coordinates. Link each location to your main Organization entity:
{
"@type": "LocalBusiness",
"@id": "https://example-firm.com/locations/pasadena/#localbusiness",
"name": "Smith & Associates Law Firm - Pasadena Office",
"parentOrganization": {
"@id": "https://example-firm.com/#organization"
},
"address": { ... },
"geo": { ... }
}Linking LocalBusiness to Your Entity Graph
Your LocalBusiness entity should be referenced in your main Organization schema via a location property, and in your LegalService entities via areaServed. This entity linking tells AI systems that your physical location, your services, and your organizational identity are all part of a single coherent entity — not disconnected data fragments. Disconnected schema blocks carry significantly less weight in AI citation decisions.
Frequently Asked Questions
What is LocalBusiness schema and why do law firms need it?
LocalBusiness schema is structured data markup that tells search engines and AI systems about your law firm's physical location, contact information, hours, and service area. Law firms need it because local queries — 'personal injury attorney near me,' 'family law firm open now' — are resolved using this data. Without LocalBusiness schema, AI systems and local search algorithms have to infer your location details from unstructured page content, which is less reliable and reduces citation confidence for local queries.
Should LocalBusiness schema use the LegalService type or the LocalBusiness type?
For law firms, the recommended approach is to implement both as separate, linked entities in your @graph. Use LocalBusiness for your firm's physical office presence (location, hours, contact) and LegalService for your practice area offerings. Nesting LegalService inside LocalBusiness or trying to combine them into one schema block creates ambiguous entity relationships that AI crawlers handle inconsistently. Link them via @id references instead.
How do I handle multiple office locations in LocalBusiness schema?
Each physical office location should have its own separate LocalBusiness schema block with its own @id, address, phone number, and geo coordinates. Link each location back to your main Organization entity via a hasLocation or subOrganization property. This structure tells AI systems that all locations are part of the same firm while allowing each to appear independently in local search results for its specific geographic area.
What are the most commonly missed LocalBusiness schema properties for law firms?
The most commonly missed properties are: geo (GeoCoordinates with latitude and longitude), openingHoursSpecification (structured hours rather than just text), serviceArea (distinguishes the area you serve from your office location), priceRange, and contactPoint with contactType set to 'customer service' or 'legal services.' The geo property is particularly important because AI systems and voice assistants use coordinate data for 'near me' query resolution.
How does LocalBusiness schema relate to my Google Business Profile?
LocalBusiness schema on your website and your Google Business Profile are complementary but separate systems. Your GBP controls how you appear in Google Maps and local pack results directly. Your LocalBusiness schema helps AI systems and non-Google search engines understand your location data. Both must have identical NAP (name, address, phone) data — inconsistency between them creates entity confusion that reduces your local AI search confidence.
Implement LocalBusiness Schema on Your Firm's Site
Our free schema audit includes a complete LocalBusiness schema review, NAP consistency check, and a deployment plan for all your office locations within five business days.
Get Free Schema AuditRelated Articles
Schema Markup for Law Firms: The 8-Node @graph Framework That Builds AI Citation Confidence
Schema markup is the foundation of AI search visibility for law firms. This guide covers the 8-Node @graph Framework — the complete structured data architecture that connects your Organization, LegalService, Attorney, FAQPage, and LocalBusiness entities into a self-verifying knowledge graph AI platforms trust.
Read Article →SchemaFAQPage Schema for Law Firms: The Highest-ROI Schema Type
FAQPage schema is the single highest-ROI structured data investment for law firms. It maps directly to how AI systems extract answers for voice search, featured snippets, and generated responses — and it can be deployed on any practice area page in under two hours.
Read Article →