Here’s a scene I see constantly with U.S. businesses that serve Spanish-speaking customers. The website is in English. Someone installed a little flag button. Click it and you get Spanish nobody wrote: “Contact us” becomes something stiff and slightly wrong, the form labels stay in English, and the owner, who serves half their customers in Spanish, believes they have a bilingual website.
They don’t. They have an English website with a layer on top, and that layer is costing them customers in both languages.
The short answer
A real bilingual website is two complete versions on separate URLs, for example / in one language and /es/ or /en/ for the other. Each one is written by a person, and each one can rank on Google on its own. It’s not a plugin. Which language comes first depends on who buys from you this week, not on which language you speak best. And it doesn’t cost double: planned from the start, it typically runs 30 to 50 percent more than a single-language site.
How many customers you’re leaving out
In 2024, 44.9 million people in the U.S. spoke Spanish at home, roughly one in seven people aged five and older. About 58.9 percent of them say they speak English “very well.” Put the other way around, around four in ten Spanish speakers aren’t fully comfortable handling things in English. That’s exactly the moment someone decides whether to call you or the business next door.
The more useful number isn’t about language, it’s about buying. CSA Research surveyed 8,709 consumers in 29 countries, and 76 percent prefer to buy products with information in their own language. It’s not that they can’t read English. It’s that in their own language they trust more and decide faster.
Three reasons the translation plugin costs you clients
1. Visitors notice in the first line
Machine translation doesn’t make dictionary mistakes; it makes trade mistakes. It translates “roofing” one way in one paragraph and another way in the next, turns “free estimate” into something no customer would say, and leaves service names stuck halfway between two languages.
The visitor doesn’t read that as a translation error. They read it as a business that didn’t bother. And if you didn’t bother to write to them in their language, it’s fair for them to wonder how much care you’ll put into their roof, their taxes or their case.
2. Google can’t rank a page that doesn’t exist
This is the damage you don’t see. Plugins that translate “on the fly” swap the language without changing the URL. For Google, that Spanish version doesn’t exist as a page, so it can’t show it to people searching in Spanish.
Google’s documentation is explicit: use different URLs for each language version, because its crawler typically visits from the U.S. without a language preference. The same page warns against automatically redirecting visitors based on their browser language, since that stops both versions from being discovered, and notes that translating only the template while leaving the content in one language creates a poor user experience.
In practical terms: every dollar you spent on SEO is working for half your market.
3. Mass, unreviewed translation is spam territory
Google’s spam policies list, under scaled content abuse, generating many pages through “automated transformations like synonymizing, translating, or other obfuscation techniques.” A twenty-page site machine-translated in one click and published without anyone reading it fits that description. Google doesn’t ban machine translation. It just doesn’t reward translation with no human review and no added value.
English or Spanish first? How to decide
There’s no universal answer, just a rule: the primary language is the one your next paying customer uses, and that changes by city and by trade.
- Miami, Hialeah, San Antonio, East Los Angeles. Spanish is often the main version, not the second one. More on that market in web design in Florida.
- Austin, Jacksonville, much of the Bay Area. If your high-ticket clients are mostly English speakers and Spanish is 20 percent of your book, English leads, and Spanish still exists in full, not as a trimmed-down page.
- Contractors and home services. Often Spanish wins for lead generation and English for closing with customers who ask about license and insurance. Both complete. See websites for contractors.
- Law, insurance, healthcare. The language that wins is the one people use to explain a sensitive problem, which is usually their first language.
Not sure? Look at your last thirty WhatsApp messages or call notes. The language they’re in is your answer, and it costs nothing to find out.
How to build a bilingual website that works
- One URL per language.
yourbusiness.com/services/andyourbusiness.com/es/servicios/. Different addresses, complete content in each. hreflangtags on both versions. This tells Google they’re the same page in another language, not duplicate content. Both directions, plus anx-default.- A visible language switcher, no automatic redirect. A link in the menu that says “Español / English.” Not flags: a flag is a country, not a language.
- Write the language, don’t translate it. The Spanish headline isn’t the translation of the English headline; it’s the headline that works in Spanish. Examples, objections and even service names can change.
- Translate everything people touch. Forms, error messages, buttons, confirmation emails, the pre-filled WhatsApp message, image alt text and legal pages. Most of the “this feels half-done” effect lives in these details.
- A sitemap that declares both versions and a correct canonical on each page, so the two versions never compete with each other.
- The same outside the website. A Google Business Profile description in both languages, review replies in the language the review was written in, and separate ad campaigns per language.
What not to translate
- License and certification names. “General Contractor License” stays as is, with a short explanation next to it.
- Customer reviews. Leave them as written. Translating a testimonial removes the only thing that made it believable.
- Terms your customers use in English even when speaking Spanish: deck, drywall, closing, escrow. Forcing a translation sounds like a brochure from another country.
What a bilingual website costs
It doesn’t cost double. Structure, design, development and setup happen once. What doubles is content, which usually adds 30 to 50 percent when the project is bilingual from day one. Adding a second language later to a site that wasn’t built for it, especially on a visual builder, costs considerably more because URLs, menus and templates have to be redone. What else moves the number is covered in how much a small business website costs.
How I build them
I code bilingual websites from scratch, not templates with a plugin: two full versions on separate URLs, with hreflang, written in both languages by the same person who builds the site. I work remotely with businesses across the United States, and base prices are published: a landing page from $349 and a 4–6 page website from $899. If you serve several cities, the next step is how to show up on Google Maps across multiple counties.