You install the plugin in four minutes. A little flag appears in the corner of the site, and anyone who clicks it sees every page in Spanish. It feels like the job is done. Six months later, you realize not one new client has found you by searching in Spanish.
That is how it usually goes with website translation plugins. The button works. The marketing does not.
If you run a business where a real share of your customers speak Spanish at home, this is worth ten minutes. The difference between a translate button and an actual Spanish website is the difference between being readable and being found.
What a translation plugin actually does
Most free translation widgets work in the visitor’s browser. Someone lands on your English page, clicks the flag, and a script swaps the words on screen. Nothing new exists on your server. There is no Spanish page at its own address for Google to crawl, so there is nothing for Google to rank.
That matters because a Spanish speaker looking for help does not usually start on your site. They start on Google, and they search in Spanish. If your site has no Spanish pages, it never appears in those results, no matter how good the translate button is.
Some paid plugins do create separate Spanish URLs, and that is a real step up. But they still lean on machine translation by default, and most owners never go back and fix it. The pages exist, and they read like they were assembled rather than written.
What Google says about language versions
Google’s own guidance on managing multilingual sites is clear on two points. It recommends a different URL for each language version rather than switching languages with cookies or browser settings. And it warns against automatically redirecting visitors from one language to another, because Google’s crawler may never see the other versions.
Read that against how most widgets work and the problem is obvious. One URL, language swapped in the browser, nothing separate for Google to index.
The three places a translate button loses customers
1. Search
Spanish searches are not English searches in a different order. Someone looking for an injury lawyer types abogado de accidentes. Someone with a toothache types dentista cerca de mí. Those searches have their own results pages, and a site with no Spanish URLs is simply absent from them.
2. Trust
A native speaker spots machine phrasing in a sentence or two. A legal term rendered literally, a dental procedure named the way nobody says it, a button that reads oddly. For a business asking someone to trust it with a case or their health, that first impression is expensive.
3. The handoff
This is the one owners miss. The page is in Spanish, but the contact form, the error messages, the confirmation email and the booking calendar are still in English. The visitor gets three steps from calling you and hits a wall. Most bilingual sites that underperform lose people right here.
What a real Spanish website includes
- Spanish pages at their own URLs, usually under /es/, one for every important English page.
- Copy written for Spanish search terms, not a word-for-word conversion of the English.
- Hreflang tags that tell Google which pages are language versions of each other.
- A Spanish path all the way through: forms, buttons, thank-you pages and the emails that follow.
- Spanish signals off the site, including your Google Business Profile services and replies to Spanish reviews.
None of that is exotic. It is just more work than a plugin, which is why most competitors skip it.
When a plugin is fine
To be fair to the plugins: if your Spanish-speaking customers already know you and only need to read your hours or your policies, a translate button is better than nothing. It costs almost nothing and it helps existing customers.
The moment you want Spanish speakers to find you, though, a plugin is the wrong tool. Finding happens in search, and search needs real pages.
The upside nobody is chasing
Here is the part worth getting excited about. In most of the cities we work in, the Spanish results for professional services are thin. Plenty of firms have a flag in the corner. Very few have Spanish pages that answer real questions.
That gap is the opportunity. A business that builds proper Spanish pages is often competing against a handful of sites instead of hundreds.
How we build it
We build the Spanish side of a site as real pages, written for how Spanish speakers search, connected to the English pages with hreflang, and carried all the way through the forms. A fluent reader on your side approves every page before it goes live. You can see the full approach, past projects and pricing on our bilingual websites page.
Which pages to build in Spanish first
You do not need to translate all 80 pages on day one. Start where the money is.
- The homepage. It sets the tone and anchors the Spanish side of the site.
- Your top service pages. The two to five services that bring in most of your revenue, or the ones your Spanish-speaking clients ask about most. For a law firm that might be criminal defense or immigration-adjacent work. For a dental office, cleanings, emergencies and the treatments families ask about.
- Contact and booking. Every form, every confirmation, every thank-you page.
- The answers your front desk gives in Spanish every week. Ask whoever answers the phone. Their list of repeat questions is your first Spanish content plan.
The blog and the deep pages can follow. A tight Spanish site that answers real questions beats a sprawling one nobody reviewed.
Search the way your customers actually talk
Spanish is not one market. A family in Dallas, a family in New Orleans and a family in Miami may use different words for the same thing, and their searches follow how they speak. Good Spanish copy does three things a plugin cannot:
- It uses the terms people type, which are sometimes English loanwords and sometimes not. Plenty of searches mix both languages in one phrase.
- It picks a register on purpose. Formal “usted” is the safe default for legal and medical work. A salon or a casual brand might go warmer.
- It keeps names, prices and phone numbers identical across both languages, so Google and your customers see one business, not two.
Before anything is written, list the main searches for each service in Spanish and check them against what real Spanish speakers on your team or among your clients would say. That short list drives everything else.
The technical mistakes that quietly undo the work
The language switch sends people home
A visitor on your English page about root canals clicks “Español” and lands on the Spanish homepage. They have to start over. The switch should go to the matching page in the other language.
Hreflang that only points one way
Language tags need to be set on both pages, each pointing at the other. When only one side declares the relationship, the signal tends to get ignored.
Half the page stays in English
Menus, footer text, image alt text, the cookie banner, the page title in the browser tab. These get missed constantly, and a native reader notices.
The Spanish side goes stale
The English page gets a new price or a new service and the Spanish page never hears about it. Decide up front who updates both, and treat a change to one language as a change to two.
Who should write and review it
Machine translation is a reasonable first draft. It is not a finished page. The pattern that works is a draft written for Spanish search terms, then a review by a fluent reader who knows your business, ideally someone who talks to your Spanish-speaking clients every week. For legal and medical sites, keep a short glossary of terms you always translate the same way, so a procedure or a charge is named consistently across every page.
We have built bilingual sites for firms including GreenClark Law Firm and Sinclair Law, both of which serve clients in English and Spanish. On legal sites especially, the review step is not optional.
What it costs
A proper Spanish version of a small site starts from $2,000. Sites with a blog archive to carry over start from $3,500. Keeping the second language current runs from $150 a month per extra language, which covers the steady trickle of updates that would otherwise leave the Spanish side behind.
Quick answers
Should the Spanish site use /es/ or a separate domain?
For most local businesses, a /es/ folder on the same domain is the simplest and keeps all your authority in one place.
Can I keep the plugin while the real pages get built?
Yes. Remove it once the real Spanish pages go live, so visitors are not offered two competing versions.
Will Spanish pages hurt my English rankings?
No. Properly tagged language versions are separate pages for separate audiences. They do not compete with each other.
Wondering what your site shows in Spanish?
Send us your site and we will check what Google sees in both languages, and whether a Spanish version would be worth it for your market.
Get a free review of your site
Matthew Martin is a digital strategist specializing in high-performance web design, brand development, and technical SEO. As Creative Director at Spade Design, he bridges the gap between aesthetic excellence and Google search compliance, engineering resilient digital presences that prioritize user experience and hold their visibility through major algorithm shifts.