European WordPress hosting for twenty-seven versions of the same page.
One market, legally. In practice a different tax rate, language and set of expectations depending on which side of a border the visitor is on.
The same product, priced differently.
Selling across the EU means the page a visitor sees depends on where they are, which is the assumption caching is built to ignore.
A tax rate that depends on the buyer
Digital sales are taxed where the customer is, not where you are. A cached price that quotes one country's rate to another is a compliance problem rather than a display bug.
Language variants that stand alone
Each translation is a complete version of the site with its own URLs. They are cached separately and declared to search engines so none is treated as a copy of another.
One origin, every member state
An EU origin reaches Lisbon and Helsinki without a separate deployment for each, and keeps the data residency answer to a single sentence.
Currency and formatting per market
Prices, dates and addresses render differently across the union, and those variations are resolved per request rather than baked into a shared cached page.
One agreement covering all of it
A single processing agreement covers every market you sell into, rather than one conversation per country.
Where cross-border sites get caught.
The single market removes the customs paperwork, not the differences. Tax, language and consumer expectations all still vary by country, and all of them touch the page.
- Tax resolved by the buyer's country, not the seller's
- Each language cached and declared as its own version
- Single EU origin covering every member state
- One processing agreement across markets
Lisbon and Helsinki from one place.
The continent is small enough that a single well-placed origin serves all of it, which is what makes the residency and tax answers manageable.
What we change for European sites
Every row comes from the same fact: the correct response varies by the visitor's country, and caching wants it not to.
| Setting | What we do | Why |
|---|---|---|
| Tax resolution | Cache keyed by the buyer's country for priced pages | Digital sales are taxed where the customer is, so a shared cached price quotes one member state's rate to a buyer in another. |
| Language variants | Cached independently with each version declared | Every translation is a full site with its own URLs, and serving one from another's cache entry is what makes them look like duplicates to a crawler. |
| Origin placement | Single EU origin covering all member states | The continent is compact enough that one location serves every market, which keeps residency a one-sentence answer instead of a per-country matrix. |
| Locale formatting | Resolved per request rather than baked into the page | Currency, date and address formats differ across the union, and freezing one country's format into a shared cached response is wrong everywhere else. |
| Agreements | One processing agreement covering every market | A separate arrangement per country turns a single-market sale into twenty-seven procurement conversations. |
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.
How is VAT handled across EU countries?
Do I need a server in each country?
How are translated versions handled?
Is one agreement enough for all markets?
Sell into all of it from one place.
Move the site to an EU origin - migration is free, every market covered.