301 Redirect Map Template for Website Redesigns in 2026

A website redesign can look perfect and still bleed search traffic because the old URLs were treated like trash.

That is the part business owners rarely see. The homepage loads. The new design looks clean. The agency sends the launch email. Then leads get weird, old bookmarks hit dead ends, Google Search Console fills with errors, and the pages that used to bring steady quote requests quietly disappear.

A redirect map prevents that mess.

Not a vague note that says “redirect old pages.” A real URL-by-URL map that shows where every valuable old page should go, who approved the destination, how important the page is, and how the redirect was tested after launch.

Google’s own site move documentation says to set up redirects from old URLs to new URLs and keep redirects for as long as possible, generally at least one year. Google’s redirect documentation also says 301 and 308 status codes mean a page has permanently moved to a new location, while temporary redirects such as 302 and 307 tell Google a move is not permanent.

That is why redirect mapping belongs in the project plan before development starts, not in a panic after launch.

What is a 301 redirect map?

A 301 redirect map is a working document that matches old URLs to their new destinations before a website redesign, CMS rebuild, domain change, URL cleanup, HTTPS move, or content consolidation.

The simplest version has two columns: old URL and new URL.

That is better than nothing, but it is not enough for a serious business website. A useful redirect map also records the current status code, proposed destination, page type, traffic value, backlink value, decision reason, implementation owner, QA result, and post-launch notes.

The goal is not to redirect everything blindly. The goal is to protect useful paths and retire dead ones cleanly.

Google explains that server-side redirects are preferred when you need to redirect users and search engines. Screaming Frog’s redirect audit workflow shows why the details matter, since a crawl can reveal redirect chains, redirect loops, final destinations, and status codes. That is the difference between a migration plan and a spreadsheet nobody trusts.

When you need a redirect map

You need a redirect map any time old URLs might stop resolving at their original address.

That includes redesigns, replatforming projects, WordPress rebuilds, Webflow moves, Shopify theme or collection changes, domain changes, HTTP to HTTPS migrations, URL slug cleanup, blog pruning, service page consolidation, location page cleanup, and ecommerce category restructuring.

Google treats a site move with URL changes as a specific migration pattern and tells site owners to prepare URL mapping, configure redirects, and monitor the move. That guidance applies whether the project is a full domain move or a smaller redesign that changes internal paths.

A small business site may only have 40 pages. It still needs the map. One service page with local rankings can be worth more than 30 low-value blog posts.

The redirect map template

Use this as your base spreadsheet. You can build it in Google Sheets, Excel, Airtable, Notion, or a project management tool. The format matters less than the discipline.

The traffic window should cover seasonality. Google Search Console performance data commonly supports up to 16 months of Search results performance history, so use that wider window if the business has seasonal demand.

For backlinks, use the tool you already pay for. Ahrefs explains that 301 redirects are commonly used to consolidate URLs and pass people from old URLs to new ones. You do not need a perfect link database, but you do need to know which URLs have outside links before you delete or merge them.

How to build the map without missing money pages

Start by collecting every URL you can find. Do not rely on the sitemap alone.

A sitemap only shows what the current site chooses to expose. It may miss old landing pages, test pages, orphan pages, retired blog posts with backlinks, indexed PDFs, or URLs still receiving referral traffic.

Use these sources together:

1. Crawl the current site with a crawler such as Screaming Frog, Sitebulb, or your SEO platform.
2. Export indexed and clicked URLs from Google Search Console.
3. Export landing page traffic from analytics.
4. Export backlink targets from an SEO link tool.
5. Pull current XML sitemaps, CMS page lists, blog archives, ecommerce collections, PPC landing pages, and old campaign URLs.
6. Search the site manually for PDFs, thank-you pages, hidden forms, and location pages.

That is the first bullet list. It earns its keep.

Screaming Frog’s bulk redirect checker can show status codes, destination URLs, chains, and loops, which makes it useful before and after launch. Search Console matters because it shows what Google already knows about the site. Analytics matters because a page with modest search traffic may still drive paid, email, referral, or direct leads.

Once the URL inventory is built, remove duplicates carefully. Normalize trailing slashes, uppercase and lowercase variants, HTTP and HTTPS versions, www and non-www versions, query parameters, and pagination. Keep the raw export in a separate tab so nobody loses evidence.

How to choose the right destination

A good redirect sends a person to the closest useful replacement.

If /services/cnc-machining/ becomes /cnc-machining/, that is an exact match. Use a permanent redirect.

If /services/emergency-repair/ was folded into /industrial-equipment-repair/, that is a close match. Use a permanent redirect if the new page genuinely covers the old intent.

If /blog/2018-trade-show-booth-recap/ has no traffic, no links, and no replacement value, let it return a real 404 or 410 instead of dumping it to the homepage. Google says permanent redirects should point users and Google Search to the correct page. A homepage redirect is not a magic cleanup button.

This is where many redesigns go sideways. Teams redirect every deleted page to the homepage because it feels safer. It is usually not safer for users. If someone clicks a link about a discontinued product and lands on a generic homepage with no explanation, they did not get what they came for.

For pages with backlinks, pick the best equivalent even if it means creating a new page. For pages with conversions, preserve the offer, form path, and internal links. For pages with search traffic, compare the old query intent before deciding where it should land.

What to do with query parameters, PDFs, and campaign URLs

Redirect maps get messy because real websites are messy.

Query parameters need a decision. Paid campaigns, UTM links, filters, and tracking parameters may point to pages that still matter. Google Analytics documents UTM parameters as campaign tracking values, so do not strip them without checking whether reporting depends on them. In most cases, the base URL should redirect and preserve safe tracking parameters when possible.

PDFs need a decision too. If a spec sheet, menu, warranty document, price sheet, or brochure has links from outside sites, redirect the old PDF URL to the new PDF or an HTML page that contains the same useful information. If you replace a PDF with a page, note that in the map so sales and customer service know where the asset went.

PPC landing pages need special handling. A Google Ads destination URL, Meta ad link, email automation URL, or QR code on printed material can keep sending visitors long after the redesign. Google Ads documentation says Final URLs define the landing page people reach after clicking an ad, so paid media links should be checked before launch, not after budget has been wasted.

Redirect rules versus one-by-one redirects

Not every redirect needs a manual row in server config.

If the old site used a clean pattern, a rule can save time. For example, /blog/old-post/ might become /resources/old-post/, or /product-category/widgets/ might become /products/widgets/.

Pattern redirects are efficient, but they are also easy to break. A rule that works for 80 percent of URLs can quietly send the other 20 percent to bad destinations. Keep the map as the source of truth, then decide whether implementation should use individual redirects, pattern rules, CMS redirect plugins, CDN rules, hosting config, or application routing.

Cloudflare, Apache, Nginx, Netlify, Vercel, WordPress, Shopify, and Webflow all handle redirects differently. Cloudflare’s redirect rules documentation, for example, distinguishes single redirects from broader redirect rule patterns. Your map should not assume the platform. It should define the business decision first.

QA the redirect map before launch

The redirect map is not done when the spreadsheet is filled out. It is done when the redirects work.

Before launch, test a staging version if your stack allows it. If staging cannot test production hostnames, at least review the intended rules with the developer, SEO lead, and business owner.

After launch, crawl the old URL list immediately. The pass criteria should be simple:

1. Critical and high-priority old URLs return the planned 301 or 308.
2. Each redirect lands on the approved destination.
3. No critical URL creates a redirect chain longer than necessary.
4. No redirect loops exist.
5. No important old URL lands on an unrelated page.
6. No important old URL returns 404, 500, blocked, or timeout unless that outcome was approved.

That is the second bullet list. Use it as the launch-day checklist.

Screaming Frog’s redirect audit guide explains that a redirect chain report can show the number of redirects, final address, and whether a redirect loops. That is exactly what you need on launch day.

Do not wait a week to check. Bad redirects found within the first hour are annoying. Bad redirects found after Google, customers, ads, and partners have been hitting them for days are expensive.

Post-launch monitoring for the first 30 days

The first month after launch is where the map proves itself.

Check Google Search Console daily for the first few days, then several times per week. Google’s site move documentation recommends monitoring traffic in Search Console and watching for crawl errors after a move. That work should be assigned before launch.

Watch these signals:

1. Search Console pages that return Not found, Soft 404, Redirect error, Server error, or Alternate page with proper canonical tag.
2. Organic landing pages that lost traffic compared with the same weekday or the same season.
3. High-value queries where the old URL disappeared but the new URL has not taken over.
4. Form submissions, phone calls, ecommerce revenue, booked appointments, and CRM source attribution.
5. External referral links hitting old URLs.
6. Paid campaign landing pages and email links that still use old paths.

That is the third and final bullet list.

Do not judge the migration by traffic alone on day one. Crawling, canonicalization, and ranking signals can take time to settle. But do not ignore obvious problems either. If the old top service page returns a 404, fix it immediately.

Common redirect map mistakes

The first mistake is starting too late. If the map begins the night before launch, it becomes guesswork. Build it during information architecture, when page decisions are still flexible.

The second mistake is mapping pages by title only. Titles change. URLs, traffic, backlinks, and conversions tell the fuller story.

The third mistake is redirecting everything to the homepage. Google documents permanent redirects as a way to send users and Google to the correct new location, not a way to hide every old URL under the homepage.

The fourth mistake is ignoring non-HTML assets. PDFs, images, downloadable files, old proposal links, warranty sheets, job postings, and event pages can all earn links or drive customer action.

The fifth mistake is removing redirects too soon. Google says to keep site-move redirects for as long as possible, generally at least one year. In practice, keep important redirects longer if old links, printed material, partner pages, or customer bookmarks still use them.

The sixth mistake is trusting a CMS plugin without an export. Redirects are business records. If a plugin fails, a theme changes, or a site moves hosts, the company should still own the map.

A simple priority model

Not every URL deserves the same attention.

Give critical priority to URLs with leads, sales, bookings, or strong local search visibility. Give high priority to URLs with backlinks, meaningful organic clicks, strong referral traffic, paid campaign usage, or important internal links. Give medium priority to useful pages with modest traffic or clear replacement pages. Give low priority to stale pages with no traffic, no links, no conversions, and no replacement intent.

This is not about protecting every page forever. It is about protecting the pages that carry business value.

A machine shop does not need to preserve a six-year-old holiday hours post unless people still land on it. It absolutely needs to preserve the old emergency repair service URL if that page brought phone calls during breakdowns.

Who should own the redirect map?

The best owner is the person responsible for launch quality, not the person who happens to know spreadsheets.

On a small project, that might be the developer. On a larger project, it may be the SEO lead or project manager. The business owner should approve the high-value decisions because they know which services, locations, products, and offers matter most.

A clean handoff includes the final redirect map, implementation location, export of active rules, crawl proof, Search Console notes, and a list of unresolved items. That documentation pairs naturally with a broader website handoff checklist, especially if the business may change vendors later.

Download-free version: copy this starter process

If you do nothing else, follow this sequence.

Export old URLs from crawl, Search Console, analytics, sitemaps, backlinks, CMS, PPC, and old campaign documents. Mark each URL by page type and business value. Pick the closest new destination. Use 301 or 308 for permanent moves. Let dead pages return 404 or 410 when there is no useful replacement. Implement redirects in the platform that controls routing. Crawl the old URL list after launch. Fix failed critical URLs first. Monitor Search Console, analytics, forms, calls, and paid landing pages for 30 days. Keep the redirects for at least one year, and keep business-critical redirects longer.

That is the job.

It is not glamorous, but it saves revenue.

FAQ

Is a 301 redirect always the right choice?

No. Use a 301 or 308 when the move is permanent. Google’s redirect documentation says 301 and 308 are permanent redirect status codes. Use temporary redirects only when the old URL should remain the primary URL over time.

Should every old URL redirect somewhere?

No. Redirect URLs that have a useful replacement, search value, backlinks, conversions, or customer value. If there is no useful replacement, a real 404 or 410 can be cleaner than sending people to an unrelated page.

How long should 301 redirects stay live?

Google recommends keeping site-move redirects for as long as possible, generally at least one year. Keep the most important redirects longer if old links, partners, printed material, or customer bookmarks still use them.

Can I use a WordPress redirect plugin?

Yes, if it is reliable, backed up, and included in the handoff. The redirect map should still exist outside the plugin so the business owns the decisions if the site moves later.

What if I already launched without a redirect map?

Build a recovery map now. Export 404s and redirect errors from Search Console, crawl old sitemap URLs, check analytics landing pages, review backlink targets, and fix the highest-value failures first. Late is worse than early, but it is better than doing nothing.

If you’re planning a redesign and don’t want traffic, leads, and old links to get lost in the move, Your Web Team can help build the redirect map, test the launch, and monitor the first 30 days. Start here: /get-started/.