Home/ Relaunches

Relaunching an exporter's website: languages, country pages and hreflang

A relaunch is the cheapest moment to set up an exporter's website for international buyers, because the URL structure is being decided anyway. Add language versions only where buyers need them, use subdirectories and two-way hreflang, and never redirect by IP.

Export crates waiting on a loading bay with shipping containers stacked behind

In one sentence

An international relaunch is a website relaunch that also sets the language and country structure of the site, its hreflang annotations and its export-specific product information.

An exporting manufacturer's website has to work for buyers who read different languages, use different standards and work in different time zones. A relaunch is the cheapest moment to get this right, because the URL structure is being decided anyway. Changing it a year later means a second migration.

This guide covers the export decisions in a relaunch: whether you need language versions at all, how to structure country and language pages, how to tell search engines which version goes where, and what export buyers look for on a spec page. The general move is covered in the website relaunch runbook.

Does an exporter need a separate site for each country?

Usually not. Many Indian exporters sell into markets where buyers read English comfortably: the Gulf, the UK, the US, much of Africa and South East Asia. For them a single English site, written for international buyers, does the job. Country versions earn their cost in two cases:

  • The buyers read another language. Spanish for Latin America, French for West Africa, Arabic where purchase decisions are made in Arabic, German for many engineering buyers in Germany and Austria. Here a translated site wins enquiries an English one does not.
  • The offer differs by country. Different approvals, product ranges, distributors or delivery terms. Then a country page has something real to say that the main site does not.

A country page that differs only in its flag and headline adds maintenance and nothing else. Start with the markets that already send enquiries, and add versions as each one proves itself.

Which URL structure should a relaunch use?

Google sets out the options in its guide to managing multi-regional and multilingual sites:

StructureFits when
Country domain, such as example.deYou have a real local business in that country and can run a separate site
Subdomain, such as de.example.comThe country site is run by a different team or hosted separately
Subdirectory, such as example.com/de/Most exporters. One site, one host, easy to maintain
URL parameter, such as ?loc=deNever. Google does not recommend it

For a manufacturer exporting from India, subdirectories are nearly always the right answer. They keep everything on the domain that has built up its authority, and one team can maintain them. Choose a pattern and keep it consistent, either language only (/es/) or language and country (/es-mx/), and do not mix the two.

How do you tell Google which version is for which market?

Use hreflang annotations. Each page lists every language or country version of itself, including itself. Google's hreflang documentation sets out the rules that matter most in a relaunch:

  • Annotations must point both ways. If the English page names the Spanish one, the Spanish page must name the English one. Google ignores the pair otherwise.
  • Use x-default for the fallback, the version shown to buyers whose language you have not covered. For most exporters that is the English page.
  • Use fully qualified URLs, including https and the domain, and point them at pages that load directly rather than through a redirect.

A product page with English, Spanish and a fallback looks like this in the head:

<link rel="alternate" hreflang="en" href="https://www.example.com/products/flanges/">
<link rel="alternate" hreflang="es" href="https://www.example.com/es/productos/bridas/">
<link rel="alternate" hreflang="x-default" href="https://www.example.com/products/flanges/">

Generate these from the page registry or CMS rather than by hand. Hand-written hreflang breaks the first time someone renames a page. For PDFs such as translated datasheets, Google accepts the same annotations as an HTTP Link header.

Should the site redirect visitors by country?

No. Google advises against changing content or redirecting based on the visitor's IP address or assumed language. It notes that most of its crawling comes from the United States, so a site that redirects by IP may only ever show Google its US version. It can also trap a buyer in the wrong version: a German engineer travelling in Dubai lands on the Arabic site and cannot get out.

Put a visible language or country selector on every page instead, and let the buyer choose. A one-line suggestion such as "View this page in Spanish" is fine, provided it does not redirect.

What does an export buyer look for on a product page?

Translation is the smaller part of the work. An export buyer compares you against suppliers from his own country and from other exporting nations, and he needs the facts in his own terms.

  • The standards he buys to. List the equivalent ASTM, EN, DIN, JIS or BS grade alongside the IS grade wherever they truly match. Never claim an equivalence you cannot certify.
  • Units he uses. Metric throughout, with imperial in brackets for North American buyers on dimensions and pressures.
  • Export proof. Countries supplied, export certifications, third-party inspection agencies you work with, and the test certificate format (for example EN 10204 3.1) you can provide.
  • Trade terms. Minimum order quantity, packing for sea freight, the Incoterms you quote, and usual lead time to port.
  • A way to reach you in his hours. Phone numbers in international format (+91), WhatsApp, and a line saying when your team answers in his time zone.

The same facts help AI assistants. A buyer in Nairobi asking an assistant for flange suppliers that meet an EN standard gets an answer built from pages that state that standard plainly. The 12 prompt test for industrial products includes location prompts you can run per market.

Who should translate the pages?

Machine translation is a good first draft and a poor final one for technical pages. It renders grade names, tolerances and terms of trade in ways a native engineer notices at once, and one wrong unit on a spec page costs more trust than an English page would have. Have a native speaker who knows the industry review every product page, starting with the ranges that sell in that market. Keep the original grade codes and part numbers untranslated, so a buyer can search them.

What changes in the relaunch plan for an exporter?

Three steps change in the usual runbook:

  • The redirect map gets a column per language. If the old site had translated pages, each one needs its own new destination in the same language, not the English page.
  • Staging checks include hreflang. Before switchover, crawl the staging site and confirm every hreflang pair points both ways and every target returns 200.
  • Listings are updated per market. Export directories, overseas distributors and embassy or trade council listings carry your old URL. Point each one at the right language version. Announcing a relaunched website covers the order in which to tell them.

After switchover, filter Search Console's Performance report by country for each target market and compare it with the same period before the move. Search Console no longer has a report for hreflang errors, so re-crawl the live site with a tool that checks hreflang pairs, once in the first week and again after any batch of new pages.

Questions people ask

Does an Indian exporter need a website in other languages?

An Indian exporter needs a website in other languages only for markets where buyers read another language or where the offer differs by country. For markets where buyers read English, one well-written English website usually does the job.

Should an export website use subdirectories or country domains?

Most manufacturers exporting from India should use subdirectories, such as example.com/es/, rather than country domains for an export website. Subdirectories keep one site and one host, and every language version benefits from the authority the main domain has already built.

What does x-default mean in hreflang?

In hreflang, x-default names the page version shown to users whose language or region matches no other hreflang annotation. For most exporters, the x-default version is the English page.

Should an export website redirect visitors based on their country?

An export website should not redirect visitors based on their country or IP address. Google advises against adapting content or redirecting by IP address, notes that most Googlebot crawling comes from the United States, and recommends a visible language or country selector instead.

Check your own site before or after a relaunch

A plain-English self-check for manufacturers: what a buyer, Google and an AI assistant see on your site today.

What readers usually ask next

Product Launch Blog is an EbizIndia publication. This article does not pitch anything; the disclosure sits here instead, and in the footer, on every page. On this topic, EbizIndia's own page: Website transformation for manufacturers: scope and steps.