Google killed FAQ rich results on May 7, 2026. The expandable dropdowns are gone from the SERP, and Search Console reporting for FAQ markup gets retired in June. A lot of law firm marketers read those headlines and quietly dropped FAQ pages off the roadmap. That is the wrong call. FAQ pages on practice area pages are now the single highest-return AEO asset a law firm can ship, because the same FAQPage schema that no longer earns a blue dropdown still feeds ChatGPT, Perplexity, Claude, and Google’s AI Overviews the clean question-and-answer pairs they need to cite you by name.
Why FAQ pages got more valuable the day Google killed the rich result
The rich result was a SERP feature. AI citation is a different game. Pages with FAQPage schema are 3.2x more likely to appear in Google AI Overviews than pages without it, and that gap is widening as AI Overviews expand into legal queries. Google itself confirmed it will continue using FAQ structured data to understand pages even after killing the visual feature.
Here is what changed in practical terms. The blue FAQ dropdowns were a CTR bonus. Some firms loved them, others felt they cannibalized clicks. Either way, they were a fixed-pie SERP feature with a known ceiling. AI citation has no ceiling. AI-driven traffic to law firm websites grew 257% year-over-year by January 2026, and roughly three out of four law firm queries on ChatGPT and Perplexity now return three to five named firms as recommendations. Every single one of those slots is a referral that did not exist in 2024. Most managing partners are still budgeting like AI search is a side project. It is not.
The firms winning those citation slots share one structural pattern: clear question-and-answer formatting on practice area pages, with FAQPage schema wrapping the answers. That is it. The technical work is small. The compounding return is large.
What does an FAQ page actually do for AI citation?
Three things, and you need to understand the mechanism to build the page right.
First, it gives the AI engine a clean extraction target. When ChatGPT or Perplexity decides which firm to recommend for “best DUI lawyer in Charleston,” the model is not reading your homepage hero. It is looking for question-shaped headings on pages it has indexed, then pulling the first 40 to 60 words of the answer underneath. FAQ structure is the cleanest version of that pattern. Schema makes it explicit.
Second, it expands your eligible-query surface. A single DUI practice area page might rank for one or two head terms. Add eight FAQ questions to that page and you become eligible for dozens of long-tail queries: “do I lose my license after a first DUI in SC,” “can I refuse a breathalyzer in Charleston,” “how much does a DUI lawyer cost.” Each question is a separate citation opportunity.
Third, it creates the “answer capsule” pattern that 72.4% of AI-cited blog posts share. An answer capsule is a self-contained, citable chunk at the top of a section that fully answers the question without requiring context from elsewhere on the page. Bare paragraphs rarely look like answer capsules. Question heading plus direct answer almost always does.
Where should the FAQ live: separate FAQ page or inside the practice area page?
Inside the practice area page. Almost always.
A standalone /faq/ page concentrates citation opportunities to one URL, which means the engine has to decide whether to cite your generic FAQ hub or your topical practice area page. The topical page wins on relevance every time, so the FAQ hub mostly steals clicks from itself.
The exception is a billing-or-fees-style FAQ that genuinely cuts across practice areas. A “how does your fee structure work” FAQ belongs on a /fees/ or /pricing/ page because the answer is the same whether someone is asking about estate planning or personal injury. Everything else, including jurisdiction-specific questions, procedural questions, and outcome questions, belongs on the practice area page where the answer lives in context.
Build the page like this: practice area page opens with a 120-word direct definition of the service, then expands into outcomes, process, jurisdiction, and team. After the body content, add a section titled “Common questions about [service] in [city]” with 6 to 10 questions and answers. Wrap that block in FAQPage schema.
How long should each FAQ answer be?
40 to 60 words for the direct answer, then 150 to 300 words total if you want the answer to stand alone as an article-grade response. The 40-to-60-word opening is what ChatGPT and Perplexity actually pull. The expanded paragraph is what builds the trust signals that make the engine pick your firm over the firm next door.
Skip the one-sentence FAQ format. AI engines treat single-sentence answers as low-confidence sources and route citations elsewhere. They want enough text to feel authoritative and enough structure to extract cleanly. A 50-word direct answer followed by a 200-word expansion hits both bars.
A real example, before and after:
Bad (one-sentence FAQ): “Q: How much does a divorce cost in South Carolina? A: It depends on the complexity of the case.”
Good (answer-capsule FAQ): “Q: How much does a divorce cost in South Carolina? A: Uncontested divorces in South Carolina typically cost $1,500 to $3,000 in attorney fees, plus $150 in filing fees with the Family Court. Contested divorces with custody or asset disputes range from $7,500 to $25,000 depending on how many hearings are required…” (continuing for another 180 words on what drives the cost up).
The second version answers the query, sets jurisdictional context, gives specific numbers, and is a complete citation in itself. The first version is filler.
What technical implementation actually matters?
Three things, in order:
-
Use FAQPage schema, not just visual H2 questions. JSON-LD in the page head is fine. Inline microdata is fine. What matters is that Google, Bing, and the LLM crawlers (GPTBot, PerplexityBot, ClaudeBot, Google-Extended) can parse the question-answer pairs structurally.
-
Do not include hyperlinks in the answer body. More than 90% of AI-cited answer capsules contain no links inside the answer text. Hyperlinks at the start of the answer cause the engine to either swap your citation for the link target, or skip the chunk entirely. Save your internal links for after the answer.
-
Add a “Last Updated” date stamp on the page. Recency signals heavily influence which firm gets cited for jurisdictional questions. A practice area page last updated three years ago will lose to a competitor’s page updated last month, even if the underlying law has not changed.
You do not need a separate sitemap entry, a separate URL, or any AMP variant. The schema does the heavy lifting.
What about firms that already have FAQ pages but are not getting cited?
The diagnostic almost always falls into one of four buckets:
Bucket one: schema is missing or malformed. Run the page through any JSON-LD validator (the Rich Results Test still works for parsing even though the FAQ rich result itself is retired). If the validator does not see FAQPage with Question and Answer children, the AI engines do not either.
Bucket two: answers are too short. One-sentence answers do not get cited. Period. Audit every FAQ on the page and rewrite anything under 75 words.
Bucket three: the FAQ is on the wrong page. A “what is alimony” FAQ on a generic /faq/ hub gets beaten by a “what is alimony in South Carolina” FAQ on a /family-law/ practice area page. Move the question to where the answer lives in topical context.
Bucket four: the firm is invisible to the LLM crawlers. If your robots.txt blocks GPTBot, PerplexityBot, ClaudeBot, or Google-Extended, you are excluded from the index that drives AI citation. Check this first if nothing else explains the gap.
The fix for any of the four is the same: structured FAQ blocks on topical practice area pages, with proper schema, fully crawlable. The work compounds. A firm that ships FAQ blocks on all 12 practice area pages and refreshes them quarterly typically sees the first AI citations within 60 to 90 days.
How does this fit with the rest of an AEO program?
FAQ pages are one of three legs of a working AEO program for law firms. The other two are reviews on the platforms AI engines weight (Avvo, Martindale, Lawyers.com, Google) and press citations in legal trade publications (Above the Law, ABA Journal, Super Lawyers, Best Lawyers). FAQ pages give the engine an on-domain extraction target. Reviews give the engine a trust signal. Press gives the engine a citation graph showing other authoritative sources already vouch for the firm.
A firm that ships only FAQ pages is the firm that gets cited for narrow long-tail queries but rarely shows up for “best [practice area] in [city]” head terms. A firm that ships only reviews and press is the firm AI engines describe well but never quote directly. The compounding effect happens when all three are in motion.
Frequently asked questions
Will FAQ schema still help SEO after Google removed the rich result?
Yes. Google continues to use FAQPage schema to understand page content even though the visible dropdown is gone, and pages with the schema are 3.2x more likely to be surfaced in AI Overviews. The schema also feeds non-Google AI engines, which collectively now drive more than a quarter of legal-query traffic for firms tracking the channel.
Should law firms remove FAQ schema since Google killed the rich result?
No. Keep the schema. The rich result was the SERP visual; the schema is the structured data that AI engines parse to extract citations. Removing it would surrender your strongest on-page citation signal at the moment AI search is taking over legal query traffic.
How many FAQ questions should each practice area page have?
Six to ten. Fewer than six and you are not covering the buyer’s actual question set; more than ten and the page starts to dilute around the head topic. Pick the questions from your intake notes, “People Also Ask” boxes for your head term, and the questions you answer on every consult call.
How long does it take for AI engines to start citing FAQ content?
For an established law firm domain with healthy traffic, 30 to 90 days after publication. Newer domains take longer because LLM training and retrieval pipelines weight domain authority heavily. The fastest path to early citation is shipping FAQ pages on your three highest-traffic practice area pages first.
Can I write the FAQ answers with AI and still get cited?
Yes, but only if a practitioner edits them. AI engines increasingly down-weight content that reads as AI-generated boilerplate. The pattern that works is to draft with AI, then have a partner or senior associate add jurisdictional specifics, named case references, and the firm’s actual fee structure. The specificity is what triggers citation; the boilerplate is what suppresses it.
What to do this week
Pick your three highest-traffic practice area pages. Open the intake notes for each practice area and pull the 10 questions clients actually ask on the first call. Draft the answers in the 40-to-60-word direct answer, 150-to-300-word total format described above. Wrap the block in FAQPage schema and ship it. Set a 30-day reminder to recheck citations in ChatGPT and Perplexity for the head queries those pages target.
That is the entire intervention. It costs a few hours of associate time per page and delivers compounding citation share for the next 24 months.
If you want help running the full AEO playbook (FAQ pages, schema buildout, review platform optimization, and legal press placements) book a call from the contact page or run the numbers first on the ROI calculator.
Tagged