A refresh improves a website’s existing foundation. A rebuild replaces or substantially reworks that foundation. The right choice depends on the problems you need to solve and the effort required to solve them well.
The site’s age or appearance alone cannot settle the question. A dated homepage may need better copy and photography. A polished site may still have an unusable mobile menu, a broken inquiry path, or an editing setup nobody can maintain.
01
Define the problem before the project.
Write down the task the website needs to support: explain a service, help a customer compare options, introduce your work, or arrange a conversation. Then identify what prevents that task today.
Use specific observations. “People ask what is included after reading the service page” points to a content problem. “We cannot add a service without breaking navigation” points to a structural problem. “We want it to feel newer” needs a clearer brief before it becomes a build.
Gather what you can verify: the current pages, customer questions, mobile observations, available search and analytics reports, and the team’s editing experience. A low inquiry count alone does not establish that the website is the cause. Offer clarity, traffic quality, seasonality, and follow-up may also need attention.
02
Look for a workable foundation.
A refresh may fit when…
- The main navigation and page structure still match the business.
- The platform is maintained and the team can make routine updates.
- The required work is concentrated in copy, images, layout, or a few customer paths.
- Mobile, accessibility, and performance problems can be corrected within the current setup.
A rebuild may fit when…
- The business model or service structure has changed substantially.
- Required functionality cannot be supported reliably by the current platform.
- Basic editing repeatedly breaks pages or requires fragile workarounds.
- Widespread structural problems make separate patches harder to maintain than a planned replacement.
These are prompts for investigation, not a scorecard that automatically recommends the more expensive option. Ask whoever is proposing the work to explain which existing parts can stay, which must change, and why.
Compare the full scope of each option: content preparation, design, development, migration, testing, training, and maintenance. A short quote that leaves those responsibilities unnamed is difficult to compare with a complete proposal. Our website cost guide shows FMP’s current planning ranges and questions to ask when comparing proposals.
03
Keep the review practical.
Walk through the site on a phone and with a keyboard. Read the service description, open the navigation, follow the main action, and check the confirmation. Note where content is missing, interaction is difficult, or the page changes unexpectedly as it loads.
Use performance reports to investigate the experience alongside those observations. Google advises evaluating page experience broadly; good Core Web Vitals results do not guarantee top rankings, and chasing a perfect score may be a poor use of time. See Google’s page experience guidance (opens in a new tab).
For a wider checklist of what the finished experience should support, read What a Conversion-Ready Website Actually Needs. Use it to describe the desired behavior before choosing the design or platform.
04
Plan what survives a rebuild.
List the useful pages, approved content, established URLs, search property access, domain ownership, contact routes, and integrations before replacing anything. Record the access the project needs and who will approve content and technical changes.
Illustrative URL and content map
- Keep: an accurate service page at its existing address. Improve the explanation and imagery without moving it just for a new design.
- Move: an old service URL to the relevant replacement when the service structure changes. Record the old URL, new URL, retained content, and redirect test.
- Retire: an outdated offer with no equivalent replacement. Do not redirect it to the homepage or an unrelated page. Decide whether a clearly labeled archive explanation remains useful or the page should be removed, and record that decision beside the old URL.
For each row, name the content reviewer and technical owner. Add the destination status, canonical URL, internal-link update, and post-launch check. These are hypothetical mapping decisions, not a client migration report.
Keep useful URLs where practical. When a page must move, map the old address to its relevant replacement and include redirects, internal links, and the sitemap in the launch plan. Avoid sending every retired page to the homepage regardless of its subject.
Google’s site-move guidance (opens in a new tab) calls for preparing and testing the destination, mapping URLs, redirecting old addresses, and monitoring both. Significant changes can cause temporary search fluctuations. A new design is not a guarantee that existing visibility will stay unchanged.
Illustrative scope decision
A service business with an editable, usable site and unclear service copy could refresh its key pages first. A business adding a substantially different customer journey to an unsupported platform may need a rebuild. These are hypothetical situations, not FMP client results.
05
Use a phased brief.
- Review and prioritize. Describe the current problems, evidence, and customer tasks. Separate essential repairs from useful improvements.
- Confirm the foundation. Decide what to retain and whether the platform can support the agreed needs. Name the migration work if a rebuild is justified.
- Prepare the content. Confirm messaging, approved images, service details, and who owns decisions before finalizing layouts. If new photography is needed, map each image to a page and customer question with the page-to-shot-list worksheet.
- Build and verify. Check mobile layouts, keyboard operation, forms, links, search metadata, redirects, and consent-aware measurement.
- Review the outcome. Confirm that important paths still work after launch. Compare available data and customer feedback without treating clicks as bookings.
A phase can be a focused refresh or part of a larger rebuild. Each should have a defined output and an owner. Confirm dates against the actual scope and the materials available.
Start with a useful diagnosis
Need priorities before a proposal?
The Website Conversion Review has a base price of $249. It includes an approximately 15-minute recorded walkthrough covering mobile, conversion, performance, and search foundations, plus a one-page five-priority action plan. Implementation is excluded.
If the need is already clear, explore Web Design or use the project estimator for non-binding planning ranges. Final scope and pricing require consultation, an approved brief, and a written proposal.
Start with the free 45-minute Google Meet consultation to confirm fit, the pages and inputs to review, and the delivery date before payment.
Primary references
Sources and further reading
Primary references used to verify the factual guidance in this article.
- Understanding page experience in Google Search resultsGoogle Search Central
- How to move a siteGoogle Search Central