Building a Bilingual (Spanish/English) Law Firm Website: Structure, hreflang and Intake

A bilingual law firm website works when each language has its own crawlable pages, the two versions point to each other with hreflang tags, and a Spanish speaker can go from search result to signed engagement without ever hitting English. Most firms get the first part half right and the last part wrong.

This guide is for firms that already serve Spanish-speaking clients, or want to, and are deciding how to build or rebuild the site. It covers structure, the technical signals Google reads, translation quality, the advertising rules that follow you into a second language, and intake. It is part of our Law Firm Marketing Guide.

One caution up front: lawyer advertising rules vary by state. Where this article cites a rule, it names the state. Confirm the details with your state bar before launch.

Choose a structure Google can crawl

Google's guidance on managing multi-regional and multilingual sites recommends using different URLs for each language version of a page. It advises against using cookies or browser settings to change the language, because Google may not find and crawl every variation. That rules out the "flag button that swaps text in place" approach many template sites use.

You have three workable options:

Both patterns show up among eSEOspace clients. Manuel Solis publishes English under /en and Spanish under /es on one domain. Barajas Law Office runs a complete Spanish site on its own Spanish-language domain, with a "View in Spanish" link on every English page. Either can work. What matters is that the Spanish pages are complete, linked and indexable.

Do not auto-redirect by language

Google's same guidance says to avoid automatically redirecting visitors based on their perceived language. A redirect can stop people, and Googlebot, from seeing every version. Instead, put a clear language link in the header of every page, pointing to the equivalent page in the other language, not to the Spanish homepage.

Set up hreflang correctly

hreflang is a small tag that tells Google "this page has an equivalent in another language, here it is." Google's documentation on localized versions of pages spells out the rules. The ones firms break most often:

1. Reciprocal links. Every version must reference itself and every other version. If the English page points to the Spanish page but the Spanish page does not point back, the annotations may be ignored.
2. Absolute URLs. Use full URLs including https://, not relative paths.
3. Valid codes. Language codes use ISO 639-1 ("en", "es"). A region is optional ("es-US"). A country code alone is invalid, and Google notes that "es-419" (Latin American Spanish) is not supported.
4. One method is enough. You can put hreflang in the page head, in HTTP headers or in the XML sitemap. Google treats them the same, and using all three adds nothing.
5. x-default. Use it for a language-selector page or the page you want shown when no listed language matches.

A minimal setup for an English and Spanish car accident page looks like this in plain terms: the English page lists itself as "en" and the Spanish page as "es"; the Spanish page lists itself as "es" and the English page as "en". Most firms only need "en" and "es". Add a region code only if you truly target different countries.

One more point from the same page: Google does not use hreflang or the HTML lang attribute to detect a page's language. It reads the content. So a page tagged "es" with half its text still in English will look like what it is.

Mark the language for screen readers too

The HTML lang attribute still matters for accessibility. WCAG 2.2 success criterion 3.1.2 Language of Parts (Level AA) asks that the language of each passage be programmatically determinable. That lets a screen reader switch to Spanish pronunciation when it reaches Spanish text. Set lang="es" on Spanish pages and mark any Spanish passage that appears on an English page. Our accessibility services cover this in audits.

Translation vs localization

Translation converts words. Localization converts meaning, so the page reads as if it were written in Spanish for your actual clients. For legal content, the difference shows up fast.

Why machine translation alone is risky

Google's spam policies describe scaled content abuse as generating many pages with little value to users, including through automated transformations such as translating. Google's multilingual guidance also warns that translating only the boilerplate (menus and footers) while leaving the main content in one language creates a poor experience. Its localized-versions page adds that language versions are only considered duplicates if the main content remains untranslated.

So machine translation can be a first draft. It should not be the published page. A bilingual attorney or a professional legal translator should review every practice page.

What localization looks like in practice

• Use the terms your clients search. A literal translation of "personal injury attorney" may not be the phrase your clients type. Check real Spanish search terms, such as "abogado de accidentes," in your keyword tools before you settle on page wording.
• Keep legal terms precise. Court names, form numbers and agency names often stay in English, with a Spanish explanation. A client needs to recognize the form when they see it.
• Rewrite examples. Local references, office directions and parking instructions should be written for the reader, not converted.
• Match tone. Decide on "usted" or "tú" once and apply it across the site. Most firms choose "usted" for a professional register.
• Translate the trust content. Attorney bios, reviews summaries, fee explanations and FAQs build trust. Leaving them in English signals the Spanish site is an afterthought.

For page structure itself, the same rules as English apply. Our guide to practice area pages covers depth, FAQs and avoiding thin location pages.

Advertising rules follow you into Spanish

A Spanish page is still a lawyer advertisement. Three state examples show how the rules can reach language specifically.

Texas. Rule 7.01(d) of the Texas Disciplinary Rules (Part VII, advertising) says a required statement or disclaimer must be made in each language used in the communication. It also says that a statement that a language is spoken does not by itself require a disclaimer in that language. In practice: if your Spanish page carries content that needs a disclaimer, the disclaimer belongs on that page in Spanish.

Florida. The Florida Bar's ethics checklist for websites, social media and video flags disclosures that are not in the same language as the advertisement or testimonial, citing Rule 4-7.12(c).

California. Comment [5] to Rule 7.1 of the California Rules of Professional Conduct says a lawyer may not state or imply they can provide legal services in another language unless the lawyer actually can, or the communication states, in that language, the employment title of the person who speaks it. So if your Spanish speaker is a paralegal or intake coordinator, say so in Spanish.

These are examples, not a full list. Other states have their own versions. Have the Spanish site reviewed against your state's rules, just as you would the English one.

Build intake in both languages

A common failure on bilingual law firm sites is a fully Spanish website that drops the visitor into English the moment they act. Walk through every step as a Spanish speaker would:

1. Phone. Does the number on Spanish pages reach someone who speaks Spanish, or a menu with a Spanish option, during the hours listed? If not, list a separate Spanish line and the hours it is staffed.
2. Forms. Field labels, placeholder text, error messages and the consent checkbox all need Spanish versions. So does the thank-you page.
3. Confirmation emails and texts. Automated replies should go out in the language the person used. Most intake tools let you route by a hidden "language" field on the form.
4. Scheduling. If you offer online booking, the booking page and reminders need a Spanish version, and the consult should be with someone who speaks Spanish.
5. Website disclaimers. The "contacting us does not create an attorney-client relationship" notice and any warning about sending confidential information should appear in Spanish next to the Spanish form.
6. Follow-up. Your intake team needs Spanish scripts and templates, not ad hoc translation.

Add the form's language as a field in your CRM so you can report Spanish leads separately. Our guide to call tracking and intake software for law firms covers routing and source tracking in more detail.

Local listings and off-site signals

Your Google Business Profile has one name, one category set and one phone number per location. You cannot run a separate Spanish profile for the same office. What you can do is make the bilingual service visible: mention Spanish in the business description, reply to Spanish reviews in Spanish, and post updates in both languages. Our guide to Google Business Profile for law firms covers profile rules for attorneys and offices.

Off the site, list the firm in Spanish-language directories and community organizations relevant to your practice. Keep the firm name, address and phone the same everywhere.

Bilingual site checklist

• Separate URL for every Spanish page, linked from its English equivalent
• Reciprocal hreflang on every pair, absolute URLs, valid "en" and "es" codes
• No automatic language redirects
• lang="es" on Spanish pages; Spanish passages marked on English pages
• Practice pages localized and reviewed by a fluent legal professional
• Disclaimers and disclosures in Spanish where your state requires them
• Truthful description of who speaks Spanish at the firm
• Spanish phone path, forms, confirmations, booking and follow-up
• Spanish XML sitemap entries and a Spanish menu
• Language captured as a lead field for reporting

Next step

If you are weighing a Spanish build for an immigration practice, read Immigration Law Firm Marketing next for trust signals and notario fraud warnings. When you are ready to plan the build, see how eSEOspace designs bilingual sites on our law firm website and SEO page.

Frequently asked questions