Map every old URL to the right new page
A redirect map lists every old URL next to the new URL it should land on. It decides where every visitor and crawler that asks for an old URL ends up. Google puts it plainly: "It's important to map your old site's URLs to the URLs for the new site."
This page covers what goes into the map, how redirect.pizza runs it for the domain you move away from, and how to check it after launch. URL changes on a hostname that keeps serving your site belong in your web server, CMS or CDN. For the full timeline, from a week before the move to a week after, use the domain migration SEO checklist.

What goes into a redirect map
- Every old URL that still matters. Pages with backlinks, traffic or rankings. Search Console, your analytics and a crawl of the old site give you the list.
- The closest match on the new site. A product goes to the same product, an article to the same article.
- One destination per old URL. Don't send many old URLs to the new homepage. Google may treat that as a soft 404.
- Merged pages are the exception. When the content of several old pages now lives on one new page, Google says they can all redirect there.
- Pages with no new equivalent. Don't force a match. Google says their URLs should return a 404 or 410 on the new site.
- A permanent redirect. Google recommends 301 or 308 for a move, and says permanent redirects don't cause a loss in PageRank.

How redirect.pizza runs the map
Import it as a CSV
Each row is a source and a destination. Import and export work on every plan. Save the map in the import format, and the spreadsheet becomes your redirect list in one upload.
Let path forwarding cover what keeps its path
If a section keeps its paths on the new domain, it doesn't need a row per URL. With path forwarding, old.com/contact lands on new.com/contact. It's on every plan.
Use regex for patterns
From Pro (Prosciutto e Funghi), one regex source can match a whole section. Start the source with an exclamation mark, wrap the part you want to keep in parentheses and reuse it in the destination as $1.
!old.com/news/(.*) redirects to https://new.com/articles/$1
Know what catches the rest
redirect.pizza matches an incoming URL in a fixed order. First the exact URL, then the same URL without case sensitivity, then the path without its query string, and finally the hostname on its own.
That last one, a root path redirect, catches every URL you didn't map. With path forwarding on, those URLs keep their path on the new domain, and a page that no longer exists there gets the new site's 404. With it off, they all land on one destination. Hundreds of old URLs on one page is what Google may treat as a soft 404. Map the URLs that matter.
Size the map against your plan
Path rules count across your whole team. Free (Margherita) includes 10 and Basic (Pepperoni) 100. Pro has 5,000, Business (Quattro Stagioni) 25,000 and Enterprise (Make Your Own) no limit. Compare the plans on the pricing page.
Keep redirect chains short
Every migration can add a hop: the 2019 URL redirects to the 2022 URL, which redirects to today's. Google recommends avoiding chains. With redirect flattening, from Pro, redirect.pizza skips the hops that run through redirect.pizza and sends visitors straight to the final destination. Hops on your own server can't be flattened.
Check the redirects after launch
- Spot checks. Paste old URLs into the redirect checker to see the status code and the final destination.
- Crawler traffic. Analytics, from Basic, splits crawler and human traffic and lists your top 50 URLs. The raw logs, from Business, filter on crawler traffic, so you see which old URLs search engines still request.
- Broken destinations. Destination monitoring, from Pro, checks every monitored destination once an hour from probes in several regions. Broken ones show up in your overview and your summary email.
- Search Console. Watch crawl errors and indexing. For a medium-sized site, Google says it can take a few weeks or more before it shows the new URLs instead of the old ones, and longer for large sites.
- How long to keep them. At least a year, as Google recommends, and longer if you can.
HTTPS on the old domain
Old URLs get requested over HTTPS too, from bookmarks, backlinks and search results. Without a valid certificate on the old domain, the browser stops at a warning before the redirect can run. That's why HTTPS redirects break. redirect.pizza issues and renews a certificate for every source hostname, with automatic HTTPS on every plan.
Frequently Asked Questions
Map every old URL that has links, traffic or rankings to its closest match on the new site, and use permanent redirects, 301 or 308. Keep a valid certificate on the old domain, avoid redirect chains and keep the redirects for at least a year. Google says to expect temporary fluctuation while it processes the move, so watch Search Console in the weeks after the switch.
A spreadsheet is enough to build the map: one column for the old URL, one for the new one. To run it, save it in the import format and import it into redirect.pizza. It answers the old domain's requests, so you don't need a server for it.
