A website redesign should solve an identifiable problem: confusing navigation, outdated positioning, difficult editing or a platform that no longer fits the business. Changing the appearance alone will not resolve weak content or a broken enquiry journey. Start by deciding what needs to improve and how you will check it.
Diagnose the current website before replacing it
Review important pages, customer questions, enquiry routes and known technical issues. Use available analytics and Search Console data to identify pages that attract relevant visits or support conversions. Keep useful content and effective journeys unless there is a reason to change them. Do not assume that every old page is poor or every new layout will perform better.
Create a content and URL inventory
Record each existing URL, its purpose and the proposed action:
- Keep useful pages and improve them where needed.
- Rewrite pages with outdated or incomplete information.
- Combine overlapping pages when one stronger page serves the same intent.
- Remove pages only after considering their users, links and replacement options.
For changed URLs, map each old address to the closest relevant destination. Sending every removed page to the homepage can create a confusing experience.
Approve content and page templates together
A redesign often stalls when layouts are approved before the team understands the content. Draft the key service and landing pages early. Test navigation labels, mobile reading order and calls to action with realistic text. Define reusable templates so future pages can follow the same structure without requiring custom design work each time.
Build and test in a controlled environment
Use staging with appropriate access controls and prevent unintended indexing. Check forms, integrations, permissions, menus and responsive layouts before launch. If the website accepts transactions or bookings, test the complete workflow. Maintain a backup and decide how to recover if a critical launch issue occurs.
Protect search visibility during the move
Preserve working URLs where practical. For necessary changes, implement appropriate permanent redirects and update internal links. Review page titles, descriptions, canonical URLs, structured data and the XML sitemap. Confirm that staging restrictions do not remain on the live site. Google provides guidance on site moves with URL changes; use it alongside a site-specific migration plan.
Monitor real outcomes after launch
Check important pages and enquiry paths immediately, then review indexing, traffic and conversion trends over a suitable period. Expect interpretation to require context such as seasonality and marketing changes. Keep a log of issues and fixes. Avoid declaring the redesign successful from appearance alone or promising that rankings cannot fluctuate.
Frequently asked questions
Can a redesign reduce existing search traffic?
Yes, especially if useful pages disappear, URLs change without suitable redirects or indexing settings are wrong. A content inventory and migration checks reduce avoidable risks but cannot guarantee unchanged rankings.
Should every URL change during a redesign?
No. Retain useful, stable URLs unless there is a clear reason to change them. A visual redesign does not automatically require a new address structure.
Is a redesign necessary for a slow website?
Not always. Hosting, images, scripts or configuration may be responsible. Diagnose the cause before choosing between targeted optimisation and a rebuild.
What should a redesign proposal include?
Look for objectives, content responsibilities, template scope, URL mapping, staging review, launch checks, ownership and post-launch support. Ask what is excluded as well as what is included.
Next steps
If speed is the main concern, start with our website performance guide. To discuss your requirements with VYLINO, email contact@vylino.com with your website URL and project brief.