Does your website need a refresh or a full redesign?

Refresh the site when its structure and tools still work. Redesign it when the business, content, mobile experience, or customer path no longer fits the system underneath.

A refresh may update copy, photos, colors, type, calls to action, and individual sections inside a sound page plan. A redesign can change navigation, page structure, responsive layouts, visual direction, integrations, and how visitors move from first impression to contact.

The age of a website is not enough to decide. A newer site can be confusing, and an older site can still work well. Start with observed problems and the amount of the current system each fix would touch.

Preserve accurate business details, strong photos, useful service explanations, working integrations, customer proof, domain ownership, and pages that already serve a clear purpose. A redesign should improve the system around good material, not erase it for novelty.

Also inventory URLs and search-relevant pages before changing the structure. A visual reset is not a reason to lose useful content or send established links to dead ends. Redirects, metadata, forms, analytics, account access, and domain settings belong in the launch plan.

Write down the business goal first. A project intended to update staff photos is different from one intended to make several new services understandable, improve quote quality, or support online ordering. The goal gives each proposed change something concrete to serve. Without it, refresh and redesign can become vague labels for a list of preferences that grows during the project.

Then inventory the current pages and mark each one keep, revise, combine, replace, or remove. Keep pages that are accurate and useful. Revise pages whose purpose is sound but whose content or presentation is weak. Combine pages that split one small idea across several destinations. Replace pages when the customer question has changed. Remove a page only after checking whether people or search engines still reach it and where that traffic should go.

Review the main customer paths as sequences. A visitor might land on the homepage, open a service, review examples, and request a quote. Another might arrive directly on a service page from search and never see the homepage. A redesign scope should support both routes. A refresh can stay section-level only when those routes already make sense and the changes do not create new dead ends.

Separate content work from visual work. New navigation labels, service explanations, proof, pricing language, and calls to action require business decisions before styling can solve anything. Updated colors and typography can improve presentation, but they cannot decide which offer belongs first or what a customer needs to know. A realistic scope assigns time for those content decisions instead of hiding them inside a visual revision round.

Define the acceptance checks before the work starts. Key pages should be reviewed at common phone and desktop sizes. Forms should reach the right inbox. Phone, email, booking, ordering, and map links should work. Titles, descriptions, redirects, analytics, privacy choices, and domain settings should be accounted for. This list turns a subjective makeover into a project with a visible finish line.

Stay on the current platform when it supports the required pages, editing workflow, integrations, account ownership, and future maintenance without awkward workarounds. Changing platforms creates migration work, retraining, new billing relationships, and new technical risks. A familiar system that can support the approved direction may be the lower-risk choice.

Consider moving when the current platform blocks essential functionality, makes basic updates unreasonably difficult, depends on unsupported tools, or keeps important accounts outside the business's control. The decision should come from specific constraints. Disliking one template is not the same as outgrowing the platform, and a new platform will not fix unclear content by itself.

If a move is justified, create a migration inventory. Record every public URL, page title, form, download, image, integration, domain setting, analytics account, tracking tag, and destination email that matters. Decide what transfers, what changes, and who has access. A redesign can look finished while quietly losing a form notification or established page if the migration is treated as a last-day technical task.

Protect the live business during the change. Build and review in a draft or preview environment, keep the current site available until launch checks pass, and plan a rollback path for important changes. Confirm domain ownership and account access before the launch window. The visual work may receive most of the attention, but access and continuity are what keep a redesign from becoming an operational surprise.

Review the homepage on a phone, submit every form, follow the main navigation, check the service information, and list what the business has changed since the site was built. Separate concrete failures from personal design preferences.

If the failures cluster around a few sections, a refresh may be enough. If they appear across the navigation, content, mobile layout, tools, and customer journey, a redesign is easier to scope honestly.

Frontstage's website audit is free for a limited time and provides a fix-first action plan. It is a useful first step when the project label is still unclear.

Ask a few customers or staff members to complete a real task without coaching. Have them find a service, check whether the business serves their location, locate proof, or start an inquiry. Notice where they hesitate and what information they expect but cannot find. A small observation session is more useful than a room full of opinions about whether the site feels modern.

The final recommendation can be mixed. A site may need a structural redesign on its service and contact paths while preserving the current platform, logo, photography, and several useful pages. That is a normal result. The best scope is not the most dramatic option. It is the smallest coherent set of changes that solves the documented problems without creating new ones.

Take a baseline before changing anything. Record the current page list, form destinations, main customer actions, account owners, and any analytics the business already trusts. Save approved copy and original images outside the website. This creates a reference for deciding whether the project improved the intended path and protects useful material from disappearing during enthusiastic cleanup.

Be careful with a refresh that slowly becomes a redesign. If a request to update the homepage uncovers new navigation, several rewritten services, new photography, a rebuilt form, and a platform limitation, stop and revise the scope. Continuing under the original label hides cost and compresses review. Naming the expanded work gives the business a real choice about priorities, schedule, and budget.

The opposite matters too. Do not sell a complete rebuild because two photos are outdated and one call to action is weak. Focused corrections can extend the useful life of a sound site and preserve a system the team already understands. Good diagnosis protects the business from unnecessary change as much as it identifies the moment when deeper work is justified.