Skip to content
العربيةLet’s talk

Practical guide

Website redesign: map old URLs and verify every destination

Prepare an old-to-new URL register for a website redesign, review meaningful replacements, test redirects and monitor unresolved paths after launch.

Lava Solutions · · 5 minute read

Two people arrange sticky notes on a glass board during a planning workshop.
Illustrative stock photo. Photo: airfocus / Unsplash.

A website redesign needs a decision for every important old address: keep it, send it to an equivalent new page, or retire it deliberately. A visually complete homepage does not show whether an old service link, saved brochure or Arabic landing page still takes visitors to the right information.

Use a URL migration register to make those decisions reviewable before launch. This guide concerns redesigns that change page addresses, with official sources checked on 18 November 2026. The examples are fictional. Search visibility can change during a move; a checked migration plan manages avoidable problems without guaranteeing unchanged rankings or traffic.

Start with the addresses people already use

Build a list from the CMS, sitemap and available URL exports or access logs. Include affected downloads and images. Google's site-move guide describes preparing old-to-new URL mappings and accounting for embedded assets.

Combine the lists without discarding their origins. A URL found only in an old brochure can still matter to a customer. Assign each record a content owner, current purpose, language, proposed destination and decision status. Keep unknowns visible instead of silently substituting the homepage.

Take a dated baseline for the pages whose continuity matters. Record what they explain, the useful downloads they offer and the next action. This gives the reviewer something to compare against the redesign beyond the page title.

Approve destinations by meaning

Ask whether someone following the old link would recognize the new page as the answer they expected. Similar wording in a URL is weak evidence. A retired maintenance service and a new equipment-sales page may share a product name but serve different needs.

Google's redirect guidance identifies server-side 301 and 308 responses for permanent moves. Choose a permanent redirect when the content really has a permanent replacement. A temporary detour is a different decision and should have an owner and review date.

For content genuinely removed with no suitable replacement, agree the removal explicitly. Google's HTTP status documentation explains that 404 and 410 responses indicate unavailable content to its crawlers. An error message styled like a page but returning success is not the same evidence as a correct status response.

A fictional mapping review

The paths below belong to a fictional business website. They are planning examples, not working Lava routes.

Old pathProposed resultReview decision
/pump-service/services/pump-maintenance/Redirect after confirming the same service scope survives
/ar/pumpsArabic counterpart still missingUnresolved: supply the equivalent page before approval
/files/pump-guide.pdfSame file at the same addressKeep and test download; verify the document is still accurate
/events/old-open-dayNo replacement or ongoing information needOwner approves removal and an appropriate error response

The Arabic row remains blocked even if the English service page exists. The reviewer should not approve an unrelated destination merely to fill the cell. If the business decides a different-language destination is necessary, record that visitor impact explicitly instead of calling it a complete Arabic counterpart.

Test each redirect through to its final content

Give the developer the approved mapping, not a verbal instruction to “redirect the old site.” For each changed URL, record the first response, destination, number of hops, final status and content match. Check for loops and an intermediate URL that redirects again. Google's move guidance recommends going directly to the final destination.

Test meaningful variants found in your inventory: an old trailing slash, a legacy file extension or a query-based address that served distinct content. Do not assume all query parameters are disposable. A generic rule can collapse different pages into one destination if the original routing logic is overlooked.

Ask a second reviewer to open the final page and check the service meaning, language, primary action and promised download. A technically successful redirect can still send people to the wrong offer. Keep the status check and content check together in the register.

Align the new site's own references

Replace internal links that still travel through old addresses. Review navigation, body links, language switching and document links. Google's canonical guidance recommends consistent canonical signals and links to the preferred URL. Check that a new page does not still declare its old or staging address as canonical.

Update the sitemap to the intended canonical destinations. Google's sitemap guidance explains that it lists preferred URLs and that submission does not guarantee crawling. Treat a valid sitemap and correct redirects as separate checks; one does not repair the other.

Keep the mapping alive after launch

Assign an owner for newly discovered old links, broken downloads and destination mistakes. Capture the launch time and every later correction so a change in observations can be investigated. Review unexpected missing-page requests against the register before adding broad redirect rules.

Use Search Console URL Inspection to distinguish information about Google's indexed copy from a live eligibility test. A successful live test does not establish that Google has indexed the page. Compare the relevant observations over time, with the same scope and filters.

Google advises keeping move redirects for as long as possible, generally at least one year. Preserve the hosting or redirect arrangement required to serve them, and record who maintains it. Do not remove the map when the visual redesign is signed off.

For Arabic and English page review, see the bilingual acceptance guide. To scope a redesign, explore Lava's website services or send your current site and proposed structure. Include known old URLs and important documents so the conversation covers continuity as well as design.

Sources & further reading

A useful next step

Bring one real workflow.

Share the process you want to improve, the systems involved and the decision you need to make.

Talk to Lava ↗