To preserve SEO rankings during a website redesign, you need a precise record of what ranks today, a redirect for every URL that changes, a staging review that catches problems before search engines do and a monitoring plan for the weeks after launch. Rankings rarely drop because of the new design itself. They drop because pages disappear, redirects are missing, content is thinned out or a stray setting tells search engines to ignore the new site.
This guide focuses on execution: the practical steps from benchmarking through launch day to recovery, as we apply them when a web design project goes live. It assumes the strategic decisions about structure and content have already been made.
Record a detailed baseline
You cannot tell whether rankings held without knowing exactly where they stood. In the weeks before launch, capture:
- A full crawl of the current site with a crawler such as Screaming Frog or Sitebulb, saving every URL, status code, title, meta description, H1, canonical tag and word count.
- Search Console exports of queries and pages for at least the last three months, and ideally twelve, for comparison with the same season later.
- Rank tracking for your priority keywords in English and Arabic, set up well before launch so there is a stable trend.
- Analytics data for organic sessions and conversions by landing page.
- Backlink data showing which URLs have links from other sites.
- Current sitemaps and robots.txt, saved for reference.
Store all of this outside the old site, because the old site will not be available to check once it is replaced.
Build the redirect map
The redirect map is the single most important document for keeping rankings. It lists every old URL and the new URL it should point to.
- Combine URLs from the crawl, the sitemap, Search Console, analytics and backlink data. Crawls alone miss orphaned pages that still receive traffic or links.
- Map each old URL to the most relevant new page, one to one where possible. Avoid sending everything to the home page, which search engines tend to treat much like a missing page.
- Use permanent 301 redirects. Avoid chains, where one redirect leads to another, by pointing old URLs directly to their final destination.
- Include images, PDFs and other files that rank or have links, and both language versions of bilingual pages.
- Decide deliberately which URLs should return 410 or 404 because the content is gone and has no replacement.
Review the staging site before launch
Crawl the new site on staging and compare it against the baseline. Check the details that most often cause ranking losses:
| Check | What to look for |
|---|---|
| Titles and descriptions | Carried over or improved for priority pages, not replaced with template defaults |
| Headings and body content | Key pages keep their main topic and depth |
| Canonical tags | Point to the correct live URLs, not staging addresses |
| Hreflang | Arabic and English pairs reference each other correctly |
| Internal links | Point to new URLs directly rather than through redirects |
| Structured data | Present and valid on the relevant templates |
| Mobile rendering and speed | Content and links match desktop; Core Web Vitals are acceptable |
Protect the staging site with a password rather than relying only on a noindex tag or robots.txt block. That way nothing needs to be remembered and removed at launch, which is where many accidental deindexing problems begin.
Launch day steps that preserve SEO rankings
- Launch at a quiet time for your business, avoiding peak seasons and major campaigns.
- Remove any noindex tags and robots.txt disallow rules left from development.
- Deploy the redirects and test a sample of old URLs immediately, including high-traffic pages and those with backlinks.
- Confirm the XML sitemap lists only live, indexable new URLs, and submit it in Search Console.
- Check that analytics, tag management and conversion tracking fire correctly on the new templates.
- Run a quick crawl of the live site to catch broken links and unexpected status codes.
- If the domain itself has changed, verify the new property in Search Console and use the Change of Address tool.
Monitor closely after launch
Some movement in rankings after a redesign is normal while search engines recrawl and reprocess the site. What matters is spotting genuine problems early.
First week
Check Search Console daily for crawl errors and the page indexing report for spikes in “not found” or “excluded” pages. Review server logs or redirect reports for old URLs still receiving traffic without a redirect, and add any that were missed.
First month
Compare rankings, impressions and organic conversions by page against the baseline. Investigate any priority page that has dropped noticeably: compare its old and new content, headings, internal links and speed. Update external links you control, such as Google Business Profile listings, social profiles and directory entries, to point to the new URLs.
First three months
Compare organic performance against the same period in the previous year to account for seasonality. Keep the redirects in place for the long term; Google advises keeping them for at least a year, and there is little reason to remove them afterward.
If rankings drop
Work through likely causes in order: indexing blocks, missing or broken redirects, canonical errors, lost content on key pages, weakened internal linking and slower performance. Most drops trace back to one of these, and correcting them usually allows rankings to recover as pages are recrawled. If a page lost substantial content during the redesign, restoring its depth is often the most effective fix.
Frequently asked questions
How long do rankings take to settle after a redesign?
For a well-executed redesign, fluctuation often settles within a few weeks, though larger sites and those with structural or domain changes can take longer. If rankings for priority pages are still well below the baseline after several weeks, investigate rather than waiting, because the cause is usually a specific, fixable issue.
Is it safe to change URLs during a redesign?
It is manageable with complete, accurate 301 redirects and updated internal links. Each changed URL still introduces some risk and a period of reprocessing, so change URLs only where there is a clear benefit, such as a cleaner structure or separate language folders, and keep existing clean URLs unchanged.
Should we redirect deleted pages to the home page?
Generally no. Redirect each old page to the most relevant new page. Sending many unrelated URLs to the home page gives users a poor experience and search engines often treat those redirects as soft errors. Where no relevant page exists, a 404 or 410 response is the more accurate signal.
Do we need to tell Google about a redesign?
There is no formal notice for a redesign on the same domain. Submit the new XML sitemap in Search Console and use URL inspection for key pages. For a domain change, verify both properties and use the Change of Address tool, keeping redirects from the old domain in place.
A new site that keeps its search value
Careful benchmarking, a complete redirect map and disciplined monitoring are what preserve SEO rankings through a redesign. The steps are methodical rather than complicated, and skipping any one of them is where most losses begin. If you are approaching a launch and want the search side handled with care, Bdazzil would be happy to talk through your plan.
