Redesign cost depends on what the current site leaves behind
A website redesign is not one standardized product. One business may need clearer copy and a better responsive layout on its current platform. Another may need new information architecture, a content migration, rebuilt integrations, and careful URL redirects. Those projects should not carry the same scope or price.
The existing site also creates work that a new website may not have. Someone has to inventory useful content, understand current traffic, identify working forms and integrations, decide which URLs should remain, and separate real platform limitations from fixable problems. A useful estimate starts with that evidence rather than a page count.
The main website redesign cost drivers
- Current-site condition. A stable site with coherent content is different from one with broken templates, outdated plugins, inaccessible controls, or undocumented custom code.
- Strategy and scope. Reworking one conversion path takes less effort than restructuring services, audiences, navigation, and the full content model.
- Copy and content. Editing accurate material is less involved than interviewing stakeholders, rewriting pages, producing imagery, or consolidating years of duplicated content.
- Design and responsive behavior. A focused visual refresh differs from establishing a complete design system and rebuilding page behavior across phones, tablets, and desktops.
- Migration and platform change. Moving content, accounts, media, products, or structured data adds mapping, implementation, and verification work.
- Functionality and integrations. Forms, booking, ecommerce, CRM connections, portals, quoting tools, and custom workflows must be preserved or deliberately replaced.
Migration and SEO work belong in the estimate
A redesign can damage useful search visibility when existing URLs, page intent, internal links, metadata, or backlinks are ignored. That does not mean every URL and sentence must remain unchanged. It means the migration needs an explicit plan.
The scope may include an indexed-URL inventory, redirect mapping, canonical review, metadata migration, sitemap updates, structured data where appropriate, analytics and Search Console checks, and post-launch monitoring. None of those steps guarantees rankings will remain unchanged, but omitting them creates avoidable risk.
Compare the work, not only the total
Ask each provider to separate discovery, content, design, development, migration, integrations, testing, launch, and support. Clarify whether the proposal assumes the current platform will stay, whether copy is supplied by the business, and how scope changes are handled.
A lower proposal may be appropriate for a focused improvement. It may also exclude redirects, mobile design, accessibility review, content migration, or production testing. A higher proposal is not automatically better either. The useful question is whether the work matches the problems the business needs to solve.
Build a redesign budget around decisions and risk
Start by documenting the business change behind the project, the customer actions the site must support, the content and functions that already work, and the failures that are expensive to keep. Then separate launch requirements from improvements that can follow later.
For broader market context, review the guide to small-business website cost. It covers new-site approaches and ongoing ownership, while this guide focuses on the extra decisions and migration work created by an existing website.