Attorney Schema Markup Best Practices
LAW FIRM SEO THAT WORKS®
Our Focus: Your Firm
Schema markup is the single most underused technical asset on most law firm websites. Google has over 30 structured data types available to content publishers, and law firm marketing professionals who skip schema leave their firms invisible to the search engines and AI systems that potential clients rely on every day. Done correctly, structured data tells Google, ChatGPT, Perplexity, and Gemini exactly who you are, what you practice, where you operate, and why you should be recommended. Done wrong, or skipped entirely, it hands that decision to third-party directories that often carry stale information.
Table of Contents
- The Attorney Schema Type Is Deprecated — Use LegalService Instead
- How Person Schema Builds Attorney Credibility in Search and AI
- LegalService Schema and Local Search: Connecting Practice Areas to Queries
- FAQPage and Video Schema: AI Visibility Beyond Traditional Rich Results
- Validating Attorney Schema and Avoiding Common Implementation Errors
- FAQs About Attorney Schema Markup Best Practices
The Attorney Schema Type Is Deprecated — Use LegalService Instead
Schema.org formally deprecated the Attorney type, noting that LegalService is more inclusive and less ambiguous. That is a significant change many firms have missed. The Attorney schema type was deprecated in 2024 and Google no longer honors it for rich results. It still validates as legitimate schema.org markup, but it triggers no enhancements and provides no citation lift.
Most law firm websites in 2026 fall into one of three buckets on schema markup: zero schema at all, generic Organization schema copied from a WordPress plugin, or the deprecated Attorney schema that Google stopped honoring. None of the three help an AI engine decide whether to cite your firm.
LegalService is defined by Schema.org as a business that provides legally-oriented services, advice, and representation, such as law firms. As a LocalBusiness, it can be described as a provider of one or more services. That definition gives you a clear framework. Your firm is not a generic local business. It is a legal service provider, and your markup should say so explicitly.
LegalService is the primary schema type for the firm itself. It is a subtype of LocalBusiness specifically built for legal service providers, and it accepts every property a firm needs: name, address, phone, opening hours, area served, accepted payment, and the list of services offered. LegalService is what gets your firm eligible for local pack listings, knowledge panel features, and AI citations as a “law firm in [city].” Use it on your homepage and your contact or about page.
If your site still runs the old Attorney type, that is a same-day fix. If your developer or a legacy SEO plugin is still pushing Attorney schema, swap it out. Use Person schema for the attorney and connect that Person to your LegalService entity through the worksFor property. That connection is what creates the entity relationship Google uses to understand your firm’s people and their credentials.
How Person Schema Builds Attorney Credibility in Search and AI
Person schema on attorney bio pages does more than add a name to a search result. Person schema for individual attorneys includes professional qualifications, bar admissions, practice areas, and biographical information that enhances personal search visibility and professional credibility. Each of those properties feeds the E-E-A-T signals that Google weighs heavily on YMYL pages, and legal content sits squarely in that category.
Think about what happens when a prospective client types a specific attorney’s name into a search bar. Google, Bing, and AI engines all maintain knowledge graphs that connect a firm to its address, attorneys, services, and reviews. If your site does not feed that graph through schema, the engines pull data from third-party directories, often with stale phone numbers, wrong office hours, or missing attorneys. Schema is how you take ownership of your firm’s entity record from the source.
The properties available inside Person schema go well beyond a name and job title. Attorney schema markup includes bar admission information, professional licenses, and educational qualifications that demonstrate competence and expertise to search engines and potential clients. Education schema details law school attendance, degrees earned, and continuing education that supports professional credibility. Award and recognition schema highlights professional achievements, peer recognition, and industry honors that distinguish attorneys in search results.
Connecting Person schema to your firm’s LegalService entity is the step most implementations miss. Use Person schema for the attorney and connect that Person to your LegalService entity through the worksFor property. That relationship is what allows Google to confirm that a specific attorney practices at a specific firm in a specific city, rather than inferring it from page text alone.
For firms with multiple attorneys, scale this systematically. A law firm should publish accurate LegalService and Organization data and connect attorney profiles with Person so search systems can understand who provides each service. Every attorney on your team deserves that structured visibility, not just the named partners.
LegalService Schema and Local Search: Connecting Practice Areas to Queries
Specificity is what separates effective LegalService schema from generic markup that does nothing. LegalService schema should specify every practice area your firm handles. Vague entries like “legal services” do not help AI match your firm to specific queries. Specific entries like “personal injury” and “criminal defense” create precise match opportunities. Each practice area becomes a citation opening when AI answers cover that topic.
The relationship between LegalService and LocalBusiness schema trips up a lot of firms. LegalService is a more specific type that extends from LocalBusiness. You start with LocalBusiness properties (address, phone number, opening hours) and then add LegalService properties (areas of law, types of legal services). You use both, not one or the other.
For personal injury firms especially, local match precision matters. With the majority of legal queries now originating on mobile devices, and many voiced through AI assistants, structured data such as LegalService with PostalAddress can reinforce your local presence and support eligibility for “near me” searches. A query like “personal injury lawyer near me” triggers a local intent match, and your schema’s areaServed and PostalAddress properties are what confirm your geographic relevance.
Multi-office firms need a different structure entirely. If you operate offices in multiple cities, your schema structure needs to reflect this hierarchy. Your main organization (headquarters) uses Organization schema with complete details. Each location then gets its own LegalService entity with a unique @id, its own address, and its own areaServed properties. Sharing a single @id across locations creates entity collisions that confuse search engines and suppress local visibility.
The schema for lawyers implementation that produces real local search results always includes areaServed with specific city or county values, hasOfferCatalog listing each practice area by name, and geo-coordinates that confirm the physical office location. Generic LocalBusiness markup with “attorney” as a description field sends the same signal as a restaurant or dry cleaner.
FAQPage and Video Schema: AI Visibility Beyond Traditional Rich Results
FAQPage schema changed significantly in August 2023, and many firms are still running outdated assumptions about what it does. FAQPage schema deserves a nuanced assessment. Google significantly reduced FAQ rich result display in August 2023, limiting them primarily to well-known, authoritative government and health websites. For most law firm sites, FAQ schema will not generate visible rich results in current SERPs.
That does not make FAQPage schema useless. The schema still has value for AI search citations, but not for the SERP look you might be paying for. AI systems including ChatGPT, Perplexity, and Google’s AI Overviews extract structured question-and-answer pairs when generating responses to legal queries. FAQPage markup makes those pairs machine-readable at the structured data level, which means your answers become candidates for AI-generated summaries even when they produce no visible rich result in traditional search.
The correct application of FAQPage schema matters as much as the decision to use it. Google requires your schema to describe what the page is really about. If your “Personal Injury Lawyer” practice area page has a small FAQ section at the bottom and you’ve wrapped it in FAQPage schema, that’s now ineligible. Implement FAQPage schema on dedicated FAQ pages where questions and answers are the primary content, not a sidebar feature.
Video schema opens a separate visibility surface that most law firm sites ignore entirely. When you host videos explaining legal processes, case types, or client rights, VideoObject schema tells search engines the title, upload date, description, thumbnail URL, and duration. Generative AI search relies on detailed content understanding to provide nuanced answers. Schema helps AI engines parse your site’s information accurately, potentially boosting visibility in voice searches, chatbots, and AI-powered ranking algorithms.
Firms investing in Answer Engine Optimization need both FAQPage and VideoObject schema working together. A prospective client asking an AI assistant “how does a personal injury settlement work?” may receive an answer pulled from your FAQ schema, accompanied by a video result pulled from your VideoObject markup. That combination of structured answer formats creates multiple entry points from a single query.
Validating Attorney Schema and Avoiding Common Implementation Errors
Deploying schema without validating it produces no benefit and can actively harm your visibility. Errors in structured data are not just inert. They can cause Google to ignore the markup entirely or, in cases of misleading schema, trigger manual action warnings. Google’s Rich Results Test checks whether your markup is eligible to generate rich results and flags errors and warnings in the code. Run that test on every page type after any schema deployment or site migration.
JSON-LD is the only format worth using. JSON-LD is the only format Google recommends. Avoid Microdata and RDFa — they are error-prone and harder to maintain. JSON-LD keeps schema markup cleanly separated from your HTML structure. For WordPress sites, this means injecting schema through a Custom HTML block or a plugin that outputs clean JSON-LD, not inline Microdata embedded in your page templates.
WordPress plugins handle the basics, but their limits are real. SEO plugins like Yoast and Rank Math include built-in schema generators. These handle Organization, LocalBusiness, BreadcrumbList, and Article schema reasonably well with minimal configuration. The advantage is speed and low technical barrier. The limitation is that these plugins generate generic markup. They will not produce the LegalService-specific schema that differentiates a law firm from a generic business.
The practical approach for most firms is a hybrid. Use a plugin for site-wide Organization, BreadcrumbList, and Article schema, then deploy custom JSON-LD for LegalService on practice area pages, Person schema on attorney bio pages, and location-specific markup for each office. This hybrid approach gets the baseline schema in place quickly while investing development time where legal-specific precision matters most.
NAP consistency across schema and other data sources is a common failure point. NAP mismatch across schema, GBP, Avvo, and footer is a silent killer. One inconsistency drops AI Mode confidence. Your firm name, address, and phone number must match exactly across your LegalService schema, your Google Business Profile, and every directory citation. Even a suite number formatted differently can create a mismatch that undermines local search confidence.
Schema also connects directly to how AI systems understand your firm’s authority. For law firms and solo attorneys serious about consistent visibility across search and AI results, schema markup is non-negotiable. By embedding structured data types such as Organization, LegalService, Person, Article, FAQPage, QAPage, VideoObject, and Review into your site, you help search engines and AI systems better understand your practice areas, attorney credentials, client testimonials, and contact details, making your content more likely to be displayed in featured snippets, knowledge panels, and AI-generated summaries.
Effective law firm SEO treats schema as infrastructure, not a one-time task. Search engines update their structured data requirements, schema.org deprecates types, and Google adjusts rich result eligibility. A law firm should avoid deprecated types and keep markup validated and current because schema support and eligibility can change over time. Firms that treat schema as a set-and-forget item end up running deprecated markup for years, invisible to the AI systems their competitors are already feeding. Contact Custom Legal Marketing to audit your current schema implementation and build the structured data stack your firm needs for 2026 and beyond.
FAQs About Attorney Schema Markup Best Practices
Is the Attorney schema type still valid for law firm websites?
The Attorney schema type has been formally deprecated by Schema.org, and Google no longer honors it for rich results. It will still pass validation tools without throwing a hard error, but it produces no enhancements and no AI citation lift. The correct replacement is Person schema for individual attorneys, connected to your firm’s LegalService entity through the worksFor property.
What is the difference between LegalService schema and LocalBusiness schema for attorneys?
LegalService is a subtype of LocalBusiness on Schema.org, built specifically for firms that provide legal services, advice, and representation. LocalBusiness provides address, phone, and hours. LegalService adds practice area specificity, service descriptions, and geographic service areas on top of those properties. Law firms should implement both, with LegalService as the primary @type and LocalBusiness properties nested within it. Using generic LocalBusiness alone sends the same signal as a restaurant or retail store.
Does FAQPage schema still produce rich results for law firm websites?
Google restricted FAQ rich results in August 2023, limiting them primarily to government and health authority websites. Most law firm sites no longer qualify for the visible FAQ accordion in search results. However, FAQPage schema retains real value for AI citation extraction. Systems like ChatGPT, Perplexity, and Google AI Overviews parse structured question-and-answer pairs when generating responses to legal queries. Implement FAQPage schema on dedicated FAQ pages where questions are the primary content, not buried at the bottom of a practice area page.
How does Person schema support E-E-A-T for attorney websites?
Person schema on attorney bio pages creates a structured data record that confirms each lawyer’s credentials, bar admissions, educational background, job title, and employer at the machine-readable level. Google’s E-E-A-T guidelines place significant weight on demonstrated expertise and real-world credentials, particularly on YMYL pages like legal content. When your bio page tells Google through structured data that a named attorney holds a specific job title, works for a specific firm, and holds verifiable credentials, you remove ambiguity that Google would otherwise have to resolve through inference.
How long does it take for schema markup to affect search visibility for a law firm?
Timeline varies by schema type and the firm’s existing authority. BreadcrumbList rich results typically appear in search within two to four weeks of correct implementation. Local Pack improvements tied to LegalService schema generally take four to eight weeks. AI Mode citations and AI Overview appearances take four to eight weeks for established firms with strong existing signals, and three to six months for newer firms building their entity record from scratch. Validation errors or NAP mismatches reset those timelines, so running Google’s Rich Results Test before and after every deployment is essential.
More Resources About Personal Injury SEO
What Our Clients Are Saying
