A law firm website should make four relationships obvious: what the firm handles, where it can help, who does the work, and which explanation answers the reader's next question. URL folders alone do not create those relationships. Page roles, navigation, internal links, and maintained firm facts do.
Design the architecture from real services and offices. Do not multiply every practice by every city and hope the resulting grid becomes useful.
Give each page type one primary job
Scroll sideways to review every column.Each row is shown as a labeled card.
| Page type | Primary job | Must establish | Should connect to |
|---|---|---|---|
| Practice | Explain matter/client fit and service decision | Represented side, scope, process, proof, next step | Relevant attorneys, offices, deeper guides |
| Location | Represent a real office and local service context | Address, access, contact, people, available practices | Attorneys and practices actually available there |
| Attorney | Establish a current person and role | Biography facts, practice, office, experience, useful work | Current practices, offices, articles |
| Guide/resource | Resolve a distinct question | Audience, answer, sources, limits, update owner | Relevant practice and next decision |
| Firm/about | Explain institution and verified proof | Identity, leadership, history/values where supportable | People, services, offices, careers/contact |
When one page tries to be a statewide service explanation, local-office landing page, attorney biography, and long guide, each job becomes harder to maintain.
Map relationships before drawing folders
Use the practice-area hub guide to decide page roles and the practice-area authority guide to keep raw volume from dictating the hierarchy.
Create a page-role record with:
- approved page name and purpose;
- audience and represented side;
- service and jurisdiction boundary;
- real office and attorney relationships;
- unique evidence or source material;
- canonical owner and proposed URL;
- parent/navigation route;
- contextual incoming and outgoing links;
- intake destination; and
- owner and update triggers.
Then draw the graph. Folder structure can support understanding and maintenance, but a page does not need to live under another page's URL to link meaningfully to it.
Use stable, readable URLs without encoding every organization change
A useful URL names the resource in plain language and survives routine staffing or navigation changes. Avoid IDs, dates, campaign parameters, and several repeated keyword layers when they add no durable meaning.
Changing an existing URL has cost: redirects, internal links, citations, bookmarks, analytics continuity, and search reprocessing. A visually “cleaner” path is not enough reason. If a change is justified, map the old URL to an equivalent final page and update internal links.
Do not put an attorney's current office into the permanent URL unless the relationship is expected to define the resource. People move. The biography can carry a stable identity while its office and practice relationships change.
Build links around reader decisions
Useful paths include:
- practice → attorneys who actually do the work;
- practice → offices where the service is available;
- practice → guide answering the next decision;
- office → practices and people available there;
- attorney → current practices, office, and authored/approved resources;
- guide → relevant service boundary and related explanation; and
- all important paths → accurate contact expectation.
Google recommends crawlable <a> elements with resolvable URLs and meaningful anchor context. Read Google's link guidance. The Juris Digital internal-linking guide develops anchor and hierarchy decisions beyond this architecture map.
Sitewide menus and footers support discovery but do not replace contextual relationships. “Learn more” repeated across cards is less useful than an anchor that tells the reader what decision follows.
Make a practice-location page earn its existence
Do not automatically create every possible combination. A distinct practice-location page needs a real service relationship and enough specific substance to help that market.
Test five conditions:
- Reality: the firm actually offers the service in the location and can support the contact path.
- Distinct need: market, forum, process, access, team, evidence, or recurring question changes the reader's decision.
- Source depth: the firm can provide more than swapped place names.
- Architecture: the page has a clear owner and useful links from practice/location paths.
- Maintenance: facts, people, law, and intake can be reviewed.
Google's spam policies describe doorway abuse, including substantially similar pages created for many regions or cities that funnel users onward. Read the current policy. A city name does not make copied content distinct.
Work through a two-office expansion
A fictional seven-lawyer business firm has two real offices and four practices. Multiplying them produces eight possible practice-city pages. The firm tests each instead of ordering eight drafts.
Scroll sideways to review every column.Each row is shown as a labeled card.
| Possible page | Real availability | Distinct local decision/evidence | Decision |
|---|---|---|---|
| Denver employment counsel | Yes | Local team, recurring manager-training process, relevant events | Create distinct page |
| Denver commercial disputes | Yes | Lead attorneys and forum/process material | Create distinct page |
| Denver transactions | Yes | No location-specific reader task beyond main practice | Use national practice + Denver office links |
| Denver succession planning | Yes | Same service/source as main practice | Use national practice + Denver office links |
| Boulder employment counsel | Yes | Different small-company workshop and local team | Create distinct page |
| Boulder commercial disputes | Limited | Service handled from Denver; no distinct local proof | Link office to main practice with accurate expectation |
| Boulder transactions | Yes | No distinct location decision | Use main practice + office relationships |
| Boulder succession planning | No current capacity | Public page would misstate availability | Do not create |
Only three of eight combinations earn pages. The architecture contains:
- four durable primary practice pages;
- two office pages;
- seven stable attorney biographies;
- three approved practice-location pages; and
- supporting guides connected by question.
The Denver employment page links to the primary employment service for the full firm-wide scope, the Denver office, participating attorneys, the manager-training guide, and the correct contact path. The primary practice page links back only where the local option helps a reader choose. This is a relationship, not a ring of reciprocal links added for keywords.
The Boulder commercial-disputes row remains a real service connection without a thin city page. The office page says how the service is handled and links to the main practice. The succession row stays absent until service reality and capacity change.
Keep attorney identity consistent
Choose one current biography as the person's canonical public profile on the firm site. Reuse governed facts—name, role, admissions, education, offices, practices, contact rules—without copying the whole biography into every page.
When an attorney joins, changes role, moves office, or leaves, use a change checklist across biographies, practices, locations, articles, schema, authorship, navigation, redirects, contact routing, and archived materials. Decide what remains historically accurate and what becomes misleading.
Do not redirect every departed attorney to the homepage automatically. A relevant team, practice, or archived resource may be appropriate; sometimes an unavailable response is more honest than an unrelated destination.
Give content hubs and architecture different jobs
A content hub organizes explanations around a subject. Website architecture governs the full system of services, offices, people, resources, navigation, URLs, and technical ownership. JD-039 handles hub versus standalone content decisions; the topic-cluster guide develops editorial grouping.
A guide should not replace the practice page's service boundary. A practice page should not absorb every legal question. Make each page complete for its job and connect the next one.
Test the structure with real tasks
Verify access and canonical behavior through the technical SEO guide, then place the accepted work inside the SEO roadmap.
Before release, ask whether a person can:
- confirm the firm handles the relevant side and matter;
- find whether and how the service is available in their market;
- identify a responsible attorney and verify current role;
- move from a guide to the relevant service without guessing;
- understand what contact starts; and
- use the path on mobile and with keyboard/screen-reader navigation.
Also crawl and inspect orphaned priority pages, redirect chains, canonical conflicts, broken links, generated variants, sitemap differences, structured-data relationships, and analytics/intake continuity.
Design for the next change
Use the website design buyer guide when the next change requires a broader template or platform decision.
Keep the page-role map, authoritative firm-fact sources, navigation rules, redirect history, template tests, and update ownership. Model the next office, new attorney, renamed practice, merger, and departure before approving the architecture.
Juris Digital's current law firm website design service covers scoped launches/rebuilds, migration protection, and named delivery roles. Its law firm SEO service connects technical/site foundations with content, local visibility, authority, and measurement. Bring the current URL inventory, practices, real offices, attorney roster, proposed expansion, and service/capacity rules. We can help build the page-role map and migration scope; the proposal defines deliverables and implementation.
