Schema markup is how a firm tells a search engine, in a format built for machines rather than readers, what a page is about. The payoff has moved. It no longer buys a decorated search result, because Google has removed the FAQ rich result it used to produce. What it buys now is an unambiguous description of your firm that Google and the AI engines can read without guessing, which matters more in personal injury than almost anywhere, because being described accurately is what gets a firm named.
What schema markup actually does for a law firm
It removes ambiguity. A search engine reading your site without structured data has to infer that the name in your header is a law firm rather than a person, that the attorney biography page is about a lawyer rather than a client, and that the page headed "Car accidents" is a service rather than an article about traffic safety. It usually gets there. In a competitive market, usually is not good enough.
Structured data replaces that inference with a statement. Google's introduction to structured data describes it as a standardized format for providing information about a page and classifying its content. The vocabulary is maintained at schema.org, which is where you check whether a property exists before you use it.
For an AI engine the effect is larger. An assistant deciding whether to name your firm has to be confident it knows which firm you are, a harder problem than it sounds when three firms in the same county share two surnames. Consistent structured data, matching consistent information elsewhere on the open web, is much of how that confidence gets built. This is the mechanical half of personal injury lawyer SEO, and usually the half that has never been done properly.
Which schema types a personal injury firm needs
Fewer than most agencies implement. A firm that gets five types right will outperform one that has scattered fifteen across its pages, because every type you add is another thing that can contradict something else.
The firm itself. One LegalService or Organization node, declared once with a stable identifier and referenced everywhere else rather than repeated. Firm name, website, phone number, office location, and the profiles that belong to you. Google's local business structured data guidance covers what it expects to match your Google Business Profile.
The attorneys. A Person node for each attorney, on their own biography page, tied back to the firm. Bar admissions, law school, practice areas, authored content. In medical malpractice work this is not decoration: both Google and the AI engines are cautious about medical questions, and an identifiable, credentialed author is one of the few signals that reduces that caution.
The case types. A Service node on each case-type page, naming the service and where you offer it, with the firm as its provider. This is what connects "motor vehicle collisions" to your firm rather than leaving a page that happens to mention both.
The questions. FAQPage markup on the pages that genuinely answer questions, using the exact wording that appears on the page. More on what this is now worth below.
The path. BreadcrumbList on every page below the home page. Trivial to implement, still rendered in Google's results, and it tells an engine how your site is organized, which matters on a site with fifty practice-area pages.
Does FAQ schema still earn a rich result in Google?
No. Google has removed the FAQ rich result from Search, having first narrowed it to well-known government and health sites and then retired the feature and its documentation. Any agency still selling FAQ schema as a way to take up more room on the results page is selling something that no longer exists.
Keep implementing it anyway. The reason has changed rather than disappeared. FAQPage markup hands an engine a clean question and answer pair instead of asking it to work out where an answer begins and ends inside a page of prose. When the engine building the answer is an assistant rather than a results page, that structure is what makes a passage quotable. The visible page earns the position. The markup makes it easy to lift.
One condition: the marked-up answer has to be the answer a visitor can read on the page, word for word. Markup describing content that is not visible is a policy violation as well as a bad idea.
The mistakes that make schema worthless
Marking up content that is not on the page. The single most common fault, and the one with an actual downside rather than a neutral one.
Declaring the firm three times. A plugin adds an Organization node, the theme adds a LocalBusiness node, and someone pasted a LegalService node into the header. An engine now has three entities sharing a phone number and no way to know which is authoritative. Declare the firm once and reference it.
Leaving the template placeholders in. Generated markup shipped with the example values still in it is more common than it should be, and nothing on the visible page reveals it.
Marking up reviews you control. Self-serving review markup on your own site is against Google's guidelines, and for a law firm it carries a second problem: the reviews a prospect actually weighs are the ones on your Google Business Profile, which you cannot edit.
Contradicting the visible page. Structured data placing the firm in one city while the footer says another, or listing practice areas the site does not cover. Every contradiction is a reason to trust the whole file less.
Not sure what your site is currently telling search engines?
The free audit includes a structured data and entity check alongside the search and AI visibility review.
Get My Free AI Visibility AuditHow to check the markup is doing anything
Run it through the validators first. The Schema Markup Validator checks the markup against the vocabulary, and Google's Rich Results Test checks whether Google can parse it and which remaining features the page qualifies for. Search Console then reports the same errors sitewide over time, which is where you notice a template change that broke every page at once.
Those checks tell you the file is valid, not that it is working. For that, ask the engines: search your firm name and read the knowledge panel, then ask ChatGPT, Perplexity, and Google's AI features who handles a case type in your city and read how you are characterized. Wrong practice areas, a wrong location, or a description merged with another firm are entity problems, and entity problems are usually structured data problems first.
Where schema fits in the wider program
Structured data is foundational rather than decisive. It will not lift a thin case-type page into position one, and no markup compensates for a site nobody links to. What it does is make sure the work that does move rankings is attributed to the right firm, described the way you would describe yourself, and available in a form an AI engine can quote. On most law firm sites it has never been audited.
We implement it in every Google SEO engagement and check it again during AI search visibility work, because the same file serves both. Once it is in place, the next question is whether the engines are naming you, which is a measurement problem rather than a markup one. That is covered in AI citation reporting for law firms.
Frequently asked questions
It is structured data added to a law firm's pages in a format search engines read directly, declaring what the firm is, who its attorneys are, which services it offers, and what questions each page answers. It does not change what a visitor sees, only how confidently an engine can describe you.
No. Google narrowed FAQ rich results to well-known government and health sites and has since removed the feature from Search along with its documentation. FAQPage markup is still worth implementing, because it gives AI engines a clean question and answer pair to quote, but it no longer changes how your listing looks in Google.
Five: one LegalService or Organization node for the firm, a Person node for each attorney, a Service node on each case-type page, FAQPage on pages that answer questions, and BreadcrumbList sitewide. Getting those five right and consistent beats scattering a dozen types across the site.
Yes, in two ways. Markup describing content that is not visible on the page violates Google's structured data guidelines and can cost you eligibility for the features you do qualify for. And markup that contradicts the visible page, on location, practice areas, or firm name, gives engines a reason to trust the rest less.
Validate the syntax with the Schema Markup Validator and Google's Rich Results Test, then watch Search Console for errors appearing across templates. The real test is behavioral: ask the AI engines who handles your case types in your city and check whether the description that comes back is actually yours.