Choose languages from commercial evidence and review capacity
German, French, Italian and English versions should not be automatic copies. Prioritise them using customer location, sales ownership, existing demand and the ability to maintain accurate content. A complete first language is more credible than several neglected versions.
Assign a reviewer for each language before production. The reviewer should check terminology, offers, navigation, forms and legal wording in context. Automated translation can support drafting, but it does not own accuracy.
- Market and customer evidence per language
- Named content owner and reviewer
- Consistent services with locally natural wording
- Fallback plan for unavailable content
Protect useful URLs during the move
Inventory current indexable URLs, traffic, enquiries, links and business-critical content. Map every retained or replaced page to its destination and use permanent redirects when a URL changes. Avoid sending unrelated retired pages to the homepage.
Keep each language on a stable, crawlable URL. Use self-referencing canonicals and reciprocal hreflang annotations for equivalent versions. Update internal links and XML sitemaps, then test status codes after deployment.
- Current-to-new URL map
- Canonical and hreflang plan
- Redirect and broken-link test
- Accurate sitemap modification dates
Align forms and measurement with the real data flow
Document what each form collects, why it is needed, where it is sent, who can access it and how long it is retained. The privacy notice and consent interface should describe the implemented tools and workflow rather than generic possibilities.
Test analytics and campaign attribution without placing form contents or personal information into event parameters. If external services or cross-border processing are involved, obtain appropriate legal advice for the actual setup.
- Form purpose and minimum fields
- Processor and destination inventory
- Consent and tag behaviour
- Test submissions in every language
Run one accountable launch checklist
Name the person who can approve content, domain changes and the final release. Coordinate DNS, hosting, email-related records, redirects, analytics and rollback responsibility. Schedule the launch when owners can inspect real pages and forms promptly.
After launch, check indexability, canonical and language annotations, redirects, forms, mobile layouts and high-value journeys. Monitor search and enquiry data over the following weeks, but do not interpret normal short-term fluctuation as proof of success or failure.
- Named release and rollback owners
- Backups and access confirmed
- Rendered multilingual checks
- Post-launch monitoring dates
Frequently asked questions
Frequently asked questions
Does a Swiss business website need all national languages?
Not automatically. Choose languages based on the customers and markets you can serve, then ensure each published version is accurate and maintainable.
Should .ch URLs change during a redesign?
Only when the new architecture gives a clear reason. Preserve useful URLs where possible; when they change, map them to relevant destinations and implement permanent redirects.
Is this page legal advice about Swiss privacy law?
No. It is a project-planning checklist. Privacy wording and data-processing decisions should be verified for the tools, organisations and jurisdictions actually involved.