Name the problem before choosing the project
“The website looks old” is a starting observation, not a project brief. Write down what a customer cannot understand or do. Is your newest service missing? Is the quote form difficult to use on a phone? Does the site describe a business you no longer run? Each problem points toward a different amount of work.
Make a short list of your most important pages and the action each one should support. For a service business, that might be understanding an offer, checking a project example, and requesting an estimate. Try those steps yourself on a phone and a computer. Record the specific point where information is missing or the journey breaks.
Choose a focused update when the foundation still fits
A focused update makes sense when the current platform is maintainable, the main navigation is useful, and the problem affects a limited part of the site. You may need clearer writing, current project photographs, an additional service page, or a repaired inquiry form.
For example, imagine a contractor whose site accurately explains its main services but has no page for a new commercial offering. A dedicated service page, relevant examples, and a better quote path may address the gap. Rebuilding every page would require a separate reason. This is an illustrative scenario, not a reported client result.
- The business and audience are broadly unchanged.
- Most existing pages are useful and accurate.
- The platform supports the required improvement.
- The problem can be stated and checked on a small set of pages.
Consider a redesign when the structure is the problem
A redesign becomes more useful when several problems share the same cause. Perhaps unrelated services are mixed together, important information is buried in images, the mobile layout repeatedly breaks, or the platform makes routine updates unreasonably difficult. Changing individual paragraphs will not solve those structural issues.
Imagine a business that has grown from one service into several departments. If every visitor still lands on one long generic page, the project may need a new service structure, clearer navigation, and different inquiry paths. For a more complicated operation, the redesign brief should also cover where requests go after submission and which staff members need access.
- The current page structure no longer matches the business.
- The same usability problem appears throughout the site.
- Required features cannot be supported reliably on the current setup.
- The visual system and content need to change together across most pages.
Keep what already helps customers find you
Before replacing pages, inventory the current URLs, useful content, contact destinations, and connected tools. Search Console and Analytics can help identify pages that people already find or use. An absence of data should be recorded as unknown, not treated as proof that a page has no value.
Keep useful URLs when practical. If a page must move, map its old address to the most relevant replacement and use an appropriate permanent redirect. Do not send every old page to the homepage. Check internal links, canonical addresses, the sitemap, and inquiry forms before and after launch. Google’s site-move documentation explains that visibility can fluctuate while changed URLs are processed.
Compare scopes using the same questions
Ask what each proposal changes, what it preserves, who supplies the content, and what makes the project ready to launch. A cheaper update can be the right choice if it solves the problem. A larger redesign can be justified when it removes a limitation that would otherwise keep recurring. Neither option guarantees traffic or sales.
- What customer problem will this work solve?
- Which pages, features, and integrations are included?
- What content or access do I need to provide?
- How will existing URLs and inquiries be protected?
- Which checks will demonstrate that the agreed work is complete?
- Who maintains the site after launch?
Bring a short brief to the first conversation
Share your current website, the services you want to prioritize, and two or three specific problems. Include your approximate budget and timing so the scope can be realistic. For larger businesses, describe repeated work after an inquiry arrives: copying details between tools, assigning requests, or chasing follow-ups.
JR Design & Development works remotely with businesses in Central New Jersey, Tampa, Florida, and elsewhere. We can start by reviewing the existing site and discussing whether a focused improvement or a wider redesign fits the work.
Further reading: Google’s guidance on website moves and URL changes.
Ready to discuss your website?
Share your current site or a short brief. We’ll identify the right scope for your business.
Discuss your project ↗All website guides →