Key takeaways

  • Good multilingual SEO services start with structure: one clear URL per language version, chosen from the options Google documents (country domains, subdomains or subdirectories), not URL parameters.
  • Hreflang tells Google which pages are versions of each other. Google’s rule: “If two pages don’t both point to each other, the tags will be ignored.”
  • Google decides a page’s language from its visible content. It does not use the HTML lang attribute or the URL for that, so the page itself must be in one language.
  • Do not redirect visitors automatically by language. Give them links to the other versions instead.
  • Translation is not enough on its own: each market needs its own keyword research, and often different content.

A multi-language website can look finished to the people who built it and still be confusing to Google: pages in two languages at once, versions that do not point to each other, and visitors bounced to a language they did not choose. Good multilingual SEO services fix those problems in the right order, starting with structure and ending with content written for each market. This article explains what a multi-language site needs, and what to expect from anyone you hire.

I have worked in SEO and digital marketing for more than 16 years, from Bucharest, with clients who work with me remotely. In audits of multi-language sites I see the same few problems again and again, and most of them are structural, not linguistic. The rules below come from Google’s documentation, which I link throughout.

If your site targets countries rather than languages, see my guide for an international SEO consultant on country targeting, and the article on a South Florida SEO company for English and Spanish pages in one local market.

What multilingual SEO services should cover

Google’s page on managing multi-regional and multilingual sites draws a useful line. “A multilingual website is any website that offers content in more than one language.” A multi-regional website, by contrast, “is one that explicitly targets users in different countries.” Many sites are both, for example a Spanish version for Spain and another for Mexico, but the decisions start from that distinction.

The same page says Google Search “tries to find pages that match the language of the searcher.” Everything in a multilingual project serves that goal: making it easy for Google to see which language each page is in, and which pages are versions of the same content.

Area What the work covers What you should receive
Structure URL pattern for each language, navigation between versions A written URL plan and a redirect map if URLs change
Hreflang Annotations for every page that has versions A validated set, with return links checked
Language switching Links to other versions, no forced redirects A switcher every visitor and crawler can follow
Translation and keywords Keyword research per language, review of translated pages A keyword list per market and notes on wording
Market content Prices, contact details, legal pages, examples per market A list of what differs by market and who owns it
Measurement Search Console properties per version Reports you can read for each language

Choosing a URL structure for a multi-language site

The first decision is where each language lives. Google lists four options and, helpfully, the pros and cons of each.

Three page cards, each marked with a different coloured speech bubble, connected to each other by double arrows, with a crossed-out fourth card in a muddled mix of colours
Figure 1. Give each language version its own URL and connect the versions; avoid pages that mix languages or depend on parameters.
Structure Example from Google Pros Google lists Cons Google lists
Country domain example.de “Clear geotargeting”, “Server location irrelevant”, “Easy separation of sites” “Expensive (can have limited availability)”, “Requires more infrastructure”, “Strict ccTLD requirements (sometimes)”, “Can only target a single country”
Subdomain de.example.com “Easy to set up”, “Allows different server locations”, “Easy separation of sites” “Users might not recognize geotargeting from the URL alone”
Subdirectory example.com/de/ “Easy to set up”, “Low maintenance (same host)” “Users might not recognize geotargeting from the URL alone”, “Single server location”, “Separation of sites harder”
URL parameter site.com?loc=de “Not recommended.”, “URL-based segmentation difficult”

Notice that country domains target a country, not a language. A Spanish version for every Spanish-speaking market cannot live on one country domain. For a business whose versions differ mainly by language, subdirectories are usually the simplest choice: one site, one host, one place to maintain. Subdomains make sense when a team or a platform has to be run separately.

Two details matter more than the choice itself. First, keep each page in one language. Google recommends “using a single language for content and navigation on each page” and avoiding side-by-side translations. Second, do not rely on code to tell Google the language. Google is explicit: “We don’t use any code-level language information such as lang attributes, or the URL.” The visible text decides.

Rank Check Reports

Before you restructure language versions, record where your main keywords rank on Google desktop and mobile today, so you can see what the move changed.

A live Google check of your keywords on desktop and mobile · from $14.99 per check · no subscription · report within one working day

Order a rank check report →

Hreflang: telling Google which page is which

Hreflang annotations tell Google that two or more pages are versions of the same content for different languages or regions. Google’s page on localized versions recommends them when content is “fully translated into multiple languages”, when you “translate only the template”, and for “small regional variations”.

There are three ways to add them: in the HTML, in HTTP headers or in a sitemap, and Google says “The three methods are equivalent from Google’s perspective.” Pick the one your platform handles most reliably. For large sites a sitemap is often easier to keep correct than tags in every template.

Two page cards joined by a double arrow with a tick, beside two page cards joined by a one-way arrow with a coral warning mark
Figure 2. Hreflang only counts when the versions point to each other; a one-way link is ignored.

Most hreflang problems I find in audits break one of these rules:

Hreflang rules from Google's documentation

  • Every version lists itself and all the others. Google: “Each language version must list itself as well as all other language versions.”
  • Links go both ways. “If two pages don’t both point to each other, the tags will be ignored.” One missing return link on a template breaks the whole set for those pages.
  • Valid codes only. “Only language codes listed in ISO 639-1 and region codes listed in ISO 3166-1 Alpha 2 are supported.” In audits I often see a region code used without a language code.
  • An x-default for everyone else. “The reserved x-default value is used when no other language/region matches the user’s browser setting.” It usually points to a language chooser or your main version.
  • Hreflang does not set the language. “Google doesn’t use hreflang or the HTML lang attribute to detect the language of a page.” If the page text is in the wrong language, the annotation will not fix it.

Hreflang connects pages that already work in their own language; it cannot make a half-translated page work.

Let visitors choose: no automatic redirects by language

Many sites detect the browser language or the visitor’s location and send them to a version automatically. It feels helpful. Google advises against it: “Avoid automatically redirecting” users between language versions, and “don’t redirect based on what you think the user’s language may be.” The reason is practical: such redirects “could prevent users (and search engines) from viewing all the versions of your site.”

Forced redirects can hide versions from a visitor who wants another language and from a crawler that always arrives from the same place. Google’s suggestion is simpler: “Consider adding hyperlinks to other language versions of a page.” A visible language switcher, with plain links to the matching page in each language (not to each home page), lets people and crawlers reach every version.

A banner that suggests another language without moving the visitor is a reasonable middle ground. The visitor stays where they landed and decides.

Translation quality and local keyword research

This is where multilingual SEO services differ most in quality. A translated page is only useful if it reads as if someone wrote it for that market, and if it uses the words people there actually search with.

A page card on the left feeding into three separate page cards through three different magnifying glasses, each card with its own coloured accent
Figure 3. Each language needs its own keyword research; translating one keyword list rarely matches how people search in another market.

Google’s documentation gives two warnings worth taking seriously. First, “Translating only the boilerplate text of your pages while keeping the bulk of your content in a single language” can create a poor experience. A translated menu around English text is not a translated page. Second, Google’s spam policies list, as an example of scaled content abuse, “Scraping feeds, search results, or other content to generate many pages (including through automated transformations like synonymizing, translating, or other obfuscation techniques)”. Translating at scale to fill a site with pages, without adding value, comes close to the pattern Google describes.

What I recommend instead:

  1. Research keywords in each language from scratch. A literal translation of an English keyword is often not what people type. Regional words, formal and informal forms, and borrowed English terms all vary.
  2. Brief a fluent writer or reviewer, not only a translator. Give them the keyword list, the purpose of the page and the questions buyers in that market ask.
  3. Translate titles, meta descriptions, alt text and structured data too. These are often left in the original language.
  4. Start with the pages that matter. It is better to have twenty strong pages in a new language than two hundred weak ones.

Free tool · Ping My URL

Published or corrected a language version of a page? Let search engines know the URL has changed.

Notify Google and other search engines about up to 5 new or updated URLs at once. Free, no sign-up.

Ping your URLs →

Content that differs by market

A multilingual site often serves different markets, and the content has to follow. Prices and currencies, delivery or service areas, contact numbers, opening hours, legal pages, payment methods and even the examples in a guide can differ. When two versions in the same language serve different countries, Google’s advice is to pick a preferred version and use canonical tags and hreflang where the content is similar or duplicated.

The practical problem is ownership. When the main site changes, who updates the German and French versions? In audits I often find language versions that stopped being updated soon after launch, with old prices or old products. A short table that lists, for each market, what differs and who updates it prevents that. If nothing differs and nobody will maintain a version, it may not be worth building.

Search Console for each language version

You cannot manage what you cannot measure, and a multilingual site is easier to read in Search Console when each version has its own view. Google’s help page on adding a property explains the two types. A Domain property “Includes all subdomains (m, www, and so on) and multiple protocols”, and it needs DNS verification. A URL-prefix property “Includes only URLs with the specified prefix”, and that includes any subfolder under it.

Your structure Properties I would set up
Subdirectories (example.com/de/) One Domain property, plus a URL-prefix property for each language folder
Subdomains (de.example.com) One Domain property, plus a URL-prefix property for each subdomain
Country domains (example.de) A separate Domain property for each domain

The page notes that “You can have up to 1,000 properties in your Search Console account”, so there is room for even a large set of versions. With a property per version you can see which language has indexing problems, which queries each version appears for, and whether a change on one version affected the others.

Free tool · SEO ROI Calculator

Estimate what a keyword in a new language could be worth before deciding how much translation and content work that market deserves.

Enter search volume, CPC and your current ranking to estimate traffic, revenue and value for a keyword. Free.

Calculate your SEO ROI →

Choosing a multilingual SEO agency or consultant

Whoever you hire, the first conversation should show they know the basics above. These are the questions I would ask, myself included:

  1. Which URL structure do you recommend for us, and why? A good answer weighs your markets, platform and team, not a fixed rule.
  2. How will you check hreflang return links across the whole site? Ask to see how they report errors.
  3. Do you redirect visitors by language? The answer should be no, with a switcher instead.
  4. Who does keyword research in each language? It should be someone fluent in that language, not only a translation of your English list.
  5. Who reviews translated pages before they go live? Someone fluent, with the brief in hand.
  6. How will we measure each version? Search Console properties per version, at least.

Be wary of anyone who promises rankings in every language at once. My SEO website structure page explains how I plan site architecture, including language versions.

FAQ

What do multilingual SEO services include?

They usually cover the URL structure for each language, hreflang annotations, language switching without forced redirects, keyword research and review in each language, market-specific content and Search Console set-up per version. The order matters: structure first, content after.

What should a multilingual SEO agency fix first?

Usually the structure and the hreflang set, because errors there affect every page. Pages that mix languages, missing return links and automatic language redirects come before new content.

Is machine translation enough for multilingual SEO?

Not on its own. Google’s spam policies name automated translation among the techniques in their examples of scaled content abuse, where many pages are generated with little value for users. A fluent reviewer working from a keyword brief is the minimum I would accept for important pages.

Do I need a separate Search Console property for each language?

It is not required, but it helps. A URL-prefix property for each language folder or subdomain lets you read indexing and query data for each version separately.

Eugen Platon

Eugen Platon

Director of SEO & Web Analytics at onwardSEO
Eugen Platon is a highly experienced SEO expert with 16+ years of experience propelling organizations to the summit of digital popularity. Eugen, who holds a Master's Certification in SEO and is well-known as a digital marketing expert, has a track record of using analytical skills to maximize return on investment through smart SEO operations. His passion is not simply increasing visibility, but also creating meaningful interaction, leads, and conversions via organic search channels. Eugen's knowledge goes far beyond traditional limits, embracing a wide range of businesses where competition is severe and the stakes are great. He has shown remarkable talent in achieving top keyword ranks in the highly competitive industries of gambling, car insurance, and events, demonstrating his ability to traverse the complexities of SEO in markets where every click matters. In addition to his success in these areas, Eugen improved rankings and dominated organic search in competitive niches like "event hire" and "tool hire" industries in the UK market, confirming his status as an SEO expert. His strategic approach and innovative strategies have been successful in these many domains, demonstrating his versatility and adaptability. Eugen's path through the digital marketing landscape has been distinguished by an unwavering pursuit of excellence in some of the most competitive businesses, such as antivirus and internet protection, dating, travel, R&D credits, and stock images. His SEO expertise goes beyond merely obtaining top keyword rankings; it also includes building long-term growth and optimizing visibility in markets where being noticed is key. Eugen's extensive SEO knowledge and experience make him an ideal asset to any project, whether navigating the complexity of the event hiring sector, revolutionizing tool hire business methods, or managing campaigns in online gambling and car insurance. With Eugen in charge of your SEO strategy, expect to see dramatic growth and unprecedented digital success.
Eugen Platon
Check my Online CV page here: Eugen Platon SEO Expert - Online CV.