The new site looks better than the old one in every way. A few weeks after launch the phone is quieter, and nobody connects the two events. This happens often, and it is almost never the design's fault. Google ranked the old pages at their old addresses. If those addresses stop working, the rankings have nothing to hold on to.
Why rankings drop after a redesign
| Cause | What happens | How to prevent it |
|---|---|---|
| Addresses changed with no redirects | Old links and search results open an error page | A redirect from every old address to its closest new page |
| Content removed or cut short | The page no longer answers the search it ranked for | Carry the text across first, then improve it |
| Indexing left blocked | The test site's noindex setting or robots rule goes live | Check both on launch day |
| Titles and headings rewritten | Google sees a different page from the one it ranked | Keep titles that work; change them later, one at a time |
| Pages merged without thought | Several ranking pages become one that ranks for none | Merge only pages that answer the same search |
| Slower pages | Heavy images and scripts replace a light old page | Test speed on a phone before launch |
Before you start: record what you have
A redesign should begin with a list, not with a mood board. Export every address on the current site from the sitemap, from Google Search Console and from your analytics. Mark the pages that bring search visits and enquiries today. Those are the pages that must not lose their address or their text.
A site such as Fluxiss, a website for an engineering consultancy with technical articles on its specialist services, shows why the list matters: every article is a separate address, and each one needs its own row.
A redirect map is a two-column sheet: the old address on the left, the new address on the right. Every old address gets a row. A page with no close match points to the nearest parent page, not to the home page by default.
Website redesign SEO, step by step
List every current address
Combine the sitemap, Search Console and analytics exports into one sheet.
Mark the pages that earn
Note which ones bring search visits and enquiries, and what they rank for.
Decide the new address for each
Keep the same address wherever you can. Where you cannot, write the new one beside the old.
Carry the content across
Move the text, headings, titles and image descriptions of every earning page before rewriting anything.
Build the redirects on the test site
Set up permanent redirects, the 301 kind, and try a sample of old addresses by hand.
Check the technical basics
One canonical address per page, a fresh sitemap, working forms, analytics installed and fast pages on mobile.
Launch and open the site to Google
Remove the test site's password and noindex setting, publish, and submit the new sitemap in Search Console.
Watch and repair
Check Search Console for not-found pages and fix each one with a redirect.
Launch day
- Open a handful of old addresses from the sheet and confirm each lands on the right new page in one hop.
- View the source of the home page and one inner page: there should be no noindex tag.
- Open the robots file and confirm it does not block the whole site.
- Submit the new sitemap in Search Console and inspect the home page there.
- Send a test enquiry through every form and the WhatsApp button.
- Keep the old site's files and database, in case something has to be looked up.
The full list of launch checks, beyond search, is in our website launch checklist.
The weeks after
Some movement is normal while Google reads the new pages. What matters is the direction. Look at Search Console every few days at first: the pages report shows addresses that return errors, and the performance report shows whether the pages that used to bring visits still do. A not-found address that once had visitors needs a redirect the same day. Leave the redirects in place for good; removing them later undoes the work.
Hold back on other big changes for a while. If you rewrite titles, change the menu and move hosting in the same month, you will not know which change caused a drop. If pages feel slower than before, deal with that first; website speed and sales explains what to check.
When the domain changes too
A new domain adds one step. Search Console has a change of address tool that tells Google the site has moved. Use it alongside the redirects, and keep the old domain registered and redirecting. Letting it lapse hands your old links to whoever buys it next.
Redirects, titles and sitemaps are part of the technical work in our SEO services, which begin with an audit when we did not build the site, and every new site from our web development team is set up for Google from the first day. Nobody can promise that rankings will not move at all, and we do not. A local business should pair the relaunch with the steps in local SEO in Karachi. If a redesign is on your calendar, send us the current site before the design starts.
Questions people ask
Will a website redesign hurt my SEO?
It can, if addresses change without redirects, ranking content is removed or the new site is blocked from indexing. With a redirect map and a launch check, most of the risk is avoidable. Some short-term movement is still normal.
What is a 301 redirect?
It is a permanent instruction that sends visitors and search engines from an old address to a new one. It tells Google the page has moved for good, so the standing of the old page can pass to the new address.
How long should I keep redirects after a redesign?
Keep them permanently. Other websites, old emails and saved bookmarks go on pointing to the old addresses, and a redirect costs nothing to leave in place.
Should I rewrite my content during a redesign?
Carry the existing text across first, especially on pages that already rank. Improve it once the new site is stable, a few pages at a time, so you can see the effect of each change.
Can you guarantee my rankings will stay the same?
No one can honestly promise that. What can be promised is the work: a complete redirect map, content carried across, and checks before and after launch.
