Short answer
Should I rebuild my site or just improve it?
A rebuild decision follows four tests, not the site's age: how many days it takes to add a new page type, whether measured mobile speed is under the threshold, whether the content team can publish without asking you, and whether security updates still arrive. If you do rebuild, the most critical deliverable is the table mapping old addresses to new ones with 301s.
Key takeaways
- Age is not a test; a five-year-old site that has been maintained can be in better shape than a two-year-old one that cannot be updated.
- The biggest risk in a rebuild is not design but losing accumulated search visibility: when the address structure changes without 301 mapping, traffic falls within weeks.
- The 301 table is not a technical detail but a deliverable that belongs in the contract.
- Before rebuilding, export the list of pages receiving traffic; it feeds both the redirect plan and the content priorities.
- A redesign is not always needed: if the problem is the content model, rebuilding the page types under the same design is usually cheaper and less risky.
Four tests that say a rebuild is due
- How many days does it take to add a new page type? If the answer is weeks, the problem is the content model rather than the design — and a redesign does not fix it, a rebuild does.
- Is measured mobile speed under the threshold? If field data shows LCP over 2.5 seconds or CLS over 0.1 and the cause is the theme and its plugin stack, patching starts to cost as much as rebuilding.
- Does the content team need a developer to publish a page? If so, the site has stopped being a publishing tool and become a maintenance item.
- Is the platform still receiving security updates? A site sitting on an end-of-life version carries the risk of going down at the next vulnerability, and that risk is independent of design.
Why does traffic drop after a rebuild?
The cause is almost always the same: the address structure changed and the old addresses were not redirected. When /services/corporate-website — an address a search engine has known for years — starts returning 404, the link equity and ranking history accumulated there go with it. The new page starts from zero even when it carries the same content.
List the old addresses
Export every address that received traffic or impressions in the last twelve months, from analytics and Search Console.
Build the mapping table
Put the new address against each old one. Where there is no equivalent, pick the closest content; do not bulk-redirect to a category page.
Implement as 301 and test
Redirects must be permanent (301) and must not chain. After launch, request every address on the list and verify the returned code.
Frequently asked
Could I just keep the address structure?
- You can, and where it is possible that is the safest route. Keeping the address structure removes the redirect risk entirely. Changing it makes sense only when the existing structure is genuinely a problem — unreadable parameter URLs, no language segmentation, addresses written from IDs instead of names — and in that case the 301 table becomes mandatory.
How long does a rebuild take?
- Duration is set not by page count but by how the content moves. If existing content is carried across as-is, it is shorter than building new; if the content is rewritten, it is longer, because copy becomes the bottleneck. At Galata Media a rebuild with no integrations runs six to ten weeks when the content is ready.
Sources
- 01Web Vitals — LCP, INP ve CLS eşikleri — web.dev, Google, 2026
- 02Understanding page experience in Google Search results — Google Search Central, 2026
- 03Robots meta tags, data-nosnippet and X-Robots-Tag specifications — Google Search Central, 2026
Queries this page answers
- website redesign
- when to redesign a website
- redesign traffic drop