Local Business Schema for Law Firms
Local Business Schema for Law Firms: A Complete Implementation Guide
The JSON-LD that tells Google exactly where your firm is, when it's open, and which office to send a client to — done wrong, it does nothing; done right, it's the difference between a Knowledge Panel and a blank stare.
Short answer: Local business schema is JSON-LD structured data — built on schema.org's LocalBusiness family, with LegalService as the correct subtype for a law firm — that declares your firm's name, address, phone number, hours, and service area in a format search engines and AI models can parse directly, rather than infer from page text. Google requires only name and address for rich-result eligibility, but a thin implementation leaves real value on the table.
Every law firm website has a footer with an address in it. Most have a contact page with a phone number and a Google Map embed. None of that, on its own, tells Google or an AI model anything definitive. Visible text is something a machine has to infer meaning from. Local business schema is different: it's a structured, machine-readable statement of fact, sitting quietly in the page's code, saying exactly what your firm is, where it is, and when it's reachable — no inference required.
This is a narrower, more technical companion to our guide on entity SEO for law firms, which covers the broader work of establishing your firm as a trusted entity in Google's Knowledge Graph. Local business schema is one of the concrete building blocks of that larger effort — the part you can actually open a code editor and implement today.
What Is Local Business Schema, and Why Does It Matter for Law Firms?
Local business schema markup uses the LocalBusiness type from schema.org — a vocabulary jointly maintained by Google, Microsoft, Yahoo, and Yandex — to describe a physical business location in structured JSON-LD. For a law firm, the correct subtype is LegalService, which schema.org treats as a specific kind of LocalBusiness.
Most consumers shopping for legal help do at least some of that shopping through search. Clio's Legal Trends Report has found that a majority of legal consumers search on their own rather than relying solely on a referral, and Clio's more recent research shows AI tools are increasingly part of that search process, with a meaningful share of AI-assisted legal questions ending in a recommendation to contact a lawyer directly. Both search engines and AI answer engines lean on structured data to figure out which local result actually matches the searcher's location and need. A firm without local business schema is asking the algorithm to guess.
LegalService vs. Attorney vs. LocalBusiness: Which Schema Type Is Correct?
This is the single most common mistake we find auditing law firm sites. Schema.org previously offered an Attorney type, and a lot of older SEO guidance — and a lot of legacy Squarespace and WordPress plugins — still reference it. That type has since been deprecated in favor of LegalService. Markup using the old Attorney type will typically still parse without throwing an error, but it no longer maps to the properties Google actively supports for rich results, which means it's quietly doing nothing.
LegalService is itself a subtype of LocalBusiness, which is in turn a subtype of Organization. That inheritance matters practically: Google's own structured data documentation recommends following the Organization property guidelines in addition to the LocalBusiness-specific ones, since a law firm entity benefits from both layers — the local-presence signals and the broader organizational identity signals.
{
"@context": "https://schema.org",
"@type": "LegalService",
"name": "Example Law Group",
"address": {
"@type": "PostalAddress",
"streetAddress": "400 Main Street, Suite 210",
"addressLocality": "Salt Lake City",
"addressRegion": "UT",
"postalCode": "84101",
"addressCountry": "US"
},
"telephone": "+18015550123",
"url": "https://www.example-law-group.com",
"areaServed": {
"@type": "AdministrativeArea",
"name": "Salt Lake County, UT"
}
}If your firm practices in more than one area of law, schema.org allows an array of types rather than a single value — for example ["LegalService", "Attorney"] is no longer the right pairing, but you can combine LegalService with a more specific practice designation where one genuinely exists. When in doubt, a single accurate LegalService declaration beats a stack of loosely related types.
What Properties Does Google Require for Local Business Rich Results?
Per Google's Search Central documentation, only two properties are strictly required: name and address. Everything past that is recommended, not mandatory — but "recommended" is doing a lot of work here, because the recommended properties are what actually make the markup useful rather than merely valid.
telephone— the primary contact number, written with country and area code.url— the fully-qualified URL of the specific location's page. This must be a working link.geo— latitude and longitude, each carried to at least five decimal places.openingHoursSpecification— structured hours, broken out by day of week, using an array if hours vary.priceRange— optional for legal services, but if used, must stay under 100 characters or Google won't display it.
Two properties that are technically supported but worth using with restraint for a law firm: aggregateRating and review. Google explicitly notes these are intended for sites that capture reviews about other businesses — not self-reported testimonials. Marking up your own five-star client reviews directly in your firm's LegalService schema runs against that guidance and is one of the more common ways firms trip a structured data policy issue.
How Do You Mark Up NAP Consistency Correctly?
NAP — name, address, phone — consistency is usually discussed as a citation-building exercise: make sure your firm's listing looks identical across every directory. It's also a schema exercise, and the two need to match each other exactly. If your PostalAddress object in JSON-LD reads "Suite 210" and your visible footer reads "Ste. 210," that's a small inconsistency, but it's the kind of mismatch that erodes the confidence Google places in the entity as a whole.
A practical rule we use with clients: whatever string appears in the visible NAP block on the page is the exact string that goes into the schema — copy it, don't retype it. This is the same character-for-character discipline we apply to FAQ markup, and it matters for the same reason: search engines and AI crawlers cross-check visible content against structured data, and mismatches read as a trust signal problem rather than a formatting quirk.
Not sure if your firm's schema is even parsing correctly? We'll run a full structured data and AI visibility check on your site — no cost, no obligation.
Get Your SEO and AI Visibility AuditWhat About Multi-Office and Multi-Attorney Firms?
Firms with more than one physical office should mark up each location as its own LegalService entity, each with its own address, telephone, and geo coordinates, rather than one schema block trying to represent every office at once. Google's documentation supports a department property for businesses with distinct sub-units under one roof, which can work for a firm with, say, a dedicated intake department with its own phone line — but for genuinely separate office locations, separate LegalService entities tied together through a shared parent Organization is the cleaner structure.
Individual attorney bios benefit from their own Person schema, connected back to the firm through a worksFor property, with a sameAs array linking out to verified bar association profiles, LinkedIn, and legal directories. That layer sits outside strict LocalBusiness markup but reinforces it — it's covered in more depth in our entity SEO guide, which walks through the full Person/Organization/LegalService relationship.
This matters differently depending on practice area. A firm handling personal injury or criminal defense cases across county lines needs its areaServed property to reflect the actual jurisdictions covered, not just the city of the office address. A family law or estate planning practice serving a single metro area has a simpler job, but the same discipline applies: don't claim a service area broader than what the firm can substantiate with visible page content, since Google's structured data guidelines are explicit that markup has to reflect what's actually on the page.
How Does Local Business Schema Connect to Your Google Business Profile?
Schema and Google Business Profile are separate systems, but they aren't unrelated. Google cross-references what your website's structured data claims against what your GBP listing says, and against what third-party directories say. When all three agree, that consistency reinforces the entity. When they conflict — a different suite number, a phone number that's been ported but not updated everywhere — schema becomes an additional source Google can use to catch and potentially correct the discrepancy, which is exactly why accuracy in the markup matters more than most firms assume.
Schema is not a substitute for an actively managed GBP profile, and it won't fix a profile that's unclaimed, unverified, or has stale categories. Firms serious about this layer of visibility generally need both a properly structured site and a maintained profile — the kind of coordinated work covered under local SEO for law firms as a discipline in its own right.
What Are the Most Common Local Business Schema Mistakes Law Firms Make?
- Using the deprecated Attorney type. Still parses, no longer maps to Google's supported properties.
- Marking up self-collected testimonials as
revieworaggregateRating. Google reserves this for sites that review other businesses. - Address mismatches between schema and visible content. Even a suite number formatted differently counts.
- One schema block covering multiple physical offices. Each location needs its own entity.
- Skipping
openingHoursSpecificationentirely. It's not required, but its absence is a missed recommended property with no real cost to adding it. - Overclaiming
areaServed. Listing every county in the state when the firm meaningfully serves two. - Forgetting the schema entirely on location-specific landing pages. A city-targeted page without
LegalServiceandareaServedmarkup is leaving the clearest possible local signal unmarked.
How Do You Test and Validate the Markup?
Before publishing, run the page through Google's Rich Results Test to catch critical errors — missing required properties will show up here immediately. It's worth also checking the Search Console structured data reports periodically after launch, since a manual action or an unparsable script tag can silently drop your markup from consideration without any visible change to the page itself. A page that looks fine to a human visitor can still be invisible to a crawler if a stray comma breaks the JSON.
Once validated, allow time for re-crawling — Google's own documentation notes it can take several days after publishing for a page to be crawled and its structured data reprocessed, longer if the site doesn't submit an updated sitemap.
Where Does Schema Fit Into a Firm's Broader Marketing Plan?
Schema is one input, not the whole strategy. It sits alongside the on-page and off-page work covered under SEO for law firms, and it reinforces — but doesn't replace — the review and citation work covered under online reputation management. A firm's site design also affects how cleanly schema can be implemented in the first place, since a templated theme with locked-down code blocks can make even simple JSON-LD changes harder than they should be.
Firms weighing whether to handle this in-house or bring in outside support often land on a fractional CMO arrangement precisely because structured data, local SEO, and content strategy need to move together rather than as disconnected projects — a philosophy we lay out in more detail in our guide to marketing strategy that goes beyond SEO. We've applied this exact schema framework across practice areas, including bankruptcy and consumer-protection firms where jurisdiction-specific areaServed markup carries real weight, and the outcomes are documented on our results page. If you want a fast read on where your own site currently stands, our free AEO audit tool is a reasonable first step before a full technical review.
The Bottom Line
Local business schema is inexpensive to implement and easy to get subtly wrong. Use LegalService, not the deprecated Attorney type. Include name, address, phone, hours, and geo coordinates at minimum, and make sure every value matches your visible page content exactly. Treat each office as its own entity. Validate before you publish, and check back after. None of this replaces the broader entity-building work — Wikidata, directory consistency, author bylines — covered in our entity SEO guide, but it's the foundation that work sits on.
Frequently Asked Questions
What is local business schema for law firms?
Local business schema is JSON-LD structured data built on schema.org's LocalBusiness family, with LegalService as the correct subtype for a law firm, that declares your firm's name, address, phone number, hours, and service area in a format search engines and AI models can parse directly, rather than infer from page text.
What's the difference between LegalService and LocalBusiness schema?
LocalBusiness is the broad schema.org category for any physical business location. LegalService is a specific subtype of LocalBusiness built for legal service providers, and it's the correct, current type for a law firm — the older Attorney type has been deprecated by schema.org.
What properties does Google require for local business rich results?
Google requires only two properties for eligibility: name and address. Recommended properties that strengthen the markup include telephone, url, geo coordinates, openingHoursSpecification, and priceRange.
Does local business schema replace my Google Business Profile?
No. Schema and Google Business Profile are separate systems that reinforce each other when the details match. A firm needs both a properly structured website and an actively managed, verified Google Business Profile.
Can a multi-office law firm use one LocalBusiness schema for all locations?
No. Each physical office should be marked up as its own LegalService entity with its own address, phone number, and geo coordinates, rather than combining multiple locations into a single schema block.
How do I test whether my law firm's schema is working?
Run the page through Google's Rich Results Test to catch critical errors, then monitor the structured data reports in Search Console after publishing. Allow several days after launch for Google to recrawl and reprocess the markup.
Related Resources
April Atwater
April has 22 years of search industry experience and holds Moz, Google, and Google Analytics certifications, specializing in SEO, AEO, and structured data strategy for law firms nationwide. Her writing has appeared in Iowa Lawyer, Arizona Attorney Magazine, Wyoming Lawyer Magazine, and The Gavel. Connect on LinkedIn.
