You can redesign a website without losing Google rankings if the pages that already bring visitors keep their content and, wherever possible, their addresses. Where an address has to change, the old one needs a permanent redirect to the matching new page. Most ranking drops after a redesign come from changed URLs with no redirects, removed content, or a staging setting that was left switched on at launch.
Why rankings drop after a redesign
Google ranks pages, not designs. A new layout, new colours and new photos do not cause a drop on their own. The drop comes when something Google relied on is no longer there. The usual causes are:
- Changed URLs with no redirects. The old address returns an error, so the page falls out of the index and the links pointing to it stop counting.
- Removed or shortened content. A service page with a full explanation is replaced by a few lines and a large image. The page no longer answers the searches it ranked for.
- Lost titles, descriptions and headings. The new templates ship with default titles, or the headings are rewritten without the words people search for.
- Staging settings left on. The new site was hidden from search engines while it was being built, and the block is still in place after launch.
- A slower site. Heavier images, sliders and scripts make pages load more slowly on mobile.
Each of these is avoidable if it is on the checklist before the build starts, not after the launch.
What to record before the redesign starts
Before anyone opens a design tool, take a snapshot of the current site. You will use it to decide what must be kept and to compare results after launch.
- A full list of current URLs. Google suggests starting with your sitemaps, the pages that get the most traffic in your analytics or server logs, and the Links report in Search Console. Include images and downloadable files such as PDFs if they get visits.
- The pages that bring search visitors. In Search Console, open the Performance report and export the top pages and the queries they rank for. These pages are the ones to protect.
- The pages other sites link to. The Links report in Search Console shows them. If one of these URLs breaks, the value of those links is lost.
- Titles, meta descriptions and headings. Export them so they can be carried over to the new pages.
- Current tracking. Note which analytics, Search Console verification and advertising tags are installed, so none are dropped in the new build.
For a UAE business with Arabic and English pages, do this for both languages. The Arabic pages have their own URLs and their own rankings, and they are easy to overlook when the brief is written in English.
Keep the URLs you can and map the ones that change
The safest redesign keeps every existing URL exactly as it is. If the page at /services/web-design/ stays at /services/web-design/, Google has nothing new to work out.
A new platform or a new site structure often changes addresses anyway. In that case, build a URL map: a spreadsheet with one row per old URL and the new URL it should lead to. Google’s guide on site moves with URL changes describes this mapping as a core step, along with updating internal links, canonical tags and hreflang annotations to the new addresses.
Rules that keep the map useful:
- Map each old page to the new page that covers the same topic.
- If two old pages are merged into one, both can redirect to the merged page.
- Do not send many old pages to the homepage. Google says redirecting lots of old URLs to one unrelated destination can be treated as a soft 404, which means the old page is handled as if it no longer exists.
- If a page is being removed and has no replacement, let it return a 404 or 410 status. Google’s documentation on HTTP status codes says indexed URLs that return a 4xx status are removed from the index, so only do this for pages you are content to lose.
Google also advises changing one thing at a time. If you are planning a new domain as well as a new design, do them as two separate projects so that any problem can be traced to its cause.
Set up permanent redirects correctly
A redirect tells browsers and search engines that a page has moved. For a redesign, the type matters. Google’s redirects documentation explains the difference:
| Type | Status codes | How Google treats it |
|---|---|---|
| Permanent | 301, 308 | The new URL is used as the canonical address and shown in search results |
| Temporary | 302, 303, 307 | Google follows it, but the old URL usually stays in search results |
Use permanent, server-side redirects. Google recommends them over meta refresh or JavaScript redirects, which it lists as fallbacks for when a server-side redirect is not possible. Google also states that permanent redirects such as 301 do not cause a loss of PageRank.
Two more points from the same guidance:
- Avoid chains. Redirect each old URL straight to its final address. Googlebot can follow up to 10 hops, but Google advises keeping chains short, ideally no more than 3 and fewer than 5. If the site already has redirects from an earlier redesign, update those to point at the newest URLs.
- Keep redirects for a long time. Google says to keep them for generally at least one year. Longer is better, because people still follow old links and bookmarks.
On WordPress, redirects are usually managed in the SEO plugin or in the server configuration. On Shopify, they are added as URL redirects in the store admin. Either way, the map from the previous step is what gets loaded in.
Checks to run on launch day
Most of the damage from a redesign happens in the first hours after launch, and most of it is easy to catch. Go through this list as soon as the new site is live:
- Indexing is allowed. Check that the robots.txt file does not block the whole site and that pages do not carry a
noindextag left over from staging. On WordPress, confirm the “Discourage search engines from indexing this site” setting is off. - Redirects work. Test a sample of old URLs from the map, including the top pages from Search Console. Each should land on the right new page in one step.
- Canonical tags point to the new URLs. Each page should reference its own live address, not the staging domain.
- Titles and descriptions are in place. Compare against the export taken before the redesign.
- Internal links use the new URLs. Menus, footers and links inside page content should not rely on redirects.
- The sitemap lists the new URLs. Submit it in Search Console.
- Tracking works. Confirm analytics is recording visits and that forms and enquiry buttons still send leads.
- Hreflang is correct. For bilingual sites, check that Arabic and English pages still reference each other at the new addresses.
If the redesign also involves a change of server, the DNS and hosting side has its own steps. Those are covered in our guide on how to move a website to new hosting without downtime.
What to watch in the weeks after launch
Some movement in rankings after URL changes is normal. Google says that for a medium-sized site it can take a few weeks or more for most pages to be processed at their new addresses, and longer for larger sites. Googlebot has to visit each old and new URL at least once.
During this period, check Search Console weekly:
- Page indexing report. The number of indexed new URLs should rise. Look for unexpected “Not found (404)” entries and add redirects for any old URLs that were missed.
- Performance report. Compare clicks and impressions for the protected pages against the snapshot taken before the redesign.
- Sitemaps report. Confirm the new sitemap is being read without errors.
Also update links you control: social media profiles, Google Business Profile, directory listings, email signatures and the landing pages used in ad campaigns. Google recommends this so visitors and crawlers reach the new URLs directly.
If a page that used to rank well has dropped and stayed down, compare the old and new versions. The cause is usually content that was removed, a title that changed, or a redirect that points to the wrong place. Our SEO service includes this kind of post-launch review.
Frequently asked questions
Will a redesign always cause a temporary drop in traffic?
Not always. If the URLs, content and titles stay the same and only the design changes, there is little for Google to reprocess. When URLs change, Google says some fluctuation is normal while it recrawls the site.
How long should redirects stay in place?
Google’s guidance is generally at least one year. We advise leaving them in place for as long as the site exists, because old links on other websites do not get updated.
Can all old pages redirect to the homepage?
No. Google may treat redirects from many old URLs to one unrelated page as soft 404 errors. Each old page should redirect to the new page that covers the same subject.
Does changing the design affect rankings if the URLs stay the same?
It can, if the new design removes text, changes headings or slows the pages down. Keep the content that ranks, and test the new pages for speed on mobile before launch.
Should the domain change at the same time as the redesign?
Google advises against combining a domain change with other large changes such as a new platform or layout. Doing them separately makes problems easier to find and fix.
If you are planning a redesign and want the URLs, redirects and launch checks handled as part of the build, see our web development service or send a short brief through our contact page and we will reply with a fixed quote.