Website Redesign or New Website? A 10-Question Checklist

The website redesign vs new website question usually starts with an owner who already feels something is off. Enquiries dried up, the site looks dated next to a competitor's, or a simple change takes the developer a week. Feeling that is enough to know you need to act. It isn't enough to know how much to tear down, and getting that wrong in either direction costs money.

Refresh, redesign or rebuild

These three words get used interchangeably, so here's how we use them.

The smallest job is a refresh: new colours, new photos, tidier typography, maybe rewritten copy on a few pages. The platform, page structure and URLs stay put. It's the website redesign vs refresh question at its lightest, and it's often enough when the site works and just looks tired.

A redesign changes how the site is organised and how people move through it: new page layouts, a new navigation, a different home page, sometimes merged or split pages. It may or may not keep the same code underneath.

Starting the code again is a rebuild, which is what most people mean by a new website. Usually that means a new platform or a hand-coded build replacing a theme. The content and the URLs can carry over, and they often should.

The 10 questions

Go through these honestly. The more you answer the wrong way for your current site, the further down the list from refresh to rebuild you should go.

1. Can the platform do what you need next year? If adding a booking flow, a customer login or a new product type means fighting the theme or paying for another plugin, the limit is the platform, and no redesign will remove it.
2. Does the site load fast on a phone? Check the Core Web Vitals assessment in PageSpeed Insights. A failing site built on a heavy theme rarely gets fixed with a new layout alone.
3. Is the mobile experience something you'd use yourself? Try to buy, book or send an enquiry on your own phone with one thumb. Tiny tap targets, sideways scrolling and forms that fight the keyboard are redesign problems.
4. Do visitors do what you want them to do? If traffic is steady but enquiries or sales aren't, the layout, calls to action and checkout flow need work, which is a redesign job before it's a rebuild one.
5. Does it still look like your business? A rebrand, a new logo or a shift towards larger clients can make an otherwise healthy site feel wrong. That's usually a refresh, unless the template can't carry the new look.
6. Is the content still accurate and useful? Old service pages, prices you no longer charge and blog posts from years ago can be rewritten on any platform. Content alone rarely justifies a rebuild.
7. How much does the site already earn from search? Pages that rank and bring in leads are an asset. The more of them you have, the more careful the change has to be, whichever option you pick.
8. Does it connect to the tools you run the business on? Payment gateways, your CRM, stock, invoicing, booking software, email marketing. Missing or brittle integrations often point to a rebuild.
9. Is it secure and maintained? Plugins nobody updates, an admin login shared by five people and a hosting account in a former developer's name are risks a fresh coat of paint won't touch.
10. What does keeping it actually cost? Add up plugin and theme licences, platform fees, the hours spent working around problems and the leads lost to a slow site. Sometimes the old site is the expensive option.

Protecting search rankings in a redesign

This is where redesigns go wrong most often, and the damage can take months to undo. A site that ranks has built up signals page by page, tied to specific URLs. Change the URLs or strip the content without a plan and Google treats the new pages as strangers.

Start with a URL inventory before anything is designed. Export every indexed URL from Search Console, your sitemap and a crawl of the live site, and mark which ones get traffic or links. That list is the brief for everything that follows.

Every old URL that changes needs a 301 redirect to the closest matching new page. Not the home page, unless the old page truly has no equivalent. Redirect chains (A to B to C) should be collapsed into single hops.

Keep page titles, meta descriptions and headings at least as good as they were. If a page ranks for a phrase, the new version should still use it. Improving them is fine. Losing them by accident, because a designer replaced the H1 with a slogan, is the common mistake.

Test before launch on a staging copy that search engines can't index. Click through the redirect list, check that nothing important has a noindex tag left over from staging, and make sure the new sitemap only lists live pages. Then launch, submit the sitemap in Search Console and watch the Pages and Performance reports for the next few weeks. A small dip right after launch is normal. A steady slide on specific pages usually means a redirect or a title went missing.

A short decision guide

If most of your problems sit in questions 5 and 6, refresh. The site works; it needs a new look and current content.

If they cluster around 3, 4 and 7, redesign. The structure and journeys need rethinking, and you want to keep what's ranking.

Rebuild when the trouble is in 1, 2, 8, 9 or 10. Those are platform problems, and a new layout on the same foundation brings them along. That's when we'd hand-code a new site, carry the content and URLs over, and redirect whatever has to move. On our Standard website plan, a seven-page rebuild with an admin panel is ₹15,000 and takes 10 to 14 days, and you own the code and hosting account at the end.

Not sure where you land? Send us a message through the contact form with your site address and the questions you answered the wrong way. We'll tell you which of the three we'd do.

Questions people ask

How often should a website be redesigned?

There's no fixed schedule. Let the checklist above make the call. The age of the site matters much less than what it can and can't do. A site that converts well can run for a long time with refreshes.

Will a website redesign hurt my SEO?

It can, if URLs change without 301 redirects or ranking content gets cut. With a URL inventory, redirects and kept or improved metadata, most sites hold their positions.

What's the difference between a website redesign and a refresh?

A refresh updates the look and some content while keeping structure and URLs. A redesign changes layouts, navigation and how pages are organised.

When should you redesign a website instead of building a new one?

When the platform can still do what you need and the problems are about layout, navigation or conversion. If speed, integrations or security are the problem, a new build usually costs less over time.

Can I keep my content when moving to a new website?

Yes, and you usually should. Pages, posts and images can be moved across, and old URLs can either stay the same or redirect to their new versions.