One site, two front doors: the walk-in from Hialeah and the HR director in Brickell
Consumer and employer-side immigration are separate businesses that happen to share a letterhead, and the homepage has to send each visitor down its own path immediately.
Give each audience a route from the first screen rather than a paragraph deeper down. One route reads as a person with a personal situation. The other reads as a company with employees and exposure. The wording of the two links does most of the work.
Diverge everything after that split. The consumer path leads to benefit and situation pages, plain language, fees explained, an easy call. The employer path leads to process, timelines, compliance and a request for a briefing rather than a consultation, because that is the language of the person reading it.
Contact routing should split as well. An HR inquiry landing in the same queue as an emergency call from a relative gets triaged by whoever happens to be free, which is the wrong person roughly half the time.
Resist the urge to present the firm as everything to everyone on one page. Practices that try it end up with a homepage that lists nine practice areas and answers no one's actual question.
Build the Spanish section as a real site, with its own phone number and its own intake
Spanish is the dominant home language across large parts of Miami-Dade, so the Spanish side is not a translation layer, it is half the product.
Give it real architecture: its own URL structure, its own navigation, hreflang declared correctly, and internal links that keep a Spanish reader in Spanish pages. A visitor who lands in Spanish and hits an English page on the second click has learned something about how the firm will handle their file.
Route it separately. A distinct tracked number on the Spanish pages tells you what that audience is worth and, more usefully, makes sure the call lands with someone who can take it. The same applies to the form: the confirmation, the autoresponder and the follow-up email all have to be in the language the inquiry arrived in.
Haitian Creole is concentrated in Little Haiti and deserves its own decision rather than a default. Publish in Creole only if the practice can serve a Creole-speaking client end to end. Half a Creole path is worse than none.
Skip the automatic translate widget. Readers who have been misled by unlicensed advisers before are alert to anything that looks machine generated, and that is exactly what those widgets look like on a page about a legal benefit.
A 'my relative was detained' route needs its own page and its own fields
The most urgent inquiry an immigration firm receives arrives from a frightened third party who does not know the vocabulary, and a generic contact form is the wrong instrument.
Miami hosts one of the largest immigration court dockets in the country, so detention inquiries are a constant here rather than an occasional exception. Build a dedicated page reached in one tap from the homepage, written for the relative rather than the client.
Ask for the small number of facts that let someone assess it: who, where they were last known to be held, any case or file number if the family has one, country of origin, a callback number and the best language for that call. Do not ask a person in that state to fill sixteen fields.
Tell them plainly what happens next and how quickly. If your office cannot respond before morning, say so and give the number that will be answered. Silence in that window is where the file is lost, and every honest firm in this county knows it.
Provide the same route in Spanish and, if you serve it, in Creole. A relative in this situation will not switch languages to reach you; they will call the next firm.
Budget Android phones on mobile data set the performance bar, not your laptop
A large share of this audience arrives on modest hardware and a metered connection, and heavy pages fail them silently before anyone sees a bounce.
Test on a low-end device on a throttled connection, not on office wifi. The difference between a site that loads in two seconds and one that loads in eight is not aesthetic here, it is whether the inquiry exists at all.
Cut the things that cost the most and earn the least: autoplaying video on the homepage, carousel sliders, chat widgets loading before the content, heavy fonts, stock photography at full resolution. Most immigration firm sites can lose half their page weight without a visitor noticing anything except speed.
Design the tap targets and the form for a thumb. Phone numbers that dial on tap, forms that trigger the right keyboard, and a layout that does not require pinching are basic and still frequently missing.
Keep the phone number visible without scrolling on every page. A meaningful share of this audience will never use the form at all, and asking them to hunt for the number is a self-inflicted loss.
You generally cannot show client faces, so build credibility out of process
The usual trust furniture of a professional website is unavailable when your clients' circumstances are precarious, which means the proof has to come from somewhere else.
Named testimonials, client photographs and case detail carry real risk in this practice, and quite apart from privacy, lawyer advertising in Florida is subject to Bar rules that shape what may be published; worth confirming the current position with your own counsel before anything goes live.
Substitute proof the reader can verify. Bar admissions and years in practice, the courts and offices you appear before, languages actually spoken in the office, published writing on the benefit types you handle, clear fee information, and a straight explanation of what a consultation includes.
Explaining the process is itself a trust signal. A page setting out what happens in week one, who the client will speak with, and how updates are given, tells a reader more about competence than an adjective ever will.
Say plainly that the firm is licensed and who the lawyers are. Readers who have been burned by unlicensed advisers are looking for exactly that, and firms routinely bury it on an about page nobody opens.
The office you list changes who walks in, so treat the location page as sales collateral
An address in Coral Gables, Brickell, Doral or Hialeah reads as a different firm to a local visitor, and the practical details around it decide whether they arrive.
Write the location page for someone getting there, not for a search engine. Parking and what it costs, whether the building has a garage, which entrance, whether transit is realistic, and whether they need an appointment or can walk in.
State the visiting policy honestly. Many immigration practices now run largely remotely, and a client who takes two buses to a locked door does not call back. If consultations are by video or phone, say so on the page with the address.
Give the building context if it needs it. A tower reception with security and lifts is a different experience from a street-front office, and a sentence describing what to expect removes a small anxiety for a visitor who has plenty of larger ones.
One location page per real office, each with its own content. Duplicated pages for cities where you have no premises are a habit worth breaking, and they tend to read as exactly what they are.
Questions we actually get
- Should we rebuild the site or fix the one we have?
- Look at three things first: how fast it loads on a mid-range phone on mobile data, whether the Spanish side is genuinely built or bolted on, and whether the intake path captures what a paralegal actually needs. If the answers are acceptable on two of the three, fixing is usually cheaper and faster. If the Spanish side is a translate widget, that alone often justifies a rebuild.
- How much content should sit in Spanish?
- Ideally everything a consumer client would read, which is a bigger commitment than most firms expect. If a phased approach is necessary, start with the situations that produce your best files rather than translating the homepage and the about page, which are the two pages that convert least.
- Can we put client testimonials or case results on the site?
- Handle both carefully. Publishing details about people with precarious status carries real risk to them, and lawyer advertising in Florida is subject to Bar rules covering testimonials and results, so it is worth confirming the current position with your own counsel. In practice we build credibility from verifiable non-client material instead.
- Do we need a chatbot or an AI intake assistant?
- Usually not first. The gain from a chatbot is small next to answering the phone in the caller's language, and a bot that gives an inaccurate impression of eligibility creates a problem no design fix will solve. If you want one, scope it to booking and basic routing only, and test it hard in Spanish.
- What platform should the site be built on?
- Whatever your team can actually update, provided it renders fast on a modest phone and supports proper multilingual URLs rather than a translation overlay. The platform argument matters far less than page weight, the intake path, and whether the Spanish section is real. We are happy to work in what you already have if it clears those bars.
