Schema markup for law firms is code added to your webpage that explicitly tells search engines and AI tools what’s actually on it: this is a law firm, this is an attorney, this is a review, this is a question and its answer. It doesn’t change what a visitor sees. It changes whether a machine reading that page can confidently identify the firm, verify the person behind the content, and trust it enough to cite it. Done right, it turns a firm and its attorneys into verified entities. Done wrong, or skipped entirely, it leaves even excellent legal content ambiguous to exactly the systems now deciding who gets mentioned in an AI-generated answer.

What Schema Markup Actually Is

Schema markup uses a shared vocabulary, maintained by Schema.org, that gives search engines and AI systems a standardized way to label the same kinds of information across every website. It’s typically written in a format called JSON-LD, a small block of structured code placed in a page’s header, invisible to a human visitor but fully readable by a machine.

The core idea is entity recognition. Search engines and AI tools no longer just read the words on a page, they try to identify specific entities, meaning people, organizations, places, and concepts, and understand how those entities relate to each other. Schema markup is how a website hands that information over directly, instead of hoping the machine correctly infers it from unstructured text.

The Schema Markup Stack a Law Firm Actually Needs

Most law firm websites fall into one of three categories: no schema at all, generic Organization schema copied from a WordPress plugin, or an outdated schema type that no longer does anything. None of these positions a firm well for AI citation. A properly built schema markup for law firms generally includes:

• LegalService, identifying the firm itself, its practice areas, service locations, and contact information
• Person, one entity for each attorney, connecting their individual credentials and identity to the firm
• FAQPage, marking up question-and-answer content in a format built for direct extraction
• Review or AggregateRating, structuring genuine review data so it’s machine-readable rather than just visible text

Each of these plays a different role, and they work best deployed together rather than in isolation.

Why “Attorney” Schema Markup Is Already Obsolete For Law Firms

Here’s a detail a lot of firms and even some agencies have missed. Schema.org formally deprecated the Attorney type, replacing it with LegalService as the correct, more inclusive classification for a business that provides legal representation and advice. Google no longer honors the Attorney type for rich results at all. It still technically validates without throwing an error, which is exactly why so many sites are still using it without realizing it does nothing anymore.

If a firm’s site was built a few years ago and hasn’t had its schema audited since, there’s a real chance it’s running on a type that quietly stopped providing any benefit. The fix is straightforward: replace Attorney with LegalService for the firm entity, and connect individual attorneys to it using Person schema instead.

Person Schema: Building Individual Attorneys as Citable Authorities

This is where schema markup for law firms does some of its most valuable and most overlooked work. E-E-A-T, meaning Experience, Expertise, Authoritativeness, and Trustworthiness, is central to how both Google and AI systems evaluate content. But experience and expertise have to be demonstrable, not just claimed in a sentence of prose. Person schema is the machine-readable evidence of exactly that.

A properly built Person entity for an attorney typically includes:

• Full name and professional job title
• Educational background, using the alumniOf property
• Bar admission and relevant professional credentials
• A sameAs array linking out to verifiable external profiles, such as a State Bar Association listing, an Avvo profile, or LinkedIn
• A worksFor property connecting the attorney directly to the firm’s LegalService entity, establishing the relationship between the person and the organization

The sameAs links matter more than they might seem to. They give AI systems a way to cross-reference and verify a real, credentialed person across multiple independent sources, rather than trusting a name that only appears on the firm’s own site. This is effectively a structured, verifiable resume that a machine can check in milliseconds, turning a blog post byline from a static piece of text into a connection to an actual, corroborated professional entity.

The Most Common Technical Failure: The WordPress “Admin” Problem

Even firms with named attorney bylines on their blog content frequently lose this benefit entirely due to a technical gap most people never think to check. Many SEO plugins auto-generate basic Article schema, but default the author field to the site’s WordPress user account rather than the actual attorney who wrote or is credited with the piece. The visible byline on the page might correctly say “By Jane Smith, Esq.,” while the underlying schema quietly attributes the content to “Admin” or “Marketing Staff.”

This is worth checking directly. Viewing a page’s structured data output will show whether the author field actually contains a proper Person entity matching the credentialed attorney, or whether it’s defaulting to a generic account. It’s an easy gap to miss and a common one, since it requires looking at the code, not just the page as it visually appears.

Why Consistency Matters More Than Any Single Schema Type

None of these schema types work as well in isolation as they do connected together. Every entity, whether it’s the firm, an attorney, or a piece of content, should use a consistent, stable identifier, called an @id, referenced the same way across every page. This is what allows an AI system to recognize that the Person entity on a blog post, the Person entity on the attorney’s bio page, and the worksFor reference on the firm’s LegalService entity are all describing the same connected relationship, rather than three disconnected pieces of information.

One 2026 multi-engine analysis of AI citation behavior found that pages using three or more connected schema types earned roughly 13% more citations from Perplexity than pages using a single schema type alone. The advantage comes specifically from the connected entity relationships, not from any one schema block working alone.

What to Expect After Implementation

Schema markup doesn’t produce instant results, and the timeline varies by type. BreadcrumbList and similar structural enhancements can show up in search within two to four weeks. Local Pack improvements tied to properly implemented LegalService schema tend to take four to eight weeks. AI Mode citations and AI Overview appearances typically take four to eight weeks for firms with strong existing authority, and three to six months for newer firms still building their entity record from scratch.

Frequently Asked Questions

Does adding schema markup improve content that’s already weak?
No. Schema markup helps machines accurately read and categorize content that already exists, it doesn’t improve the underlying quality of thin or generic writing. Strong content paired with proper schema performs far better than either element alone.

Is Attorney schema still worth using if a site already has it?
No. Schema.org deprecated the Attorney type and Google no longer honors it for rich results. It still validates without an error, but it provides no citation or ranking benefit, and it should be replaced with LegalService for the firm and Person schema for individual attorneys.

Can a law firm implement this schema stack itself, or does it require a developer?
Basic implementation is possible with the right plugin or template support, but verifying the output, especially checking whether author fields correctly reference real Person entities rather than a generic account, requires reviewing the actual structured data code, not just the visible page.