A bilingual website needs two complete customer journeys. Someone arriving on a Spanish service page should understand the offer, read supporting information, and contact the business in Spanish. The English version needs the same care. Translating the navigation while leaving the important details in another language creates an unfinished experience.
For bilingual website SEO, begin with useful localised pages at stable URLs. Connect equivalent translations, make the language choice visible, and check that each version answers the questions its audience actually asks.
Give each language a clear address
A simple structure for an English and Spanish business website is English at the root and Spanish under /es/. For example, /services/ and /es/servicios/ can represent the same service overview. Keep that pattern consistent across the site.
Google recommends separate URLs for different language versions. Let visitors switch language through visible links instead of forcing them into a version based on their location. A person travelling abroad may still want their usual language.
Build a page map before development. List each English address beside its Spanish equivalent, its purpose, and the person responsible for the text. Mark genuinely untranslated pages as missing rather than pretending that an unrelated page is an equivalent.
Connect translations without merging them
The hreflang annotation identifies language alternatives. For a paired page, include the English and Spanish addresses in both versions, including each page’s own address. Google requires reciprocal links and fully qualified URLs, as explained in its localised-page documentation.
Canonical links serve a different purpose: identifying a preferred URL among duplicate or similar pages. A complete Spanish translation should normally identify its own preferred Spanish address. Google’s canonical guidance recommends a canonical in the same language when using hreflang.
Make this relationship part of the content model. Pair articles with a stable translation key, even when their slugs differ. That gives the language switcher a reliable destination when a title or address changes.
Localise the buyer’s questions
Begin each version with the same business facts, then review how a local customer would describe the problem. An English article about “off-the-shelf software” might naturally become an article about “software estándar” in Spain. A literal translation is only useful if readers actually understand it.
Review service names, examples, units, dates, calls to action, and form messages. If a service has different availability or conditions in a market, state those differences clearly. Do not create the impression of a local office or support team that does not exist.
Ask a fluent reviewer to complete a task using only one language. Can they find the right service, understand what happens next, and submit an enquiry? This catches awkward translations that a paragraph-by-paragraph review can miss.
Check the page a visitor actually receives
Before launch, inspect a representative service page and article in each language. Use this short review sheet:
- Does the title describe this particular page in the correct language?
- Is there one clear main heading and a useful introduction?
- Does the language switch open the equivalent page?
- Do internal links stay in the selected language where a translation exists?
- Are image descriptions, errors, and contact instructions understandable?
- Do canonical and language-alternative links use the final production domain?
- Can search engines access the pages you intend to publish?
Test on a phone as well as a desktop. Compress images, reserve space for media, and avoid loading an interactive component when plain content will do. Google uses Core Web Vitals in its ranking systems, while explicitly stating that good scores do not guarantee high rankings. Performance is part of a useful website, not a substitute for relevant content.
Maintain both versions after publication
Assign one owner to each translation pair. When pricing, services, or contact details change, update both pages in the same task. Review language links when an article is renamed or removed, and maintain an explicit replacement if its address changes.
Evaluate each language separately using search queries, relevant enquiries, and the questions prospects still ask. A page can attract visits without helping the right customer decide. Record changes and allow enough observation time to distinguish a useful improvement from a short fluctuation.
If publishing changes requires too much manual work, map the process using our automation guide. Keep editorial review in the workflow so convenience does not turn into inconsistent translations.
A well-structured bilingual website gives each audience a complete experience and gives search engines clearer signals. It cannot guarantee visibility. Start by checking one important page in both languages, then apply the same standard across the site.