International SEO and hreflang for multilingual sites without duplicate content

When an industrial company decides to expand abroad, the first hurdle isn't commercial: it's technical. Should I launch a .de for Germany or create a /de/ folder on my website? Why is Google showing my Spanish version to an engineer in Chile? And why, after translating the entire catalog, is international traffic not showing up? The answer almost always lies in the architecture and in how you tell Google which version to serve each user. Let's take it step by step, without unnecessary jargon but with the rigor this topic demands.

The first decision: domains, subdomains, or subdirectories

Before you translate a single word, you need to decide how the URLs for each market are organized. And it's not a cosmetic choice: it determines how Google distributes your website's authority and how much effort it spends crawling it. There are three options:

• ccTLDs (country-code domains such as .de or .fr): a separate domain for each market.
• Subdomains (de.brand.com): separate, but hanging off your main domain.
• Subdirectories (brand.com/de/): everything lives on a single website.

In industrial B2B, where quality backlinks are hard to earn, splitting authority across multiple domains is usually a mistake for a mid-sized company. If your main website took years to build its reputation and you launch a .fr, that new domain starts practically from scratch. That's why, for most manufacturers, we recommend subdirectories: they concentrate all your link equity on a single root domain and let the reputation you've earned in your home market boost rankings in new markets from day one.

Why subdirectories win on crawling and authority

Crawl budget is critical when you have multilingual catalogs. Running five separate domains forces Google to split its resources among them, and if you rarely update your content (common in heavy machinery), the secondary domains get sidelined. A subdirectory structure centralizes crawl frequency: every link your English version earns also indirectly strengthens your German version.

ccTLDs do have one real advantage: the domain signals the country by default. If you go with subdirectories, you lose that automatic geographic signal, so you'll need to make up for it with a flawless Google Search Console setup and hreflang tags that make it clear which market each folder targets.

The “mirror” machine translation mistake

One of the costliest mistakes is cloning your website and running it through machine translation without review. Google detects patterns of unreviewed translation and may treat it as auto-generated content. But the underlying problem is semantic: the English word “fittings” can be translated into Spanish as “accesorios” in general, but in fluid engineering the correct term is “racorería.”

A literal 1:1 translation ignores how each market actually searches. An engineer in Mexico doesn't use the same words as one in Spain (“goma” vs. “caucho” for rubber, “computadora” vs. “ordenador” for computer). If you don't adapt your technical terminology to each variant, you lose the trust of expert readers and dilute your relevance. International SEO requires technical transcreation, not just translation.

What is hreflang? The protocol that keeps your pages from cannibalizing each other

The best way to understand the hreflang attribute is to stop thinking of it as a language tag. It doesn't tell Google “this page is in French”; it tells it, “If the user is in France and browsing in French, serve them this URL instead of the generic one.” In practice, it's a routing system.

Its most important job for SEO is preventing duplicate content. If you have one version for the US and another for the UK with the same technical copy in English, Google will see them as copies and show only one. Hreflang tells Google those pages are equivalent alternates, not duplicates.

The two golden rules of hreflang tags: self-reference and x-default

The most common syntax error we find in audits is leaving “orphan” tags. For Google to validate your architecture, two rules are non-negotiable:

• Self-reference: if page A points to page B as an alternate, page A must also point to itself. Without that, Google assumes there's a configuration error.
• Return link: if A points to B, B must point back to A. Without that two-way “handshake,” Google ignores the instruction.
• The x-default safety net: you need to define a fallback URL for users who don't match any language version (a user in Turkey, for example).

A solid minimum implementation always includes a cluster like this:

How to roll out without “friendly fire” between markets

Cross-border cannibalization happens when Google isn't sure which regional version to show and picks the one with the most historical authority instead of the most relevant one. If an engineer in Chile searches for “compresor de tornillo” (screw compressor) and gets your Spain URL (/es/) instead of your LATAM one, you lose critical relevance: local currency, distribution network, electrical standards. To avoid this, your launch needs to follow a strict protocol:

Variants of the same language and where to add the signals

The trickiest case is when you have variants of the same language (US vs. UK, Spain vs. Mexico). Data sheets are usually 95% identical (same performance curves, same CAD drawings), and that sets off duplicate content alarms. The fix isn't to artificially rewrite the technical descriptions, but to make your hreflang tags so clear that Google understands the duplication is intentional and necessary. To reinforce the differences without touching the product engineering, localize these elements:

• Local contact: phone number and address of the local branch or distributor.
• Units of measure: metric (bar, kW) vs. imperial (psi, HP), depending on the market.
• Standards: highlight CE marking in Europe or UL/NEMA in the US.
• Currency and logistics: prices in local currency and lead times from the regional warehouse.

As for where to place hreflang, there are three options: tags in the HTML, HTTP headers, or the XML sitemap. For large websites with thousands of SKUs, adding 20 lines of hreflang to every page bloats the document and slows down load times. That's why we recommend implementing it in the XML sitemap: it keeps the HTML lean, lets you manage every language from a single file, makes it easier to isolate errors in Search Console, and avoids breaking your live site with a copy-and-paste mistake in the tags.

Local signals for AI search engines (GEO)

Classic SEO was built on URLs and keywords. The new discipline, GEO (generative engine optimization), works with entities and relationships. When an engineer asks ChatGPT Search or Perplexity, “Who are the leading cryogenic valve distributors in Germany?”, the model doesn't just read text: it tries to validate the relationship between your brand and a specific territory.

If your architecture is right (you have the /de/ folder) but you're missing local entity signals, AI may treat you as a foreign company with no real capacity in the region. AI search engines prioritize logistical feasibility in their B2B answers. To get cited as a local supplier, your digital footprint needs to show that your presence goes beyond a translation: verifiable physical addresses and structured data that tie your domain to the territory.

Structured data AI can understand

Hreflang helps Google choose the URL; Schema.org markup helps AI understand your global business model. Your JSON-LD needs to be granular for each regional subdirectory: marking up headquarters alone isn't enough. To lock in your relevance in international generative search, implement:

• areaServed: defines the countries or regions (ISO 3166 codes) where you deliver and provide support.
• availableLanguage: ties the supported technical language to each service region.
• contactPoint: associates local phone numbers with the contact type ("sales", "technical support") in each market.
• hasPOS: if you have physical branches, mark them up with their exact coordinates.

By structuring this data, you stop being “text in German” and become a digital statement that you're a legitimate, operational player in that market. That semantic validation is your competitive edge over companies that only translate text without building a data infrastructure behind it.

Frequently asked questions

Request your free assessment →See SEO for industry

Related articles