Redesigning a website without losing useful content or URLs

Plan a website redesign around useful content, URL mapping, platform decisions, and a tested launch path that respects existing customers.

A website can look dated and still contain valuable work: a useful service explanation, an article customers return to, or a link people have saved. Before replacing it, find out what deserves to come with you.

For a small business, a redesign should address the business’s current needs while respecting the ways people already find and use the site. The design, content, and launch plan belong in the same conversation.

Start with what the website needs to do now#

Has the offer changed? Are you selling products, taking inquiries, or explaining a service that needs more context? Is it difficult to update the site? Define the practical need before deciding which platform or visual direction to use.

In the Colorado Sauce Company project , we moved from Wix to Shopify and built around cases, offers, discounts, and customer accounts. Product pages, email flows, and recipe content supported that scope. Another business may need a simpler service website rather than an ecommerce platform.

Inventory the pages before rewriting them#

Make a list of current URLs and what each page does. Note the pages that explain core services, receive relevant inquiries, or contain useful information. If you have search or analytics data, use it as one input; customer questions and your own knowledge of the business matter too.

Record downloadable files and images people may link to. An inventory is also a chance to identify outdated claims, missing contact information, and content that no longer reflects the business.

Map changes deliberately#

For every URL you plan to change, identify the most relevant destination. Keep useful URLs when there is no reason to alter them. When content moves, plan redirects that your hosting platform can actually support.

Google’s site-move guidance recommends mapping old URLs to their new destinations and setting up redirects. Search visibility can fluctuate during a move. A redirect plan reduces avoidable confusion; it is not a guarantee that rankings will remain unchanged.

Don’t send every retired page to the homepage merely because it is convenient. Work out whether the content has a genuine replacement and review the behavior with the person implementing the site.

Turn the URL inventory into a decision sheet#

An inventory becomes useful when each old address has a disposition and someone responsible for checking it. Here is a hypothetical example; these paths are illustrative, not routes on this website.

Existing URLDecisionReason and verification
/services/repair/Keep the addressThe service still exists. Confirm updated content loads at the same URL.
/old-consulting/Move to /services/consulting/The new page genuinely replaces the old one. Check the redirect and destination.
/event-2024/Retain as a clearly dated archive if usefulPast attendees may still need the information. Remove any implication that registration is open.
/discontinued-offer/Review for removal without an unrelated substituteConfirm there is no equivalent service before deciding how the retired URL should behave.

Include internal links pointing at the old URLs, not just the destinations themselves. Someone should verify both the old entry point and the new navigation path. Store the approved mapping with the launch notes so it is available if a missing route is discovered later.

Give each launch risk a response#

Before release, name the person who can correct a broken form, restore a missing page, or reverse a failed deployment. Keep a copy of the current content and the configuration needed to recover it. Confirm the recovery process with whoever manages hosting rather than assuming that a backup automatically means a quick restoration.

Review the most important customer paths immediately after release, when they are running on the real domain. A preview can pass while a production setting differs. Record what was checked, what remains open, and who will watch for problems during the next operating period.

Make local services easy to understand#

A business that travels to customers should make its real service area clear. A business with visiting hours needs accurate location and contact information. Put that detail where it helps someone decide whether to inquire.

Write service pages around distinct needs, not a repeated city-name formula. Someone comparing installation with repair may need different explanations and examples. Our local SEO guide covers how to approach that content.

Test the whole path before launch#

Review the website on a phone and desktop. Follow links from service pages to the inquiry form. Check required fields, failure messages, and successful delivery through an authorized test. Confirm image loading, page titles, and the URLs visitors will reach from old materials.

Make a short launch checklist with an owner for each task. Include domain settings, redirects, forms, search metadata, and a way to recover if something goes wrong. Decide who is responsible for updates after handoff.

Review what happens after the change#

Watch for broken links, unexpected inquiry changes, and customer questions that the new content still doesn’t answer. A redesign is a release you can learn from, not the end of the work.

Antilo’s website design services bring planning, copy, design, and implementation together. Tell us what your current site is struggling to do and we can work out a useful next step.

If the redesign also changes your offer or page structure, work through the website planning guide before finalizing the new site.

Next step

What needs attention in your business?

We can start with the decision you are facing, the project you need to finish, or the marketing you cannot keep up with. We’ll discuss the work involved and whether we can help.