All website guides

Website refresh or rebuild: how to choose the right scope

Start with what customers need to do and what your existing site can still support. The right scope comes before a new look.

Illustrative photograph: a business owner and designer reviewing a website together

Generated illustrative photograph—not a client project.

The short answer.

A refresh can make sense when the platform is supported, the main functions work and the problems are concentrated in content, navigation or design. A rebuild is more likely when the underlying setup prevents important improvements or creates recurring maintenance problems. Review the evidence before choosing either route.

1. Separate the business problem from the design preference

Write down three things the website needs to help a customer do. For a Connecticut service business, those might be checking whether a service fits the job, confirming the actual service area and sending a useful inquiry. Then try those tasks on a phone without relying on what you already know about your business.

Record the point where each task becomes unclear. A hidden contact link, a service that is no longer offered and an image that takes too long to load are different problems. A new color scheme alone will not solve them. This short task review gives the project a useful brief instead of a collection of visual preferences.

2. Look for the parts worth keeping

A familiar domain, useful service pages, accurate project information and a working contact form can all have value. Review existing URLs, Search Console information if available, analytics and real customer questions. Keep a record of pages that receive relevant visits or support a useful conversation; do not assume everything old should disappear.

For example, a fictional Bristol carpentry business might have clear information about fitted storage but an outdated homepage and a difficult mobile menu. A focused refresh could improve those entry points while retaining the useful service information. That is an illustrative decision, not a claim about a client result.

3. Check whether the current platform can support the plan

Ask whoever maintains the site about its theme, plugins, hosting, backups and available access. Can normal updates be applied? Can the content be edited without workarounds? Are the forms and any payment or booking connections dependable? Make a current backup before investigating changes that could affect the site.

A supported WordPress setup with a manageable page structure may support a refresh. A brittle collection of unsupported extensions, inaccessible accounts or a platform that cannot deliver an essential function may justify a rebuild or migration. One broken component does not automatically require replacing everything; identify the source and the realistic options first.

4. Compare two written scopes, not two vague prices

Ask for a focused option and a broader option built around the same priorities. Each should explain which pages change, who prepares the copy and images, which functions are included and what testing is planned. Separate the website project from hosting, licenses, maintenance and any ongoing search or marketing work.

Compare the cost of leaving important problems unresolved as well as the cost of the work. A smaller project is useful when it addresses the actual obstacle. A rebuild earns its place when it makes required improvements practical and maintainable. Neither label tells you what is included; the written deliverables do.

5. Protect the parts customers and search engines already use

Keep existing URLs when they still make sense. If addresses must change, map each important old page to the most relevant new destination and plan permanent redirects. Review page titles, descriptions, internal links, image descriptions and genuine business details as part of the content work. A relaunch is not a reason to delete useful local information.

Check who controls the domain, hosting and business email before making changes. A hosting or nameserver change can affect email if records are not carried over correctly. Keep a rollback plan, avoid unrelated account changes during launch and agree who will check the live site afterward. Search visibility can fluctuate, so preservation work should be specific rather than promised as a guarantee.

6. Define what “ready to launch” means

Use a short acceptance list: the agreed pages are accurate, the mobile layout is usable, key links work, the forms reach the intended recipient and essential accounts remain accessible. Test actual customer tasks, including error messages and the confirmation shown after an inquiry. Review accessibility and performance concerns appropriate to the project scope.

For a Bristol or wider Connecticut business, location details should describe where the business genuinely operates. A redesign should not create an office address or a list of town pages just to look local. Agree on a few useful measures after launch, such as completed inquiries and relevant visits, and distinguish those from unsupported promises about rankings or sales.

Bring these five items to a website review

01. Your main services and the action a visitor should take.

02. Three examples of where the existing site creates confusion.

03. Account ownership, hosting and backup information.

04. Pages and URLs worth retaining, with available search or inquiry evidence.

05. A clear budget discussion and a list of functions the site actually needs.

A few useful answers.

Can we improve the website without changing the domain?

Often, yes. A design refresh or rebuild does not inherently require a new domain. Keep a recognizable, business-controlled domain unless there is a separate reason to change it, and plan any migration carefully.

Will a redesign improve our Google rankings?

A redesign can address specific content, usability and technical problems, but appearance alone does not guarantee a ranking change. Preserve useful pages and measure what happens after the agreed improvements.

How do I know whether a quote covers a refresh or a rebuild?

Ask for the page list, platform work, content responsibilities, functionality, testing, launch support and exclusions in writing. Compare those details rather than relying on the project label.

Sources and further reading.

These official resources explain the platform or registration details. Provider features, prices and recovery processes can change; check the current terms for your own setup.

Google: site moves and URL changes

WordPress: backups

Start with a review of the existing website.

AG Creative Works is based in Bristol and works with Connecticut businesses. Share the site, the services it needs to explain and the part that is not working well.

Talk about your website

Keep exploring.

Website Design

What does a WordPress website cost?

How to register a domain name for your business

Your next step
can be a conversation.

Tell us what your business does and what needs to work better. We can start there.

Tell us about your project [email protected]

What’s next?

Let’s work it out.