Website Redesign Checklist: How to Redesign Without Losing Google Rankings

Export at least twelve months of data from Google Analytics and Google Search Console: sessions, conversions by page, top landing pages, and clicks, impressions and average position for your key queries. A full year captures seasonality, which matters for most UAE businesses, where Ramadan and the summer months often shift demand.

Record Core Web Vitals and PageSpeed Insights scores for your main templates too. Without a baseline, you cannot prove the new site performs better, or spot quickly that it performs worse.

Rank every page by organic clicks, conversions and inbound links. The pages at the top of that list are your protected assets: their URLs, core content and on-page targeting should survive the redesign unless there is a strong reason to change them. The Links report in Search Console shows which of your pages other sites point to.

Run a full crawl with a tool such as Screaming Frog and combine it with your XML sitemap, a CMS export and your analytics landing pages. Include PDFs, images and other files that receive traffic. This inventory becomes the foundation of your redirect map, so it needs to be complete.

Define what the redesign must achieve in measurable terms: more qualified enquiries, higher conversion on service pages, faster load times, a bilingual launch. Agree who signs off decisions, what is in scope and what is not. Google recommends changing one thing at a time where possible, so if a domain change or CMS migration is also planned, decide whether it should happen as a separate step from the redesign itself.

Budget belongs here too. Our guide to website development cost in Dubai explains what drives the final figure.

Sort every URL from your inventory into one of four groups:

Keep pages that perform and still reflect the business. Update pages with ranking potential but outdated copy. Consolidate thin or overlapping pages into one stronger page. Remove pages with no traffic, links or business value. Every decision here feeds directly into the redirect plan.

Build the new sitemap and navigation from your audit, not from a blank page. Map the main user journeys, such as service page to case study to enquiry, and keep important pages within a few clicks of the homepage. Validate wireframes with real users or client-facing staff before visual design starts.

Design reusable templates rather than one-off pages, and build performance in from the start: compressed images, minimal scripts, clean code. Accessibility, including colour contrast, focus states, alt text and keyboard navigation, is far cheaper to build in than to retrofit. For UAE audiences, decide early whether you need Arabic, because right-to-left layouts affect templates, navigation and forms, not just copy.

This is the phase where your choice of web development partner in Dubai matters most. If you are still comparing suppliers, read our guide on how to choose the right web development company in the UAE.

Test the staging site as if it were already live:

A URL that does not change needs no redirect and carries no migration risk. Only change URLs when the old structure is genuinely broken: dated parameters, inconsistent folders or slugs that no longer match the content. Changing URLs for cosmetic reasons adds risk without adding value.

For every page you keep, preserve or improve the title tag, meta description, H1, main body content and structured data. Point internal links directly at the new URLs, and give each new page a self-referencing canonical tag. A striking template that strips out the copy which earned a page its rankings will lose those rankings.

Protect the staging site with a password, or block it with robots.txt or noindex rules, so unfinished pages are not indexed. Then write a launch-day list of every block to remove. Google lists leftover noindex and robots.txt blocks among the common mistakes that stop a new site being indexed properly.

Take the inventory from the benchmark stage and give each old URL a single destination: the new page that best matches its intent. Start with the pages that earn traffic and links, then work through the rest. Pages you remove with no equivalent should return a 404 or 410 status rather than redirect somewhere irrelevant.

Google recommends permanent server-side redirects, such as 301 or 308, and states that they do not cause a loss in PageRank. Redirect each old URL straight to its final destination. Googlebot can follow up to 10 hops in a chain, but every extra hop adds latency for users, so collapse any chains left over from previous migrations.

Redirecting large numbers of old URLs to the homepage is a shortcut that backfires. Google warns that it confuses users and may be treated as a soft 404. The exception is consolidation: if several old pages were merged into one new page, redirecting them all to that page is correct.

Google advises keeping redirects for as long as possible, generally at least a year, so it can recrawl the site and transfer signals, including links from other websites. Remove them sooner and backlinks to old URLs start leading to errors. If you are also changing domain, submit a Change of Address in Search Console once the redirects are live.

Where you can, go live during a quieter period for your traffic, then work through this list straight away:

Expect some movement. Google notes that rankings can fluctuate while it recrawls a changed site, and that for medium-sized sites it can take a few weeks or more for the new URLs to replace the old ones. Check the Page indexing and Performance reports weekly, compare clicks and conversions against your baseline, and fix any spike in 404 errors immediately.

Finally, update the links you control: your Google Business Profile, social profiles, email signatures and ad campaigns should all point to the new URLs, and it is worth asking the sites behind your most valuable backlinks to update theirs.