Pakistan
USA
Canada
UK
Dubai
Australia
Germany
- Record what you have before you change anything: URLs, rankings, traffic and links.
- Every old URL needs a place to go. Missing redirects are the most common cause of loss.
- Test on staging and keep it out of Google's index until launch.
- After launch, watch Search Console daily for the first weeks and fix errors fast.
Why redesigns hurt rankings
A redesign changes much more than colours. New templates mean new HTML, new page structure and often new URLs, headings and internal links. Google has to crawl and evaluate all of it again. If the old pages vanish without redirects, the links and history they earned disappear with them. If content is trimmed to look cleaner, the searches those pages matched may go with it.
None of this is inevitable. A redesign done carefully can improve rankings, because faster pages and clearer structure help. The difference is planning. This checklist follows the order we use on projects, from before the first design file to the weeks after launch.
Before you design: benchmark everything
You cannot protect what you have not recorded.
- Crawl the current siteUse a crawler such as Screaming Frog to export every URL, title, heading, status code and internal link.
- Pull performance dataFrom Search Console and GA4 export pages with clicks, impressions and conversions over a long period, to see which pages matter.
- Collect backlink dataUse Search Console links plus a tool like Ahrefs or Semrush to find pages with valuable external links.
- Record rankingsSave positions for your important searches so you can compare later.
- Save a copyBack up the site, database and media. Keep the old version reachable until the new one is proven.
Deciding whether to redesign at all
Not every site needs a rebuild. If the problem is a dated look, a refresh of colours, typography and a few key pages may be enough, with the structure and URLs untouched. If the problem is slow loading, a speed project often beats a redesign. Rebuild when the platform cannot be maintained, the structure blocks your marketing, or the site cannot work well on mobile.
Be honest about why you are redesigning. 'We are bored of it' is a weak reason when the site brings in leads. 'Our enquiries are poor and visitors cannot find our services' is a strong reason, and it tells the designer what to fix. Write the goal down and measure it afterwards.
Planning: structure, URLs and content
Decisions made here prevent most launch-day problems.
- Keep URLs where you canIf a page's address does not need to change, do not change it.
- Map old to newBuild a spreadsheet of every old URL and its new destination, one to one, with the nearest relevant page for any removed content.
- Preserve winning contentPages that earn traffic keep their text, headings and intent. Improve them, do not strip them.
- Plan the navigationMake sure top-ranking pages stay within a few clicks of the homepage and keep internal links.
- Retain metadataCarry over titles, descriptions, canonical tags, schema and image alt text, or improve them deliberately.
- Decide what to retireThin or duplicate pages can be merged or removed, but with a redirect to the best match.
Redirect rules of thumb
The map is the single most valuable file in the project.
Situation | What to do | Reason |
|---|---|---|
URL unchanged | Nothing to redirect | Keeps history intact |
URL moved | Permanent redirect to the new equivalent | Passes users and signals to the new page |
Page merged | Redirect to the merged page that now covers the topic | Avoids a dead end |
Page removed, no equivalent | Redirect to the closest parent category or return a proper 404 or 410 | Avoid sending everything to the homepage |
Domain change | Redirect each page to its counterpart and use Search Console's change of address | Keeps links and history together |
Staging and pre-launch testing
Treat this stage as the safety net.
- Block indexing on stagingUse password protection or noindex while testing, and remember to remove the block at launch. Forgetting this is a classic error.
- Compare templatesCheck headings, internal links, schema, canonical tags and robots rules page type by page type.
- Test redirectsRun the old URL list through the redirect rules and confirm each lands on the right page with a single hop.
- Check speed and mobileTest on real phones. Our guide to Core Web Vitals lists what to fix.
- Verify trackingConfirm GA4 events, conversion tags and Search Console verification work on the new build.
Content and on-page elements to carry across
Rankings sit on words, so treat text as an asset. Keep the main heading, introductory copy and answers to common questions on pages that already perform. If the design needs less text, move the detail lower down the page or into an expandable section instead of deleting it. Images need their alt text, file names and compression kept sensible, and videos should not be the only place where key information appears.
Check internal linking too. A new menu can quietly cut links to important pages, and a footer that lost its service links can flatten your hierarchy. Look at structured data on templates: product, FAQ, local business and article markup should survive the move. For a deeper review of what to fix, see our on-page SEO services.
Working with a developer and an SEO together
The best projects put the SEO requirements in the brief before design starts. Share the URL list, the redirect rules and the target pages with the designer, and ask for a staging link at the first milestone. Hold a launch call with everyone: developer, content owner, marketer and the person watching Search Console. Agree who rolls back if something breaks, and how long the rollback takes.
For agencies working across time zones, such as ours in Lahore for clients in the UK, UAE or US, set the launch window so that someone is online on both sides for the first day. We cover this planning in our custom website versus template comparison when a rebuild is on the table.
Launch day and the weeks after
Most recoveries are won in the first fortnight.
- Remove noindex and update robots.txtCheck live robots rules and meta tags immediately after launch.
- Submit the new sitemapUpload it in Search Console and spot-check that key pages are indexed.
- Test forms, calls and checkoutA broken enquiry form costs more than any ranking dip.
- Watch Search Console dailyLook at coverage, crawl errors and performance by page group.
- Fix 404s quicklyCheck the errors report and add missing redirects.
- Update external profilesChange links on Google Business Profile, social pages and directories.
- Keep the old redirects for a long timeDo not remove them after a few weeks.
Pakistan: practical notes
Many Pakistani redesigns happen with a quick turnaround and a budget that does not include SEO. The designer finishes the visual work, the client approves it, and the old site is switched off overnight. Ask your developer in writing whether redirects, metadata and tracking are included, and who tests them. If the answer is vague, hire someone who owns that part, or ask our website redesign services team to review the plan.
Consider your visitors as well. A redesign that adds heavy sliders and video backgrounds may look fine in the office and crawl on a mobile connection. Mobile data users often leave a slow site without a second thought. Local businesses should also check that their Google Business Profile still links to the right pages and that the phone number and address are consistent. Our local SEO checklist covers this.
Mistakes that cost rankings
We see these in audits of sites that dropped after a redesign.
Redirecting everything to the homepage
Google treats blanket redirects as unhelpful. Send each page to its real counterpart.
Launching with noindex still on
The site disappears from results until someone notices.
Deleting blog content to simplify
Those posts often bring the traffic that feeds your leads.
Changing too much at once
New platform, new URLs, new copy and new brand in one go makes causes impossible to trace.
No post-launch monitoring
Small errors compound for weeks. See our notes on technical SEO mistakes.
Forgetting images and PDFs
Old media files can carry traffic and links, so redirect or keep them.
Junaid's take on safe redesigns
In my experience, redesign projects fail on logistics, not on design. Nobody owned the URL list, nobody tested the redirects and nobody looked at Search Console on day two. The new site might be gorgeous and still lose half its visitors.
If you only do three things, make them these: keep URLs wherever possible, build the redirect map before development ends, and keep a person responsible for monitoring after launch. I would also avoid launching on a Friday or before a seasonal peak for your business.
If you are weighing a rebuild against a refresh, our SEO audit services can show which pages carry your traffic before you commit, and you can contact us to plan the migration.
Junaid has worked on website development for more than 18 years, across SEO, paid media, web development and custom software. He founded SEOnumber1, builds WordPress plugins, CRMs and web applications, has served 500+ clients in 48 countries, and holds Google Ads, Analytics and Google Blue and Green Belt certifications. He is a National Level Award Winner in Digital Marketing. Read his story or ask a question about this article.