A website may need a fresh design while still having pages, links, or content that your business shouldn’t lose sight of. Some people might find a guide through Google; others might bookmark an address or use a form your team already knows well.
Redesigning carefully means deciding what should change and what deserves continuity. There is no way to guarantee that visibility will remain untouched, but you can prepare the transition to avoid unnecessary changes and catch issues early.
Table of Contents
Start with what the website does today
Before discussing the new structure, identify the services the website presents, the pages your team relies on, and the journeys through which inquiries arrive. Include forms, downloadable documents, languages, and connected tools: a page might seem secondary from a design perspective yet be vital for sales and customer service.
If you have access to Search Console and analytics, check which pages appear in search, receive visits, or take part in relevant journeys. Data helps prioritize, but it requires context: a page with traffic alone does not prove it generated a sale.
When there isn’t enough data, an inventory is still useful. Ask your team which links they share frequently, which questions the current pages answer, and which content needs updating. This allows you to separate what is known from what will need to be checked during the project.
Decide what to keep, improve, or retire
A redesign does not require replacing all content. A service description may remain useful even if its presentation needs to change; a guide may deserve a revision rather than a new URL; a page that no longer reflects your offerings may require a different decision.
Evaluate each piece by its function for the client and for the business. Does it help explain a service? Does it answer a question your team frequently receives? Does it have a URL referenced elsewhere? This evaluation helps determine what to keep, what to rewrite, and what should be removed from the new structure.
If there are multiple pages on the same topic, check which question each one answers before merging or deleting them. Sharing a keyword does not necessarily mean they serve the same purpose.
Treat URLs as part of the transition
A web address is an access point: it may appear in search results, emails, documents, or links from other sites. If it remains suitable, keeping it can save transition work. If it must change, agree on which new page corresponds to each previous address and how it will be redirected.
The destination should be relevant to the person following the link. Sending all retired URLs to the homepage can cause visitors to lose the context they were looking for. It is also advisable to update internal links so they point to the final pages and to review each language separately.
The Google documentation on URL changes explains aspects of planning and monitoring a migration. The specific scope depends on whether only a few pages are changing, or if the domain, platform, or entire structure is changing as well.
Design, content, and technology are not isolated decisions
The new website may need a clearer structure, revised copy, or a different way to present services. Those decisions affect what visitors find and how pages relate to one another.
There are also less visible dependencies. The domain, hosting, email, and measurement tools may be managed by different providers. Changing the website does not necessarily mean moving everything. Before doing so, the team should know who controls each service and which connections could be affected.
On bilingual sites, review how language versions relate to each other, which URL each uses, and whether links lead to pages and forms in the corresponding language. An accurate translation loses value if the next step leads to a user journey the visitor did not expect.
Agree on how the launch will be handled
The redesign proposal should identify who prepares the launch, what backup will be kept, and what will be done if an issue arises. Having an available backup and a tested restoration are not the same thing; it is worth understanding what safeguard exists and who can deploy it.
Before launching, the team must review the included journeys: navigation, service pages, links, and contact options across relevant devices and languages. Forms deserve special attention: displaying a success message and actually receiving an inquiry are different steps. Our guide on how form inquiries arrive explains that distinction.
After launch, agree on a monitoring period and designate who will review issues, changed URLs, and search signals. Search engines can take time to reflect changes, and visibility may fluctuate; comparing periods with proper context helps investigate what is happening without attributing every fluctuation to the new design.
What to ask for in a redesign proposal
Ask for the scope to clarify which pages and languages will be worked on, who provides and approves content, which features will be retained, and how changing URLs will be managed. Also ask about revision rounds, schedule dependencies, and the responsibility for going live.
Ongoing continuity deserves its own discussion: hosting, maintenance, licenses, and content improvements may be part of separate agreements. A clear proposal should allow you to understand what is included in the initial project and what you will need to contract or manage afterward.
If you are considering changing your website, share its URL, the pages you consider essential, and the issues you want to resolve. At Capricorn Nexus, we can review the scope of your redesign and define with you what is worth keeping and what needs a new solution.
