Your rebuilt homepage loads perfectly. But a customer opens an old quotation link and lands on an unrelated page, while a bookmarked service page returns an error. A website move is not complete merely because its front page looks correct.
For a UAE business changing page URLs, the practical question is whether each valuable old link still takes visitors to the right information and enquiry route. This guide explains how to prepare and accept a redirect map. Google documentation was checked on 11 October 2026.
First establish whether your URLs are changing
A hosting change that preserves the same public URLs is different from a move that changes the domain, subdomain or page paths. Google's hosting-change guidance focuses on preparing and testing the new infrastructure, switching DNS and monitoring traffic. Do not invent new page addresses simply because the hosting provider changed.
If URLs are changing, record both old and new locations. A redesign, a domain move and a content rewrite are separate decisions; combining them makes the cause of any problem harder to isolate. Agree what must change before building redirect rules.
Build the old-to-new map from real entry points
Start with the existing sitemap, a crawl of the current site and any available landing-page or server-log data. Ask sales and marketing for URLs used in quotations, QR codes, campaign links and customer messages. Include important PDFs and language versions, not only pages linked from the main menu.
For each old address, record its intended destination, decision owner, expected response and test result. Use explicit outcomes:
- Unchanged: keep the URL and verify that the expected content still loads.
- Moved: send visitors to the matching replacement page.
- Consolidated: use a combined page only when it genuinely answers the old page's purpose.
- Retired: agree what should happen when there is no relevant replacement, rather than hiding every removal behind the homepage.
A hypothetical supplier moving an installation guide should point the old link to the corresponding guide or a relevant consolidated resource. Sending that visitor to a broad corporate homepage loses the context that brought them there.
Check the response and the destination
Google's URL-move guidance recommends server-side permanent redirects, such as 301 or 308, where possible. It advises direct destinations rather than chains and warns that unrelated homepage redirects can be treated as soft 404 errors. A page that visually loads is therefore not enough evidence.
Have the developer or migration specialist record the first response, every redirect hop, final URL and final response for each mapped address. Then have a business reviewer open priority destinations and confirm that the correct service, language and contact route are present.
ITZ's website migration service can scope the mapping and acceptance checks. Request a Website Redirect Review with the current site address, planned changes and important campaign or customer links.
Run a focused acceptance checklist
- Priority old links: test service pages, campaign landing pages, frequently shared downloads and both language versions where applicable.
- Direct links: check bookmarks and external entry points, not only navigation from the homepage.
- Destination content: verify the expected page and ensure it is not an error message disguised by a successful response.
- Enquiry journey: on mobile, follow the relevant CTA, check form access and confirm that service context is retained.
- Query strings: test important campaign parameters and functional parameters separately; do not strip everything without understanding its purpose.
- Missing pages: test a deliberately nonexistent URL and verify an honest, useful error response.
- Loops and broad rules: test combinations of HTTP/HTTPS and www/non-www hosts without creating circular redirects.
Use a controlled form test only with the owner's approval and a clearly identified test submission. A visible success screen alone does not establish inbox delivery or a genuine sales lead. If submission is outside the test scope, record that limitation explicitly.
Align the page signals and keep monitoring
Update internal links, canonical URLs, the sitemap and applicable language annotations to the intended destinations. Remove staging-only indexing blocks from production pages that should be discoverable. Google's migration guidance generally recommends retaining redirects for at least a year, and longer where people still use old links. Search visibility can fluctuate during processing; no redirect plan guarantees unchanged rankings.
Assign an owner to review failures after launch. Keep a dated issue list with the old URL, observed result, intended destination and correction. Prioritise broken customer journeys over cosmetic cleanup. For broader discovery problems, coordinate a separate technical SEO review instead of treating every traffic change as a redirect fault.
Use the website launch checklist for adjacent launch tasks. Track actual enquiry submissions and business follow-up separately from page visits or CTA clicks. A migration report should state what was tested, what remains unresolved and which measurement data is available.
Request your website redirect review
Share the current and proposed domains, a sample of important old links and the intended launch date. Ask ITZ to define a review covering the URL map, redirect responses, destination content and mobile enquiry access. The concrete next step is a prioritised correction and acceptance plan.
