A website migration checklist for UAE businesses
Before replacing a website, list the old links customers still use and decide where each one should land. Test at least one complete booking from an old address to the person who handles it. Keep the list after launch so you can trace a lost enquiry or explain a change in search traffic.
Which pages and enquiry routes need to survive the move?
Walk through yesterday’s business before opening the design files. A visitor might have found an Arabic service page in Google, followed a link that reception sent six months ago or scanned a printed English price list. The redesign needs to account for all three ways in. A new homepage can work perfectly while the old booking link on the printed sheet takes customers to an error.
Collect addresses from the current sitemap, your list of published pages and the landing pages shown in Google Search Console. Add the links the business actually gives to customers. Look in email signatures, branch listings, saved WhatsApp replies, printed QR codes and active campaigns. Before opening a link, copy the full address printed on the card or stored in the message. Then open it on a phone and record the final address in a second column. A link that already redirects still needs to work after the move. Note the language, the offer on the page and who handles the next step. A brochure PDF or a booking page run by another provider can matter as much as a page in the main menu.
Keep a copy of the starting figures. In Search Console, save clicks and impressions by page for a recent period with complete data, using the UAE country filter if you want to measure UAE search traffic. In the enquiry log, record how many messages actually reached each branch in those dates. These two records answer different questions. If staff never recorded the source of an enquiry, leave it unknown.
Make a redirect map the branch manager can read
A redirect map is a list of old addresses and what a person should find at each one after launch. Have the business choose the closest equivalent page. Have the developer add the technical response and check it on the live site. Use the old address just as it appears on the printed card or in the search report, including the language prefix.
Imagine a training studio in Dubai moving its English and Arabic workshop pages to a new booking system. The studio and paths below are fictional. In your own sheet, use full addresses so that someone can spot a change of domain, too.
| Previous path | Decision | Customer check |
|---|---|---|
/en/classes/ |
Keep the address and serve the updated timetable here | Open a class and find its current dates |
/en/trial-class/ |
Permanently redirect to /en/workshops/trial/ |
The same trial and its booking option appear in English |
/ar/trial-class/ |
Permanently redirect to /ar/workshops/trial/ |
The Arabic visitor can book the same trial |
/en/past-one-off-event/ |
The event has ended and has no replacement. Return 404 or 410 if the page is removed | A useful error page offers a route to the current timetable |
Keep an old event page if people still need the programme, venue information or recordings. Mark the event as past and remove the expired booking action. Two pages can share a destination when that page genuinely covers both old offers. Sending every retired class to the homepage makes a saved link hard to use and Google may treat it as a soft 404. Google’s guide to moving a site with URL changes.
What should the developer show you before launch?
Ask for a test version and the completed map. Choose one address from each type of change. For a moved page, have the developer show a permanent server redirect, normally 301 or 308, leading directly to the final page. For an unchanged address, check that the page opens there. If only the hosting provider changes and all public addresses stay the same, there is no address change to explain to visitors. Google has a separate guide for moving hosting.
Open the new navigation, a service page and an article that sends readers to booking. Each internal link should go straight to its current destination. Ask which URL the page declares as its preferred version, also called its canonical. On pages with translations, check that the language switch reaches the matching service in the other language. A customer who selected the Marina branch should not have to discover that selection has silently changed when they switch to Arabic.
Agree who can pause launch if a critical booking route fails, and who can put the last working site back online. If both versions can accept bookings during the move, decide where staff will check both queues and how they will recognise an enquiry they have already handled.
Follow one old link all the way to reception
On launch day give the receptionist and the developer the same sample reference, such as MIGRATION-TEST-01. Open the old link from the studio’s saved message on a phone. Choose the trial, select the branch and submit a clearly labelled test enquiry using contact details your team controls. Write down what the visitor sees after sending. Ask reception to find the message by its reference and read back the branch, class and preferred language. A success screen tells you what the visitor saw. The message in reception’s inbox tells you what the team can act on.
Test a second entry route that bypasses the homepage, such as a QR code on a leaflet. For a WhatsApp link, check the recipient and send a marked test message if the recipient is expecting it. If a form creates a booking in a live calendar, use a slot staff have set aside and cancel the test afterwards. Record who checked each route and remove the test rows from sales reporting. Our guide to tracing an enquiry explains what to count when a click opens a conversation.
How do you check the move in Google Search Console?
Submit the updated sitemap in the verified property. When the whole site moves to a different domain, keep both properties verified. Once the site has moved and its redirects work, use the Change of Address tool for that domain move. For renamed paths on the same domain, use the redirect map and sitemap. Inspect a new service address and compare the indexed report with the live test. The indexed report describes Google’s stored information. The live test checks the URL as Google can reach it now. A successful live test can come before indexing and neither test verifies that reception received a booking. Google’s URL Inspection documentation.
Check an old address from each group in the map, then inspect the corresponding new address. On a moved page, expect the old address to redirect. On its replacement, check that the preferred address is correct and the page is available for indexing. If the indexed report still shows the old version, compare its last crawl date with the launch date before making further changes. Recheck the same samples once Google has crawled them again.
What to do if bookings or search clicks drop
If search clicks are steady but reception sees fewer enquiries, start with the booking path. Read the phone number on the WhatsApp link, check the form destination and run the marked test again. Look for messages arriving in an old shared inbox. If the form creates a record but no notification, have reception check that queue until its alerts work again.
If clicks appear to fall on the old page, add the equivalent new page to the comparison. Search Console may now attribute traffic to the new address. Compare the same country and the same number of complete days including the same weekdays. Mark closures, sold-out classes and campaigns that ended that week. A short period with very few clicks gives little evidence about the effect of the move.
If a crucial old link breaks, correct its redirect or restore its working content, then open that exact link again. If valid new pages are excluded from indexing, ask the developer to check for a preview-only address, an accidental noindex instruction or a canonical that points back to the old site. Keep the map after launch. It gives the next person an answer when a customer sends an old flyer and asks where to book.
For a rebuild, include the map and the enquiry tests in your website project brief. If you are asking BEIZ Studio to estimate a website redesign, a handful of real public links and a named person who can confirm receipt at each branch will help us agree what you can test at handover.
Know what you need?
Let’s make it happen.
Start with a conversation. We’ll come back with a plan, a timeline and an estimate.
Let’s talk