To translate a website to Portuguese, first decide whether you are targeting Brazil, Portugal or both, because vocabulary, spelling and tone differ between them. Then publish the Portuguese version on its own URL (for example /pt-br/) and translate the pages with a translation tool or a translator. Have a native speaker review the pages that sell, and localize prices, payment methods and SEO metadata. Add hreflang tags (pt-BR, pt-PT) so Google shows each audience the right version.
Each step is covered below, along with the Brazil and Portugal differences that trip people up and three ways to do the translation.
Key takeaways
- Portuguese is one of the most-used languages on the web. W3Techs puts it at 4.1% of websites whose content language it can identify, sixth after English, Spanish, German, Japanese and French (W3Techs, September 2026).
- Pick one variant per audience. Brazilian and European Portuguese differ in everyday vocabulary, some spellings, grammar and tone.
- Give each variant its own URL and hreflang code:
pt-BRfor Brazil,pt-PTfor Portugal, or plainptif you publish one version for everyone. - Localize more than the text: currency (R$ or €), number formats, payment methods such as Pix in Brazil and MB WAY in Portugal, and legal pages.
- For most sites, machine translation plus native review of the main pages is the sensible balance.
Step 1: choose Brazilian or European Portuguese (or both)
Brazil is by far the largest Portuguese-speaking market. If you sell in Portugal or to Portuguese-speaking Africa, though, European Portuguese is the better fit there. Decide by where your traffic and customers come from rather than by which variant is bigger.
You have three options:
| Approach | When it fits | Hreflang |
|---|---|---|
| Brazilian Portuguese only | Most of your Portuguese-speaking traffic is from Brazil | pt-BR (or pt if it is your only Portuguese version) |
| European Portuguese only | You sell mainly in Portugal | pt-PT (or pt) |
| Both | You have real demand in both markets and can maintain two versions | pt-BR and pt-PT, plus one of them as pt if you want a fallback |
If you publish only one Portuguese version, Brazilian readers will understand European Portuguese and vice versa. Picking the “wrong” variant won’t stop people understanding you. The site will just feel foreign, and it will convert worse.
Step 2: know the differences that matter on a website
| Brazil (pt-BR) | Portugal (pt-PT) | |
|---|---|---|
| Mobile phone | celular | telemóvel |
| Screen | tela | ecrã |
| Bus | ônibus | autocarro |
| Train | trem | comboio |
| Breakfast | café da manhã | pequeno-almoço |
| Contact (noun) | contato | contacto |
| Fact | fato | facto |
| ”I am doing” | estou fazendo | estou a fazer |
| Addressing the reader | você is the normal, friendly form | tu is informal; formal copy often avoids the pronoun or uses você sparingly |
| Currency | Real, written R$ 1.234,56 | Euro, usually written 1234,56 € |
Both variants write dates day first (27/09/2026) and use a comma as the decimal separator. Spelling was partly unified by the 1990 Orthographic Agreement, but differences like contato/contacto remain, and a spell checker set to the wrong variant will “correct” your text in the wrong direction.
For interface text, check the words customers click most. Carrinho (cart) is common in both, but terms for checkout, accounts and shipping vary. Put your choices in a glossary so every page uses the same terms.
Step 3: give Portuguese its own URL
Search engines index URLs. The Portuguese version needs its own address. A translation that appears only after a script runs or a cookie is set will not do. The usual options:
- A subfolder, such as
example.com/pt-br/. This is the simplest and keeps everything on one domain. - A subdomain, such as
br.example.com. - A country domain, such as
example.com.br. It sends the strongest country signal and takes the most maintenance.
Then add hreflang tags so every page lists its Portuguese and other-language equivalents, including itself, plus an x-default. Our hreflang language codes list has the exact codes, and the complete hreflang guide shows how to check them.
Step 4: translate the content (three ways)
Option A: professional human translation
A native translator produces the most natural text and is the right choice for your homepage, pricing, legal pages and campaigns.
- You get the best quality and tone, and idioms and marketing copy are handled properly.
- It is slow and costly for large sites, and every later change needs another round.
- Give the translator your glossary and a note on tone (for example “informal, você, Brazilian spelling”).
Option B: free browser or public translation tools
Tools that translate a page on the fly in the visitor’s browser are fine for reading. They are no good for publishing a Portuguese website.
- The translated text usually has no URL of its own, so it cannot rank in Google.
- You cannot correct mistakes or enforce brand terms.
- Metadata, image alt text and structured data typically stay in the original language.
Option C: a website translation tool (machine translation plus editing)
A website translation tool machine-translates every page, publishes it on a Portuguese URL, keeps it in sync as your site changes, and lets you edit any sentence.
- It is fast, covers the whole site including metadata, and stays up to date.
- Machine output still needs review on the pages where mistakes cost you.
- The approach that works: machine-translate everything, then have a native speaker review the pages that bring traffic and revenue. See our translation quality workflow for how to organize the review.
Step 5: localize the buying experience
Translation makes you understood. Getting paid takes localization:
- Show prices in BRL in Brazil and EUR in Portugal where you can actually charge in that currency, and use the local number format.
- Offer the payment methods people expect. In Brazil that means Pix (the Central Bank’s instant payment system) and boleto bancário. In Portugal, MB WAY and Multibanco references are common. Card-only checkouts lose buyers in both.
- Brazilian shoppers often expect to pay in installments (parcelamento), so say clearly whether you offer it.
- Brazilian checkouts often ask for a CPF (individual taxpayer number) and use the CEP postcode. Portugal uses a seven-digit postcode and the NIF tax number on invoices.
- Privacy notices should reflect Brazil’s LGPD or the EU’s GDPR, whichever applies.
- Say which languages support is available in, and in which time zone.
Step 6: Portuguese SEO
- Research keywords in Portuguese, separately for each variant. As the table above shows, the Brazilian and European terms for the same product often differ.
- Translate titles, meta descriptions and image alt text, since these are what searchers see first.
- Translate structured data (product names, FAQ answers) so rich results appear in Portuguese.
- A few weeks after launch, check indexing in Search Console by filtering on the
/pt-br/folder and on country (Brazil, Portugal).
Our guide on translating SEO keywords for different audiences walks through the process.
Step 7: test before and after launch
- Read the homepage, a product page and the checkout in Portuguese on a phone. Portuguese text often runs longer than English, so check buttons and menus.
- Place a test order and read every email you send.
- Ask a native speaker from the target country to do a five-minute “does this feel local?” review.
- After launch, compare conversion rate on the Portuguese version with your original language.
How to translate your website to Portuguese with ConveyThis
ConveyThis supports Portuguese, plus Portuguese (Brazil) and Portuguese (Portugal) as separate languages, so you can publish one version or both. Setup takes four steps:
- Create an account and add your website, or install the plugin or app for your platform (WordPress, Shopify, Webflow, Wix and more; see all integrations).
- Choose your source language and add Portuguese (Brazil), Portuguese (Portugal) or both.
- Choose the URL structure: subfolders, subdomains or
?lang(second-level domains are available on the Extreme plan). Hreflang tags are added automatically. - Review your key pages in the visual editor, add your glossary terms (for example celular vs telemóvel), and invite a reviewer with a team role.

Page titles, meta descriptions and JSON-LD are translated along with the visible text, and translation memory reuses approved sentences across pages. Words are counted only when translated content is shown to visitors, and bots do not count. The Free plan covers one language and 5,000 words; see pricing for larger sites.
Frequently asked questions
Should I use Brazilian or European Portuguese for my website? Use the variant of the market you sell to. If most Portuguese-speaking visitors are from Brazil, use Brazilian Portuguese. If you sell mainly in Portugal, use European Portuguese. If both markets matter, publish both with pt-BR and pt-PT hreflang tags.
Can Google Translate translate my website into Portuguese? It can show a visitor a machine translation in their browser, but that version has no URL of its own, so it will not rank in Google, and you cannot edit it. For a Portuguese site that ranks and converts, publish translated pages on their own URLs.
What hreflang code should I use for Portuguese? pt-BR for Brazil, pt-PT for Portugal, or pt for a single version aimed at all Portuguese speakers.
How long does it take to translate a website into Portuguese? With a website translation tool, a first machine-translated version can be live the same day. Budget extra time for native review of your most important pages.
To start reaching Portuguese-speaking customers, translate your site with ConveyThis.