What Is FAQPage Schema and Why Should Law Firms Care?

FAQPage schema is a type of structured data markup — code you add to your web pages — that explicitly tells Google and other AI systems that a section of your content is formatted as questions and answers. When Google recognizes this markup, it can display your FAQ content directly in search results as expandable accordion items below your blue link, significantly increasing how much screen real estate your result takes up.

For law firms, this is genuinely useful for two separate reasons. First, the visual impact in traditional search results: a law firm page with FAQ rich results can display three or four question-answer pairs directly in the search result, expanding your listing from a single two-line snippet to something that takes up a third of the screen. That increased visibility improves click-through rates on competitive queries. Second, and increasingly more important: FAQPage schema helps AI systems like Google's AI Overviews, ChatGPT, and Perplexity parse your content accurately. When an AI synthesizes an answer to a legal question, it draws heavily on content that is pre-structured as Q&A pairs. Your schema markup is essentially handing the AI a pre-formatted answer card.

Most law firm websites don't have any FAQ schema at all. Some have FAQ sections written as prose or accordion widgets, but without the underlying markup that tells search engines what those questions and answers actually are. That gap is an easy competitive advantage to capture. It doesn't require rebuilding your website — it requires adding a JSON-LD script block to your existing pages.

For a broader look at how structured data fits into your overall search strategy, see our complete schema markup guide for lawyers.

What FAQ Schema Actually Looks Like

FAQ schema is implemented as a JSON-LD script block in the <head> of your HTML page. It doesn't change anything visible on your page — it's metadata that search engines and AI systems read in the background. Here's what a minimal example looks like for a personal injury practice area page:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "How long does a personal injury claim take in Ontario?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Most personal injury claims in Ontario settle within 1–3 years of the accident. Simple cases with clear liability and modest injuries can resolve in 6–12 months. Complex cases involving serious injuries, disputed liability, or multiple defendants often take 2–4 years, especially if they proceed to trial. Your lawyer will give you a realistic timeline after reviewing the specifics of your case."
      }
    },
    {
      "@type": "Question",
      "name": "Do I have to pay upfront for a personal injury lawyer?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "No. Most personal injury lawyers in Ontario work on a contingency fee basis, meaning you pay nothing unless your case settles or wins at trial. The lawyer's fee is typically a percentage of the settlement or award, agreed upon before representation begins."
      }
    }
  ]
}
</script>

Notice a few things about this markup. The @type is set to FAQPage at the top level. Each question is a Question object with a name property (the question text) and an acceptedAnswer containing the answer text. The answers are plain text — no HTML tags inside the answer text field. The questions are phrased the way a real client would ask them, not as keyword-stuffed technical phrases.

The question text in your schema should match the visible question on your page. Google will penalize FAQ schema where the markup doesn't reflect what's actually visible to users. Never add FAQ schema to questions that aren't displayed on the page.

Which Pages Should Get FAQ Schema First

Not every page on your law firm website needs FAQ schema, and not every page would benefit equally from it. The most impactful pages to start with are practice area pages, location pages, and high-traffic blog articles — in that order.

Practice area pages are the highest priority. These are pages like "Personal Injury" or "Family Law" that describe a specific service your firm offers. Clients researching whether to call a lawyer almost always have questions — about cost, timelines, what to expect, what their options are. Adding 4–6 FAQ items to each practice area page and marking them up with FAQPage schema turns these pages into candidate sources for Google AI Overviews and rich results simultaneously.

Location pages should come second if you serve multiple cities or areas. A page targeting "Family Law Barrie" will often rank for queries like "how does divorce work in Barrie" — and FAQ schema makes that content more eligible for AI citation. Include location-specific questions where you can, like questions about local court processes, Law Society of Ontario requirements relevant to your area, or jurisdiction-specific timelines.

Blog articles and resource guides are where FAQ schema delivers most of its AI citation value. If you've written a 2,000-word guide on "What to Do After a Car Accident in Ontario," adding 5–8 FAQ pairs at the end — marked up in schema — significantly increases your odds of being cited in an AI Overview when someone asks that question. The AI prefers structured, parseable content, and FAQ schema is exactly that.

Writing Questions That Actually Get Featured

The quality of your FAQ content matters as much as the schema markup itself. Google and AI systems evaluate whether your FAQ pairs are genuinely useful and whether the answers are accurate and complete. Here's what makes a FAQ question work well in schema:

Phrase questions the way clients actually ask them. "How long will my case take?" not "What is the timeline for personal injury litigation in Ontario?" Real clients don't use legal language when they're searching. If you're not sure what questions people ask, look at your own intake process — the questions clients ask on the first phone call are almost always the right ones for FAQ schema.

Give complete, self-contained answers. Each answer in your FAQ schema should make sense on its own without the surrounding context of your page. AI systems often extract individual Q&A pairs in isolation. An answer that begins "As mentioned above..." or "See the section on X..." is useless as a cited source. Write every answer as if it's the only thing the reader will see.

Include specific, local detail where relevant. FAQ answers that mention Ontario, specific statutes (like the Insurance Act), or local procedural details (like filing in Superior Court of Justice vs. Small Claims Court) are more valuable for local AI search than generic answers. The specificity signals expertise and local authority, which is exactly what AI systems are looking for when choosing sources to cite.

Keep answers between 40 and 300 words. Too short and there's not enough substance for AI to work with. Too long and you're writing an essay, not an FAQ answer. Google's own documentation suggests that FAQ answers should be concise and factual. Aim for the sweet spot: thorough enough to be genuinely useful, tight enough to be readable in isolation.

Common Mistakes Law Firms Make With FAQ Schema

FAQ schema is straightforward to implement, but there are a handful of mistakes that consistently prevent law firms from getting the results they're after. Here are the ones I see most often.

Mismatched markup and visible content. This is the most common error. A law firm adds FAQ schema with five questions, but only three of those questions are actually visible on the page — the others were cut during editing. Google explicitly requires that FAQ schema only mark up content that users can see. If the schema doesn't match the visible content, Google will ignore it or flag it as a spam signal in Google Search Console.

Using HTML tags inside the answer text. The text field inside acceptedAnswer should be plain text. No bold tags, no links, no bullet point markup. Some tools will automatically strip HTML from this field, but many won't. Invalid JSON from embedded HTML is one of the most common reasons FAQ schema fails validation.

Putting the same FAQ schema on every page. Google expects FAQ schema to reflect the specific content of the page it's on. If you have identical FAQ markup on your homepage, your personal injury page, and your car accident page, Google will likely ignore it — and may flag it as duplicate structured data. Each page's FAQ schema should be unique and relevant to that page's specific topic.

Not validating the markup. Always test your FAQ schema using Google's Rich Results Test tool (search.google.com/test/rich-results) before publishing. It will tell you immediately whether your JSON-LD is valid, whether it qualifies for rich results, and flag any issues. This takes two minutes and prevents wasted effort on broken markup.

For full implementation details and additional schema types that complement FAQPage, see our article on LocalBusiness schema for law firms and our broader guide to entity SEO for law firms.

Validating and Monitoring Your FAQ Schema

Implementation is only half the work. You also need to validate that your markup is correct and monitor it over time. There are two free tools that handle this well.

Google's Rich Results Test lets you paste a URL or raw HTML and immediately see whether your schema is valid and eligible for rich results. It shows you exactly how Google parsed your markup, flags any errors, and tells you which rich result types your page qualifies for. Run every page through this test after adding FAQ schema before considering the implementation done.

Google Search Console has an Enhancements section that tracks rich result status across your site over time. After implementing FAQ schema on multiple pages, check Search Console weekly for the first month. It will tell you how many pages have valid FAQ markup, how many are eligible for rich results, and flag any new errors. Impressions from FAQ rich results will also start appearing in your performance data — look for clicks with FAQ-specific formatting in the search results preview.

Beyond these tools, manually test your FAQ schema for AI citation by asking ChatGPT, Gemini, and Perplexity the exact questions you've marked up. If your markup is working and your content is strong enough to be cited, you should start seeing your firm's content referenced in AI-generated answers within a few weeks of Google re-crawling your updated pages. See our guide on AI SEO reporting for law firms for a full framework on tracking this kind of visibility.

Frequently Asked Questions

Yes — FAQPage schema still triggers rich results in Google Search for many queries, particularly on mobile. Google has pulled back on showing FAQ rich results for some high-authority sites, but for most law firms, properly implemented FAQ schema still expands your search result with accordion Q&As and increases your effective click-through rate. More importantly, FAQ schema helps AI systems parse your content accurately for AI Overviews and citation, which is increasingly where the real value lies.

Aim for 4 to 8 questions per page. Too few and you're not giving Google enough Q&A pairs to work with. Too many and the markup starts to look spammy — Google has been known to ignore FAQ schema on pages that feel like keyword-stuffed FAQ dumps rather than genuinely helpful Q&A content. The key is that every question should be something a real prospective client would actually ask, and every answer should be thorough enough to be genuinely useful.

Yes, but it's more valuable on practice area pages and blog posts than on your homepage. The homepage is rarely the right place for detailed FAQ content — clients landing there want to understand what you do and how to contact you, not read a list of legal Q&As. Add FAQ schema where the FAQ content genuinely fits: at the bottom of practice area pages, on location pages, and on content hub articles where you've written substantial Q&A sections.

It significantly improves your chances, yes. AI Overviews draw heavily on structured, question-formatted content because it's pre-parsed and machine-readable. FAQ schema explicitly labels each question-answer pair in a format that AI systems can directly extract. When Google's AI synthesizes an answer to a legal question, pages with FAQ schema that directly address that question have a meaningful advantage over pages with identical prose content that isn't structured. Think of FAQ schema as handing AI a pre-formatted answer card.

It depends on your website setup. On WordPress sites, plugins like Rank Math or Yoast SEO Premium let you add FAQ schema through a visual interface without touching code. On custom-built sites, you or your developer will need to manually add a JSON-LD script block to each page. For a static HTML site, it's a simple copy-paste into the head section. The JSON-LD format itself is straightforward — the sample code in this article is all you need to start.