Planning a Website Redesign Without Losing the Useful Parts
Scope an agency website redesign around content, user journeys and reusable components before committing to visual production.

A redesign is an opportunity to remove friction, not a requirement to replace every useful part of a website. Before opening a blank design file, your agency should identify what visitors need, what content already works and which constraints caused the current site to become difficult to manage. This gives the redesign a purpose beyond a different visual style.
Audit the content and the journey
List the pages that support enquiries, explain services or answer recurring questions. Mark obsolete pages and content that needs rewriting. Review the navigation from a visitor’s perspective: can someone understand the offer, inspect relevant work and contact the business without guessing?
Record existing URLs before changing the information architecture. Where a page moves, the implementation scope should account for an appropriate redirect. Content migration, metadata and internal links are production tasks rather than details to discover at launch.
Establish a system before designing every page
Start with representative page types and components. A service page, case study and article may cover most of the site’s patterns. Agree typography, spacing, cards, forms and image treatment before rolling those decisions across the entire page list.
This approach makes review more focused. Stakeholders can assess the visual language and navigation early instead of discovering a recurring problem across twenty finished layouts.
Scope implementation and handover
Clarify whether the engagement includes content entry, responsive frontend work, CMS setup, integrations and browser checking. Confirm who supplies final copy and approves redirects. A design-only project and a launch-ready implementation have different responsibilities.
CEVUNO can support the interface design and frontend production portions of a redesign. The useful starting point is a page inventory, your preferred platform and the business priorities that should shape the first release.
Turn the page inventory into a decision log
A website redesign checklist should begin with the current site rather than a blank sitemap. Record each useful URL, its purpose, the owner of its content and whether the information remains accurate. Then classify it for retention, revision, consolidation or removal. This turns an abstract redesign into a set of editorial and technical decisions the agency can review.
Take a service page that receives enquiries but looks dated. Its visual treatment may need a complete change while its explanation and URL remain useful. By contrast, three overlapping service pages may need consolidation. The design brief should reflect those differences. Replacing everything with a new navigation label is not a content strategy.
Give content migration its own scope
Moving text and images into a new system takes production time. The team must account for headings, image rights, captions, metadata, contact information and links. If the CMS model changes, old content may not fit directly into the new templates. Identify who cleans the source material and who enters and checks it.
If URLs change, agree a redirect map before release. Check that important internal links point to the final destination and that the sitemap reflects the current structure. A redirect is a way to handle a changed location; it does not replace deciding which content should exist in the first place.
Approve a representative page family
For a B2B website redesign, a homepage, service template, case study and contact flow may expose most recurring patterns. Review them with realistic content before producing every page. Ask whether the system handles a long title, a sparse case study, a complex service and an image-free section without breaking its rhythm.
A useful approval is about rules as well as individual layouts: how sections begin and end, how calls to action are introduced and how supporting material fits the grid. When these rules are clear, additional pages can be produced with fewer arbitrary decisions.
Define the first release around business priorities
Not every possible improvement needs to block launch. Separate issues that prevent visitors completing the main journey from enhancements that can follow. A missing privacy link, broken enquiry form or inaccessible menu needs a different priority from an optional animation. Assign an owner and acceptance criterion to each launch requirement.
CEVUNO can support design and frontend production for a redesign while your agency retains strategic and client ownership. Supply the page inventory, editing requirements and known integrations during scoping. That gives the estimate a concrete basis and helps distinguish the launch work from a future optimisation backlog.
Explore CEVUNO’s design, development and creative services or browse the portfolio concepts to see the type of production we can discuss with your agency.
Make room for your next project.
Tell us what your agency needs to produce. We’ll review the scope, estimate the work and confirm availability together. Monthly partnerships and one-time projects are available.


