International B2B SEO: a strategy for selling in Europe without badly duplicating your website and content

An engineering company in Piedmont decides to push into Germany. It has the website translated into German, publishes it under /de/ and waits. Six months later the German pages hardly ever appear on Google.de, and when they do, it’s for words no buyer searches for. The problem is rarely the translation itself: what’s usually missing is a structure that tells Google which version to show to whom, and content written around the real searches in that market. The short answer is this: one version for each market that matters, preferably in subfolders, linked with reciprocal hreflang, self-referencing canonicals and copy localised from the country’s own keywords, measured market by market.

ccTLDs, subfolders or subdomains: which structure should you choose?

For a B2B SME entering two or three European markets, the subfolder (example.com/de/) is almost always the best choice: it inherits the main domain’s authority, is managed with a single CMS and costs little. Country-code domains (example.de) make sense when there’s a local subsidiary, a dedicated team and a budget to grow a separate website.

In its guide to multi-regional and multilingual sites, Google lists the options without imposing one, and advises against only URL parameters (?lang=de). Here’s the practical comparison, seen through the eyes of a company selling machinery or components:

Structure	Example	Advantages	Disadvantages	When to choose it
Country-code domain (ccTLD)	example.de	Clear geographic signal, trust from local users	Each domain starts from scratch in terms of authority; management costs multiply; it only works for one country	A local subsidiary with its own marketing team
Subfolder	example.com/de/	Inherits the domain’s links and authority; a single CMS; low maintenance	Geographic signal less obvious to users; a single server	Almost all B2B SMEs, especially at the start
Subdomain	de.example.com	Simple technical separation (different platforms)	The target country isn’t clear from the URL; authority has to be built on the subdomain too	Shops or portals on platforms different from the main website
URL parameter	example.com?lang=de	None worth mentioning	Not recommended by Google; hard to segment and measure	Never

A detail worth knowing: since 2022, Search Console no longer lets you set a target country for a website or section. Since then the signals have been the country-code domain, hreflang and the local signals on the page (address, phone number, language, currency). If you choose subfolders, you need to take good care of the latter.

Targeting by language or by country: what does it depend on?

You target by language when the offer, prices and terms are the same for every country that speaks it; by country when price lists, regulations, distributors or delivery arrangements differ. For many B2B companies, /de/ is enough for the whole German-speaking world, until Austria and Switzerland call for different content.

A practical rule we use: create a country version only if you can write something different in it. If de-DE, de-AT and de-CH would have the same text word for word, start with a single “de” version and add variants when there are concrete differences (an Austrian reseller, prices in Swiss francs, certifications required in Switzerland).

How do you set up hreflang without errors?

Hreflang is the annotation that tells Google which URLs are versions of the same page in different languages or countries, so it can show each user the right one. It only works if it’s complete and reciprocal: every version must reference itself and all the others, otherwise Google ignores the annotations.

The rules, according to Google’s documentation on localised versions (updated on 24 September 2026):

• the language code follows the ISO 639-1 standard (de, fr, it), the optional country code follows ISO 3166-1 Alpha 2 (DE, AT, CH);
• a country on its own isn’t valid: “de-AT” is fine, “AT” isn’t; and the United Kingdom is “GB”, not “UK”;
• x-default indicates the page to show to people who don’t fall into any of the specified languages (usually the English version or a language selection page);
• annotations can be added in three equivalent ways: tags in the HTML head, an HTTP header (useful for PDFs, such as tech sheets and catalogues) or an XML sitemap.

Here’s how the block looks in the head of a product page available in Italian, German for Germany and Austria, French and English. Exactly the same block must be repeated on all five versions:

<link rel="alternate" hreflang="it" href="https://www.example.com/it/riduttori-epicicloidali/" />
<link rel="alternate" hreflang="de-DE" href="https://www.example.com/de-de/planetengetriebe/" />
<link rel="alternate" hreflang="de-AT" href="https://www.example.com/de-at/planetengetriebe/" />
<link rel="alternate" hreflang="fr" href="https://www.example.com/fr/reducteurs-planetaires/" />
<link rel="alternate" hreflang="en" href="https://www.example.com/en/planetary-gearboxes/" />
<link rel="alternate" hreflang="x-default" href="https://www.example.com/en/planetary-gearboxes/" />

Which method should you choose? For websites of up to a few hundred pages, the HTML tag generated by the CMS is the easiest to check. Beyond thousands of URLs (catalogues, B2B e-commerce with many variants), the sitemap lightens the pages and can be generated automatically from the product database. The HTTP header is needed almost exclusively for non-HTML files.

The errors we find most often in audits:

1. Missing return links: the Italian page points to the German one, but the German one doesn’t point back.
2. Wrong URLs in hreflang: addresses with redirects, returning 404, with parameters or without the trailing slash the site uses.
3. Made-up codes: “en-UK”, “de-EU”, “ch” used for Switzerland (it’s actually the language code for Chamorro).
4. Hreflang pointing to the home page: all the German pages listing the Italian home page as their alternative, because the corresponding page doesn’t exist. It’s better to list nothing than to list a different page.
5. Hreflang pointing to pages set to noindex or blocked by robots.txt: Google can’t use an alternative it doesn’t index.

Since 2022 Search Console no longer reports hreflang errors, so checks need to be done with a crawler (Screaming Frog, Sitebulb, Ahrefs, SEOZoom) and with Search Console’s URL inspection on the most important pages.

Canonicals and duplicate content across versions: are de-DE and de-AT duplicates?

Versions in different languages aren’t duplicate content. Versions in the same language for different countries (de-DE and de-AT) can be, and Google advises using canonical and hreflang together so that the right URL is shown in each country. Every version must have a canonical pointing to itself, never to the version in another language or for another country.

The classic mistake is putting a canonical on the Austrian page pointing to the German one “to avoid duplicates”. The result is that Google treats the Austrian page as a copy not to be indexed, ignores the hreflang and shows the German version to Austrian users too. The guidelines on duplicate URLs say so clearly: with hreflang, the canonical should be specified in the same language.

That said, two almost identical pages remain a risk. If de-DE and de-AT differ only by one word in the footer, Google may still choose one as canonical and rarely show the other. The useful differences to include in the Austrian version are concrete: the distributor or technical contact in Austria, delivery times, ÖNORM standards where relevant, local vocabulary (in Austria January is “Jänner”), references from Austrian customers. If there are no differences to write, a single “de” version is the cleanest solution. On this topic you’ll also find a chapter on duplicates in our guide to why a page isn’t ranking.

Localisation or translation: what can you hand over to AI?

Translating means rendering the same text in another language; localising means rewriting it for the buyer in that country, with their words, their units, their standards and their proof of trust. AI greatly speeds up the first part, while the second still needs a person who knows the market and the product.

In the projects we work on, we split the work like this:

Task	Can be automated with AI	Needs human review
First translation of descriptive copy	Yes, with a glossary provided to the model	Proofreading by a native speaker from the sector
Technical terminology	Only if the glossary has already been validated	Yes, always: one wrong term costs you credibility with an engineering department
Units of measurement, number and date formats	Yes (decimal commas, date formats, inches for English-speaking markets)	Spot checks
Standards and certifications	No	Yes: DIN in Germany, NF in France, local markings and requirements
Titles, meta descriptions, URLs	A draft, yes	Final choice based on local keyword research
Case studies, references, reviews	No	Yes: you need customers and testimonials from that country
Legal pages (in Germany and Austria the Impressum is mandatory: § 5 DDG and § 5 ECG)	No	Yes, with a legal adviser

Anyone using AI to translate entire catalogues needs to budget for a review: a grammatically correct German text that uses textbook terms instead of the ones engineers actually use won’t convince any buyer.

Social proof deserves separate attention. A French purchasing manager trusts a case study with a French company, a trade fair they attend (Global Industrie, for example) and a phone number with a +33 prefix or a contact who speaks their language.

Why aren’t German or French keywords simply translations of Italian ones?

Every market describes the same products in its own words, with different search habits and different levels of specificity. Translating the Italian keyword list leads you to optimise pages for terms nobody searches for, while local competitors own the right ones.

Let’s take a hypothetical example. An Italian sheet metal fabrication company has its best page optimised for “taglio laser lamiera conto terzi” (contract laser cutting of sheet metal). Translated literally into German it would become something like “Laserschneiden Blech Lohnfertigung”. Research on the German market might show that buyers use compound and verbal forms such as “Blech lasern lassen” or search directly for “Laserzuschnitt”, and that “Lohnfertigung” is used more for generic subcontracting. In France the same need might be expressed as “découpe laser tôle sous-traitance”, with a results page dominated by directories of industrial suppliers. These are hypotheses to be checked on the market, case by case.

The method we follow:

1. Start from the terms used by customers, distributors and sales staff in the country (quotes, emails, enquiries received through the website).
2. Expand with keyword research tools set to the right country’s database (Google.de, Google.fr, not Google.it in German).
3. Look at the real results pages for each term: who ranks, what type of page, what intent. Search intent can change from one country to another even for the same word.
4. Build the keyword-to-page map for each market, accepting that some pages will exist only in certain languages.
5. Only then write the copy or have it written, with the chosen keywords in the brief for the translator or copywriter.

Local search engines and AI search: is Google enough across Europe?

In almost every European country Google remains the reference search engine, B2B included: according to StatCounter, in September 2026 it accounted for 89% of searches in Europe, with Bing at 5%. There are, however, local exceptions and a new channel to consider in every language: AI answers.

The exceptions to know about: in the Czech Republic there’s still Seznam, a local search engine (around 15% of searches in September 2026 according to StatCounter), worth considering if that market is strategic; Bing carries more weight where buyers work on company workstations with Edge and Copilot, and the website deserves at least to be verified in Bing Webmaster Tools.

On the AI front, on 7 October 2025 Google extended AI Mode to more than 35 new languages and offers it in German, French and Dutch too, while ChatGPT and Perplexity answer in the language of the person asking. A German buyer who asks an assistant which European gearbox manufacturers offer fast delivery will get sources in German or English: if your pages exist only in Italian, you’re left out. The rules for being chosen as a source are in our guide to GEO and in the SEO checklist for AI search: they apply in every language, with the difference that brand mentions on third-party sites also need to be built in the target country (trade associations, industry portals, local technical press).

How do you measure SEO across several countries in Search Console and GA4?

You measure by market, not by website: in Search Console by adding a property for each subfolder or domain, in GA4 by segmenting by country and by section of the site. Without this separation, the data from the larger Italian market drowns out everything else.

In Search Console:

• create a URL-prefix property for each version (https://www.example.com/de/), alongside the domain property: the reports become readable market by market;
• in the performance report, use the country filter and the page filter together: German impressions on Italian pages show that hreflang isn’t working or that the German version of that page is missing;
• open the generative AI performance report, available for all sites since 31 August 2026: it shows, by country, the impressions of your pages in AI Overviews and AI Mode, without clicks or queries, and it’s the simplest way to see in which markets AI answers use you as a source;
• check the indexing of each section, because new versions are the first to end up in “Crawled – currently not indexed”.

In GA4:

• create an exploration or report with the country and page path dimensions, to see who lands on which version;
• mark forms, quote requests and catalogue downloads as key events, with a parameter indicating the language version, so that leads can be attributed to the right market;
• compare organic traffic by country with the enquiries received by the sales staff covering that area: that’s the figure management cares about.

What changes for lead generation and CRM

In projects where we also work on automation and CRM, the form on each version passes the language and country of origin to the CRM, the lead is assigned to the agent or distributor for that area and receives emails in their language. If a German company fills in the form and receives an automatic reply in Italian, a good part of the SEO work is lost at that moment.

The same goes for B2B e-commerce: price lists, currencies, intra-EU VAT and delivery terms must be consistent with the version the customer arrived on, otherwise organic traffic stops at the basket.

Mistakes to avoid in international SEO

The costliest mistakes are three: automatic redirects based on IP address or browser language, versions that are badly or only partly translated, and hreflang pointing to pages Google can’t index. All three are easy to prevent.

• Automatic IP-based redirects. Google explicitly advises against them: most crawling starts from US addresses, so Googlebot risks seeing only the English version. On top of that, an Italian buyer on a business trip to Munich ends up on the German site. A banner suggesting the version and an always-visible language selector are better.
• A single, badly translated language. An English version done in a hurry, full of calques from Italian, is seen by every market that doesn’t have its own language version. It’s often the most important page on the website and the least cared for.
• Hreflang pointing to pages that are noindexed, redirected or returning 404. This happens after a redesign, or when translations are published on staging with noindex and then forgotten.
• Pages translated only in part: menu and footer in German, product copy in Italian. Google’s guide to multi-regional sites describes this as an unpleasant experience for users.
• A language selector that leads to the home page instead of the corresponding page.
• Forgetting the PDFs: tech sheets and catalogues are often the documents engineers search for most, and they stay in Italian only.

Checklist for launching a new market

Before publishing a new version of the website, these are the items to tick off one by one.

1. Market and goal defined: country or language, products to present, who handles leads in that area.
2. Structure chosen (subfolder, subdomain or ccTLD) and URLs translated into the market’s language.
3. Keyword research done on the country’s database, with a keyword-to-page map.
4. Copy localised and reviewed by a native speaker who knows the sector; technical glossary approved by the engineering department.
5. Titles, meta descriptions, image alt text and structured data in the right language.
6. Complete, reciprocal hreflang, with self-reference and x-default, verified with a crawler.
7. Every page’s canonical pointing to itself.
8. No automatic redirects by IP or language; a selector that leads to the corresponding page.
9. Local signals in place: an address or contact in the country, phone number, currency, Impressum where required, privacy policy and cookie banner in the market’s language.
10. Sitemap updated and submitted, Search Console property created for the new section, website also verified in Bing Webmaster Tools.
11. Forms connected to the CRM with language and country, automatic emails translated, assignment to the right salesperson or distributor.
12. GA4 reports by market and a first indexing check at two and six weeks.

If the new market is part of a broader industrial marketing plan, it’s worth aligning the launch with trade fairs and campaigns in the country, so that the first organic visitors already find a recognised brand.

Want to find out whether your website is ready for markets abroad?

With an international SEO audit we check structure, hreflang, canonicals, indexing by country and the quality of the language versions, and compare your pages with the keywords buyers use in the markets you’re interested in. At the end we tell you what to fix straight away, what can wait, and whether it makes sense to open a new market now or to strengthen the existing ones first.

You can book a call with Federico or write to us via the contact form. You’ll also find details of how we work on our SEO service page.

Frequently asked questions

Is a .de domain or a /de/ subfolder better for selling in Germany?

For most B2B SMEs, the subfolder: it inherits the main domain’s authority and is managed as a single website. A .de domain makes sense when there’s a local structure able to grow it as a standalone site.

Does hreflang improve rankings?

Hreflang doesn’t push a page up the rankings: it helps Google show the right version out of those you have. The indirect benefit is that each market sees the page in its own language, with more clicks and fewer bounces.

Should I use a single canonical for all languages?

No. Each language version must have a canonical pointing to itself. A canonical pointing to another language leads Google to treat it as a duplicate and not show it.

Can I translate my website with AI?

Yes, for the first draft, provided you supply a technical glossary and have the copy reviewed by a native speaker from the sector. Standards, local references, legal pages and keyword choice need to be handled by people who know the market.

How can I tell whether hreflang is working?

Search Console no longer reports hreflang errors, so you use a crawler to check reciprocity and codes. Then you check in Search Console whether users in each country are landing on the right version, combining the country filter with the page filter.

Are automatic country-based redirects prohibited?

They’re not prohibited, but Google advises against them because Googlebot crawls mainly from US addresses and may not see the other versions. A banner suggesting the language and a visible selector achieve the same result without the risk.