Illustrative scenario: not a client case study
During a rebrand, the team focused on a beautiful launch date. The quiet work that protected discovery was a spreadsheet mapping old URLs to the closest new destinations, reviewed by someone who understood both the customer journey and the content.
Inventory before design freezes
Crawl the current site, export analytics and Search Console landing pages, review backlinks and list important files, languages and templates. Include URLs that do not currently receive much traffic but hold useful equity or references.
Mark each URL as keep, improve, merge, redirect or retire, with a reason. Do not invent a replacement merely to fill a column.
Map intent, not only paths
Map an old product, service or location page to the closest page that answers the same decision. A generic home page is rarely a good destination for every retired URL.
Keep language and regional intent aligned. Check that Arabic, English, Dubai and Abu Dhabi variants do not silently point to the wrong audience.
Test the release candidate
Protect a staging environment from unintended discovery while checking links, canonicals, metadata, structured data, forms, redirects, robots rules and sitemaps.
Test representative old URLs and new templates, including mobile interactions and logged out access. Have content owners verify meaning, not only status codes.
Launch with a rollback conversation
Prepare the redirect rules, monitoring list, release owner and escalation path before launch. Preserve the old inventory and mapping so a confusing result can be investigated.
Avoid stacking multiple migrations or changing every content decision at the same moment when the timeline allows. Smaller changes make diagnosis clearer.
Monitor patterns after launch
Watch crawl errors, redirects, indexed examples, important landing pages, enquiries and server evidence. Compare groups of URLs rather than reacting to one impression change.
Fix broken redirects, missing links and accidental directives quickly; then update the map with what was learned. A migration finishes when the new site is stable, not when the switch flips.
Worked example
Illustrative release process using gnl.agency: export the current English and Arabic route list, map each changed route to its closest equivalent, test redirects in a staging release, and compare the post release sitemap with the approved map. Keep the old route when no equivalent is supported instead of inventing a destination.
What to take away
- Inventory current URLs and evidence before design freezes.
- Redirect to the closest useful destination.
- Test staging and representative old URLs.
- Monitor patterns and keep the mapping alive after launch.
Frequently asked questions
Do I redirect every old URL?
No. Redirect useful URLs to a genuinely relevant successor. Retire obsolete URLs deliberately and avoid sending unrelated visitors to the home page.
Should we change content during a migration?
Some improvement is sensible, but isolate major changes when possible. Keeping a clear change record makes discovery and conversion effects easier to interpret.
How long do redirects stay?
Keep them while users and external references may rely on the old address, following a reviewed redirect policy. Do not remove them simply because the launch is complete.