Complete inventory
A crawl of the existing site, cross-checked with Search Console and analytics, listing every page, file, form, redirect and external integration together with its traffic.
A migration has succeeded when visitors notice nothing except a faster site. These work steps make sure of that.
A crawl of the existing site, cross-checked with Search Console and analytics, listing every page, file, form, redirect and external integration together with its traffic.
Together we decide for each section: keep, merge, revise or delete. Deleted content that has visits or inbound links gets a sensible redirect.
Text, images, metadata and language links are moved by script rather than copied by hand. That preserves relationships, and the import can be repeated as often as needed before launch.
Every old URL is mapped to a new one and set up as a 301 redirect. We test the map automatically against the list from the inventory.
Language versions with correct hreflang tags, a consistent URL structure and a check that every page points to its proper counterpart in the other languages.
Booking engine, newsletter, forms, analytics with consent and all interfaces are set up in the new system and verified with real test transactions.
The old site stays online unchanged until the switch. The switch itself takes minutes; preparing for it takes a few weeks.
Crawl, traffic analysis and a list of all integrations. From these come the content decisions, target structure and a timetable that works around your peak season.
The target CMS is configured, the existing design carried over or a new one implemented, import scripts written and first trial imports run.
Old and new pages compared, all redirects and language links tested, and sign-off by your team on a staging environment.
Final import, domain switched in a quiet window, error pages and Search Console watched over the following weeks, with the old environment kept for a while as a fallback.
Every language multiplies the risk of a migration. A site in four languages does not just have four times the pages; it has four times the URLs, the hreflang links and the chances of one version being tied to the wrong one. A single hreflang mistake can lead Google to show a guest from Rotterdam the Italian page. On multilingual sites we therefore check each language pair individually, before and after the switch.
Yes. The new site is built and approved on a staging environment while the old one keeps running unchanged. The switch itself takes a few minutes and happens in a low-traffic window. For a hotel we schedule it outside the main booking period.
They are carried over if the old system allows an export. For security reasons passwords cannot always be transferred; in that case users get a link to set a new one when they first log in.
Minor fluctuations over a few days are normal. A lasting drop is usually caused by missing redirects or cut content, which is exactly what the redirect map prevents. We measure visibility before and after the switch to catch problems early.
That depends on who maintains the site, how many languages and integrations there are and what skills you have in-house. Common targets are WordPress, a current TYPO3 release or a headless CMS. We make a recommendation after the inventory.
Effort depends on page count, languages and how easily the old system can be read out automatically. After the inventory you receive a phased quote, and additional work is billed at €110 per hour plus VAT.
Tell us the current system, the rough number of pages, the languages and why you want to switch. We will reply with an approach and the risks we would keep an eye on.
Your enquiry has arrived
Our reply reaches you within one working day. Outages that leave your staff unable to work are dealt with first.
We could not find that town. Try another spelling, or choose whichever provincial capital lies closest; as everything is handled remotely, you get the same service in all nine Austrian states.