A website redesign is the moment when many Gulf businesses quietly lose their search traffic. New designs change URLs, drop pages that were earning enquiries, leave out the Arabic version, break the WhatsApp button or forget the map link, and nobody notices until calls fall. This checklist is for owners and marketing managers who have commissioned a revamp, and for the people building it. It follows Google's published guidance for site moves and adds the Gulf-specific items we check on bilingual sites with WhatsApp-led enquiry flows. Work through it in four phases: before you design, before you launch, on launch day, and in the weeks afterwards.
Phase 1: before design starts
- Crawl the current site and export every URL with its title, status code, indexability and word count. Include the Arabic section.
- Record your baseline. From Search Console and analytics, export clicks, impressions and top queries by page for the last 12 months, and enquiries by source (forms, calls, WhatsApp clicks, direction requests). Without a baseline you cannot tell whether the new site is better.
- List the pages that earn enquiries. Mark each as keep, merge, improve or retire. Pages with enquiries or backlinks should not be retired casually.
- Collect backlinks. Use Search Console's links report and your own records to list the pages other sites point to.
- Inventory every integration. Forms, CRM, WhatsApp widgets, call tracking, booking systems, payment gateways, maps embeds, tag manager and analytics.
- Agree what must not change. Business name, phone numbers, address format and opening hours must stay consistent with your Google Business Profile.
Phase 2: build the redirect map
Google's documentation on site moves with URL changes says to decide where each old URL should redirect, use permanent server-side redirects (301 or 308 where possible), and point each old URL directly at its final destination because chained redirects add latency. It warns against sending many old URLs to one unrelated page such as the new home page, which may be treated as a soft 404, and says to keep redirects for as long as possible, generally at least one year.
- Create a spreadsheet with columns for old URL, new URL, redirect type and notes. Every indexed old URL gets a row.
- Match by topic. A retired service page should redirect to the closest remaining service page, not the home page.
- Map the Arabic URLs too. A frequent failure is redirecting English pages and forgetting Arabic ones.
- Include URL variants: with and without trailing slash, www and non-www, and old query-string URLs that are indexed.
- Test the map on staging with a script that requests each old URL and confirms a single hop to the right target.
Phase 3: content, structure and technical checks on staging
- Titles, descriptions and headings. Every page has a unique title and description and one H1. Don't let the template replace good page titles with the business name.
- Indexing controls. Remove staging noindex tags and password protection at launch, and remove any robots.txt block. Check the live robots.txt and canonical tags after launch.
- Canonicals. Each page points to itself; Arabic pages do not point to English ones.
- Hreflang. If you have English and Arabic, each pair must reference each other and itself. Our technical guide on bilingual website structure has the rules.
- Arabic version. Confirm the Arabic pages are included in the new build, with RTL layout, Arabic metadata and Arabic form messages. A revamp is a bad time to discover the Arabic section was a plugin the new theme doesn't support.
- Internal links. Update navigation and in-page links to the final new URLs so they do not rely on redirects.
- Structured data. Carry over organisation, local business, breadcrumb and FAQ markup where it matches visible content. Do not add rating markup you cannot support.
- Performance. Test on a mid-range Android phone on mobile data; compress images; avoid layout shift from late-loading widgets.
- Images. Keep descriptive file names and alt text, in both languages.
Phase 4: Gulf-specific enquiry paths
- WhatsApp. Test every WhatsApp button and link on iPhone and Android: does it open the right number with the right prefilled text? Check it doesn't cover the primary call-to-action or cause layout shift on small screens.
- Calls. Make phone numbers tappable. If you use call tracking, make sure the number on the site still matches the Google profile enough for consistency.
- Maps. Check the embedded map and the direction link point to the correct place. For service-area businesses, don't publish an address nobody visits; see our guide to Google Maps for service-area companies.
- Forms and consent. Confirm forms reach the CRM, the confirmation message shows, and marketing consent boxes are unticked and stored. See our UAE consent guide for the records to keep.
- Regulated content. Clinics and property companies must re-check required elements after redesign: licence or permit numbers and advertising wording. See our guides on DHA clinic advertising rules and permit numbers on property sites.
- Payments and booking. Run a real transaction in test mode and then live with a small amount, if your site takes payments.
Launch day
- Launch at a low-traffic time and avoid peak seasons such as the weeks around Ramadan and Eid, when your team may be away.
- Deploy redirects together with the site, not afterwards.
- Run the crawl against the live site and compare it with the old inventory.
- Submit the new sitemap in Search Console and remove the old one. Google's guide says old sitemaps can show redirect warnings during a move, which can be ignored. Change of Address is only needed if the domain changes.
- Check the live robots.txt, a sample of canonical tags and hreflang annotations.
- Test forms, WhatsApp, call links and analytics events on the live site.
- Update URLs on your Google Business Profile, social profiles, email signatures and directory listings.
The first four weeks after launch
- Check Search Console daily in the first week for crawl errors, soft 404s and sudden drops in indexed pages.
- Compare weekly clicks and enquiries with the baseline. Google says that for small and medium sites a move can take a few weeks to settle, and larger sites longer, so don't judge on day two.
- Fix 404s that have backlinks first.
- Ask sites that link to you to update their links to your new URLs.
- Keep the redirects live for at least a year, as Google advises.
Red flags to raise with your developer
- "We will redirect everything to the home page."
- No staging site, or no way to test redirects before launch.
- The Arabic version is "phase two".
- Nobody has access to the old analytics and Search Console data.
- The new site is image-heavy with text embedded in pictures.
How FiveNodes can help
We run revamps remotely from our Lahore engineering hub, with an Albuquerque HQ address and no Gulf office, and we can review a planned redesign before it launches. See our web design and development service, SEO service, and the market pages for the UAE and Saudi Arabia. Request a free audit of your current site or contact us.