VDNX
ESLet’s talk

Web design & development·5 min read

How to structure a Spanish and English website

A bilingual website is not a selector that translates one screen. It needs two related journeys, a clear mapping between pages and a process for maintaining them.

Begin by defining two complete journeys

A bilingual website should let someone complete the main task in either language. Before deciding technical labels, walk through the homepage, services, contact route and every conversion step as two related experiences. Translating the navigation while an important page remains in the other language produces an incomplete journey, even when the selector appears to work.

Create an inventory with one row for each page intention and columns for the Spanish URL, English URL, content owner and status. Some pages may not have an equivalent yet. Record that gap rather than silently sending a visitor to a different page that answers another question. The map also reveals the real workload: the project must cover titles, error messages, confirmations, metadata and links, not just body text.

Give every version a stable URL

Google recommends different URLs for each language instead of changing the content at one address according to cookies or browser preferences. A simple structure can keep the primary language at the root and place the second in a directory, such as `/servicios/` and `/en/services/`. Subdomains and other arrangements are also possible; the important point is to choose a rule the team can maintain consistently.

Do not confuse language with country. `es` describes Spanish-language content, while a variant such as `es-ES` adds a region. If the service and content do not change by country, regional versions create extra relationships and maintenance without a clear need. Slugs can be adapted to make sense in each language, provided the content map preserves the relationship between the two URLs.

  • One unique and permanent URL for every page and language.
  • One directory or subdomain rule applied across the site.
  • Readable slugs in the language of the page.
  • No query parameters as the foundation of the language system.

Connect equivalent pages, not just homepages

The language switch should lead to the equivalent of the current page. Sending every service page back to the English homepage makes people start again and can hide information that is already available. If no translation exists, explain that the page is not yet available and offer an identified alternative rather than pretending two unrelated pages are equivalent.

Hypothetical example: a company has `/servicios/mantenimiento-web/` and `/en/services/website-maintenance/`. Both explain the same scope, while their wording and examples are adapted for each audience. The selector connects those pages. A local announcement available only in Spanish should not link to a different English article. It can remain in Spanish with a visible notice, or stay out of the English navigation until a suitable version exists.

Declare the language and alternatives for different purposes

Each document should declare its language on the HTML element with `lang="es"` or `lang="en"`. MDN explains that this makes the language programmatically determinable and helps assistive technology, including screen readers, use the correct pronunciation. A substantial passage in another language can also be marked separately.

To relate localised versions for search engines, a site can use `hreflang` in HTML, HTTP headers or a sitemap. Google treats these methods as equivalent and warns that maintaining several at once can make implementation harder. Every set should include the page itself and all other versions, using complete URLs, and the relationships must be reciprocal. `x-default` can indicate a selector or fallback for unsupported languages, but it does not replace the actual language versions.

Let people choose the language

The selector should be a visible link that works with a keyboard, not an option hidden behind an ambiguous icon. Name each language recognisably, retain the selection where appropriate and allow it to change from any page. A flag represents a country rather than a language; `Español` and `English` usually express the decision more clearly.

Avoid automatically redirecting someone based only on an IP address or an assumption about the browser. Google notes that such redirects can stop both users and crawlers from seeing every variation. A site can suggest an alternative without blocking the current page, perhaps with a quiet notice offering English that can be dismissed. The requested URL should remain available.

Create a paired update process

Technical structure fails when the two versions drift apart. Give each content item a shared identifier, language-specific status, review date and owner. When a price, service condition or form step changes, create work for both pages. Do not publish a new claim in one version and leave the other indefinitely different without acknowledging the difference.

Equivalence does not require literal translation. Facts, limits and the next step should match, while tone and examples can be adapted. Review headings, alternative text, validation messages, automated emails, structured data and internal links too. A page can look translated while still sending visitors to forms or documents in the wrong language.

  • Does every main page have an identified partner or an explained gap?
  • Does the selector preserve context instead of always returning home?
  • Do `lang` and the alternate relationships match the visible content?
  • Do forms, confirmations and links remain in the selected language?
  • Does an important update trigger review of both versions?

Test the journey before adding more languages

Test both versions in a new session, on a small screen and with keyboard navigation. Enter through an internal page, switch language, complete the form and go back. Confirm that URLs respond, strings are not mixed and the sitemap or selected annotations connect the correct pairs. Automated checks can find broken links or missing relationships, but they cannot establish that the writing answers the reader's intention equally well.

With this map, adding a third language stops being a matter of copying a menu and becomes a scope decision. The website is ready when it can maintain complete pages, clear ownership and testable equivalents. If those resources are not available, two well-kept journeys are usually more useful than opening several partial versions.

Sources and documentation

Content created with AI assistance. Check the sources, date and scope of each guide.

Let’s define the next step for your website.

Tell us what your business needs and where your current website falls short. We can help you define the scope.

Let’s talk about your idea