Website redesign vs. new website: which makes more sense?

Compare your options

Scroll the comparison horizontally on smaller screens.

Distinguish a new look from new foundations

A cosmetic redesign changes visual presentation: typography, spacing, imagery and layout. A structural rebuild changes how the site is organised or implemented. A project can involve both, but they have different testing and migration needs.

Start with the problem. If customers cannot find the phone number, that may need a focused interface fix. If staff cannot update services without editing brittle code, changing the colors will not address the underlying constraint.

Audit what deserves to stay

List the live URLs, important service explanations, useful photographs, enquiry destinations and links from other sites. Review any available analytics and Search Console information with authorised access. A page that looks dated may still answer a valuable question or receive qualified visits.

Confirm ownership of the domain, hosting, content and connected accounts. Record which integrations or operational systems must keep working. Preserve brand assets that remain useful; a rebuild does not require replacing a recognisable identity.

Compare costs using the same requirements

Request two scoped options where practical: targeted improvements and a replacement. Include content work, platform fees, testing, migration, staff handover and expected maintenance responsibilities in both. Compare the effort needed to reach the same business requirement.

Rebuilding may be more economical when each required improvement adds another workaround to a platform that cannot meet the brief. That is a project-specific judgement, not a rule that older sites should be discarded. Ask the provider to explain what can be retained and why replacement is necessary.

Treat URL preservation as part of the project

Keep useful URLs when possible. If addresses must change, map old pages to the most relevant replacements before launch and implement appropriate permanent server-side redirects. Do not send every retired page to an unrelated homepage. Update internal links, canonical tags and the sitemap to match the new structure.

Google’s site-move guidance explains that processing a move takes time and visibility can fluctuate. A redesign is not a traffic guarantee. Test important redirects and real HTTP status codes, check retained content and monitor crawl or indexing issues after launch. Avoid changing domains, content and platform simultaneously unless the project requires it.

Test the customer task, not just the screenshot

Try the site on a narrow screen, with a keyboard and on a slower connection. Can a visitor understand the service, navigate back, read the content and submit an enquiry? Test the form’s error and success states and confirm that messages reach the correct monitored destination.

Review media weight, unnecessary scripts and layout movement. Measure the relevant pages before and after the change using a consistent method. A cleaner visual design can still be slower if it introduces excessive media or dependencies.

Choose a narrow, reviewable next step

Prepare your current URL, the problems you want solved, the pages worth retaining and any required integrations. Agree scope, a launch checklist and a rollback route before changing production settings. Leave working operational systems in place until their replacements are approved and tested.

A focused Apping rebuild may fit the US$1,950 package for up to five pages when it meets the standard scope. Larger migrations, additional content, integrations and custom development require assessment; hosting and ongoing services remain separate. Share the requirements before assuming the package covers the whole existing site.