Website decisions

Redesign or Repair? A Website Decision Guide for Orlando Businesses

Choose between a content update, a focused repair and a rebuild using the actual problem, the parts worth keeping and a reusable decision worksheet.

Orlando Advertising · Published October 21, 2026 · Sources checked October 21, 2026

Describe the problem first

Replace “we need a new website” with a specific observation. Perhaps customers cannot tell which service to choose, the mobile navigation is difficult, or updating basic information takes too much work. Each problem points to a different kind of change.

Record the affected page or task and what you observed. Low inquiry volume alone does not identify the cause: traffic quality, service fit, inquiry delivery and follow-up may also matter. A scoped review can help answer the missing questions before you choose a solution.

Option one: update the content

A content update may fit when the site is usable and maintainable but explains the business poorly. Examples include outdated services, unclear coverage, missing process details or overlapping pages. Better copy and a clearer page structure can be the relevant work.

Hypothetical example: a business now offers both residential and commercial work, but its website explains only the residential service. If the current platform supports the needed pages and inquiry route, the useful first step may be a content plan rather than a replacement website.

Option two: repair the specific obstacle

A targeted repair may fit when the information and overall structure work but a particular step fails. That might be a broken link, an awkward small-screen layout or a confusing form. Establish the cause and required platform access so the repair has a clear boundary.

For example, a form may display a success message while receipt remains unverified. Investigating the receiving process answers that problem more directly than redesigning the homepage. Similarly, a speed warning helps identify something to investigate; it does not by itself establish that the whole site needs replacing.

Option three: rebuild around demonstrated needs

A rebuild becomes a stronger option when the current platform or structure cannot reasonably support the agreed needs. Perhaps essential features cannot be added appropriately, the content model prevents necessary pages, or maintenance constraints make repeated repairs impractical. Ask for an explanation of the actual limit.

Compare what the repair and rebuild options solve, what each leaves unresolved and who maintains the result. Include content migration, changed integrations and customer-journey testing in the comparison, not only the appearance of the new site.

Keep the parts that already help people

Before a significant change, list important pages, useful content and functioning inquiry routes. Available search or analytics data can help when suitable access is authorized. Decide which page addresses can stay and which need a planned replacement.

For changed addresses, Google recommends mapping old URLs to appropriate new destinations, updating internal links and testing redirects. It also explains that significant changes can cause temporary search fluctuations. Plan the transition as part of the project rather than treating it as cleanup after launch.

Copy this decision worksheet

Observed problem: customers or our team struggle to ___ on ___.

Evidence: we observed or tested ___. We still need to check ___.

Keep: these pages, URLs, features or workflows already help: ___.

Content option: improving ___ would address ___; it would leave ___ unresolved.

Repair option: changing ___ would address ___; it would leave ___ unresolved.

Rebuild option: the demonstrated limitation is ___; replacement would address ___ and require this transition work: ___.

Compare: each viable option costs ___, needs ___ and leaves ongoing responsibility with ___. Mark unknowns before choosing.

Acceptance check: we will know the change works when we can observe or test ___.

If you rebuild, plan the old-to-new handover

Copy this record for each important page or download. It connects the old address to the customer’s next step, so you and your provider can agree what survives and what needs checking.

Old address: ___. What the visitor expects to find or do: ___.

Why it matters: ___. Evidence available, or still needed: ___.

Decision: keep the address / move to a relevant replacement / combine useful content / retire it.

New address, if needed: ___. Content or file to carry forward: ___.

Customer’s next step: call / form / booking / download / other ___.

Person implementing the change: ___. Check, result and date: ___.

Open issue and owner: ___. Launch approval and follow-up owner: ___.

For example, a business could keep its contact address while moving a renamed service. The old service link should reach a relevant replacement, not an unrelated homepage. With no replacement, use an intentional not-found response. Have the provider confirm the approach on your platform.

Before launch, check the agreed old links, new navigation and downloads. For permanent moves, ask for tested redirects and an agreed maintenance owner. Changing hosting while keeping the same addresses is a different job from changing page addresses.

Test the customer path through to its receiving destination, using authorized dummy details for forms. Record unresolved issues and who will handle them. Agree which of these tasks the quote includes; the worksheet is a planning aid, not an added service commitment.

Agree on a testable finish line

Match the acceptance check to the problem. For unclear scope, review the accuracy and clarity of the new service explanation. For an inquiry route, test the relevant steps with appropriate authorization. For changed URLs, check the important old and new routes.

Use performance and accessibility checks where they help evaluate the change, alongside practical checks of the customer’s task. Google cautions against chasing a perfect score solely for search ranking. The goal is a useful, maintainable website; the worksheet and a new design alone cannot establish business or search results.

A practical starting checklist

Describe the problem before choosing a solution.
Separate missing information, broken steps and structural limits.
Identify useful content and routes to preserve.
Compare full scopes, including transition and maintenance.
Plan and test any changed page addresses.
Use acceptance checks that match the observed problem.

Sources and context

This is an original AI-assisted explanation, with factual statements checked against the linked sources. The practical workflow is our recommendation, not a claim that Google requires every step. Guidance can change. No rankings, traffic or business results are guaranteed.