A website redesign should solve specific problems. Changing colours and replacing the theme is not automatically an improvement.
The safest approach is to identify what currently works, what does not and what must be preserved before development starts.
> A redesign is also a migration project. > > Existing URLs, rankings, analytics and conversion paths can be damaged if the new site is launched without a plan.
Before the redesign
Audit the current website
Record:
• important landing pages • organic traffic pages • pages with backlinks • contact and booking flows • conversion pages • indexed URLs • existing redirects • forms and integrations
Export useful Search Console and analytics data before launch.
Define the goal
Common redesign goals include:
• more enquiries • better mobile experience • faster pages • improved credibility • easier editing • better SEO structure • ecommerce expansion • easier maintenance
Try to prioritise two or three measurable outcomes.
Content checklist
Do not automatically delete older pages.
For each URL, decide whether to:
• keep it • improve it • merge it • redirect it • remove it
Preserve useful text that already ranks or answers important customer questions.
SEO checklist
Before launch, map old URLs to new URLs.
Check:
• title tags • meta descriptions • headings • canonical URLs • robots directives • sitemap • internal links • schema where relevant • image alt text • redirects
Any URL that changes and has value should normally have an appropriate 301 redirect.
Design checklist
A modern design should make the next step obvious.
Check:
• clear hero message • visible calls to action • readable font sizes • strong contrast • mobile navigation • trust elements • service explanations • contact details • forms that are not unnecessarily long
Performance checklist
Test the new site on mobile before launch.
Review:
• image compression • WebP/AVIF where appropriate • caching • font loading • third-party scripts • video embeds • unused plugins • server response • Core Web Vitals
Technical checklist
Confirm:
• HTTPS works • www/non-www redirects are consistent • staging is not indexable after launch • production is not accidentally set to noindex • forms deliver correctly • analytics fires • Search Console is configured • sitemap is accessible • error pages work • backups exist
Launch-day checklist
1. Take a final backup. 2. Deploy the new site. 3. Remove staging restrictions from production. 4. Test priority URLs. 5. Test forms and checkout. 6. Verify redirects. 7. Submit or verify the sitemap. 8. Check Search Console. 9. Check analytics. 10. Monitor 404 errors.
After launch
Expect search engines to recrawl the website over time. Watch for:
• sudden traffic drops • indexing issues • redirect errors • broken internal links • form failures • layout problems on real devices
A redesign is not finished the second DNS points to the new site.
Should you redesign or improve the existing site?
Sometimes a full rebuild is unnecessary.
If the current website has a solid technical foundation, you may only need:
• new content • speed work • a clearer home page • improved service pages • better calls to action • technical SEO fixes
A good provider should be willing to tell you when a rebuild is not required.
Planning a WordPress redesign?
SiteForge can review an existing website, keep useful content and rebuild the parts that genuinely need improvement.
View SiteForge WordPress website design.
Common Website Redesign Mistakes
Redesigning without checking existing rankings
A page may look outdated and still bring valuable search traffic. Before removing or renaming URLs, check Search Console and analytics so useful pages are not accidentally lost.
Changing every URL
A redesign does not require a completely new URL structure. Keeping strong, logical URLs can reduce migration risk and the number of redirects required.
Launching with placeholder content
Replacing established service pages with short temporary copy can weaken both usability and SEO. Final content should ideally be ready before launch.
Forgetting conversion tracking
If forms, calls and bookings were tracked on the old site, reproduce that tracking on the new version and test it.
Frequently Asked Questions
Will a website redesign hurt SEO?
It can if important pages are removed, URLs change without redirects, metadata is lost or the new site is accidentally blocked from indexing. A carefully planned redesign can preserve existing signals and create a better technical foundation.
Should I keep old blog posts?
Keep posts that still receive traffic, have useful backlinks or answer relevant customer questions. Improve or merge weak content rather than deleting everything simply because it is old.
Should a redesign include new hosting?
Not automatically. Change hosting when performance, reliability, management or support justify it. Avoid adding a hosting migration to the project without a reason.
How long should I monitor SEO after launch?
Monitor the website closely during the first days and weeks, then continue watching Search Console as Google recrawls changed URLs and content.