Redesign without losing important pages

Sam has now reviewed ClearFlow Plumbing's services, website content, technical checks and local information. He's ready to look at the proposed redesign more closely.

The new layouts may look very different. But an important question comes before choosing what the new pages will look like:

What happens to the addresses people already use?

ClearFlow already has a water heater repair page at:

clearflow.example/water-heater-repair

Someone might have saved that address or followed a link from another website. The same risk applies to pages people reach through search results. If Sam changes an address without planning what happens to the old one, visitors could reach a missing page.

A redesign is a chance to improve the experience. It isn't a reason to make useful pages harder to find.

In Lesson 5, Sam planned the purpose of each existing page. Now he adds another column: the page's current address.

Nothing about the draft redesign requires another service page or a second URL for the same service.

Sam can improve the page layout, write clearer descriptions, update navigation and make contact links easier to use while keeping these addresses.

Before recommending a move on a real project, a designer should also look for important pages in the site's CMS, sitemap, analytics and available search information. That helps avoid overlooking pages just because they aren't prominent in the menu.

While sketching the redesign, Sam notices that a new folder structure could make the water heater page look like this:

Suggested new address: /services/water-heater-repair

It seems tidy. But ClearFlow already has a useful page at /water-heater-repair, and no business or technical need has been established for changing it.

Sam chooses the simpler approach:

• Current address: clearflow.example/water-heater-repair
• Address in Sam's plan: clearflow.example/water-heater-repair

Decision: Keep the address. Improve the page itself.

That means Sam can use the proposed heading Water heater repair in Austin, the new content draft and the improved mobile contact layout without creating an extra redirect or an additional service page.

The homepage still introduces both services. The water heater page still explains water heater repair. The drain cleaning page keeps its own purpose. The redesigned navigation can link directly to those same addresses.

The rule Sam is learning: Change a URL because there's a good reason, not because a new template or keyword idea makes another address look attractive.

Sometimes a redesign does require a different URL. Perhaps an agreed change to the website structure or a confirmed platform limitation means a page cannot keep its old address.

Sam considers a backup scenario for ClearFlow's article.

Suppose a later approved build must move the no-hot-water article from:

/blog/no-hot-water-what-to-check

To:

/guides/no-hot-water-what-to-check

The article is still helping people with the same question. Only its address would change.

Sam would make a redirect map, showing the old address and the relevant new one. The developer could then use a permanent redirect, commonly called a 301 redirect, when the move is approved and ready.

A permanent redirect takes someone who visits the old address to the replacement page. It also tells search engines that the address has moved permanently. A server-side 308 is another permanent redirect option.

Why not send everyone to the homepage?

Someone clicking a link about a water heater problem expects that information. Sending that person to the homepage, or to a different service page, doesn't meet the same need. Google also advises against redirecting unrelated pages to one generic destination.

Sam doesn't need to move the article today. He's prepared the right response if a future, justified change is agreed.

Imagine the article move eventually goes ahead.

Sam would ask the developer or website administrator to check three things:

1. The old link works. Visiting the old article address takes someone directly to the matching new article. No broken page and no unnecessary chain of redirects.
2. The redesigned website uses the new link. Navigation and any internal links should point straight to the new address, rather than relying on a redirect every time someone clicks.
3. The new page works properly. Check that the new article loads, has the intended content and isn't accidentally blocked from search. The page's canonical URL and the sitemap should also reflect the final address when applicable.

If an old page has been removed and there is no useful replacement, Sam should not invent a destination just to avoid a missing-page response. That needs a separate decision, and sometimes a proper 404 or 410 response is more suitable than an irrelevant redirect.

A redirect helps protect a move. It doesn't guarantee identical rankings or traffic. A site can still experience changes while search engines process new addresses.

There's another issue Sam already knows about.

The earlier review of /water-heater-repair found a noindex instruction. Sam recorded that in Lesson 9 and prepared a technical investigation request.

Keeping the URL doesn't remove noindex. And changing the URL wouldn't be a proper fix either.

Those are two different jobs:

• URL planning: Make sure an old address continues to work, or redirects to the appropriate new page if a move is truly needed.
• Indexing review: Confirm why an important page has a noindex instruction, obtain approval for the appropriate correction and verify the result.

Sam keeps both items visible in the handover, so the person responsible for the website doesn't mistake a redirect plan for permission to change indexing settings.

Before moving on, Sam applies the same approach to Cedarline Web Studio.

The studio already has a services page at /services and a portfolio at /work. Sam has drafted improvements to both. He doesn't need to create fresh addresses simply because the text or layout is changing.

If you redesign your own studio website, try the same question: Which existing page addresses can stay exactly as they are?

Checking this early makes it easier to plan the project, explain the decisions to a client and avoid preventable launch problems.

A useful page can keep its address even when its design and wording improve. When an address truly needs to change, map the old URL to the right replacement, use a suitable permanent redirect, update your own links and verify both ends of the move.

Sam's recommended ClearFlow plan still keeps all six existing URLs. The possible article move is a backup example, not a reason to change the website today. The water heater page's earlier indexing issue is still on the technical follow-up list.