Four types of schema markup matter for almost every law firm: LegalService (or LocalBusiness with a legalService category) for the firm itself, Person for each attorney bio, FAQPage for question-and-answer content, and BreadcrumbList for site hierarchy. Everything else is optional, and most of what agencies sell as “comprehensive schema implementation” is theater that won’t change a thing about how you rank.
Schema is real. Schema also gets oversold. Here’s what each type actually does, where to put it, and the trap agencies fall into when they bill for schema as a deliverable.
What schema actually does (and doesn’t do)
Schema markup is structured data — code in the back of your page that tells Google, “this is a law firm, located at this address, with these attorneys, offering these services.” It doesn’t make you rank higher directly. What it does is two things. First, it helps Google understand your page faster and more confidently, which can affect how Google decides where to show you. Second, it makes you eligible for certain enhanced results — like FAQ snippets, breadcrumb links in the SERP, or knowledge-panel data.
What schema doesn’t do: it doesn’t fix a thin page, it doesn’t compensate for missing content, and it doesn’t move a page up the SERP by itself. Schema is a clarification layer on top of substantive content. If the content isn’t there, no amount of schema will save the page.
Schema doesn’t make a bad page rank. It makes a good page rank a little more confidently. Anyone telling you otherwise is selling you a deliverable that fits neatly on an invoice.
The four types that matter
LegalService (or LocalBusiness with legalService category). This goes on the homepage and on your contact page. It tells Google: this is a law firm, here’s the name, address, phone, hours, the practice areas served, the geographic area served. For most firms, LegalService is the right schema type. If your firm is heavily local-pack-dependent (which most firms are), LocalBusiness with appropriate legal categories can also work and is sometimes interchangeable. Don’t agonize over the distinction — pick one and implement it well.
Person. This goes on each attorney bio page. It tells Google: this is a real person, here’s their name, their job title (attorney at [firm]), their education, bar admissions, areas of focus. Person schema feeds into how Google understands the expertise behind your firm — it’s a direct E-E-A-T signal. For multi-attorney firms with dedicated bio pages, Person schema is one of the higher-leverage implementations because it ties named expertise to the firm. More on attorney bio pages here.
FAQPage. This goes on pages with genuine question-and-answer content — usually FAQ pages and Answer-style pages like this one. Implemented correctly, FAQPage schema can make your page eligible for the FAQ rich result in the SERP (the expandable question list under your listing). It’s been on Google’s quiet-rollback list a few times — sometimes the rich result shows, sometimes it doesn’t — but the schema itself is still worth implementing where the content genuinely supports it. The trap: don’t add FAQPage schema to a page that isn’t actually Q&A. Google penalizes mismatch.
BreadcrumbList. This goes on every interior page that’s nested in a hierarchy — your practice pages, your knowledge content, your answers. It tells Google the page’s place in the site structure (“Home > Practice Areas > Personal Injury”) and makes you eligible for breadcrumb links in the SERP, which improves click-through rate. Cheap to implement, broadly useful, and underrated.
Schema types that are optional (and how to decide)
There are dozens of other schema types schemas.org defines, and agencies will sometimes pitch “complete schema implementation” as if all of them matter. Most don’t, for most firms. A few are worth considering if the content fits:
Review and AggregateRating can make you eligible for star ratings in the SERP. Useful, but the rules are strict — the reviews schema’d must be visible on the page, on your own site, and not just embedded Google reviews. Many firms try to shortcut this and get penalized. Worth doing carefully. More on review schema here.
Article for genuine long-form content (long-form guides, in-depth knowledge pages). Helps Google understand the article structure and authorship. Useful where the content earns it.
Service as a parallel to LegalService for individual practice area pages. Optional — LegalService at the site level usually carries the signal, and adding Service schema to every practice page is sometimes more overhead than benefit. I usually skip it unless there’s a specific reason.
Everything else — Event, Course, JobPosting, Recipe (yes, agencies sometimes leave Recipe schema in template installs) — is either irrelevant to a law firm or actively misleading. If your agency is implementing schema you can’t explain, ask why. The answer should be specific.
The schema theater trap
I audit firms that have spent thousands on “comprehensive schema implementations” where the agency dropped sixty fields of LegalService schema onto every page of the site. The fields are technically valid. The pages don’t rank because the underlying content is thin. Schema isn’t the problem and schema isn’t the fix — but the invoice line item gave the agency something to point at when the rankings didn’t move.
Done right, schema is a 90-minute project for a small firm and a one-week project for a larger one. It’s not an ongoing service. Once it’s implemented and validated, it sits there working. If your agency is billing for “ongoing schema management” as a recurring line item, you’re paying for theater. More on schema implementation here.
Where to put each type, in plain English
Page-level placement matters. LegalService schema goes on the homepage and contact page, where the firm’s identity is the subject of the page. Person schema goes on each individual attorney bio page — one Person object per attorney, on the page that’s actually about that attorney. FAQPage schema goes only on pages where the visible content is genuinely a question-and-answer format. BreadcrumbList goes on every page nested under a parent (your practice pages, your knowledge content, your answers).
One common mistake: dropping the same site-wide schema block on every page regardless of whether it applies. LegalService on a blog post doesn’t help. Person schema on a practice page doesn’t help. Schema should match what the page is actually about. If you can’t articulate, in one sentence, what the page is about and why the schema fits, the schema doesn’t belong there.
Related reading: anatomy of a ranking practice page, E-E-A-T signals for law firm pages, and why aren’t my rankings improving.