---
title: "Discussion on \"Redesign or Rebuild Your Website? How to Tell and What to Protect\" | Hashnode"
description: "Discussion on \"Redesign or Rebuild Your Website? How to Tell and What to Protect\". In most cases, I'd start by fixing what is broken, or by redesigning how the site looks, before I'd rebuild it from scratch. A rebuild makes sense when the platform underneath is the problem. Whicheve"
url: "https://hashnode.com/posts/redesign-or-rebuild-your-website-how-to-tell-and-what-to-protect/6ad9716671b5a7056efdae98"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Redesign or Rebuild Your Website? How to Tell and What to Protect](https://jealousgx.hashnode.dev/redesign-or-rebuild-your-website-how-to-tell-and-what-to-protect?utm_source=hashnode&utm_medium=feed)

In most cases, I'd start by fixing what is broken, or by redesigning how the site looks, before I'd rebuild it from scratch. A rebuild makes sense when the platform underneath is the problem. Whicheve

Oct 22 · 5 min read · jealousgx.hashnode.dev  
Read the article

-   [#website-redesign](https://hashnode.com/tag/website-redesign)
-   [#website-rebuild](https://hashnode.com/tag/website-rebuild)
-   [#small-business](https://hashnode.com/tag/small-business)
-   [#seo](https://hashnode.com/tag/seo)
-   [#web-development](https://hashnode.com/tag/web-development)

## Written by

[JealousGx](https://hashnode.com/@jealousgx)

@jealousgx

  
[View profile](https://hashnode.com/@jealousgx)

I am a Fullstack Web Developer

Hello, I'm a highly skilled full stack web developer with a rich background in creating and maintaining dynamic websites that drive online engagement and brand awareness. My expertise extends beyond WordPress to include a versatile skill set.

## Responses 2

Markdown supported · ⌘↵ to post

[Ascendra Ventures](https://hashnode.com/@ascendra-ventures)

[Oct 22](https://hashnode.com/posts/redesign-or-rebuild-your-website-how-to-tell-and-what-to-protect/6ad9716671b5a7056efdae98/comment/6ad976bd4069ef078f1045ff)

Naming the real problem first is the step most site owners skip. "It feels old" can mean slow, hard to edit, dated, or quiet, and only some of those need a rebuild, so the symptom to fix table does more work than any feature checklist.

The protect list is the part I would send to clients before any quote. Listing the pages that bring in enquiries from Search Console, keeping their addresses, and testing every redirect before launch covers most of the traffic losses I have seen after a relaunch. Google's advice to change as little as possible at once is worth repeating too: new design first, new addresses later, so any drop can be traced to one change.

One addition: write the protected list into the scope as acceptance criteria. If the top twenty pages must keep their address or land on the right page in one redirect, that becomes part of done and gets checked before handover. Do you include a post launch Search Console check in the fixed scope?

[JealousGx](https://hashnode.com/@jealousgx)

[Oct 22](https://hashnode.com/posts/redesign-or-rebuild-your-website-how-to-tell-and-what-to-protect/6ad9716671b5a7056efdae98/comment/6ad976bd4069ef078f1045ff#reply-6ad980b27da34b18a0688963)

Thanks, that is a good addition. Writing the protected list into the scope as acceptance criteria makes it part of done, and I like that it gets checked before handover.

To answer your question: yes, I'd include a Search Console check after launch in the scope. I'd look at the same pages from the protected list and fix any that lost visits first.
