Schema Markup for Law Firms: The AEO Essentials
The schema types every law firm needs to be machine-readable and citable by AI: LegalService, FAQPage, Review, Person, and more.
By Deztrox
This guide is part of Answer Engine Optimization: the complete guide for professional services.
Schema markup makes a law firm machine-readable by labeling your pages with structured data (JSON-LD) that AI engines can parse without guessing. The types that matter most for a law firm are LegalService or Attorney for the firm entity, FAQPage for your answer content, Review and AggregateRating for reputation, Person for attorney bios, and BreadcrumbList for site structure. Add these correctly and engines like ChatGPT, Perplexity, and Google AI Overviews can identify who you are, what you practice, where you operate, and whether people trust you.
Most firms have not done this. According to NP Digital, more than 79% of businesses are not optimizing for AI search at all, which means clean structured data is still a real edge.
Why Schema Matters for AI Engines
AI engines read the web in fragments and reassemble facts to answer a question. Plain HTML forces them to infer your practice areas, location, and credibility from prose, which is error-prone.
Schema removes the guesswork. It states, in a fixed vocabulary, that this entity is a law firm, that it practices personal injury law, that it serves a given city, and that it holds a 4.8 average rating from 212 reviews.
When an engine can verify those facts quickly, it is more comfortable citing you. This is the technical groundwork behind answer engine optimization for professional services.
LegalService and Attorney: The Firm Entity
LegalService is the core type for a law firm. It is a subtype of LocalBusiness, so it inherits address, geo coordinates, telephone, openingHours, and areaServed.
Use it on your homepage and main practice-area pages. Fill in name, address, telephone, areaServed, priceRange, and sameAs (links to your Google Business Profile, Bar association listing, and social profiles).
Attorney is a narrower subtype for an individual lawyer. Use LegalService for the firm and Attorney for a solo practitioner’s page. For multi-lawyer firms, pair LegalService for the firm with Person schema on each bio.
FAQPage: Your Direct Answer Layer
FAQPage schema marks up question-and-answer blocks so engines can lift a clean answer straight from your page. This is the highest-impact type for AI citation.
According to Presence AI, content that pairs FAQ format with schema is cited around 76% of the time. Questions like “How long do I have to file a personal injury claim in my state?” map directly to how people prompt AI engines.
Keep each answer self-contained and factual, and keep the markup identical to the visible text. Here is a small, correct example.
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [
{
"@type": "Question",
"name": "How much does a personal injury consultation cost?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Our personal injury consultations are free. We work on contingency, so you pay nothing unless we recover compensation for you."
}
}
]
}
Review and AggregateRating: Trust Signals
AI engines weigh reputation heavily when recommending a professional service. Review schema marks up individual client reviews, and AggregateRating summarizes the overall score.
Place AggregateRating on the firm entity (inside your LegalService markup) with ratingValue and reviewCount. Only mark up reviews that genuinely appear on the page, since fabricated or hidden review markup violates Google’s guidelines.
Comparison content benefits here too. According to Presence AI, comparison-style content is cited around 74% of the time, so pages that compare your firm against alternatives, backed by real ratings, earn attention.
Person Schema for Attorney Bios
Each lawyer’s bio page should carry Person schema. This connects a named individual to credentials, education, bar admissions, and the firm.
Use name, jobTitle, alumniOf, worksFor (pointing to the LegalService entity), and sameAs for their professional profiles. AI engines increasingly answer “who is the best estate attorney in…” style prompts, and Person schema gives them a verifiable entity to name.
BreadcrumbList: Site Structure
BreadcrumbList schema tells engines how a page sits within your site hierarchy, for example Home > Practice Areas > Personal Injury.
This helps engines understand topical relationships and which page is most specific to a query. It is low effort and worth adding sitewide, especially on deep practice-area and location pages.
LocalBusiness vs. LegalService
You generally do not need both. LegalService already extends LocalBusiness and inherits its local properties, so applying both to one page is redundant.
Use LocalBusiness only for non-legal entities you might run separately. For the firm itself, LegalService is the precise, correct choice.
Schema Type Mapping
| Schema type | What it tells AI | Which page it goes on |
|---|---|---|
| LegalService / Attorney | Firm entity, practice, hours, location, service area | Homepage, practice-area pages |
| Organization | Brand identity, logo, official links | Homepage (firm-wide) |
| FAQPage | Direct answers to common client questions | FAQ pages, practice-area pages |
| Review / AggregateRating | Reputation and trust signals | Firm entity, testimonials page |
| Person | Individual lawyer identity and credentials | Attorney bio pages |
| BreadcrumbList | Site hierarchy and page context | All deep pages, sitewide |
| LocalBusiness | Local entity fallback (LegalService inherits this) | Non-legal entities only |
Why This Is Still an Opportunity
Citations are not confined to the usual winners. According to ALM Corp, roughly 62% of AI citations come from sources outside Google’s top 10 results, which means a smaller firm with clean structured data can be quoted even without dominating traditional rankings.
Combined with the fact that most firms are not optimizing for AI at all, structured data is one of the fastest moves a firm can make. Pair it with strong answer content, as covered in AEO for law firms, and you cover both the technical and content sides.
Implementation Checklist
Add JSON-LD in the page head, one block per type, and keep every value consistent with the visible content on the page. Mismatches can get markup ignored.
Validate every page with Google’s Rich Results Test and the Schema.org validator before publishing. Re-check after any template change, since theme updates often strip or break structured data.
Then confirm the engines actually read it by checking your citations, which connects directly to how to get cited by ChatGPT. Schema is the foundation, but content and tracking close the loop.
Schema markup is the cheapest, highest-certainty step in making a law firm visible to AI engines. Get the entity, answers, and trust signals labeled correctly, and you remove the main reason engines skip a site: they could not parse it.
To see how structured data fits the full picture, read the pillar on answer engine optimization for professional services, then request an AI visibility audit to find exactly which schema your firm is missing.