Website Redesign Cost: What to Keep, Fix, and Rebuild

If your website needs replacing, the first pricing conversation should cover what it already does for your business. A service page that brings inquiries, a useful FAQ, and a booking link customers recognize all deserve attention before anyone draws a new homepage.

JPA Creations' Website Foundation projects start at $2,500. Your website redesign cost depends on the pages, copy, features, revision rounds, and launch work agreed in a fixed quote. An existing site adds another decision: what to carry forward, repair, or retire.

Decide Whether You Need Repairs or a Rebuild

Write down the problems you want the project to solve. “The site feels old” is a starting point. “Customers cannot find our main service on their phones” gives a designer something specific to investigate.

Focused repairs may make sense when your pages are accurate and easy to maintain, but a form, navigation menu, or contact button needs attention. If the main problem is unclear service information, start by reviewing the copy and page structure.

A rebuild deserves consideration when the current platform makes ordinary changes difficult, the site no longer represents your services, or fixing one layout problem repeatedly creates another. Ask the provider to explain why replacement is appropriate for your particular site.

Have that discussion before choosing a design. It helps keep the project focused on the work your business needs.

Make a List of What Must Survive

Before removing pages, record the current site addresses and what each page is for. Use search and analytics data where available, then add what you know from customer conversations.

Look for:

• Service pages people use before contacting you.
• Articles or resources receiving search visits or links from other websites.
• Forms, phone links, booking tools, and downloads customers rely on.
• Useful photographs, project examples, and answers to recurring questions.

Give each item a decision: keep it, revise it, combine it with another page, or remove it. A page with little recorded traffic may still be useful to someone reviewing a proposal or checking your qualifications.

For example, a specialist service page might need clearer copy while keeping its existing address. A redesign gives you a chance to improve that page without automatically starting it over.

What Changes a Website Redesign Quote?

Page count matters, but it does not describe all the work. These details help explain why two proposals can look very different.

Content That Needs Reworking

Moving approved text is different from researching your services, interviewing you, rewriting pages, and organizing project examples. Identify who supplies the business facts, who writes, and who approves. Include image selection and permission to use existing photographs in that conversation.

Features That Need Reconnecting

A contact form, booking calendar, customer portal, or payment system needs its own requirements. Specify what customers should be able to complete and where the information should go. Moving a tool from one platform to another may also mean changing a subscription or rebuilding an integration.

The Amount of Migration Work

An established site can contain old articles, downloads, images, and page addresses beyond its main menu. Reviewing and moving those assets takes time. Ask whether the quote includes that inventory, content transfer, redirects, and checks after launch.

Decisions and Revision Rounds

Agree on which pages and design stages you will review, how feedback is collected, and how many revision rounds are included. If you add a service section or change the project direction after approval, confirm the additional price and schedule before that work starts.

Put URL Changes in the Written Scope

A URL is a page's web address. When an address changes, someone following an old search result or saved link still needs a useful destination.

Ask for a list matching changed old addresses to their new pages. Google's site-move guidance recommends this mapping and permanent redirects for URL changes. It also advises updating internal links and checking the redirects. Sending every retired page to an unrelated homepage is not an appropriate replacement for that work.

If the addresses are staying the same, confirm that explicitly. You do not need to rename useful pages just because the layout changes.

Google also notes that rankings can fluctuate while it processes significant changes. A migration plan helps manage avoidable problems; it cannot promise unchanged rankings. Name who will review search visibility and unexpected broken links after launch, and for how long.

Agree on the Launch Checks Before the Build

Ask what you will be able to review before approving launch. A finished design should also work for the customer trying to use it.

Your checklist can include:

• Content: the agreed pages are present, with correct services, contact details, and approved claims.
• Mobile use: navigation, text, buttons, and forms are usable on a phone.
• Inquiries: test messages reach the intended destination, and the customer sees a clear confirmation.
• Existing links: the agreed old addresses reach their intended pages.
• Measurement: the agreed analytics and inquiry tracking are installed and checked.
• Handover: you know how to request changes and which accounts you control.

Ask the provider to record what was checked and any remaining issues. Compare completed website projects with these practical questions in mind. A screenshot can show design choices; opening the site lets you try the navigation and contact path yourself.

Prepare Access and Separate the Ongoing Costs

List the accounts involved: domain registration, hosting, the current website platform, analytics, search tools, and any booking or form services. Confirm who can grant access and whether your current agreement affects moving the site.

Also separate the project fee from hosting, domain renewals, paid tools, and ongoing care. Those expenses are outside JPA's base Website Foundation fee. Ask which subscriptions you will still need after the move and who handles future updates.

A typical JPA small business website takes 3–6 weeks after kickoff. Your proposal sets the schedule; scope, missing access, content, and approvals can change it.

Get a Quote for Your Existing Site

Bring your current URL, the problems you want solved, and the pages or features you want to keep. Our questions to ask a web designer can help you prepare for the conversation.

Review Website Foundation and the redesign service, then share your website project. We will arrange a call to clarify the work before preparing your fixed quote.