Updated 19 October 2026.
DigiStreet field guide
Website Redesign Without Losing SEO: Redirect Map Checklist
A redesign can change templates without changing URLs, or it can replace hundreds of addresses at once. The redirect map is the control sheet that keeps each valuable old URL connected to the most relevant new destination.
Start the map before design sign-off. Export every indexable URL, then add traffic, links, conversions, status, proposed destination and the reason for the change. A beautiful wireframe cannot tell you which old product guide still earns qualified visits or which campaign URL has links from partners.
Google’s site-move guidance says to prepare a URL mapping, use server-side permanent redirects where possible, update internal links and point canonical annotations to the new URLs. It also advises avoiding redirect chains and keeping redirects for at least a year. Those instructions belong in the release plan, not in a post-launch repair ticket.
A redirect map is not a request to send every retired page to the home page. Each old URL needs an equivalent destination, a justified consolidation, or a real 404 or 410 when no replacement exists. The sheet below makes that decision visible before the old route disappears.
Use this as a working file: keep the URL, date, owner and source beside every decision.
The redirect-map columns
| Old URL | Decision | New URL or status | Launch check |
|---|---|---|---|
| /old-service/ | Equivalent page | /services/new-service/ | 301 direct to a 200 page |
| /old-guide/ | Merged into updated guide | /guides/topic/ | Content and anchors retained |
| /campaign-2023/ | No replacement | 410 | Removed from internal links |
| /old-image.webp | Media moved | /uploads/new-image.webp | Image URL resolves |
| /contact-us-old/ | Route renamed | /contact/ | Form and analytics tested |
Build the redirect map before code freezes
Inventory every route that can be discovered
Combine the XML sitemap, CMS export, analytics landing pages, Search Console pages, server logs and backlink records. Each source catches something the others miss. Include PDFs, images and campaign routes when they attract visits or links.
Mark the pages that must keep their purpose
Record the primary topic, audience, conversion and strongest links for important URLs. The new destination should answer the same need. Similar words in the slug are not enough if the redesigned page serves a different buying stage.
Choose one final destination
Map an old URL directly to the final 200-status page. A chain from old to temporary to final adds latency and creates another place for the route to break. Check whether older redirects already point into the set you are changing.
Use permanent server-side redirects for permanent moves
Google recommends server-side permanent redirects such as 301 or 308 where possible. Keep temporary 302 responses for genuinely temporary routes. The map should state the intended status so development and QA test the same behaviour.
Update canonicals on the new pages
Each new page should identify its new URL as canonical when that is the chosen indexable address. A canonical that still points to the retired URL conflicts with the redirect and can slow down the move. Check rendered HTML, not only the CMS field.
Replace old internal links
Menus, body links, breadcrumbs, related content and structured navigation should point straight to the new URL. Internal links that depend on redirects waste requests and hide forgotten templates. Search the rendered site after release.
Rebuild the XML sitemap
The new sitemap should list the canonical 200-status URLs, not redirecting or retired addresses. Submit it in Search Console and keep a dated copy of the old and new URL lists for monitoring.
Test the staging restrictions separately
A staging site may need access controls or noindex protection, but those controls must not travel to the production release. Put robots, meta robots and authentication checks into the launch sheet with named owners.
Sample by business value and template
Test every high-value URL plus examples from each product, service, article, location and media pattern. Automated status checks find broken routes; a human check confirms that the destination still answers the original need.
Monitor both sides after launch
Watch old URLs, new landing pages, crawl errors, sitemaps and conversions. Expect search visibility to fluctuate while pages are recrawled. Record material drops by page group so the response follows evidence rather than a sitewide assumption.
A release sequence the redesign team can own
Freeze the URL decisions before content migration begins. Design, content, development and SEO should review the same sheet. If a page is being merged, name the material that moves and the editor responsible. If it is retired, record why no destination is relevant. This prevents a late batch rule from sending unrelated old pages to a generic category or home page.
Add automated checks for old URL status, final destination status, redirect hops, canonical value and presence in the new sitemap. Run the same file against staging where routes can be tested safely, then again against production after release. Keep the two outputs so a repair can be traced to the launch window.
Treat analytics and forms as part of the migration. Page paths, content groups, thank-you routes and key events may change even when the visible form looks familiar. Test a real enquiry path, label the record, and confirm it arrives in both analytics and the receiving sales system.
Check links beyond the website. Update paid campaigns, social profiles, business listings, email templates and partner links that send meaningful traffic. A redirect can protect the visit, but a direct update removes delay and gives the user a clearer destination. Prioritise the sources that send real sessions.
Keep the map after launch. Google advises retaining redirects for at least one year, and visitors may use old bookmarks for longer. Add newly discovered old routes to the same file, record the redirect date and test them with the established method instead of creating an undocumented rule.
Judging, ordering and testing redirects at scale
A simple rule for merge, redirect or 410
Take each old URL and ask what a visitor arriving from Google wanted. If one new page answers that need, redirect to it. If two old pages answered the same need, merge their useful content into one new page and redirect both. If nothing on the new site answers it, return 410 and remove the internal links. For example, a services site with 60 old pages might end up with 44 direct redirects, 10 pages merged into 5, and 6 retired. The exact numbers matter less than the habit. Every row carries one of the three decisions and a reason, because rows without a reason are the ones that end up pointing at the home page.
Pattern rules that look tidy and break pages
Pattern rules save time and cause quiet damage. A rule that sends everything under /blog/ to /insights/ works only if every slug stayed the same. Where a few slugs changed, those pages land on 404 errors that nobody notices until a crawl. Test each pattern rule against the full old URL list, not three samples. Watch for matching that is too wide, such as a rule for /service that also catches /services-pricing/. Case matters too, since most servers treat /Contact/ and /contact/ as different paths, so check the capitalised versions that appear in old emails, brochures and printed material.
Collapsing the hops a redesign leaves behind
Redesigns stack on top of earlier redesigns. For example, /services-old/ was redirected to /services/ two years ago, and the new site now moves /services/ to /what-we-do/. A visitor following the oldest link takes two hops. Fix it by editing the original rule to point at /what-we-do/ directly. Do the same for the protocol and host variants. The http and https versions, with and without www, should each reach the final address in one step instead of passing through each other. Run a crawler over the old URL list and sort by number of hops. Anything above one is a row to fix.
Keeping campaign tracking intact through a redirect
Old campaign URLs often carry parameters such as utm_source. Whether the query string survives a redirect depends on how the rule is written, so test it instead of assuming. Open an old URL with a test parameter added, follow the redirect, and check that the parameter is still in the address bar of the final page. If it is dropped, paid and email traffic loses its source label and shows up as direct. Then confirm the landing page fires analytics once. Fix the rule before any new campaign links go out, because the damage to reporting cannot be repaired after the fact, and the old links keep sending traffic for years.
Choosing which rows get a human check first
In a large inventory, sort the sheet by clicks over the last twelve months, then by number of linking domains, and see how many rows it takes to reach most of the traffic on your own export. Those rows get a person's check of the destination's content, headings and form. The long tail can be covered by automated status and hop checks. For a site with 400 URLs, that might mean hand-reviewing 40 and scripting the other 360. Ask your developer for the crawl output as a spreadsheet with old URL, final URL, status code and hops, so you can sort and challenge it yourself. Ask for the same file again after launch to confirm nothing moved.
Evidence from DigiStreet work
A website route is more than a visual page. It carries links, search history, campaign references and customer bookmarks. The map keeps those relationships visible while the interface changes.
For a new DigiStreet website, published pricing starts from ₹1,00,000 plus GST. Redirect planning depends on the inventory and migration scope, so it should be written into the proposal rather than assumed after design approval.
Questions people ask before using this guide
Do all old URLs need a redirect?
No. Redirect an old URL when there is a relevant replacement; use a real 404 or 410 when the content is gone and no equivalent exists.
Should every removed page redirect to the home page?
No. Google warns against irrelevant redirects because they can confuse visitors and may be treated as soft 404s.
How long should permanent redirects stay active?
Google recommends keeping them for at least one year; keeping useful old routes longer can also help visitors using old links.
Should internal links still point to old URLs?
No. Update internal links to their final destinations so visitors and crawlers do not travel through redirects.
What does a DigiStreet website start from?
Published DigiStreet website pricing starts from ₹1,00,000 plus GST.
When should the redirect map be tested?
Test before release on staging where possible, immediately after production release, and again while crawl and traffic data settle.
Put the next decision on one page
Bring the current brief, the evidence you already have and the business action that matters. DigiStreet will tell you what should be checked first.
