Multilingual SEO: How to Rank a Website in Two Languages

Multilingual SEO is the work of making each language version of your website discoverable to people searching in that language. In practice it means five things: give every language its own URL, keep each page in a single language, connect the versions with hreflang, research keywords natively in each language, and let visitors switch languages instead of redirecting them. Do those and Google can find, understand and serve each version. Skip any one and translated pages tend to sit in the index without impressions, or never get indexed at all.

This guide is for small businesses and SaaS teams adding a second language. It sets out the rules that matter, where machine translation fits, and the mistakes that most often keep a second language invisible.

What is multilingual SEO?

Multilingual SEO is optimising a site that offers content in more than one language so that each language version ranks for searchers using that language.

Google draws a useful line between multilingual and multi-regional sites in its guide to managing multi-regional and multilingual sites. A multilingual site offers content in more than one language, such as a Canadian business with English and French versions. A multi-regional site explicitly targets users in different countries, such as a manufacturer shipping to both Canada and the US. Many sites are both.

The distinction matters because it changes what you build:

If you are adding a language, think multilingual first and add regions only when the content genuinely differs by country. The broader market and structure decisions sit in a full international SEO strategy.

Five rules that make a multilingual site rankable

Five technical and editorial rules decide whether Google can see, understand and correctly serve each language version.

1. One URL per language. Google recommends separate URLs for each language version rather than swapping content with cookies or browser settings. Googlebot usually crawls from the US and sends requests without an Accept-Language header, so content that changes by browser language may never be crawled. A subdirectory such as /es/ is the simplest choice for most small sites.

2. One language per page. Google determines a page's language from its visible content, not from the lang attribute or the URL. Keep the body, navigation, buttons and metadata in the same language. Side-by-side translations and English menus on Spanish pages make the signal ambiguous.

3. Connect versions with hreflang. hreflang tells Google that /pricing and /es/precios are the same page for different languages. Each version lists itself and every alternate, and every link must be reciprocated. The full syntax and the errors to avoid are in the hreflang tags guide.

4. Translate everything that shows in search. Title tags, meta descriptions, image alt text, structured data and, ideally, URL slugs belong in the page's language. Google says localized words in URLs are fine, as long as you use UTF-8 and escape URLs properly. An English title on a Spanish page undermines both relevance and click-through.

5. Let users choose, never force. Google advises against automatically redirecting users to a language version based on what you think their language is. Add a visible language switcher on every page, linking to the equivalent page rather than the other language's home page.

Should you machine-translate your website?

Machine translation is a reasonable first draft for multilingual SEO, but publishing it unedited at scale is a risk to both rankings and conversions.

Google's spam policies describe scaled content abuse as generating many pages that provide little value to users, and they list "automated transformations like synonymizing, translating" among the examples. That does not make translation spam. It does mean that pushing hundreds of raw auto-translated pages, with no editing and no added value, matches the pattern the policy targets.

There is also a simpler commercial problem. A literal translation targets the words your home market uses, which are often not the words people search for in the new language. You end up with grammatically correct pages ranked for terms nobody types.

A practical middle path:

• Machine-translate as a draft for long, stable pages such as documentation or policies.
• Research keywords natively before writing titles, headings and key pages. The free methods in keyword research without tools work in any language when you search from the target market.
• Have a fluent speaker edit every page that matters commercially, especially product, pricing and landing pages.
• Fact-check numbers, units and legal references, which translation engines carry over unchanged even when they are wrong for the new market. A routine for fact-checking AI-written articles applies just as well to translated ones.

Also know that Google may already show your pages to speakers of other languages. Its translated results feature can translate the title and snippet of a result into the searcher's language and open a machine-translated view of the page. That is a bonus, not a substitute: the visitor sees an automatic translation of your page, not a page written for them.

How should you structure the content plan?

Start with the pages that already earn money in your main language, localise those properly, and expand from there.

Translating the whole site at once is tempting and usually wasteful. Most sites get most of their leads from a small set of pages. Localise those first: home page, main product or service pages, pricing, and the blog posts that already bring in sign-ups. Then add new content written for the second market from its own keyword research, not just translated from your archive.

Keep the language versions in sync. When you update the English pricing page, the Spanish one should change in the same release. Out-of-date translations quietly erode trust, and a page whose alternates disagree on price or features creates support work.

Decide early whether every article needs a counterpart. Not every blog post deserves a translation. A post about a US tax deadline has no value in Spain. Only pair pages that make sense in both markets, and only add hreflang between real equivalents.

Common multilingual SEO mistakes

Most multilingual sites fail for the same few reasons, and each is easy to check in an afternoon.

• Language switching without separate URLs. If /pricing shows English or Spanish depending on a cookie, Google sees one version, usually English.
• Automatic redirects by IP or browser language. These can stop Googlebot from reaching your other versions. Use a switcher or a dismissible banner.
• Missing or one-way hreflang. Unreciprocated pairs are ignored, so Google may show the English page to Spanish searchers.
• Canonical tags pointing to the original language. This tells Google the translation is a duplicate. Each version should canonicalise to itself.
• Half-translated pages. Translated body text under an English title, menu and footer sends a mixed language signal.
• Translated keywords nobody searches. Keywords must come from research in the target language, not from a dictionary.
• Language switcher links to the home page. A visitor reading your English pricing page who clicks "Español" should land on the Spanish pricing page, not the Spanish home page.
• Publishing and forgetting. Translations drift out of date as the original changes. Build updates into the release process.

If you fix only two, fix the URLs and the hreflang. Without separate crawlable URLs and correct annotations, nothing else in multilingual SEO can take effect.

Frequently Asked Questions

What is the difference between multilingual and international SEO?

Multilingual SEO focuses on serving content in several languages so each version ranks for searchers in that language. International SEO is broader: it covers targeting different countries, choosing domain structures, localising prices and legal details, and measuring results by market. A multilingual site may serve one country in two languages, while an international site may serve many countries in one language.

Does Google penalise translated content?

Google does not penalise translated content as such. Properly translated pages are not treated as duplicates of the original. The risk comes from publishing large volumes of unedited automated translations that add little value, which Google's spam policies list as a form of scaled content abuse. Edited, localised translations with their own URLs and hreflang are standard practice.

Should translated pages have translated URLs?

Translated URL slugs are optional but helpful. Google says localized words in URLs are fine, provided you use UTF-8 encoding and escape URLs correctly. A slug in the page's language reinforces relevance for searchers and looks more trustworthy in results. Keep the language folder, such as /es/, consistent so the structure stays easy to manage and audit.

Do I need a separate sitemap for each language?

No. One sitemap can contain every language version, and Google accepts hreflang annotations inside it as an alternative to HTML tags. Some sites prefer a sitemap per language folder because it makes indexing problems easier to spot in Search Console. Either approach works, as long as every localized URL is included and each one returns a 200 status.

How many languages should a small business start with?

Start with one additional language, chosen from evidence such as existing visitors, customers or sales from that market. Each language needs its own keyword research, editing and ongoing updates, so adding several at once spreads a small budget thin. Prove the second language brings leads or revenue before investing in a third.

Where to start with multilingual SEO

Good multilingual SEO is mostly discipline: one URL per language, one language per page, reciprocal hreflang, native keyword research, translated metadata and a switcher instead of redirects. Start with the pages that already earn money, localise them with a fluent editor, and add a second-market content plan built on that market's own searches.

Keeping two languages in step every month is where small teams usually fall behind. Agent Solo's Growth plan publishes in two languages with hreflang, canonicals and per-market keyword research built in, and Scale goes up to five languages. If your second language is still not ranking, join the early access list.