TL;DR — Generic "Personal Injury Lawyer in [City]" pages stopped ranking somewhere around the March 2024 Core Update. What ranks now are case-type-specific pages — "Rear-End Collision Lawyer in Tampa," "Amazon Delivery Truck Accident Attorney in Dallas" — built with 8 structural sections, LegalService schema, tight internal links to a central PI pillar, and conversion elements that don't make the user hunt for a phone number. This guide is the template. Steal it.
Key takeaways
- Google's March 2024 and August 2024 Core Updates collapsed rankings for thin, generic "PI Lawyer in [City]" pages. The winners are case-type-specific pages with 1,500–2,500 words of substantive, jurisdiction-accurate content.
- A PI practice area page needs 8 structural sections: H1 with modifier + geography, intent-matching intro, legal framework for that case type, damages/compensation, process, FAQ, attorney bios with schema, and conversion elements above and below the fold.
- City + practice area pages (e.g.,
/tampa/rear-end-collision-lawyer/) outperform single-page-per-city strategies by 3–5x in signed cases, but only if the content is genuinely localized — not spun. - Internal linking should route from case-type pages up to a single PI pillar and laterally to related case types (rear-end → whiplash → soft-tissue injury). Avoid flat architectures where every page links to every page.
- LegalService, Attorney, and FAQPage schema are table stakes. If your practice area pages don't have them, you're handing rankings to firms that do.
- Conversion elements matter more than most firms think: a visible phone number above the fold, a short form (3–5 fields max), and click-to-call that actually works on mobile. A page that ranks but doesn't convert is just expensive decoration.
Why generic "Personal Injury Lawyer in [City]" pages stopped ranking
If your firm still has one giant "Personal Injury Lawyer" page trying to cover car accidents, trucking, slip-and-fall, dog bites, and medical malpractice all at once — and a handful of city pages doing the same thing — your rankings have probably been sliding for two years and you might not know why.
Here's what happened. Google's March 2024 Core Update and the follow-up August 2024 update did something specific: they downgraded pages that covered broad topics without depth and upgraded pages that demonstrated real subject-matter expertise on a specific query. The Google Search Central documentation on helpful content is explicit about this — pages that exist to cover a keyword rather than to answer a specific question underperform.
For PI firms, this cashes out as a simple rule: the query "rear-end collision lawyer Tampa" is a different query than "car accident lawyer Tampa" is a different query than "personal injury lawyer Tampa." Google treats them differently. The search intent is different. The damages frameworks are different. The defendant profiles are different. A page that tries to rank for all three will lose to three pages that each rank for one.
The firms winning PI SEO in 2026 figured this out and built practice area architectures accordingly. This guide is what their pages look like.
The 8 sections every PI practice area page needs
A practice area page is not a blog post. It's not a brochure. It's a conversion-optimized document that signals to Google "this firm has deep expertise in this specific case type in this specific jurisdiction" and signals to the reader "these people have handled cases exactly like mine."
These are the 8 sections, in order. Deviating from this order isn't forbidden, but every successful PI practice area page we've built uses some version of it.
Section 1: H1 with case-type modifier + geography
The H1 should contain the exact query modifier and the geography. "Rear-End Collision Lawyer in Tampa, Florida." "Amazon Delivery Truck Accident Attorney Serving Dallas County." Not "Our Auto Accident Practice" or "Tampa Personal Injury Attorneys." The H1 is the highest-weight SEO signal on the page — don't waste it on brand language.
Section 2: Intent-matching intro (100–150 words)
The first paragraph should restate the searcher's situation in their own words. Someone typing "rear-end collision lawyer Tampa" has been rear-ended in Tampa. Say that. "You've been rear-ended on I-275, I-75, or one of Tampa's other major corridors. The driver behind you is almost certainly at fault under Florida Statute §316.0895, but their insurer is already working to minimize what they pay you."
Two things happen when you do this. First, Google sees the query intent matched in the first 100 words, which is where most AI Overviews and featured snippets are pulled. Second, the reader knows in 10 seconds that this page was written for them, not for an algorithm.
Section 3: Legal framework for this specific case type
This is where most law firm websites fail. A rear-end collision page in Florida needs to discuss Florida's comparative negligence statute (Fla. Stat. §768.81), the presumption of fault in rear-end cases, PIP coverage and its limits under Fla. Stat. §627.736, and the 2023 tort reform changes that moved Florida from pure to modified comparative negligence.
This is 400–600 words of substantive legal content that proves to Google you know the jurisdiction. It's also the content your state bar's advertising rules care about most — it has to be accurate. If you're in Florida, this section must comply with Florida Bar Rule 4-7.13 on deceptive advertising — no promises about outcomes, no implied guarantees.
Section 4: Damages and compensation
What can a plaintiff recover in this specific case type? Medical bills, lost wages, pain and suffering, loss of earning capacity, loss of consortium, punitive damages where applicable. For each, cite the Florida (or Texas, or Georgia) legal basis and note any caps.
This section is where generic templates get firms in trouble. Florida caps on non-economic damages in medical malpractice are different from Texas caps on punitive damages are different from Georgia's lack of cap on pain and suffering. If your damages section is the same across state pages, Google knows it and your bar might too.
Section 5: Process — what happens from call to settlement
A short, honest walkthrough of the case process for this specific case type: initial consultation, investigation, demand letter, pre-suit negotiation, filing suit if necessary, discovery, mediation, trial. Include realistic timeframes. ("Most rear-end cases resolve within 6–14 months. Cases involving traumatic brain injury or disputed liability take longer.")
This builds trust. It also ranks for long-tail process queries like "how long does a car accident settlement take in Florida."
Section 6: FAQ (4–8 questions)
See section 9 for the full FAQ strategy. Short version: this is where you pick up featured snippets and AI Overview citations.
Section 7: Attorney bios with schema
Who's handling this case type at your firm? Named attorneys, with photos, bar admission, years of experience, notable case results (with bar-compliant framing), and Attorney schema markup. This feeds E-E-A-T signals directly.
Section 8: Conversion elements (above and below)
A phone number in the header, a click-to-call button, a short consultation form in the sidebar or below the hero, a chat widget if you're equipped to handle it 24/7, and a final CTA block at the bottom. Covered in detail in section 7 below.
What schema markup does a PI practice area page need?
The minimum viable schema stack is three types: LegalService, Attorney, and FAQPage. Without these, you're leaving ranking signals on the table that competitors with proper implementation are collecting for free.
Here's how each one works in practice.
LegalService schema goes on every practice area page. It tells Google this page represents a specific legal service offered by a specific firm in a specific area. Required properties: name, provider (nested Organization or LegalService), areaServed (the geography), serviceType (the case type — "Rear-End Collision Litigation"), and url. Add hasOfferCatalog if you want to list sub-services.
Attorney schema goes on attorney bios. Required: name, jobTitle, worksFor, alumniOf, knowsAbout (the practice areas this attorney handles), and memberOf (bar associations). This is how Google populates the attorney cards in local packs and AI Overviews.
FAQPage schema goes on the FAQ section of the page. Each Q/A pair becomes structured data that Google can pull into People Also Ask boxes and featured snippets. This is the single highest-ROI schema you can add — we've seen practice area pages pick up 3–5 featured snippets within 30 days of adding FAQPage markup to existing content.
A fourth that's worth adding when applicable: BreadcrumbList schema, so Google understands your site architecture (Home → Practice Areas → Car Accidents → Rear-End Collisions).
Validate everything with Google's Rich Results Test before shipping. Invalid schema is worse than no schema.
How do city + practice area landing pages work?
They work by being real pages, not spun templates. A proper architecture looks like this:
/practice-areas/rear-end-collisions/ ← case-type pillar
/tampa/rear-end-collision-lawyer/ ← city + case-type
/st-petersburg/rear-end-collision-lawyer/ ← city + case-type
/clearwater/rear-end-collision-lawyer/ ← city + case-type
The case-type pillar covers the legal framework in general terms for the state. Each city page localizes it: Tampa-specific accident statistics, the relevant courts (Hillsborough County Circuit Court), common accident locations (I-275, I-4 interchange, Dale Mabry Highway), local medical providers you've worked with for treatment liens, and — ideally — case results from that city.
Why the multi-location play outperforms single-city strategies
Across the 14 states we work in, firms running properly built city + practice area architectures sign 3–5x more cases from organic than firms running a single PI page per city. The math is straightforward: ten cities × four core case types = forty pages competing for forty different local query sets instead of ten pages competing for ten.
But the failure mode is obvious. If all forty pages are templates with the city name swapped in, Google treats them as doorway pages and de-indexes them. Google's own guidance on doorway pages is explicit about this.
The rule of thumb: each city page must have at least 400–600 words of genuinely local content that would not appear on any other city page. If you can't write that for a given city, don't build a page for that city.
Firm-stage callout: how many city pages should you build?
- For a firm in its first 12 months: Pick one city (where your office is) and two core case types. Build two excellent city + practice area pages, not twenty mediocre ones. You'll rank faster and convert more.
- For a mid-size firm ($5M–$25M): Build out your immediate metro (typically 3–5 cities) across your top 4 case types. That's 12–20 pages. Add expansion cities only after the core metros are converting.
- For an established firm ($100M+): You probably already have 50–200 location pages. The work is usually pruning — killing the thin ones that are dragging down domain authority — before adding more. We've seen established firms add 30% to organic traffic by cutting 40% of their page count.
Internal linking: pillar, case-type, and city pages
The architecture that ranks looks like a tree, not a spiderweb.
At the top: one central Personal Injury pillar page — the highest-authority page in the cluster. Below it: case-type pillar pages (car accidents, truck accidents, slip-and-fall, medical malpractice). Below each case-type pillar: city-level pages and sub-case-type pages.
The three internal linking rules that matter
Rule 1: Every page links up to its parent. A Tampa rear-end collision page links to the Rear-End Collisions pillar and to the Personal Injury pillar. This concentrates authority up to the pages you most want ranking for head terms.
Rule 2: Related case-type pages link laterally. Rear-end collisions → whiplash treatment → soft-tissue injury claims → delayed onset injuries. These are the actual reading paths of someone researching their case. Google rewards this pattern because it matches real user behavior.
Rule 3: Never link from every page to every page. Flat site architectures were an SEO tactic in 2015. In 2026 they signal to Google that you don't have a hierarchy — which means you don't have real subject-matter expertise. PageRank dilution is real; keep it concentrated.
A comparison of the common internal linking patterns and how they perform:
| Architecture | Setup | How it ranks | Best for |
|---|---|---|---|
| Flat (all pages linked from nav) | Easy | Poorly — dilutes authority | Nothing. Avoid. |
| Silo (strict separation by practice area) | Medium | Well on head terms, weakly on long-tail | Firms with 2–3 tightly defined practice areas |
| Hub-and-spoke with lateral links | Harder | Best overall — ranks head + long-tail | The standard PI architecture. Use this. |
| Topic cluster with pillar at center | Hardest | Dominates long-tail, slower on head terms | Firms investing heavily in content long-term |
For most PI firms, hub-and-spoke is correct. Our AI SEO service builds this architecture as the default.
Content length, keyword density, and freshness signals
How long should a practice area page be? Between 1,500 and 2,500 words for a case-type pillar. Between 1,200 and 1,800 words for a city + practice area page. Below 1,000 and you look thin; above 3,000 and you lose the reader before the conversion elements.
What about keyword density? Ignore it as a metric. Google hasn't ranked on density in a decade. What matters is semantic coverage — does the page use the full vocabulary of the case type? For rear-end collisions, that means: tailgating, following distance, whiplash, cervical strain, property damage, diminished value, PIP, uninsured motorist coverage, bodily injury liability. Hit the vocabulary naturally; don't count instances.
Freshness signals Google weights:
dateModifiedin schema (update when you meaningfully update the page — not monthly as a trick)- Citing recent case law or statute changes by year
- Adding new FAQ entries as new questions emerge
- Updated attorney bios and case results (when bar-compliant)
Generic advice like "update your page every 90 days" is useless. Update when there's a real update. Google's spam systems are very good at detecting pages where only the date changed.
What conversion elements actually move the needle?
A ranking page that doesn't convert is an expense, not an asset. Four elements matter, in order of impact.
1. Phone number visible above the fold, on every page, on every device. Mobile traffic is 70%+ of PI inbound. If someone has to scroll or tap a menu to find your phone number, you've lost calls. Make it a large, tappable, tel-link: <a href="tel:+18135551234">.
2. A short form, not a long one. Name, phone, short description of the incident. That's it. Every field you add past four cuts conversion roughly 5–10%. You are not qualifying leads on this form — you are capturing them. Qualification happens on intake.
3. Click-to-call buttons that actually work on mobile. Test them on an iPhone and an Android before launching. We routinely audit firms whose click-to-call buttons are broken on specific device/browser combinations, costing them 20–30% of potential calls from those devices.
4. Chat or after-hours coverage — if you can actually staff it. A chat widget that isn't answered is worse than no widget. A managed chat service with 24/7 response (answered by humans with your intake script) can lift signed cases 15–20%, especially for firms in metros with heavy evening/weekend accident volume.
Above-the-fold trust signals worth including: verdict/settlement totals (with proper bar-compliant framing — "past results do not guarantee future outcomes"), years in practice, review counts from Google (cited with source and date — "4.9/5 from 412 Google reviews as of April 2026"), and any relevant bar certifications the attorneys actually hold.
Frequently asked questions
How long does it take for new PI practice area pages to rank?
For city + practice area pages in lower-competition metros, expect local pack movement in 30–90 days and meaningful organic traffic in 90–180 days. In hyper-competitive metros (Houston, Atlanta, Tampa, Los Angeles), plan on 6–9 months before new pages break into page one for the primary query. Case-type pillar pages targeting state-level terms ("truck accident lawyer Texas") typically take 9–12 months to rank competitively. Pure organic SEO is the slowest channel in the PI marketing stack — which is why we don't recommend running it alone.
Should we build separate pages for every sub-case-type?
Only if there's real search volume and real legal distinction. Separate pages for rear-end collisions, head-on collisions, and T-bone crashes make sense — different fault patterns, different damages, different search volumes. Separate pages for "Monday morning car accidents" or "grocery store parking lot accidents" usually don't — you'll end up with thin doorway pages. The rule: if you can write 1,200+ words of genuinely distinct content about the sub-case-type and there's documented search volume, build it. Otherwise, fold it into the parent.
What's more important for PI SEO — practice area pages or blog content?
Practice area pages, by a wide margin. Practice area pages capture high-intent bottom-of-funnel queries — the searcher has been injured and is looking for a lawyer right now. Blog content captures top-of-funnel research queries that rarely convert directly. A firm with 20 excellent practice area pages and zero blog content will sign more cases than a firm with 200 blog posts and generic practice area pages. Build the practice area foundation first; add content marketing only after the core pages are converting.
How do we handle bar advertising rules for case results on practice area pages?
Carefully, and state-by-state. Most state bars (Florida, Texas, New York, California among them) permit listing past results with required disclaimers — typically some version of "past results do not guarantee future outcomes" and a statement that each case is decided on its own facts. Some states require specific font sizes or placement for disclaimers. Before publishing any case results, check your jurisdiction's specific rule — for Florida, that's Rule 4-7.13 and 4-7.14; for Texas, Rule 7.02. When in doubt, have outside counsel review the language. Losing a ranking is recoverable. A bar grievance is not.
Can we just have AI write all our practice area pages?
You can, and Google will notice within a quarter. Pure-AI practice area pages share statistical patterns that Google's systems identify — generic phrasing, missing jurisdiction-specific detail, identical structural scaffolds across pages, no real first-person expertise signals. Pages we build with AI content workflows start with AI-generated scaffolding but require subject-matter review and localization from a human with actual PI expertise. The unit economics of AI-assisted content are dramatically better than traditional agency content. The unit economics of pure-AI spam are a short-term ranking followed by a drop.
How many practice area pages should our site have?
For a firm in its first 12 months: 2–4. For a $5M–$25M firm with a defined metro: 12–30. For an established firm with multi-state operations: 40–150. The ceiling is determined by how much genuinely unique, locally-accurate content you can produce and maintain. A page you can't keep accurate is a page that will eventually hurt you. More pages is not better; more ranking pages is better.
Next step
If you want to know which of your current practice area pages are ranking, which are dragging down your domain authority, and which sub-case-types your competitors are capturing that you're not — that's exactly what our free AI audit produces. 48-hour turnaround. No sales call required. You get the map; what you do with it is up to you.
The firms winning PI SEO in 2026 aren't the ones with the biggest content budgets or the oldest domains. They're the ones who rebuilt their practice area architectures around how Google actually ranks pages now — and stopped optimizing for how it ranked them in 2019.