Website redesign checklist: from first audit to the weeks after launch.

Signs it's time for a redesign

A site rarely needs a redesign overnight. The same complaints usually come back for months, and if several of the points below sound familiar, a redesign is worth more than another round of patches.

• Pages load slowly on a phone, where many of your visitors arrive.
• Nobody on your team can update a page without calling the original developer.
• The site isn't available in Arabic or French.
• The design looks dated next to your competitors.
• The site brings in visits but almost no calls, quote requests or messages.

Before you start: take stock of what you have

The costliest redesign mistakes happen before a single page is designed. Access is the point most often overlooked: the domain may have been registered by a former employee or an old agency, and recovering it can block the whole project.

• Write down the goals: more quote requests, a bilingual site, a site your team can edit, or all three.
• List what works today: the pages that get traffic or generate contacts.
• Export a complete inventory of current URLs, with each page's title and description.
• Get access to Google Analytics and Google Search Console, or set them up if they don't exist.
• Find out who holds the logins for the domain, hosting and business email, and bring them under your company's control.

Keep your search rankings

Google ranks pages, not companies. When a page's address changes without a redirect, the history it has built up is not passed on, and visitors following old links land on an error.

The safest approach is to keep the URLs that already rank. When an address has to change, set a permanent 301 redirect from the old URL to the most relevant new page. A 302 tells search engines the move is temporary, so it is the wrong tool for a redesign.

• Keep existing URLs wherever possible.
• Map every old URL to its new equivalent and set 301 redirects; avoid sending everything to the home page.
• Avoid redirect chains: each old URL should point straight to its final destination.
• Keep the titles and meta descriptions that already perform, and improve the others.
• Generate a new XML sitemap that lists only the final, live URLs.
• Protect the staging site with a password, or at least a noindex tag, so it never appears in Google. A robots.txt block alone does not stop URLs from being indexed.

Content and languages

A redesign is the right moment to sort your content, and any page you remove still needs a redirect to its closest replacement. For a multilingual site, Arabic needs a true right-to-left design, not a mirrored copy of the French pages.

• Decide, page by page, what to keep, rewrite, merge or remove.
• Give each language its own URL and declare the versions to Google with hreflang tags.
• Translate buttons, forms and error messages too.

Launch day checks

Go through this list on the live site, not only on staging, and test on a real phone. One classic trap: the noindex tag that protected staging gets carried over to production, so remove it first.

• Submit every form and confirm the messages reach the right inbox.
• Check that your business email still works if DNS or hosting changed.
• Confirm that analytics records visits and form submissions.
• Test a sample of old URLs and confirm each returns a 301 to the right page.
• Make sure HTTPS works everywhere and that HTTP addresses redirect to HTTPS.
• Verify that missing pages show a helpful 404 page that returns a real 404 status.

After launch: watch and fix

Rankings can move for a while as Google recrawls the site, so judge results over several weeks, not days, while spotting real problems quickly.

At Neodott., we rebuild dated sites on a modern stack while keeping what already works, such as your content and page addresses, so this phase stays calm rather than urgent.

• Submit the new sitemap in Google Search Console and watch the page indexing report.
• Look for crawl errors and 404s, and add redirects for any old URL you missed.
• Run a broken link check across the site.
• Compare traffic and contact requests with the previous period, week after week.
• Use Search Console's change of address tool only if you moved to a new domain name.