A website redesign fails quietly. The new site looks better, loads faster, and passes every stakeholder review, then three months later organic traffic has dropped by a third and nobody can point to why. The cause is almost always the same: nobody ran a website redesign checklist against the old site before the build started, so the pages that were earning real traffic, rankings and leads got redesigned, renamed or removed without anyone checking what would break.
This checklist doubles as a website redesign audit. Run it before you redesign your website, not after the new site goes live, and hand the findings to whoever is briefing the designer or agency on the rebuild.
Export every page that earns organic traffic first
Pull a full list of URLs from Google Search Console’s Performance report, sorted by clicks over the last twelve months, before anyone touches the sitemap. Dubai businesses often discover during this step that a blog post from three years ago, or a service page nobody markets internally, is quietly bringing in more organic sessions than the homepage. That page needs a plan for the new site: a matching URL, a preserved heading structure and the same core content, not a guess that “we’ll rebuild something similar.”
Cross-check this list against your XML sitemap and against any pages a developer has flagged for removal. A page missing from both the traffic export and the new sitemap is the page most likely to disappear without anyone noticing until rankings drop.
Record current rankings before the audit gets stale
Take a snapshot of where your primary keywords rank right now, not from memory. Rankings shift week to week, and a redesign audit done against outdated rank data will miss a page that recently started ranking or wrongly protect one that stopped converting months ago. Google Search Console’s Performance report again covers this, filtered by query and by page, alongside any rank tracking tool already in use internally.
Record average position, impressions and clicks for the top 20 to 30 queries by volume. This becomes the baseline you compare against four, eight and twelve weeks after launch, so a ranking drop gets caught and diagnosed while the cause is still obvious, rather than six months later when the old site’s structure is a memory.
Map every old URL to its new equivalent before launch, not during it
A URL migration map is the single most common gap in a rebuild, and it is the fastest way to lose organic traffic overnight when it gets skipped. Every URL on the current site needs a documented destination on the new one, whether that destination is the same URL, a renamed page, or a 301 redirect to a merged or consolidated page. Google Search Central’s guidance on site moves is explicit that redirects need to point to the most relevant replacement content, not a blanket redirect to the homepage, which is the shortcut that causes the most damage during rushed migrations.
Build this map as a spreadsheet: old URL, new URL, redirect type, and a note on what content changed. Hand it to the developer as a requirement, not a nice-to-have, and test a sample of redirects on staging before the DNS switch, not after.
Audit the conversion paths that currently work
A redesign brief usually focuses on how pages look. It rarely asks how a visitor currently gets from a service page to a phone call, a form submission or a WhatsApp enquiry, and that path is exactly what a new template can break. Screenshot the current calls to action, contact forms and any live chat or booking widget on your top-converting pages before the rebuild starts, and note where each one sits on the page.
Check the current conversion rate for each of those pages in Google Analytics 4 so the new design has a number to beat rather than a vague brief to “make it convert better.” A new layout that looks sharper but buries the phone number below the fold, or replaces a working contact form with a generic one, will cost leads even while rankings hold steady.
Decide what stays, what merges and what gets cut, based on data
Every redesign project accumulates a wish list of pages to remove because they look dated or off-brand. Before cutting anything, check that page’s traffic, rankings and conversions against the data gathered in the steps above. A page that looks embarrassing internally can still be one of the top three organic entry points to the site, and removing it without a redirect to a genuine replacement is how a rebuild trades a design win for a traffic loss.
Where two or three older pages genuinely cover the same topic, plan to consolidate them into one stronger page with a 301 redirect from the others, rather than deleting the weaker ones outright. That keeps whatever ranking signal they built up, instead of starting the topic from zero on the new site.
Bring the checklist to the brief, not the retrospective
Every item above needs to happen before a designer opens Figma or a developer starts building templates, because a sitemap built without this data will repeat whatever assumptions are already wrong about which pages matter. Dominate Online runs this audit as the first stage of every rebuild through its website design and development service, so the traffic and rankings a site already has going into a redesign are the floor for the new one, not a casualty of it.
For teams handling the audit internally before bringing in a designer, the same principles covered in this breakdown of SEO web design fundamentals and in these tips for building a user-friendly website are worth applying to the new templates once the audit above is complete.