←  All terms
R
Migration & Relaunch

Redirect Mapping

Redirect mapping pairs old URLs with appropriate new destinations, especially during migrations and relaunches.

Redirect mapping creates a clear relationship between existing URLs and their new destinations during a migration or relaunch. Old URLs should be inventoried carefully and matched to the most relevant replacement pages wherever possible. Thorough testing before launch and continued monitoring afterward help prevent broken redirects, unnecessary chains, and avoidable SEO losses. The concept is closely related to Redirect and SEO Migration.

Read more

Redirect

SEO Migration

Content Inventory

Website Migration

FAQ

Redirect Mapping

How does redirect mapping handle pages with no new counterpart?
Pages without a counterpart are redirected to the closest relevant overview page or deliberately answered with a 410 or 404 status. Redirecting to the homepage is considered a weak solution because content and destination do not match. The decision is made per URL group and recorded in the mapping.
What typical mistakes happen in redirect mapping?
Common mistakes include blanket redirects to the homepage, redirect chains, and forgotten URLs that carry backlinks or traffic. Loops and typos in destinations add to the list. These errors usually stem from a missing inventory and missing tests. A spot check rarely suffices; an automated comparison of every row in the table is more reliable.
How does redirect mapping differ from a single redirect?
A single redirect is the technical rule; the mapping is the planning behind it. The mapping decides which old address leads to which destination and supplies the blueprint for many rules at once. Without that planning, isolated rules pile up with no overall picture, often producing chains, loops, or blanket redirects to the homepage.
How is a redirect mapping built?
The starting point is a list of all known legacy URLs, drawn from a crawl, the sitemap, analytics, and Search Console. Each address gets a topically matching destination and a redirect type. The table is tested against the new site before launch. Source, target, and rationale should be documented so later changes stay verifiable.
When is a redirect mapping needed?
A redirect mapping is needed whenever URLs change: during a relaunch, domain change, platform switch, or new site structure. Without it, visitors and crawlers land on error pages, and accumulated signals are lost. Purely visual changes that keep every address need no mapping. The deciding question is whether existing addresses remain reachable.