5 Technical Pre-Launch Checks for Multilingual Websites

When expanding into international markets, many business owners take a straightforward approach: translate the website content into a few target languages, host the new pages, and hit publish. Shortly after launch, traffic appears, but incoming leads and inquiries remain near zero. After a brief audit, management usually concludes, “The translation quality must be terrible.”

However, translation quality is rarely the primary culprit.

Consider a common scenario: A prospect in Germany searches for a product on Google.de. They click a search result, only to land on your English homepage featuring a banner that reads, “This website is also available in German.” Google clearly knew a German version existed—so why didn’t it display the German page directly?

This is almost always a technical configuration error. The site failed to explicitly tell search engine crawlers which English page corresponds to which German page, or sent contradictory technical signals. Unwilling to make guesses in a confusing setup, Google defaults to the safest action: displaying your main English URL or demoting the site’s overall rankings.

Before launching a localized site, run through this five-point technical audit. It requires no coding knowledge—simply review these questions with your development team or web agency. If they provide clear, consistent answers, your technical foundation is solid.

1. Check hreflang Tags: The Only Language Pairing Signal Search Engines Trust

hreflang tags are code snippet attributes placed in your website’s HTML headers. They function as a language mapping table, telling search engines: “This page is the English version, the corresponding German version is at URL X, and the Spanish version is at URL Y.”

Without this map, Google relies on automated guesses. Because different language versions of the same site share similar structures and images, search engines may flag them as duplicate content rather than localized equivalents.

Google’s official documentation is explicit: separate language versions require distinct URLs and explicit hreflang tags defining their relationships. If you rely solely on browser language detection or IP-based dynamic switching, search engines will likely fail to discover your alternate language pages altogether—because Google’s crawlers primarily originate from US IP addresses without sending language preference headers.

What to check:

• Open the source code of a page in each language version and verify that hreflang tags are fully populated.
• Pairings must be reciprocal: If the English page references the German page, the German page must reference the English page back. One-way references are ignored.
• Every URL listed in hreflang tags must be live and accessible (not pointing to broken links or redirect chains).
• Language declarations in hreflang tags must match those declared in your XML sitemap. You can use both methods, but their data must be identical.

2. Check URL Structure: Every Language Needs a Fixed Address

Some websites manage language versions using URL query parameters, such as example.com?loc=de. Google’s documentation explicitly advises against this structure. Parameter-based URLs make it difficult for search engines to segregate language content and rank pages effectively for specific geographic markets.

There are three main structural options, listed here in order of suitability for mid-sized businesses:

1. Subdirectories (example.com/de/) — Recommended: This is the ideal choice for most growing businesses. It is straightforward to set up, low-maintenance, runs on a single server, and consolidates domain authority under your primary brand domain. (The minor drawback: users cannot always immediately tell whether /de/ stands for the German language or the country of Germany).
2. Subdomains (de.example.com) — Acceptable: Works well technically, but carries slightly higher management overhead and similar potential user ambiguity between language and country code.
3. Country-Code Top-Level Domains / ccTLDs (example.de) — High Effort: Offers the clearest geographic targeting signal, making it worth heavy investment for key core markets. However, for a business expanding into five or six international markets simultaneously, purchasing and managing separate domain properties inflates infrastructure and marketing overhead rapidly.

The core question to ask your team: Does every language version have a permanent, dedicated URL that functions without relying on URL parameters, browser cookies, or IP redirects? If not, fix the URL structure before proceeding.

3. Audit Machine-Translated Pages: Automation Isn’t “Set and Forget”

The cost of automated machine translation has dropped dramatically. This creates a common temptation: bulk-translate every page on a site into dozens of languages and publish them all overnight. Traffic may well go up, but leads stay flat.

The issue isn’t that Google outright bans machine translation. Google’s guidelines do not state that machine translation is forbidden; rather, they state that a page’s target language must be unambiguous and obvious. Every page should use a single, consistent language across its navigation, body text, and UI components—avoiding side-by-side translated layouts.

Problems arise in two places:

• Incomplete translation: Machine translation plugins often convert main product descriptions while leaving headers, footers, navigation menus, and embedded image text in the original source language. To search engines, these mixed-language pages are ambiguous and signal poor user experience.
• Indexation penalties: Mass-generating automated pages without configuring proper hreflang pairings leads search engines to treat the new pages as thin, duplicate content—resulting in dropped indexation and degraded search visibility.

What to check: Spot-check the homepage and two product pages in each language. Is the page fully presented in the target language? Verify there are no un-translated navigation menus, untranslated image copy, or mixed-language sections. Finally, confirm that your hreflang tags cover every auto-generated page. Miss a single one, and that whole batch of pages is effectively left unprotected.

4. Review Language Switchers: Avoid Automatic IP Redirects

Imagine a prospective client in Germany visits your primary domain (example.com). Your server detects their German IP address and automatically redirects them to example.com/de/. While this seems user-friendly, it creates a major indexing bottleneck: Google’s web crawlers crawl primarily from US-based IP addresses. An automatic IP redirect forces the crawler away from your primary pages, preventing search engines from ever discovering or indexing your alternate language content properly.

Furthermore, international B2B buyers frequently browse through corporate VPNs or centralized data centers, making IP location detection unreliable.

The correct approach: Do not use automatic, IP-based redirects. Allow all visitors to land on the primary URL, present a clear and accessible language switcher in the website header, and let users choose their preferred language. Rely on hreflang tags to guide search engines so that international users arrive at the correct language version directly from search engine result pages (SERPs).

Development agencies often implement IP redirects assuming it enhances user experience, but the skipped step does not translate into traffic—the unintended side effect is compromised search crawlability.

5. Validate On-Site Localization Beyond Copy

Even with technical configurations 1 through 4 in place, websites frequently fail at the final hurdle: commercial localization. A target customer lands on a fully translated German page, but when they reach checkout, pricing is strictly listed in USD and the only accepted payment method is PayPal.

An international commerce survey published by Airwallex in 2024 highlighted two critical consumer data points:

• 93% of international consumers report that they may abandon a purchase decision if prices are not displayed in their local currency.
• 77% of consumers will drop out of the checkout process entirely if their preferred local payment method is unavailable.

This isn’t an SEO problem, but it is the last link in the chain where traffic arrives and conversions don’t. The objective of an international website goes beyond earning indexed pages—it must guide a prospective buyer from discovery to completed transaction. Language is merely the first layer; localized currency, supported payment gateways, accurate shipping details, and regional support contact options complete the conversion funnel.

What to check: Complete a test inquiry or mock purchase end-to-end for every target market before going live. You’ll find that many of the problems sit outside Google.

What Remains Unresolved

This checklist addresses how to ensure your website is technically interpreted correctly by search engines. But there’s one question I haven’t worked out: whether Google’s stance on machine-translated pages will keep shifting.

In theory, once hreflang is correct and each page sticks to a single language, a machine-translated page earns the right to compete in rankings. But in some highly competitive industries, could the conversion gap between human localization and machine translation be large enough to make technical configuration itself secondary? I don’t have enough data to call it. What I can say for now: clearing out technical errors first is the lowest-cost step with the most certain payoff.

References

• Managing Multi-Regional and Multilingual Sites | Google Search Central
• Unlocking Global Growth: Payment Strategies for Cross-Border Commerce | Airwallex