Every page type — FAQ, glossary, case study, comparison — has a schema pattern and on-page structure that AI engines recognize and cite. Master the templates that win more AI visibility.
The highest-leverage play in AI search is page-type structure: a FAQ page, glossary page, case study, or comparison page that follows the semantic schema law firms ignore. Learn the eight page types every firm should ship, the JSON-LD patterns that unlock AI citations, and how to audit your existing content for citability.
Use the interactive map below to explore each one — click any node to read what it covers and jump to its page.
Nine essential page-type playbooks and technical guides
Architectural guides and technical implementation for every page type
Learn why FAQ pages are cited more often by ChatGPT and Perplexity than generic blog posts, and how to structure them for maximum AI visibility.
Includes FAQPage schema, question-shaped headings, answer-first format, and the hub-spoke model for organizing 20+ FAQs.
Glossaries establish your firm's domain-specific language and improve entity disambiguation for AI models.
Use DefinedTerm schema, organize as a hub index, and link every term back to related practice areas.
Case studies are the highest-converting page type and the most cited for E-E-A-T signals.
Structure as Article + Review schema, lead with the result, include the challenge and solution, and add the mandatory outcomes disclaimer.
Comparison pages ("Personal Injury vs. Wrongful Death," "Mediation vs. Arbitration") rank in AI overviews for research queries.
Use structured tables, side-by-side analysis, and cite both sides fairly to win credibility with AI models.
About pages and attorney bios are E-E-A-T signals for AI models: credentials, experience, publications, and social proof.
Mark up with Person schema (hasOccupation, knowsAbout, hasCredential, alumniOf) and link to verified external profiles (LinkedIn, state bar, Wikipedia).
Directory and location index pages are your hub for all offices, neighborhoods, and service areas.
Use ItemList schema, render the full location list server-side (no JS), and link every item to its location spoke with consistent NAP.
Resources (downloadable guides, calculators, checklists, templates) are high-conversion, low-friction authority plays.
Host on your own domain, not Gumroad/Typeform, to keep link juice in-house; use ResourcePage schema and cite the tool in related FAQs and articles.
Content cannibalization kills AI citations: two pages answering the same question split authority and confuse AI models.
Learn how to cluster your site by intent, identify cannibalization with AI, pick a hub owner, 301-redirect thin pages, and consolidate internal links.
Vector embeddings of every page let you cluster content by semantic similarity, detect cannibalization automatically, and measure citability at scale.
Ingest your WordPress posts into Supabase, embed with OpenAI, and use cosine similarity to find redundant/thin pages.
The intents AI engines fan a search into — and where we make your firm the answer.
A hub is a topic index (e.g., /personal-injury-faqs) that links down to every related spoke. A spoke is a single-topic deep dive (e.g., /personal-injury-faqs/how-long-statute-of-limitations). Hub = navigation + authority; spoke = answer-first content. Every page should be one or the other.
Yes. FAQPage, HowTo, DefinedTerm, BlogPosting, Article, CaseStudy (as Article), and comparison pages all ship with schema. Schema must match visible content — if it isn't on the page, don't mark it up. One missing field doesn't break the type, but every field that exists should be in the schema.
Yes, strategically. A case study can include a how-to section (mark it as nested HowTo). A glossary can include FAQs. But one dominant type should drive the primary schema (@type). Never nest FAQ pages inside other page types — separate FAQ pages rank independently.
Monitor branded search queries in Google Search Console (GSC) for your name/brand mentions (AI overviews are tagged as AOAG). Cite-rate correlates with direct-answer blocks, question-shaped headings, fact density (numbers + dates + attribution), and off-site authority mentions. Run an <strong>AI citation checklist</strong> before shipping any new page.
Cannibalization kills citations. An unfocused FAQ page and a generic blog post about the same topic split authority. Solution: pick one owner (usually the hub FAQ page), delete or 301-redirect the other, and interlink ruthlessly. Audit by clustering your pages by intent, not by publication date.
Hybrid. A glossary hub (/personal-injury-glossary) is its own index. But individual terms also link from their parent practice-area hub (/personal-injury) so they're discoverable both ways. Double-link: term ↔ hub AND term ↔ practice area. Glossary spokes also link sideways to related terms.
Start with a free 23-point AI visibility report — see exactly where ChatGPT, Gemini, Claude and Perplexity cite your firm today, and what closes the gap. Delivered in 24 hours. No credit card.
