14 Nov 2026
Article

Umbraco to WordPress Redirect Mapping: Keep Old Links Connected to the Right Content

Prepare a reviewable URL map for an Umbraco migration, including historical redirects, language paths and destinations that match the original content.
Jagjeet Singh, full stack developer and WordPress engineer
Jagjeet Singh

Full Stack Developer · WordPress Engineer

Illustrative content editing workspace with modular website sections, a tablet preview and printed block sketches.

In this article

Illustrative workspace or concept artwork; not a photograph of a client office or a screenshot proving delivered project features.

A redesigned WordPress website can launch successfully while older links from search results, customer bookmarks and campaign material lead nowhere useful. An Umbraco migration needs a map between the addresses people already use and the content they should reach after launch.

Redirect mapping is a distinct deliverable within Umbraco to WordPress migration. It should be reviewed alongside the content model and rebuilt templates. I can scope that work around the website’s actual URL history, with a testable destination list rather than an assumption that every old address should go to the new homepage.

Inventory published URLs and historical entry points

Start with the current sitemap, published content export, known campaign links and available search or analytics landing-page records. Include important downloads and other entry points that are part of the agreed scope. Record where each address came from so the agency can distinguish a current page from an older link still in use.

Do not rely on a single homepage crawl for a large website. A page may be reachable through a campaign, another domain or an old redirect without appearing in the main navigation. Ask the existing maintainer about those routes before the old environment is decommissioned, while the configuration can still be inspected.

Review Umbraco’s existing redirects separately

Umbraco’s URL Redirect Management documentation describes tracking old document URLs after publishing changes and serving redirects when a saved address matches. That existing history is relevant to a platform migration; a list of only today’s preferred URLs can miss it.

Ask for the redirect inventory and any additional server or proxy rules. Do not assume all routing behaviour lives in one CMS screen. Identify which rules are exact addresses, which depend on a host or language, and which need separate review before an equivalent is implemented on the new hosting setup.

Match destinations by purpose and content

For each old address, identify the equivalent new page, a genuinely relevant consolidated page or a deliberate retirement decision. Put the decision and reviewer in the mapping file. A redirect should help a visitor continue the task that brought them to the old page.

If several pages are being merged, ask the content owner to approve the relationship rather than automatically assigning the broadest service page. If no suitable replacement exists, record that fact and agree the appropriate response. A large migration is easier to review when uncertain destinations are visible instead of hidden behind a blanket rule.

Treat language and hostname changes explicitly

A multilingual site may have language segments, separate domains or other routing conventions. Record the old language and the intended new language for each page. A translated page should not silently send a visitor to unrelated default-language content merely because the paths look similar.

Check how hostnames, trailing slashes and relevant query parameters are handled. Distinguish a tracking parameter from a parameter that changes the actual content. The migration brief should identify those behaviours and the systems responsible for them, with representative examples available for acceptance testing.

Choose permanent redirects without unnecessary chains

Google’s site-move guidance recommends server-side permanent redirects, such as HTTP 301 or 308, where technically possible. A permanent redirect tells a browser or crawler that the content’s address has moved; it does not guarantee an unchanged ranking.

Aim to connect an old entry point directly to its intended final destination. If an old address already redirects to another old address, review the full path rather than carrying unnecessary intermediate steps forward. Test for loops and destinations that return an error. Keep the implementation method appropriate to the host and the agreed maintenance process.

Update links within the new website as well

Redirects help older entry points, but the new website should use its intended addresses internally. Review navigation, body links, image links, buttons and download references. A site that constantly sends its own visitors through old addresses creates avoidable complexity and makes future troubleshooting harder.

Include the preferred page addresses and the new sitemap in the launch checks. Also inspect representative translated pages and links inside imported rich text. A redirect map and an internal-link review are related tasks with different evidence, so the quote should state whether both are included.

Test the map and agree post-launch review

For the agreed inventory, check the original address, response, redirect path and final destination. Keep the expected result alongside the observation. Prioritise important enquiry pages and entry points with known traffic, while recording any exclusions from the test scope.

After the authorised launch, review available error and search data for relevant missed addresses. Not every new error requires a redirect: the content owner should decide whether the request belongs to the site and has a suitable destination. Agree who handles that review and how later additions to the map are approved.

Send a URL inventory for a migration proposal

Share the existing website, CMS and hosting access constraints, planned language structure, proposed page list and any available redirect export. Identify content being merged or retired and the person who can approve destinations. Explain when the old environment is expected to become unavailable.

Through Umbraco to WordPress development and migration, I can quote the content mapping, rebuild and agreed redirect checks. Keep those deliverables visible in the brief so the project is evaluated on the visitor journey as well as the appearance of its new templates.

Jagjeet Singh, full stack developer and WordPress engineer

Written by

Jagjeet Singh

Full stack development, WordPress engineering and practical web products. I work with businesses, teams and agencies in India and worldwide.

Put the ideas to work

Let’s build something useful.

A website, online store or a system that fits the way your business works.