Multilingual Website SEO: How to Set Up English and Spanish

Multilingual website SEO means giving every language version of your site its own crawlable URL, its own keyword research and its own signals, so Google can match each page to the right searcher. For a U.S. business, that usually means English and Spanish. Do five things well: use separate URLs, add hreflang, research keywords in each language, write for the local reader, and check indexing in Search Console.

TL;DR

Give each language its own URL, such as /es/ subfolders, and keep one language per page.
Add hreflang so every version lists itself and all its alternates, plus an x-default.
Research Spanish keywords from scratch. Do not translate your English list.
Let visitors choose their language. Do not force a redirect.
Check each version in Google Search Console after launch.

What multilingual SEO actually is

A multilingual site is any site that offers content in more than one language. Google says it tries to find pages that match the searcher's language. So your job is to make each version easy to find, easy to tell apart and easy to trust.

It is not the same as targeting countries. A Spanish page for U.S. readers is a language decision inside one country. Search Engine Land separates international SEO (consistency across shared languages) from multilingual SEO (nuance in each language). Both need clean technical SEO to avoid confusion between pages.

Does it help rankings? Search Engine Journal reports that Google does not officially confirm language as a ranking factor. Still, content in the searcher's language likely matters for queries in that language. That is the point of a Spanish version: you show up for searches your English pages can never win.

Choose your URL structure first

This is the hardest decision to undo, so make it early. Martin Splitt of Google's Search team has described three common options: country-code domains, subdomains and subdirectories. Each has pros and cons.

For most U.S. businesses serving English and Spanish speakers, we suggest subfolders:

Option	Example	Best for
Subfolder	example.com/es/	Most small and mid-size businesses
Subdomain	es.example.com	Large sites with separate teams
Separate domain	example.mx	Targeting a specific country

Subfolders keep your authority on one domain and are simple to maintain. Search Engine Land also recommends consistent URL patterns, like /fr/ and /es/, to reduce crawl complexity.

If you do run separate domains per country, plan your domain routing carefully. A guide to country-specific URL redirects covers how that routing works.

Google also recommends different URLs for each language version rather than cookies or browser settings. Googlebot usually crawls from the U.S. and does not send a language preference, so a cookie-based page may never be seen.

Set up hreflang the right way

Hreflang tells Google which page belongs to which language. Google's documentation sets out the rules:

Each language version lists itself and every other version.
Alternate URLs are fully qualified, with the https:// and the domain.
An x-default page can catch visitors whose language you do not serve.
You can use HTML tags, HTTP headers or a sitemap. They are equivalent, and using all three adds no benefit.

For a U.S. English and Spanish site, your English page would carry en-US, es-US and x-default entries. The Spanish page carries the same set. The codes combine language and region, so es-US means Spanish for the United States.

Keep canonicals consistent. Each page should point to itself, so /en/ is canonical to /en/ and /es/ to /es/. Never canonicalize the Spanish page to the English one. That tells Google the Spanish page is a duplicate, and it can drop it.

Do keyword research in Spanish, not translation

This is where most bilingual sites lose. Search Engine Land notes that direct keyword translation rarely works, because people do not express needs the same way across languages. Start from intent, then look at how people search.

Here is a process you can follow:

List what each page must do for the customer, such as book a quote or call.
Ask a native Spanish speaker how they would search for it. Expect several phrases per topic.
Check the top results on Google for those phrases. See who ranks and what they offer.
Build a separate keyword target for each language version of each page. Do not assume a one-to-one match with English.
Review your local competitors' pages with an SEO competitor analysis to find gaps in the Spanish results.

In the U.S., mixed phrasing is also real. Many people search with a blend of Spanish and English. If your own search data shows it, write pages that include those natural phrases.

Design the site for real people

SEO gets people to the page. Design keeps them there. The U.S. government's Digital.gov guidance is a good baseline:

Put the language switcher in the global navigation, at the top right.
Let users toggle to the matching page, not the home page.
Show each language by its own name: Español, English.
Test with the audience you are writing for, since the experience should feel culturally relevant.

The same guidance strongly discourages machine translation as the only method. If you use translation software, have a qualified language professional review the text before it goes live.

Two more rules from Google. It uses the visible content of a page to decide the language, not the lang attribute or the URL. And it recommends one language per page, so avoid side-by-side translations.

Do not redirect visitors by guess. Splitt advises against forcing users to a version. Linking to each version gives people a choice and helps Googlebot find the pages.

Localize the details too. Swap images, examples, phone prompts and calls to action when they do not fit the Spanish-speaking customer. Titles, meta descriptions, alt text and internal links all need a Spanish version.

Perspective

We build bilingual sites for business owners in Canada and the US. The same mistake shows up often. Someone treats the Spanish version as a copy job at the end of a project.

We think it works better as part of the build. Plan the URLs, the language switcher and the page templates before a word is translated. Then both languages get the same care, and nothing has to be rebuilt later.

We also like to keep you in the loop from the first sketch to launch. You see the structure, you approve the keyword map, and you know why each page exists. That is how a second language becomes a real source of customers instead of a duplicate of your site.

Loic

Check that each version is indexed

After launch, verify. Open Google Search Console and inspect a few URLs in each language. Compare the user-declared canonical with the one Google selected. They should match.

Watch the indexing report for pages that Google says are duplicates of another page. Pages in the other language may show as alternates with a proper canonical tag. That is normal. The problem is when Google picks the wrong language as canonical, which usually points to missing self-canonicals or incomplete hreflang.

Fix, resubmit your sitemap, then give it time. Reindexing can take days to a couple of weeks.

Mistakes to avoid

Search Engine Land lists the usual ones: skipping market research, assuming your authority and links carry over, translating before doing keyword research, ignoring internal links in localized content and thinking only about text.

Add to that list: incomplete hreflang sets, a Spanish page canonicalized to English, and a language picked by IP address with no way to switch. Each one hides a language version from Google or from the visitor.

Also be selective. Translate the pages that earn customers first: services, location pages, contact and your top articles. Add the rest as you can maintain quality.

Work with us on your bilingual site

We are an independent studio in Kelowna and Vancouver, BC. We design and build custom websites, including bilingual sites, and we handle the technical SEO setup that goes with them. You can read about our SEO implementation work or see everything we do on our services page.

Tell us who you want to reach and in which languages. We will scope the structure, the pages and the SEO setup with you, and quote the project to fit.

FAQ

Is a multilingual website good for SEO?

It can be. A page in the searcher's language is more likely to match their query, and Spanish pages let you compete for searches your English pages cannot. It works when each version has its own URL, its own keywords and correct hreflang.

How do I handle multiple languages on one website?

Give each language its own URL, usually a subfolder like /es/. Keep one language per page, add a visible switcher, and link each page to its equivalent in the other language. Add hreflang so Google connects the versions.

Should I use automatic translation?

Not on its own. Digital.gov advises having a qualified language professional review any machine translation before it is published. Spanish copy that reads naturally also earns more trust from customers.

Do I need hreflang for an English and Spanish site?

Yes, if both versions cover the same content. Hreflang tells Google which version fits which searcher. Each page should list itself and its alternates, with fully qualified URLs.