Portuguese WordPress hosting for a language with two official spellings.
The same Portuguese word can be written differently in Lisbon and São Paulo, and both are correct. A visitor searching in one spelling will not find content written in the other.
Two correct spellings of one word.
European and Brazilian Portuguese diverge in spelling as well as vocabulary, and a search box treats them as unrelated strings.
Search that spans both orthographies
A Brazilian visitor typing their spelling of a word should find European content and the reverse. Matching folds the known divergences rather than comparing literally.
Variants declared, not merged
If you publish separate European and Brazilian versions, each needs its own URLs and regional declaration. Undeclared, they read to a crawler as duplicates of each other.
An EU origin for a European audience
Portuguese visitors are served nearby with storage in the EU, keeping latency and residency to a single answer.
A far larger audience across the ocean
Portuguese-language traffic is dominated by Brazil, so if that audience matters the origin decision is a genuine trade-off rather than an afterthought.
CNPD questions answered
The Portuguese regulator asks where data is held and who processes it, answered with a location and a subprocessor list.
Correct in one place, wrong in another.
The failure is a search returning nothing for a word that is plainly on the page, because the visitor and the author learned different official spellings of it.
- Known orthographic divergences folded for matching
- Regional variants given their own URLs and declarations
- Origin choice made knowing where the audience is
- Storage and processors documented
Lisbon is not the whole audience.
A Portuguese-language site often has more readers in Brazil than in Portugal, which makes origin placement a real decision rather than a default.
What we change for Portuguese sites
One language with two official written forms, and an audience that may be mostly on another continent.
| Setting | What we do | Why |
|---|---|---|
| Search folding | European and Brazilian spellings matched against each other | Both orthographies are correct and they diverge in specific, known ways, so literal matching fails for readers who learned the other one. |
| Regional variants | Given separate URLs with regional declarations | Publishing both variants without declaring them leaves a crawler reading two legitimate versions as duplicate content. |
| Origin decision | Made against where the audience actually is | Portuguese-language traffic is dominated by Brazil, so an EU origin may be serving the smaller half of the readership. |
| Storage disclosure | Location and processors recorded for the regulator | The Portuguese authority asks concretely, and an answer describing a provider's network does not close the question. |
| Log identifiers | Visitor addresses truncated before writing | Full addresses in plain files accumulate personal data for a purpose nobody documented at collection. |
Simple, transparent pricing.
Every plan includes free migration, daily backups, SSL and 24/7 support.
- 1 WordPress site
- 10 GB NVMe disk
- Free SSL
- Daily backups
- One-click deployment
- Support tickets
- 5 WordPress sites
- 50 GB NVMe disk
- Free SSL
- Daily backups
- One-click deployment
- Priority support tickets
- 20 WordPress sites
- 200 GB NVMe disk
- Free SSL
- Daily backups
- One-click deployment
- Dedicated support
Questions, answered.
Why does my Portuguese search miss words on the page?
Should I publish separate Portuguese and Brazilian versions?
Where should the origin be if most readers are in Brazil?
What does the Portuguese regulator ask about?
Be found in either spelling.
Move the site across. Migration is free, search configuration checked.