Bilingual Websites Done Right: Serving Spanish Speakers

A bilingual nonprofit website is not finished when the homepage has been translated.

The real test is whether a Spanish-speaking visitor can complete the same important tasks as an English-speaking visitor: understand the services, decide what to do next, fill out a form, make a donation, find contact information, and receive confirmation in the same language.

That requires translation, but it also requires UX, governance, and technical implementation.

Translation and localization are related, but different

Translation focuses on carrying meaning from one language into another. Localization goes further: terminology, tone, examples, formatting, calls to action, and cultural context may need to change so the experience makes sense for the intended audience.

Recommendation: for routine marketing copy, treat machine translation as a first draft only. For benefits, health, safety, or other high-stakes information, use a qualified reviewer who understands both the language and the subject matter.

Do not turn “human reviewed” into a checkbox. The reviewer should know what they are reviewing for.

Make the language switch easy to find

A user should not have to understand the current language to figure out how to change it.

A practical pattern is a visible text control such as:

English | Español

Keep it available on mobile and desktop.

Google Search Central suggests adding links to other language versions of a page so users can choose one, and advises against automatically redirecting users from one language version to another based on what you think their language may be.

Source: Google Search Central, Managing Multi-Regional and Multilingual Sites. Google Search Central: managing multi-regional and multilingual sites

Keep people in the language they selected

If a visitor selects Spanish, the experience should not unexpectedly return to English when they:

• open a program page,
• fill out a form,
• encounter an error,
• donate,
• receive a confirmation message,
• download an important resource.

This is where a bilingual website can become fragmented.

Audit journeys, not just pages.

Prioritize by user need when budget is limited

A fully multilingual content program can be a big project. If you need to phase it, prioritize pages based on who needs them and what is at stake.

For an organization serving Spanish-speaking communities, a reasonable first tier often includes:

• homepage or primary landing page,
• programs and services,
• how to get help,
• intake or appointment forms,
• contact information,
• key resource and service information,
• donation flows if Spanish-speaking donors are part of the audience.

Lower-priority institutional content may follow later.

That prioritization is a strategy decision, not a universal rule. Use analytics, community feedback, and program knowledge to set the order.

Do not rely on a translation widget as your entire strategy

Browser and machine-translation tools may help some visitors, but they do not give you control over accuracy, search visibility or the full journey the way organization-owned Spanish pages do.

If your most important pages are only accessible through an automatic overlay, ask:

• Can staff review and correct the translated text?
• Are forms and validation messages translated?
• Are PDFs translated?
• Can Spanish pages rank independently in search?
• Can you control Spanish titles and descriptions?
• Does the translation persist throughout the journey?

If the answer is no, the system may be useful as a fallback but insufficient as the core bilingual experience.

Build multilingual SEO intentionally

Google’s guidance on localized versions says each language version must list itself as well as all other language versions (the hreflang annotations).

Recommendation: do not simply translate English keywords word for word. People may search differently in different languages and communities.

For Spanish pages:

• research actual Spanish-language queries,
• write Spanish titles and meta descriptions,
• use descriptive Spanish headings,
• link internally between relevant Spanish pages,
• make sure search engines are allowed to index the page,
• implement hreflang correctly where appropriate.

Source: Google Search Central: localized versions of your pages

Decide how your organization will write Spanish

Your audience may use different terms and levels of formality depending on country, region and community, so you may need to choose a voice deliberately.

Make deliberate choices about:

• formal versus informal address,
• preferred terms for programs and services,
• whether technical terms need plain-language explanations,
• whether certain content should be adapted for a local audience rather than literally translated.

Then document those decisions in a short language guide so the site stays consistent as new pages are added.

Treat imagery with the same care as language

A bilingual site can still feel disconnected from the community if the photography and examples feel generic or tokenized.

Whenever possible, use real, consented imagery from the organization and its work. When stock photography is necessary, choose it deliberately and avoid turning ethnicity into a visual prop.

Representation should support the story rather than stand in for one.

Build an ongoing content workflow

Launch is one step. Keeping both versions current afterward is the ongoing work.

Define:

1. Who creates the source content?
2. Who translates or localizes it?
3. Who reviews it?
4. Who publishes both versions?
5. What happens when only one version is updated?

A simple status field in your content workflow — English ready / Spanish ready / both published — can prevent the two versions from quietly drifting apart.

Bilingual website checklist

• Clear language switcher on desktop and mobile
• Stable language choice as people navigate
• Separate language URLs where appropriate
• hreflang implemented correctly
• High-priority user journeys complete in both languages
• Forms, errors, confirmations, and emails included
• Qualified review for high-stakes content
• Spanish-specific search research and metadata
• Language and terminology guide for staff
• Correct language attributes and form labels in each language
• Ongoing translation workflow after launch

The goal is equal access to the important parts of the experience

A bilingual website does not need to pretend that every page has the same priority on day one.

It does need to be honest about what is translated, deliberate about what comes first, and reliable when a Spanish-speaking visitor is trying to accomplish something important.

Related: 10 website problems worth checking first.