International SEO for Exporters: hreflang Done Right

International SEO with hreflang tells Google which version of a page should appear for each language and country. If you export, it stops a German buyer from landing on your Portuguese page, or two English versions from competing with each other. This guide shows how to structure, mark up and verify it.

Decide first: language, country or both?

This question shapes everything. If your English content serves any market, one English version is enough (en). If prices, currency, standards or contacts change by country, create distinct versions, such as English for the United States (en-us) and English for the United Kingdom (en-gb).

For most small and mid-size manufacturers, start with a few well-maintained languages, for example English and Portuguese, and add Spanish or German only when there is real demand and someone to maintain the content.

How hreflang works

Each page points, in the HTML head or in the sitemap, to all its equivalent versions, including itself. Language codes follow ISO 639-1 and country codes ISO 3166-1. There is also an x-default value for users who match none of the versions.

• pt-br: Brazilian Portuguese;
• en: generic English;
• en-us: English for the US;
• es: Spanish;
• x-default: default version or language selector.

Rules that fail most often

1. Reciprocity: if page A points to B, B must point back to A. Without it, Google ignores the markup.
2. Self-reference: every page lists itself among the versions.
3. Absolute, canonical URLs: use full addresses that match the declared rel=canonical. Never point to a URL that redirects.
4. Correct codes: it is en-gb, not en-uk; and pt-br, not br.
5. One set per page type: the Portuguese product page links to its English equivalent, not to the homepage.

Avoiding duplicate content

Versions in different languages are not treated as duplicates. The risk appears when two near-identical pages, like US and UK English, exist without differentiation. In that case, genuinely adapt the content (units, vocabulary, contacts, currency) or keep a single English version.

Do not machine-translate and publish without review. Poor text pushes buyers away and may be treated as low-quality content. Adapting also means changing examples, standards and references, not just words. To build a bilingual site, see the multilingual website development work.

How to check that it worked

• Test a few pages with an hreflang validator and look for reciprocity errors.
• Check Search Console performance by country to see whether each market gets the right version.
• Search from outside Brazil, with a VPN or colleagues abroad, to see the real result.
• Review the setup whenever you add or remove a language.

Next step

List the ten most important pages on your site, confirm that each has an equivalent in the other language and implement hreflang on those first. Then extend it to the rest.

Frequently asked questions

Is hreflang required for a bilingual site?

Not required, but recommended. Without it Google has to guess which version to show each user.

Can I put hreflang in the sitemap instead of the HTML?

Yes. On large sites, the sitemap is often easier to maintain than editing every page header.

Does hreflang guarantee Google shows the right version?

It is a strong hint, not a command. Google still weighs other signals such as location and content.