Bilingual Websites: Do You Need Spanish, English, or Both?

If you do business in Puerto Rico, your website has a question to answer that mainland businesses never think about: which language does it speak?

The default answer — "both, obviously" — is right about half the time and expensive the other half. Here's how to decide properly.

Start With Who's Actually Buying

Not who might visit. Who pays you.

Mostly local customers. A barbershop in Caguas, a mechanic, a bakery, a contractor working residential jobs. Your customers think, search, and ask for recommendations in Spanish. A Spanish-first site with an English page for the occasional visitor is plenty.

Mostly tourists or mainland clients. Vacation rentals, tour operators, anything near the cruise terminals, or professional services selling to companies stateside. English carries most of the weight. Spanish still matters for local staff, suppliers, and credibility — but it isn't where the revenue is.

Genuinely split. Medical practices, law firms, real estate, logistics, hospitality. These need both, done properly, and the cost is justified because a customer who can't read your site in their language calls someone else.

Selling to businesses, not consumers. Look at how your clients write their own materials. In a lot of PR industries, business happens in English even when every person in the room speaks Spanish. Match your market, not your preference.

What "Both" Actually Costs

This is the part nobody warns you about. Two languages isn't a translation fee — it's a permanent doubling of the work.

• Every page exists twice. Change your services? Two edits. New photo captions? Two. A typo fix? Two.
• Every future page exists twice. A blog post is now two posts. Fifty posts becomes a hundred.
• Things drift. The Spanish page says you're open until 6, the English one still says 5, because someone updated one and forgot the other. This happens to almost everyone, and it looks worse than having one language.
• Forms, emails, and error messages count too. A perfectly translated site that sends a confirmation email in the wrong language breaks the illusion immediately.

Budget roughly 40-60% on top of a single-language build, and expect ongoing maintenance to be genuinely double. That's fine when both languages earn — and a waste when one of them is aspirational.

Don't Use Auto-Translate

Please don't put a Google Translate widget on your site and call it bilingual.

• It reads as machine-translated, which signals "this business didn't care enough to do this properly" to the exact customer you were trying to reach.
• Search engines don't index it. Auto-translated content is generated in the browser, so it doesn't exist as far as Google is concerned. You get zero SEO benefit in the second language — which was probably the whole point.
• It butchers your terms. Industry vocabulary, product names, and legal language come out wrong in ways you won't notice and your customers will.

If a language matters enough to offer, it matters enough to write.

Translation vs. Actually Writing It

There's a difference between translating a page and writing the page for that audience.

Your English homepage might open with a straightforward value proposition. The Spanish version that converts best might lead with the family-business angle, or a different sense of formality — usted versus tú is a real decision, and getting it wrong makes you sound either cold or unprofessional depending on which way you miss.

Marketing copy — homepage, services, calls to action — should be rewritten for each audience. Everything else — policies, FAQs, technical details — can be straight translation. That split keeps the cost sane while keeping the parts that sell actually persuasive.

Getting the Technical Part Right

If you do build two versions, three things need to be handled or the SEO benefit evaporates:

• Separate URLs for each language. /es/servicios and /en/services, or separate subdomains. Each language needs its own address that a person can link to and a search engine can index.
• hreflang tags telling search engines which page is which language, so Google shows the Spanish page to Spanish searchers instead of guessing.
• A visible language switch that goes to the same page in the other language, not back to the homepage. Getting bounced to the homepage every time you switch is the most common bilingual-site bug I fix.

Detecting a visitor's browser language and redirecting automatically sounds helpful and usually isn't — plenty of people in PR use English-language phones and want the Spanish page. Offer, don't decide.

What I'd Recommend for Most Small Businesses

Pick your primary language — the one your paying customers actually use — and build that properly. Then add a single well-written page in the second language covering what you do, where you are, and how to reach you.

That gets you 80% of the benefit for 20% of the ongoing burden, and you can expand later once you can see from your analytics whether the second language is pulling real traffic.

The full two-version build is the right call when both audiences genuinely buy from you. It's the wrong call when one language is there because it felt like it should be.

Not sure which way your business leans? Tell me who your customers are — I work in both languages and I'll give you an honest read on whether the second version earns its keep.