Website redesign without losing rankings: a redirect plan
A step-by-step plan for relaunching a website without losing search traffic: URL inventory, mapping, redirect rules, launch checks and monitoring.
A manufacturer launches a new website on a Monday. It looks far better than the old one. The product pages have cleaner URLs, the blog has moved to a new section, and old PDF brochures have been removed. Two weeks later, enquiries from search have halved. Search Console shows hundreds of 404 errors, all for URLs that used to rank and still have links from distributors’ sites.
Most traffic loss after a redesign comes from URLs that changed without a redirect. Search engines treat a new URL as a new page unless you tell them otherwise with a permanent redirect. The work is not difficult, but it has to happen before launch, and it needs a complete list of the old URLs. Done properly, a redesign with new URLs can keep most of its rankings, and some pages recover within weeks.
Step 1: build a complete inventory of old URLs
You cannot redirect what you have not listed. Collect old URLs from several sources, because each one misses something.
- A crawl of the live site with a tool such as Screaming Frog or Sitebulb. This finds pages linked from navigation and content.
- The current XML sitemap.
- Search Console’s performance report, exported for the last twelve to sixteen months. This shows URLs that receive impressions, including ones no longer linked internally.
- Analytics landing page reports for the same period.
- Backlink exports from Search Console’s links report or a third-party tool. These show external links pointing at URLs you may have forgotten.
- Server access logs, which show what bots and users actually request.
Merge these into one spreadsheet, normalise them (scheme, host, trailing slash, lowercase where your server is case-insensitive), and remove duplicates. Add columns for clicks, impressions and number of linking domains. That tells you which URLs matter most.
Do not forget non-HTML resources. PDFs, images that rank in image search, and old campaign landing pages often carry links.
Step 2: map every old URL to its best new home
For each old URL, choose one of three outcomes.
- Redirect to the closest equivalent new page. A product page goes to the same product. A blog post goes to the same post at its new address.
- Redirect to the nearest relevant parent if there is no equivalent. A discontinued product goes to its category, not the home page.
- Return 410 Gone, or 404, if the content is deliberately removed and nothing relevant replaces it.
Avoid redirecting everything to the home page. Google tends to treat mass redirects to irrelevant pages as soft 404s, so they pass little value and confuse users.
Work through the high-value URLs by hand. For large sites, use patterns for the rest. If old product URLs were /products.php?id=123 and new ones are /products/blue-widget, you need a lookup from IDs to slugs, usually exported from the database.
Keep the mapping in a version-controlled file, not just a spreadsheet. It becomes the input for your redirect rules and your tests.
Step 3: write the redirect rules
Use 301 redirects for permanent moves. Redirect in one hop, straight from old URL to final new URL. Chains of redirects slow crawling and lose some signal along the way.
Put redirects at the web server or CDN rather than in application code where possible. They are faster and keep working even if the application has an error. In nginx, a map handles thousands of exact redirects efficiently:
# /etc/nginx/conf.d/redirects.map
# old path new path
/about-us.html /about/;
/products.php?id=123 /products/blue-widget/;
/blog/2018/05/choosing-pumps /insights/choosing-pumps/;
/downloads/brochure-2017.pdf /resources/brochures/;
# in the http context, outside any server block
map $request_uri $redirect_target {
include /etc/nginx/conf.d/redirects.map;
}
server {
listen 443 ssl http2;
server_name www.example.com;
if ($redirect_target) {
return 301 $redirect_target;
}
# pattern rule for a whole section
location ~ ^/news/(.*)$ {
return 301 /insights/$1;
}
}
The map block must sit in the http context. Matching on $request_uri includes the query string, which is what you need for old dynamic URLs.
On Apache, the same job uses RewriteMap or a list of Redirect 301 lines in the virtual host. On a hosted CMS, use its redirect manager, but check its limits before importing thousands of rules.
Also redirect protocol and host variations. If the old site served both http and www-less versions, those should go straight to the final https URL in a single hop.
Step 4: carry over what made pages rank
Redirects preserve links. They do not preserve content. If a page ranked because it answered a question in detail, and the new design replaces it with a short summary, rankings will drop even with a perfect redirect.
Before launch, check these for each important page:
- Main content and headings are equivalent or better, not trimmed for design.
- Title tags and meta descriptions are carried over or deliberately improved.
- Internal links point to new URLs directly, not through redirects.
- Canonical tags reference the new URLs.
- Structured data, such as Product, Article or Organization markup, is still present.
- Pages are not blocked by robots.txt or a noindex tag left over from staging.
That last item causes more failed launches than any other. Staging sites are usually blocked from indexing, and the setting is easy to carry across.
Step 5: test before and on launch day
Test the redirect file against the staging server, using your mapping as the test suite. A small script is enough.
#!/bin/bash
# check-redirects.sh: each line of mapping.tsv is "old_path<TAB>expected_path"
BASE="https://staging.example.com"
while IFS=
{{ pageBg }}
Infigini IT Services · Dehradun, India
Software, cloud and AI systems, built to last.
Infigini designs, builds and operates custom software for universities, healthcare providers and enterprises. Our work ranges from ERP platforms and AI knowledge assistants to the cloud infrastructure they run on.
{{ marquee }}
Services
Nine disciplines, one engineering team.
The same team handles architecture, build and production, so nothing is lost passing work between departments.
Our products
We also build products of our own.
Two proprietary platforms we own and operate, plus open-source libraries published on GitHub and npm. The patterns we recommend to clients come from running them.
Engineering stack
The technologies we use, organised by layer.
About Infigini
IT systems that organisations depend on every day.
Infigini IT Services builds software that simplifies infrastructure management and supports new ideas. We work with developers and organisations to build, deploy and scale their systems, with a focus on security, scalability and ease of use.
Our work covers campus ERPs used by thousands of students, AI assistants on Azure, appointment systems for clinics and hospitals, and the cloud servers they run on. We look after these systems from the first requirement through years of production.
Mission
To give organisations scalable IT systems that simplify infrastructure management, so that businesses of any size can work more efficiently and grow faster.
Vision
To become a global provider of next-generation IT solutions that integrate advanced technology into everyday operations.
Our values
{{ v.n }}
{{ v.t }}
{{ v.d }}
Industries
The sectors we work in.
Services
Services built around your operations.
One engineering team covers architecture, build and production operations. Choose a single discipline, or bring us in for the whole system.
Specialised services
Looking for something specific?
← All services
Service {{ svc.n }}
{{ svc.title }}
{{ svc.long }}
What's included
—{{ it }}
Loading…
Sound familiar?
{{ land.problemsTitle }}
What's included
{{ land.includesTitle }}
{{ x.n }}
{{ x.t }}
{{ x.d }}
Ways to work with us
{{ land.plansTitle }}
How it works
{{ land.stepsTitle }}
{{ st.n }}
{{ st.t }}
{{ st.d }}
Why Infigini
{{ land.whyTitle }}
Technologies we use
{{ t }}
FAQ
Questions we get asked.
Industries
Industries we build for.
Most of our work is for organisations whose systems carry real operational weight: campuses with thousands of students, clinics booking patients all day, and enterprises whose HR and finance processes cannot stop. These pages cover what we build for each sector.
Projects · {{ projectCount }}
Our work, from 2020 to today.
This list covers our platforms, client systems and open-source libraries. Client names are withheld at their request.
← All projects
{{ proj.cat }} · {{ proj.year }}
{{ proj.title }}
{{ proj.summary }}
Client{{ proj.client }}
Year{{ proj.year }}
Category{{ proj.cat }}
Visit live ↗
Context
{{ proj.ctxText }}
The challenge
{{ c.n }}{{ c.t }}{{ c.d }}
What we built
{{ b.n }}{{ b.t }}{{ b.d }}
How it fits together
{{ proj.architecture }}
Why this stack
{{ t.t }}{{ t.d }}
Related services and reading
Products
Platforms we run. Libraries we publish.
TechLogHub and EasySiteControl are proprietary platforms that Infigini owns and operates. Our open-source libraries are on GitHub and npm for anyone to use, and we use them in client projects too.
Proprietary platforms
Proprietary · Live{{ p.year }}
{{ p.title }}
{{ p.summary }}
{{ p.stackLine }}
Open-source libraries · GitHub & npm
{{ l.title }}
{{ l.year }} · {{ l.stackLine }}
{{ l.body }}
How we work
Five stages, from first conversation to production.
Each stage ends with a deliverable you keep. You get software you can use every two weeks, so nothing important arrives as a surprise at the end.
{{ s.n }}
{{ s.t }}
{{ s.d }}
You receive{{ s.out }}
Journal · {{ postCount }} articles
Notes from the engineering team.
Practical write-ups on cloud and DevOps, AI systems, ERP platforms and the frontend and backend work behind them, plus guides for teams planning a software project.
← Journal
{{ post.cat }} · {{ post.updatedText }} · {{ post.read }} read
{{ post.title }}
{{ post.dek }}
{{ post.byline }}
Loading article…
{{ b.x }}
{{ b.x }}
{{ b.x }}
Glossary
Terms we use, in plain English.
Short definitions of {{ glossCount }} cloud, DevOps, AI, data, security and business software terms, each with an example and links to the guides and services where it matters.
← Glossary
Definition
{{ term.term }}
{{ term.short }}
Loading…
{{ b.x }}
{{ b.x }}
{{ b.x }}
FAQ
Common questions.
These cover scope, timelines, ownership and what happens after launch. If your question isn't here, write to us.
{{ f.a }}
Contact
Tell us what you are building.
A few sentences are enough to start. We reply within one business day.
Registered office11 Shree Ram Puram Lane No.2,
Kanwali Road, Dehradun,
Uttarakhand 248001, India
GSTIN05AAIFI1118B1Z3
What happens next
{{ s.n }}{{ s.t }}{{ s.d }}
Thank you. We have your message.
An engineer will reply within one business day.
Legal
{{ legalTitle }}
Last updated 9 November 2026
{{ x.eyebrow }}
{{ x.h }}
Talk to us