A practice-area content architecture built on the questions clients actually ask, structured for featured snippets and AI answers. Organic became the firm intake engine.

Client identity withheld. Figures compare month twelve to the pre-engagement baseline month, both outside seasonal peaks.

The situation

A regional law firm had a respectable site, a decade of practice, and a blog of announcements nobody searched for. Competitors with thinner credentials outranked them on every question a potential client types at midnight. Meanwhile the firm’s intake team answered those same questions by phone all day: the expertise existed, unpublished.

What we found

The gap analysis mapped the client-question universe for their practice areas: hundreds of real queries, from panicked basics to fee and process questions, clustered into topics. The firm’s coverage touched a fraction, in dense pages built for peer review rather than worried humans. Structurally, there was no architecture: practice pages, scattered posts and no interlinking that told machines this firm owned these topics. Attorney bios carried no schema, no bylines, no entity trail, so a decade of expertise was machine-invisible.

The strategy

Build topical authority the way engines measure it: pillar pages per practice area, clusters answering every significant client question beneath them, written in plain language with the direct answer first and the legal nuance after. Structure everything for extraction, because these are exactly the queries where snippets and AI Overviews answer first. And make the attorneys legible as entities, so the expertise carried weight.

The work

Phase 1: the architecture (weeks 1-4)

Question research from search data, intake-call notes and competitor gaps became the topic map. Each practice area got a pillar brief and a prioritized cluster list, sequenced by consultation value.

Phase 2: production with an answer-first spine (months 2-9)

Content shipped weekly through a strict template: the question as the heading, a plain forty-word answer immediately below, then the depth, caveats and next steps, with FAQ schema and interlinks wired into the cluster. Attorneys reviewed every piece; their edits became part of the expertise capture for the next ones.

Phase 3: the expertise layer (months 3-6)

Attorney entities were built properly: bio pages with Person schema, consistent bylines across the new content, profiles aligned, and contributed commentary placed on two regional publications. The firm’s organization entity got the same treatment.

The results

Snippets came first: the answer-first template began winning featured positions within two months. As AI Overviews expanded across legal queries, the same structure carried straight into them; by month twelve the firm held citations in Overviews on more than thirty tracked questions, often above directories that had owned the category for years. Consultation requests attributed to organic rose 73% against baseline, with intake reporting a new pattern: callers arriving pre-educated by the firm’s own pages, shorter calls, better-fit matters.

What made the difference

Writing for the worried human first and the machine’s extraction second, in that order, with one template enforcing both. And publishing the expertise the firm already gave away by phone daily. Nothing was invented; it was transcribed, structured and owned.

Explore the services behind this engagement: Semantic SEO, Entity SEO and AI Overview Ranking.