bg-up-triangles

URL Structure for Multilingual Personal Injury Sites

Employee

LAW FIRM SEO THAT WORKS®

Our Focus: Your Firm

Personal injury firms that serve multilingual communities face a technical challenge most overlook: the URL structure of their Spanish or Vietnamese pages directly determines whether those pages rank, get crawled, or compete against their own English content. Getting this right is not a minor detail. It shapes how Google allocates crawl budget, how link authority flows across language versions, and whether a prospective client searching in Spanish ever finds the firm at all. Law firm marketing at this level requires a clear technical framework before a single page goes live.

Table of Contents

The Subdirectory Model Outperforms Subdomains and Separate Domains for Personal Injury Firms

Subdirectories on a single root domain, structured as /es/ for Spanish or /vi/ for Vietnamese, give personal injury firms the strongest combination of SEO authority consolidation and technical simplicity. Subdirectories on a single domain are the second-best option after country-code top-level domains and are preferred for SEO authority consolidation. For U.S.-based personal injury firms targeting Spanish speakers in the same metro markets they already serve, a separate ccTLD adds cost and complexity without a meaningful ranking benefit. Subdirectories keep domain authority unified.

Subdomains, such as es.yourfirm.com, are treated by Google as separate sites. That means the authority built by your English pages does not automatically carry over. A firm that has earned strong backlinks to its English car accident lawyer page gets no direct equity transfer to es.yourfirm.com/abogado-de-accidentes/. The subdirectory model avoids that split entirely.

The practical URL pattern for a bilingual personal injury site looks like this. The English car accident page lives at /car-accident-lawyer/. The Spanish equivalent lives at /es/abogado-de-accidentes/. Each page is a distinct canonical URL. Google recommends using different URLs for each language version of a page rather than using cookies or browser settings to adjust the content language on the page. Serving language variants through cookies or JavaScript redirects creates a situation where Googlebot, which crawls primarily from U.S. IP addresses, sees only the English version and never indexes the Spanish one.

The sub-practice breakdown matters here too. Custom Legal Marketing’s analysis of 31,977 ranking URLs found that motorcycle accident, slip and fall, truck accident, and car accident pages all show keyword-in-path rates above 68%. That pattern applies equally to Spanish-language sub-practice pages. A Spanish-language slip and fall page benefits from a URL like /es/abogado-por-resbalon-y-caida/, not a generic /es/lesiones/ catch-all.

Hreflang Annotation Is the Technical Mechanism That Connects Language Versions

Hreflang tells Google which version of a page to serve based on a user’s language preference. Without it, Google may serve the English version to a Spanish-speaking searcher, or index only one version and treat the other as a duplicate. If you use different URLs for different languages, use hreflang annotations to help Google Search results link to the correct language version of a page.

The annotation goes in the <head> of every language variant of the page, and each variant must reference all other variants, including itself. For a bilingual personal injury site with an English page and a Spanish page, both pages carry two <link rel="alternate" hreflang="..."> tags. The English page points to itself with hreflang="en" and to the Spanish version with hreflang="es". The Spanish page does the same in reverse. Each language version must list itself as well as all other language versions.

Missing the return tag is the most common implementation error. Studies show 75% of hreflang implementations contain errors, including missing return tags, broken URLs, or incorrect ISO codes, and a single error in a hreflang cluster causes Google to ignore the entire cluster. For a personal injury firm, that means the Spanish pages simply do not receive the language targeting signal, and the firm loses ranking opportunity in the exact searches it built those pages to capture.

Use fully qualified URLs in every hreflang tag. Alternate URLs must be fully-qualified, including the transport method (http/https). A tag pointing to /es/abogado-de-accidentes/ without the domain will fail. The correct format is https://yourfirm.com/es/abogado-de-accidentes/. Pair this with an XML sitemap that lists all language variants for each URL, giving Google a second discovery path for the Spanish pages.

Firms pursuing multi-lingual law firm SEO should also add an x-default hreflang tag on the homepage and any language-selector pages. If you have specific URLs for users in different locales, provide a generic page for geographically unspecified users of that language, and use the x-default value: <link rel="alternate" href="https://example.com/" hreflang="x-default" />.

URL Architecture
Three URL Structure Options for Multilingual Personal Injury Sites
How each approach handles authority, crawlability, and technical overhead for U.S.-based firms targeting Spanish-speaking clients.
Subdirectory (Recommended)
yourfirm.com/es/abogado-de-accidentes/
Authority Unified
Single domain, full equity flow
Subdomain (Caution)
es.yourfirm.com/abogado-de-accidentes/
Authority Split
Treated as separate site by Google
Separate Domain (Avoid)
abogadolesiones.com
Authority Isolated
Full rebuild required; no equity transfer
🎯
The subdirectory model preserves every backlink your English pages have earned. A separate domain for Spanish content starts from zero authority, meaning a firm’s years of link building benefit only the English site.
Source: Google Search Central, Managing Multi-Regional and Multilingual Sites, updated December 2025.

Spanish-Language URL Slugs Must Use Translated Keywords, Not Transliterated English

A Spanish-speaking person injured in a car accident searches in Spanish. They type “abogado de accidentes de auto en Houston,” not “car-accident-lawyer-houston” in a Spanish browser. The URL slug of your Spanish page must reflect the actual search terms Spanish speakers use, which means genuine keyword research in Spanish, not word-for-word translation of English slugs.

Among people who spoke a language other than English in the U.S., approximately 61% spoke Spanish. That represents tens of millions of potential clients across the country, concentrated in markets like Los Angeles, Houston, Miami, Chicago, and Phoenix. Many of these individuals search exclusively in Spanish when looking for legal help after an accident.

The URL structure for a Spanish personal injury page should follow the same keyword-in-path logic that works for English pages. Custom Legal Marketing’s URL data shows motorcycle accident, slip and fall, and car accident pages achieve keyword-in-path rates above 68% in top-3 results. Spanish pages should mirror this. A bilingual firm serving Houston could structure its Spanish sub-practice pages as: /es/abogado-de-accidentes-de-auto/houston/, /es/abogado-de-camiones/houston/, and /es/abogado-por-resbalon-y-caida/houston/. Each URL communicates the practice area and city to both users and search engines.

Avoid using English words in Spanish slugs. A URL like /es/car-accident-abogado/ sends a mixed signal and ranks for neither language well. Google uses the visible content of a page to determine its language and does not use code-level language information such as lang attributes or the URL. You can help Google determine the language correctly by using a single language for content and navigation on each page. That same principle applies to the URL slug: keep it in one language, and make it the language of the page’s content.

As a Forbes Agency Council piece on bilingual law firms missing out on a huge SEO benefit has noted, firms that treat their Spanish pages as afterthoughts, with generic slugs and translated-only content, leave a significant portion of their potential market unreachable through organic search.

Canonical Tags and Duplicate Content Rules for Multilingual Personal Injury Pages

Each language version of a personal injury page is a distinct canonical URL. The English page at /car-accident-lawyer/ and the Spanish page at /es/abogado-de-accidentes/ are separate canonical documents. They should never point to each other via the canonical tag. Language variants should not canonicalize to each other. Each language version is a distinct canonical URL.

A common mistake is setting the Spanish page’s canonical to the English version, which tells Google to treat the Spanish page as a duplicate and suppress it from Spanish search results. This kills the entire purpose of building a multilingual site. The canonical tag on each language version should point to itself.

Translated content that shares substantial structure with the English version does not trigger duplicate content penalties as long as hreflang is implemented correctly. Google understands that a Spanish car accident page and an English car accident page cover the same topic for different audiences. The hreflang cluster is what communicates this relationship. Use hreflang to tell Google about the variations of your content, so that Google can understand that these pages are localized variations of the same content.

Machine translation creates a separate problem. Google’s quality systems detect machine-translated content with high accuracy, and unedited machine translation generates low-quality content penalties that suppress rankings across all language versions, not just the translated page. For personal injury firms, this is particularly consequential. Spanish-language personal injury pages are YMYL content. Google applies heightened quality standards to any page that could affect a person’s legal situation, financial decisions, or safety. Human-reviewed, professionally written Spanish content is a requirement for competitive rankings, not an optional upgrade. Firms building out a complete multilingual law firm website should budget for professional legal translation from the start.

Site Architecture and Internal Linking Across Language Versions

The internal linking structure of a multilingual personal injury site must treat each language version as its own coherent architecture. Spanish pages should link to other Spanish pages. English pages should link to other English pages. Cross-language internal links are acceptable for language switcher navigation, but the main content links within each version should stay within that version’s URL structure.

A firm’s Spanish homepage at /es/ should link to its Spanish practice area pages, just as the English homepage links to English practice area pages. The Spanish car accident page should link to the Spanish truck accident page and the Spanish slip and fall page. This builds topical depth within the Spanish version of the site and gives Google clear signals about the relationship between Spanish pages. Law firm SEO for multilingual sites requires this internal architecture to be built deliberately, not left to chance.

The language switcher itself deserves careful URL planning. Every page should include a visible link to its counterpart in the other language. That link should go to the exact equivalent page, not to the homepage of the other language version. A Spanish-speaking user on the Houston car accident page who switches to English should land on the English Houston car accident page, not the English homepage. This is both a user experience requirement and an SEO signal that reinforces the hreflang relationship between the two pages.

Sitemaps for multilingual sites should be structured to include all language variants. To specify language variants in a sitemap, add a <loc> element specifying a single URL with child <xhtml:link> entries listing every language/locale variant of the page including itself. If you have three versions of a page, your sitemap will have entries for the URLs of each version, and each entry will have three identical child entries. Submit the sitemap to Google Search Console and verify that each language version is being crawled and indexed. Firms that also invest in Answer Engine Optimization for their multilingual pages should ensure the Spanish content is structured with the same question-and-answer formatting used on English pages, since AI tools and voice assistants also serve Spanish-language queries.

FAQs About URL Structure for Multilingual Personal Injury Sites

Should a personal injury firm use subdirectories or subdomains for its Spanish-language pages?

Subdirectories are the better choice for most personal injury firms. A structure like yourfirm.com/es/ keeps all domain authority on a single root domain, which means the backlinks and trust signals your English pages have accumulated benefit the Spanish pages as well. Subdomains such as es.yourfirm.com are treated as separate sites by Google, which means the Spanish version starts with no inherited authority and must build its own ranking signals from scratch.

Do Spanish-language personal injury pages need their own hreflang tags even if the firm only serves U.S. markets?

Yes. Hreflang is not just for international targeting. When a firm has both English and Spanish versions of the same page, hreflang tells Google which version to serve to which user based on language preference, not geographic location. Without it, Google may choose the wrong version for a Spanish-speaking searcher in Houston or Los Angeles, or treat one version as a duplicate of the other and suppress it from search results entirely.

Can a personal injury firm use the same URL slug in English for its Spanish pages?

Using English slugs on Spanish pages is a missed opportunity. Spanish-speaking users search in Spanish, and the URL slug is part of the page’s relevance signal. A slug like /es/abogado-de-accidentes/ aligns with actual Spanish-language search queries. A slug like /es/car-accident-lawyer/ does not match how Spanish speakers search, and the mismatch reduces the page’s relevance for Spanish-language queries.

What happens if a personal injury firm sets the canonical tag on its Spanish page to point to the English page?

Google treats the Spanish page as a duplicate of the English page and removes it from Spanish search results. The canonical tag tells Google which version of a page is the “primary” one for indexing purposes. When a Spanish page canonicalizes to its English counterpart, Google indexes the English version and ignores the Spanish one, which defeats the entire purpose of building a bilingual site. Each language version must have a self-referencing canonical tag.

How does machine-translated content affect rankings for multilingual personal injury pages?

Google’s quality systems can detect machine-translated content, and unedited machine translation can suppress rankings across all language versions of a site, not just the translated pages. Personal injury content falls under YMYL, or Your Money or Your Life, guidelines, which means Google applies heightened quality standards. Spanish-language personal injury pages require professionally written or human-reviewed content to compete effectively. Firms that publish raw machine translations often find their Spanish pages underperform even when the URL structure and hreflang implementation are technically correct.

More Resources About Multilingual Personal Injury SEO

What Our Clients Are Saying

Five star rated Law Firm Marketing Agency

CLM is the Real Deal

Jason at CLM is the real deal when it comes to SEO. I don’t think that you could make a better choice.

- Paul Greenberg, Briskman Briskman & Greenberg
Five star rated Law Firm Marketing Agency

My Traffic has Tripled

My traffic has tripled and my website consistently refers new clients to my social security and disability law firm.

- David W. Magann, David W. Magann, PA
Five star rated Law Firm Marketing Agency

More Leads than Ever Before

CLM’s dedication and unwavering support for our law firm is very much appreciated. I'm getting more leads than ever before.

- Henry Enright, Todd J. Leonard Law Firm