Getting a website for business in Austria looks like a solved problem – until you hit the local rules that no generic tutorial mentions. As someone who builds websites in Vienna for founders from all over the world, I see the same avoidable mistakes again and again: a missing Impressum, a cookie banner that does nothing, a site in English only that quietly turns away half the local market. This guide walks you through what is genuinely Austria-specific, how to find and vet a developer here, the traps that catch newcomers, and a launch checklist you can actually work through. Practical, not theoretical.
What makes Austria different
Most of the web works the same everywhere. A handful of things do not – and in Austria, getting them wrong ranges from embarrassing to legally expensive.
The Impressum (§ 5 ECG) is mandatory
This is the one newcomers miss most often. Austrian law (§ 5 of the E-Commerce-Gesetz, ECG) requires a legal notice – the Impressum – on almost every business website. It must state, among other things, your company name, physical address, contact details, commercial register number and UID (VAT ID) where applicable, and the chamber of commerce membership. It has to be easy to find, typically one click from every page. A missing or incomplete Impressum is not a formality: it can trigger warnings (Abmahnungen) and real fines. If you take one thing from this article, take this.
GDPR and cookies – with EU teeth
You have heard of GDPR, but in Austria enforcement is real, not theoretical. Any tracking, analytics or embedded service that sets cookies or sends data needs a proper consent banner – one that actually blocks scripts until the user agrees, not a decorative bar that loads Google Analytics regardless. You also need a privacy policy (Datenschutzerklärung) describing what you collect and why. Google Fonts loaded from Google servers famously triggered a wave of warnings here; self-hosting fonts is now standard practice for good reason.
The .at domain and the language question
A .at domain signals „local and here to stay” to Austrian customers and is worth registering even if you also hold a .com. Registration runs through nic.at and requires valid contact data. The bigger strategic decision is language: Austria is a German-speaking market, and a German-only or German-plus-English site will almost always outperform English-only for local customers. If your audience is genuinely international, a bilingual site (German and English) is the pragmatic answer – built properly with correct language tagging so search engines serve the right version.
Payments: EPS, Klarna and the local habits
Card payments work, but Austrian shoppers have local preferences. EPS (Electronic Payment Standard) is an Austrian online bank-transfer method that many customers expect and trust. Klarna (buy now, pay later / invoice) is widely used across the DACH region. Offering only PayPal and card leaves conversions on the table. For a shop targeting Austrian buyers, plan for EPS and Klarna alongside the usual options from the start.
Invoices, UID and the paperwork behind the site
If you sell online, your invoices must meet Austrian requirements: your UID (VAT ID) where you have one, correct VAT rates, sequential invoice numbers and the legally required details. This is less a website feature than a business-setup question, but it shapes how your shop and checkout need to behave – so raise it with your developer early rather than discovering it after launch.
Austria-specific requirements at a glance
| Requirement | What it means | Why it matters |
|---|---|---|
| Impressum (§ 5 ECG) | Legal notice with company details, register no., UID, chamber membership | Mandatory; missing one risks warnings and fines |
| GDPR consent + privacy policy | Script-blocking cookie banner, Datenschutzerklärung | Enforced in the EU; decorative banners do not count |
| .at domain | Local domain via nic.at, valid contact data | Signals local presence and trust |
| German (+ English) content | At least German for local reach; bilingual if international | English-only quietly loses local customers |
| EPS / Klarna payments | Local bank transfer and pay-later options | Expected by Austrian shoppers; boosts conversion |
| Compliant invoicing | UID, correct VAT, sequential numbers | Legal requirement for selling online |
How to find a developer – and what to ask
The hard part is not finding someone who can build a website; it is finding someone who understands the Austrian context and will not vanish after launch. When you talk to a candidate, these questions separate the professionals from the order-takers:
- „How will you handle the Impressum and GDPR consent?” A competent developer answers this without hesitation. A blank look is a red flag.
- „Will the site be bilingual, and how do you set up German and English?” Look for a proper multilingual setup with correct language tags, not two disconnected copies.
- „Who owns the domain, hosting and accounts?” The answer must be: you. If access stays with the agency, you are a hostage, not a client.
- „What happens after launch – updates, backups, support?” A website is not a one-off. Clarify ongoing care before you sign, not after something breaks.
- „Can I see live sites you built for businesses here?” Real local references beat a polished portfolio of templates.
For a sense of what a full build involves end to end, my web development service page lays out the process; if you are weighing budgets, I have written separately on what a professional website actually costs.
One more practical note on working across a language barrier: you do not need to speak German to run this process well, but your developer does need to bridge it for you. The legal texts – Impressum, privacy policy, terms – exist in German for a reason, and a good partner will either provide compliant versions or point you to the right source, rather than leaving you to translate a boilerplate and hope. If a candidate treats the German-language compliance side as „your problem”, that tells you how the rest of the project will go.
Typical traps for newcomers in Austria
The mistakes I clean up most often, so you can avoid them:
- English-only, „we will add German later”. Later rarely comes, and every month you lose local visitors who bounce because they cannot read the site comfortably.
- A cookie banner that blocks nothing. Installed to look compliant, it loads tracking regardless – the worst of both worlds: no consent, full liability.
- No Impressum, or one copied from a German site. Austrian requirements differ from German ones; a copy-paste Impressum can be as wrong as none.
- Ignoring local payment habits. A shop without EPS or Klarna feels foreign to Austrian buyers and converts worse.
- Agency lock-in. Domain and hosting registered under the agency name, no admin access for you – until you want to leave and cannot.
There is a pattern behind most of these: treating the website as a one-time purchase rather than a running part of the business. The Impressum needs updating when your details change, the consent setup needs to keep pace with the tools you add, and the German content needs to actually exist before you count on local customers finding you. Newcomers who see the site as „build it once and forget it” hit these walls six months in – exactly when the business is starting to depend on it.
Launch checklist
Before you go live, walk through this list – it covers the Austria-specific essentials the generic guides skip:
- Complete, correct Impressum linked from every page (§ 5 ECG)
- Working, script-blocking cookie consent plus a privacy policy
- German content in place (bilingual if your audience is international)
- .at domain registered with valid contact data, and you as the owner
- Local payment methods (EPS, Klarna) enabled if you sell online
- Compliant invoicing with UID and correct VAT set up in the shop
- Self-hosted fonts and no uncontrolled third-party data transfers
- Backups, updates and a support arrangement agreed in writing
- Full admin access to domain, hosting and all accounts held by you
Conclusion
A website for your business in Austria is not harder to build than anywhere else – it just comes with a handful of local rules that a generic developer will skip and a local one will handle without being asked. Get the Impressum, real cookie consent, German content and local payments right, keep ownership of your domain and accounts, and you have a site that works for Austrian customers and stays out of legal trouble. The expensive mistakes here are all avoidable if you know they exist – which, having read this, you now do.
Setting up a business in Austria and need a website that fits the local rules from day one? Send me a quick message via the contact form. I will walk you through what your project needs – in plain English, no legalese – usually the same working day.
