First find out what the website really needs to do
Identify pages that bring relevant traffic, priority services, repeated pre-sale questions, places where visitors stop and how the site connects to sales or CRM.
Content: what to keep, rewrite or remove
Do not migrate everything automatically. Keep useful pages, rewrite unclear service content and remove outdated material that no longer supports the offer.
SEO: do not lose addresses that already work
Review titles, descriptions, canonical URLs, sitemap, robots, internal links, redirects, pages with organic traffic and technical issues that could move into the new version.
Conversion: inspect the path to enquiry
Check CTAs, forms, mobile usability, wording around price and process, and measurement of key actions after launch.
Technology that must not be forgotten
Hosting, performance, security, forms, integrations, redirects, content editing and backups should be part of the redesign decision, not late implementation details.
The output should be a decision, not just a bug list
A good audit says what to change, what to protect, what to postpone and what business priority the redesign should serve.
When to audit internally and when to invite help
Internal teams know the business context. Outside help is useful when SEO, conversion, technical debt or strategic trade-offs need an independent view.
Summary: redesign starts with understanding the current site
The new website will be stronger if it protects what works and solves the real blockers, not just the visible design problems.
Related service: Websites and web applications