What Is LegalService Schema, and Why Does It Matter for Law Firms in 2026?
What Is LegalService Schema, and Why Does It Matter for Law Firms in 2026?
Google quietly retired the old Attorney schema type. It also just cut FAQ rich results entirely. Here's what actually still works, and what your firm's website needs to say to be understood by both Google and the AI tools now doing the recommending.
LegalService is the schema.org structured data type built specifically for businesses that provide legal representation and advice. It replaced the older Attorney type, which schema.org has formally deprecated. In 2026, LegalService schema matters less for classic Google rich results — several of which, including FAQ, have been scaled back — and more for giving AI search tools like ChatGPT, Perplexity, and Google AI Overviews an accurate, verifiable identity to cite when someone asks for a recommendation.
Structured data has always been a background technical detail — code most website visitors never see, sitting quietly in a page's source. But schema.org's own vocabulary keeps evolving, and 2026 has brought two changes law firms need to understand: an old attorney-specific schema type going away, and a widely-used rich result feature disappearing from Google Search entirely. Neither change makes schema markup less important. Both change what "doing it correctly" actually means right now.
What Is LegalService Schema?
LegalService is a structured data type defined at schema.org, described as "a business that provides legally-oriented services, advice and representation, e.g. law firms." It's a subtype of LocalBusiness, which means it inherits properties like address, phone number, and hours, while adding the ability to describe what legal services a firm actually offers.
In plain terms: structured data is a way of labeling the content already on a page so that machines, not just human readers, can understand what it means. A visitor reading a law firm's homepage understands instantly that they're looking at a personal injury firm in a specific city. Search engines and AI models need that same information spelled out explicitly, in a standardized vocabulary, rather than inferred from paragraph text.
Why Did Schema.org Deprecate the Attorney Type?
For years, law firms had a choice between a generic ProfessionalService type (which also covered dentists, accountants, and electricians) and a narrower Attorney type. Schema.org has now deprecated both. The Attorney type's own documentation states plainly that it "is deprecated - LegalService is more inclusive and less ambiguous." ProfessionalService was deprecated for similar reasons, described in schema.org's own documentation as having caused "confusion with Service."
Deprecated doesn't mean the markup breaks or throws an error — old Attorney schema will still validate as legitimate JSON-LD. But it does mean firms are marking up their site with a type schema.org itself no longer recommends, which is a poor long-term bet when the alternative, LegalService, is actively maintained and more descriptive.
Why Does LegalService Schema Matter for Law Firms in 2026 Specifically?
Google has been consistent on one point for years: structured data is not a ranking signal. It doesn't move a page from position ten to position five. What it does is determine eligibility — whether a page qualifies for an enhanced search appearance at all, and, increasingly, whether AI systems can confidently understand and cite what a business actually does.
That second part is where 2026 changes the calculus. A growing share of prospective clients are asking AI tools directly — "who's a good bankruptcy attorney near me," "best criminal defense lawyer for a DUI case" — rather than typing a search into Google and clicking through blue links. Those AI systems build their answers from a mix of crawled content and structured signals. A firm's homepage might clearly read as a law firm to a human, but without LegalService markup connecting name, location, and specific practice areas in a standardized format, an AI system has to infer that same information from prose — and inference is exactly what schema markup exists to remove. This is part of why AEO for law firms has become inseparable from traditional SEO for law firms — the two now depend on the same underlying technical foundation.
Where does schema actually live? In the code of the site itself — which is one reason it's worth confirming with whoever handles your website design that structured data is part of what gets maintained, not just visual layout.
Not sure what schema your site is actually running?
Run a Free AEO AuditWhere Should LegalService Schema Actually Appear on a Law Firm's Site?
A few placement principles matter more than exhaustive markup everywhere:
- Homepage and contact page. These establish the firm's core identity — name, address, phone, hours — and are the natural home for the primary
LegalServiceblock. - Individual practice area pages. A firm handling personal injury, criminal defense, and family law should specify each practice area explicitly, rather than relying on one vague "legal services" description to cover all three.
- Consistency with your Google Business Profile. Name, address, and phone number in your schema should match your GBP listing exactly — mismatches between the two create the kind of ambiguity structured data exists to eliminate. The same consistency principle applies to online reputation management: review counts and ratings referenced in schema should reflect what's actually visible on the page.
- Multi-location firms. Each office needs its own accurately-scoped
LegalServiceentity rather than one blended block covering every location.
What Happened to FAQ Schema, and Should Law Firms Still Use It?
This is the update most law firm marketing advice hasn't caught up with yet. Google's own developer documentation now states that "as of May 7, 2026, FAQ rich results are no longer appearing in Google Search," with the rich result report and Rich Results Test support being dropped in June 2026 and Search Console API support ending in August 2026.
It's also worth noting something that was true even before this change: Google's guidelines have always restricted FAQ rich results to "well-known, authoritative websites that are government-focused or health-focused." A law firm's blog post was never actually eligible for the visible FAQ rich result in Google Search — that particular payoff was always out of reach for this industry, whether or not the markup was implemented correctly.
None of that means FAQPage schema is worthless now. The visible checkmark-in-Google's-SERP is gone, but the underlying structured question-and-answer data still gives AI systems a clean, extractable format to pull from when generating an answer. The reason to keep using FAQ schema in 2026 isn't for a Google rich result that was never available to law firms anyway — it's for AI answer engines that read the same structured markup for a different purpose.
What Are the Most Common LegalService Schema Mistakes?
- Still running the deprecated Attorney type. It won't break anything, but it's a missed opportunity to use the more descriptive, actively-maintained type.
- Vague practice area descriptions. "Legal services" tells a machine almost nothing. "Personal injury litigation" and "Chapter 7 and Chapter 13 bankruptcy" are specific enough to match an actual search or AI query.
- Markup that contradicts the visible page. If schema claims a practice area or credential the page's actual content doesn't support, that mismatch undermines trust in the data, not just for that one property.
- One-and-done implementation. Schema.org's vocabulary changes over time — the Attorney deprecation is proof of that — and markup implemented once in 2020 and never revisited is likely already out of date.
- Treating schema as a ranking hack. It's an eligibility and clarity signal, not a shortcut past content quality, E-E-A-T, or genuine topical authority.
LegalService schema is the current, correct way to tell both Google and AI answer engines exactly what a law firm does and where — and it matters more now that classic rich results like FAQ have been pulled back, shifting more of the weight onto how clearly a firm's structured data speaks for it in AI-generated answers. Firms still running the deprecated Attorney type, or skipping structured data altogether, are leaving that identity signal to guesswork. It's one piece of a strategy that goes beyond basic SEO — see our proven results for real law firms for what that looks like in practice.
Frequently Asked Questions
What is the difference between LegalService and Attorney schema?
Does LegalService schema help a law firm rank higher in Google?
Should every page on a law firm's website have LegalService schema?
Is FAQ schema still worth using in 2026?
How does LegalService schema affect AI search visibility?
Sources
- Schema.org, LegalService type definition
- Schema.org, Attorney type definition (deprecated)
- Schema.org, ProfessionalService type definition (deprecated)
- Google Search Central, FAQ structured data documentation
- Google Search Central, General structured data guidelines
April Atwater
April Atwater leads Dashing Digital Marketing, a Salt Lake City-based agency working exclusively with law firms on SEO, AEO, and GEO. DDM's Dashing Digital Authority Framework™ has helped attorneys across the country turn website visitors into signed clients. (In case you're wondering: this post itself uses BlogPosting, FAQPage, and BreadcrumbList schema, not LegalService — DDM is a marketing agency, not a legal services provider, so LegalService wouldn't accurately describe this page.)
