Multilingual SEO for SaaS: hreflang, URLs and untranslated pages

How to run multilingual SEO for a SaaS: URL structure, hreflang, untranslated pages, canonicals and a checklist to catch leaks before they get indexed.

The short answer

Multilingual SEO for a SaaS comes down to four things: one URL per language, hreflang that links every version to every other version, a canonical that points to the page itself, and no language URL that serves content in another language. Most of the damage I see comes from the last one.

Start with the URL structure

Give every language its own URL.

  • Subdirectories (/en/, /es/) are the easiest to run. They keep everything on one domain and one set of authority.
  • Subdomains and country domains work, but each one is closer to a separate site to maintain.
  • One URL that changes language by cookie, IP or browser setting is the option to avoid. A crawler sees one version, and visitors cannot link to the one they want.

Do not redirect visitors automatically by IP or browser language. Suggest a language with a banner and let them choose. Crawlers mostly arrive from one location, so automatic redirects can hide your other versions from them.

Set up hreflang so it holds

Hreflang tells search engines which page is the equivalent in which language. It is a signal, not a command. The rules that matter:

  1. Each page lists all its alternates, including itself.
  2. Every alternate links back. A link without a return link may be ignored.
  3. Use valid codes: a language (en) with an optional region (en-US).
  4. Add an x-default for the page you want as the fallback, usually the language selector or the English version.
  5. Keep it in one place, the head, the HTTP headers or the sitemap, and keep it consistent with the page.

If a page has no translation, do not give it an hreflang that points at a page that does not exist. List only versions that are real.

Canonicals: each page points at itself

A canonical tells search engines which URL is the main one among duplicates. A Spanish page is not a duplicate of the English one. If every language version has a canonical pointing at /en/, you are asking search engines to drop the translations.

So the rule is simple: a self-referencing canonical on every language version. Make sure it does not contradict your hreflang.

The untranslated page problem

This is the failure I look for first. A site supports a set of languages, but its router also answers on language paths that are not on the list, or on a listed language where the page was never translated. The page loads, the text is in English, the head says lang="en", and the canonical points at the English URL.

Search engines can still discover and index that URL, and it can start ranking in places where you did not intend it to. You end up with duplicate pages under paths nobody planned.

To fix it:

  • Unsupported language path: return a 404, or a permanent redirect to the equivalent page in a supported language. Remove it from the sitemap.
  • Supported language, page not translated: do not publish the URL until it is translated. If it must exist, redirect it to the original or mark it noindex.
  • Page translated only in the menu and footer: that is not a translation. The main content must be in the page’s language.

To find these, crawl your site and compare three things for each URL: the language in the path, the lang attribute, and the actual language of the main text. Any mismatch is a bug.

Translate for the market, not word for word

A translation that keeps the English keywords and phrasing can read fine and still match nothing anyone types in that language. Research the queries in the target language, adapt titles and descriptions, and localize examples, currency and screenshots. Machine translation is fine as a first draft, but someone who speaks the language should read it. Publishing large volumes of unreviewed automatic translations to capture queries runs into the same spam policy on scaled content that I cover in how Google treats AI-generated content.

A checklist you can run this week

  1. List every language path that returns a 200. Compare it with the languages you support.
  2. Check that lang, the title, the description and the main text match the path language.
  3. Check that each page has a self-referencing canonical.
  4. Validate hreflang: self-reference, return links, valid codes, x-default.
  5. Make sure the sitemap lists only real, translated URLs.
  6. Check that internal links stay inside the same language.
  7. Set inLanguage in your structured data to match the page.
  8. In Search Console, filter performance by URL path and country to see what each version actually earns.

This site works the same way: English and Spanish versions with reciprocal hreflang and an x-default, and every page in both languages.

Expand slowly

Launching ten languages at once multiplies the chance of leaks. Choose the markets where you have real demand, test a full pair of equivalent pages, measure for a few months and then add the next language.

If you want a second pair of eyes on a multilingual setup, the GEO audit includes hreflang, canonical and indexing checks, and you can run the free audit on any page first.

Frequently asked questions

What is the best URL structure for a multilingual SaaS site?

Give each language its own URL, for example a subdirectory such as /en/ and /es/. Subdirectories are the simplest to run and keep authority on one domain. Whatever you choose, do not switch language on the same URL using cookies or IP detection.

Do I need hreflang on every page?

On every page that has an equivalent in another language. Each version should list all its alternates, including itself, and every alternate must link back. A page with no translation should not claim one.

Should the canonical point to the English page?

No. Each language version should be canonical to itself. A canonical pointing at the English page tells search engines the translation is a duplicate.

What should I do with pages that are not translated yet?

Do not publish a language URL that serves another language. Either wait until the page is translated, or send the language URL to the equivalent page with a permanent redirect or a 404.

How many languages should a SaaS launch with?

Fewer than you think. Pick the markets where you have demand, test a complete pair of equivalent pages, measure for a few months, then expand.