Quick answer: Schema markup is code that labels the facts on a law firm’s web pages so software can read them. ONE400 treats it as low-cost site hygiene, not a shortcut to AI citations. Google says its AI features don’t require structured data, Microsoft says schema helps Copilot understand content, and a 2026 Ahrefs test found that adding schema didn’t raise citations for pages AI already cited. Start with LegalService, Person, Article, FAQPage, and Organization markup written in JSON-LD.
What is schema markup, and why does it matter for law firm AI search?
Schema markup is code that labels the facts on a web page so software can read them without guessing. ONE400 writes it in the schema.org vocabulary, formatted as JSON-LD (JavaScript Object Notation for Linked Data), the format Google recommends.
A page can say in plain text that an attorney practices family law in Phoenix. Schema says the same thing as labeled data: a Person, a job title, an employer, a practice area, a location.
I think of it as a name tag for a page. People skim the room and read the tag. Machines read the tag first and the room second.
Does Google require schema markup for AI Overviews and AI Mode?
No. Google’s guide to optimizing for generative AI features on Search says generative AI search needs no structured data and no special schema.org markup.
Google still recommends using structured data as part of an overall SEO strategy, because it supports eligibility for rich results. Google’s structured data documentation also says markup should describe only information visible to the user.
My read: schema earns its place as cheap hygiene. Content quality decides whether an answer engine quotes you. Schema removes some ambiguity about who is speaking.
Does schema markup help ChatGPT, Claude, Gemini, and Perplexity?
Microsoft is the only major AI platform ONE400 can find that has said publicly that schema helps its AI. Search Engine Land reported that Fabrice Canel, principal product manager at Microsoft Bing, said at SMX Munich in March 2025 that schema markup helps Microsoft’s LLMs understand content for Copilot.
Beyond Microsoft, the public record is thin. Google calls schema optional for AI Overviews and AI Mode, and that guidance covers Google Search, not the standalone Gemini app. ONE400 hasn’t found published documentation from OpenAI, Anthropic, or Perplexity that says their systems read schema markup.
Independent testing points the same way. Ahrefs tracked 1,885 pages that added JSON-LD and compared them with matched pages that never did. Across Google AI Overviews, AI Mode, and ChatGPT, adding schema produced no meaningful increase in citations. Every page in the sample was already being cited, so the study can’t say whether schema helps a page AI hasn’t found yet.
Delivery matters. Vercel and MERJ analyzed AI crawler traffic in December 2024 and found that none of the major AI crawlers rendered JavaScript, including OpenAI’s OAI-SearchBot, ChatGPT-User, and GPTBot, and Anthropic’s ClaudeBot. Gemini was the exception among AI tools, because it runs on Googlebot’s infrastructure, which does render JavaScript.
Schema injected by a tag manager or other client-side script loads after the page does, so crawlers that skip JavaScript probably never see it. Put JSON-LD in the server-rendered HTML. That’s the precondition, not the payoff: a searchVIU test found that five AI systems, including ChatGPT, Claude, and Perplexity, pulled only visible text when fetching a page live and ignored the JSON-LD.
Which schema types should a law firm add first?
A law firm should add LegalService, Person, Article, FAQPage, and Organization markup first. Each one labels a fact that answer engines already try to extract from firm websites.
| Schema type | What it labels | Where it goes |
|---|---|---|
| LegalService | Firm name, address, phone, practice areas, service area | Homepage and each location page |
| Person | An attorney or author: name, job title, employer, profile links | Bio pages, and as the author inside Article |
| Article | A blog post: headline, author, dates, publisher | Every blog post |
| FAQPage | Question and answer pairs that appear on the page | Pages with a visible FAQ section |
| Organization | Brand name, URL, logo, social profiles through sameAs | Sitewide |
Use LegalService for the firm. Schema.org lists the older Attorney type as deprecated and calls LegalService more inclusive and less ambiguous. Attorney is a subtype of LegalService, so switching existing Attorney markup over loses nothing.
Here is a bare-bones LegalService template. The values are placeholders for a fictional firm, so swap in your own.
{
“@context”: “https://schema.org”,
“@type”: “LegalService”,
“name”: “Example Family Law, PLLC”,
“url”: “https://www.example.com”,
“telephone”: “+1-555-555-0100”,
“address”: {
“@type”: “PostalAddress”,
“streetAddress”: “100 Main Street”,
“addressLocality”: “Phoenix”,
“addressRegion”: “AZ”,
“postalCode”: “85001”
},
“areaServed”: “Phoenix, AZ”
}
Is FAQ schema still worth adding after Google dropped FAQ rich results?
Yes, with modest expectations. Google stopped showing FAQ rich results on May 7, 2026, and removed the feature’s documentation on June 15, 2026, according to Google Search Central’s documentation changelog. FAQPage remains a valid schema.org type, and Google retired the rich result, not the markup.
ONE400 writes FAQPage markup into every post draft for two reasons. Writing a real question-and-answer section forces a clean layout that answer engines can lift from. And Microsoft says schema helps its models read content.
The FAQ markup must match the questions and answers visible on the page. ONE400’s post on how to get your law firm cited by ChatGPT and AI search covers where FAQ content fits in the bigger picture.
How do you add schema markup to a law firm website?
Audit what your site already outputs, write JSON-LD for each page type, match it to visible content, serve it in the HTML source, and validate it. The work takes an afternoon for a small site.
- Audit existing markup. View the page source and search for application/ld+json. SEO plugins and themes often add schema you never reviewed.
- Choose types per page. Use the table above. A homepage gets LegalService and Organization. A blog post gets Article, Person, and FAQPage.
- Write JSON-LD. Google recommends JSON-LD over other formats when your setup allows it.
- Match visible content. Google says not to add structured data about information users can’t see, even if it’s accurate.
- Serve it in the HTML source. Skip client-side injection, since many AI crawlers don’t run JavaScript.
- Validate and recheck. Test each page type with the Schema.org validator, and use Google’s Rich Results Test for types that still earn rich results. Retest after theme updates, plugin updates, and redesigns. Update dateModified when a page changes in substance.
Firms that want a technical audit can look at ONE400’s law firm SEO services, which start with discovery, auditing, and site architecture.
What schema mistakes do law firm websites make?
The most common law firm schema mistake is assuming someone else already handled it. Most firm owners I talk to have never heard the word schema. They figure a plugin takes care of it, or it was never set up at all, and they come to ONE400 because their marketing feels stuck.
My fastest diagnosis is a Google search for the firm’s own name. I point at what comes back: the description under the firm’s link, the business panel, the phone number, the address. That listing starts to tell a story about the site’s overall health, schema included.
Owners are often surprised to see wrong or outdated information about their own firm in that listing.
Schema is one of several places that information can come from, alongside the page copy, the Google Business Profile, and directory listings. Google’s guidance sets the rule for the schema piece: markup describes what the page shows. A phone number in schema that differs from the phone number on the page is a conflict, and conflicts make it harder for any system to know which version is right.
Two other mistakes show up often. The first is duplicate markup, where a theme and an SEO plugin each output their own Organization or LegalService block with different details. The second is marking up the firm’s own testimonials as reviews. Google doesn’t show review rich results for self-serving reviews of a business on its own site, and state bar advertising rules on testimonials apply either way.
Is schema markup enough to get a law firm cited by AI?
No. Schema markup is one part of answer engine optimization (AEO), not the part that earns citations on its own. In ONE400’s experience, schema works best alongside site health, content strategy, and mentions of the firm on outside sites.
ONE400 starts with site health. Site health work usually means fixing 404 errors, cleaning up 301 redirects, and getting the sitemap right.
Next comes a content strategy. The strategy decides which schema goes on which pages and where the firm should earn mentions and listings on outside sites.
The firms that see results treat schema as one part of that build, not the build itself.
Frequently asked questions
Does my law firm website need schema markup to show up in ChatGPT?
No. OpenAI hasn’t published documentation saying ChatGPT reads schema markup, and a 2026 Ahrefs test found that adding schema didn’t increase ChatGPT citations for pages already being cited. Schema still costs little to add, and Microsoft has said it helps Copilot. Strong, specific content does the heavy lifting.
What is the best schema type for a law firm website?
LegalService is the best type for the firm itself. Schema.org deprecated the Attorney type in favor of LegalService. Pair it with Person markup for each attorney and Organization markup for the brand.
Should a law firm use JSON-LD or microdata?
JSON-LD. Google recommends JSON-LD when your site setup allows it, because it’s easier to implement and maintain at scale. It also sits in one block of code instead of being woven through the page HTML.
Can I add schema markup myself or do I need a developer?
A WordPress site can usually take JSON-LD through an SEO plugin or a header snippet. Have a developer confirm the markup appears in the server-rendered HTML source, since many AI crawlers don’t execute JavaScript. A developer also helps when plugins output conflicting markup.
How do I check whether my schema markup works?
Paste the page URL or code into the Schema.org validator at validator.schema.org. It flags syntax errors and shows how each type is parsed. Then compare the output to the visible page and confirm every labeled fact appears on it.
Talk to ONE400
ONE400 can audit your firm’s current markup and tell you what to fix first. Contact ONE400 to start.
