A location page exists to serve a real market the firm genuinely covers; a doorway page exists to catch a search the firm merely wants. The two look similar in a site menu and could not be more different to the systems scoring them, and the gap between them is one of the most common, most expensive self-inflicted wounds in personal injury SEO. This piece explains how location pages actually work, how the machinery identifies the fakes, and the honest architecture for firms with one office, three offices, or a whole service region.

Why PI firms mass-produce city pages

The logic seems airtight from the owner’s chair. Clients come from forty towns. Searches happen in forty towns. Therefore: forty pages, one per town, each swapping the city name into the same template. A vendor can generate them in an afternoon, the sitemap looks thorough, and for a while, some of them even rank.

The logic fails because it models the machine as a filing cabinet that rewards having a folder for everything. The actual machinery is an evaluation system that scores what each page is, what its neighbors are, and whether the entity behind it genuinely operates where it claims. On all three checks, mass-produced city pages testify against their own site.

The three mechanisms that catch doorways

Pages are scored on their own content quality. Google’s patent on processing web pages based on content quality, US 8775924, describes exactly the judgment owners hope does not exist: pages evaluated for the substance they carry, not the keywords they mention. A city page whose only city-specific element is the city’s name has a measurable quality problem no template can hide, because there is nothing underneath the find-and-replace.

Pages inherit their neighborhood. The quality-by-neighbor-features patent, US 9183499, is the one every multi-city template should fear: a resource is evaluated partly by the features of the resources around it. Forty near-identical siblings do not just fail individually. They drag each other down, and they drag the money pages down with them, because the site’s overall quality prior is computed from the whole family. This is why pruning doorway pages routinely helps the pages that remain: the neighborhood improves.

And the local stack checks the entity, not just the page. Google patented detection of related local entities, US 9858291, part of a machinery that connects businesses, places, and the content about them. A firm with one verified office in one city, claiming dedicated presence in forty, creates a record where the pages assert what the entity layer contradicts. Corroboration engines resolve contradictions by lowering confidence, and confidence is what local visibility is made of.

Put plainly: the machines ask three questions of every location page. Is there anything really here? Is it surrounded by siblings that say otherwise? And does the firm’s verifiable footprint support the claim? Doorways fail all three by construction, which is why no amount of polishing an individual template ever rescues the fleet.

What a real local page contains

The test for whether a location deserves a page is whether you can fill the page with things that are true and specific to that place. A real local page for a PI firm carries substance a template cannot fake:

The courts and venue reality for that county: where the case would actually be filed, which courthouse, what that means for timelines. The roads, corridors, and crash patterns that generate the area’s cases, stated factually. The local rules that change outcomes: notice deadlines for claims against that city or county, transit authorities with their own clocks, whatever applies in that state. The office or meeting reality, honestly: a real address if one exists, how the firm actually serves the area if not. The named attorneys who appear in those courtrooms. And the questions claimants from that area actually ask, which intake can supply.

Writing that page requires knowing the market. That is the point. The page is hard to fake because the knowledge is the content, and this is exactly why a genuine local page outcompetes ten templates: it is the only one in the set that could not have been written about anywhere else.

The honest architectures, by firm shape

One office, one metro: one deep local page, or the homepage itself carrying the local depth, plus practice pages that reference the market naturally. Resist the suburb-page temptation entirely; the metro page covering real suburbs with real substance beats twelve thin satellites.

A few genuine offices: one real page per office, each with its own complete identity, address, staff, courts, and content, each corroborated by its own verified profile. The pages differ because the places differ; if two office pages could swap cities by find-and-replace, they are not done.

A service region without offices everywhere: a regional architecture that tells the truth. County or region pages built on venue and court knowledge, clearly framed as where the firm practices rather than where it pretends to sit. In my experience the truth-telling version outranks the fake-office version over any horizon that matters, because it accumulates trust instead of contradiction.

Nested, not flat: location pages belong under the structure they serve, state above city where both exist, so the site’s own hierarchy teaches the machine the geography. I rebuilt my own site’s architecture this way, every flat slug redirected into its nested home, precisely because the hierarchy itself is information.

Where the true substance comes from

The usual objection to real local pages is that there is nothing to write. There is; it just does not live in keyword tools. Four sources fill a genuine location page with material no template can copy.

The court system’s own records: every state publishes which courts serve which counties, where they sit, and how their caseloads run. Venue is the most local fact in a personal injury case, and almost no firm page explains it.

The state’s transportation and safety data: crash tables by county and corridor, published by the agencies themselves. Stated factually, with the agency named in the sentence, this is the difference between “we serve Springfield” and demonstrating that the firm knows how Springfield gets hurt. The discipline is to pull the agency’s table, never a competitor’s summary of it, because the summaries in this industry are reliably wrong.

The local-government layer: notice deadlines for claims against the city or county, transit authorities with their own claim clocks, municipal defendants' special rules. These vary by place, change outcomes, and are precisely what a worried local searcher cannot find explained anywhere.

And intake itself: the questions callers from that market actually ask, the roads they name, the employers and hospitals that recur. A month of intake notes contains more real local content than any tool export ever will.

A page built from those four sources takes real hours. It is also unfakeable, unmatched by any competitor running templates, and true, which the next algorithm update cannot take away.

The audit, and the deletion courage

Auditing an existing city-page fleet takes an afternoon and one honest question per page: if the city name were removed, would anything on this page tell you which market it serves? Pages that fail get one of three verdicts. Merge: fold any real substance into the nearest genuine page and redirect. Rebuild: the market is real and worth a true page, so write one. Delete: the market was aspirational, the page is a liability, and removal is addition by subtraction.

Owners resist deletion because the pages feel like assets and ranked once upon a time. The neighbor-features mechanism is the answer to that resistance: every thin sibling is a tax on every strong page, paid continuously, whether or not anyone looks at the bill. The firms that prune feel it in the pages they kept.

One caution from the audit chair: never mass-delete without mapping redirects and checking what actually earns traffic or links first. Doorway cleanup is surgery, not demolition; the protocol matters as much as the decision.

Where this sits in the framework

Location architecture spans two pillars: Intent Capture, because geography is half of every local query, and Authority Reinforcement, because the entity record must corroborate every place the site claims. My free PI Authority Scorecard checks both in its 90-second pass, and the location questions are among the most commonly failed; the full local method is free in my guide at behzadhussain.me with the research behind the patterns at behzadhussain.me

And when a new market becomes real, when the firm genuinely starts taking cases there, the page follows the fact rather than preceding it. Geography earned is geography that ranks; geography claimed is a liability on a timer.

The rule that survives every algorithm update: build a page for every market you can tell the truth about, and no page for any market you cannot. The machines are corroboration engines, your competitors' templates are confession documents, and in a vertical this crowded, being the one firm whose geography is real is a stranger advantage than it should be.

About the Author

Behzad Hussain — Personal Injury SEO Strategist

Behzad Hussain is a Personal Injury SEO Strategist, independent researcher, founder and CEO of Rank Brilliance, and creator of the Personal Injury Organic Authority Engine. He helps competitive personal injury law firms build organic case acquisition systems through technical SEO, Semantic SEO, structured data, topical authority, and entity reinforcement.