Resources

Website rescue guide

Should You Repair or Rebuild Your Small-Business Website?

A small-business website should usually be repaired when the platform, ownership, content, and overall structure remain sound and the problems are contained. A rebuild may be more practical when access is unclear, the platform is fragile or unsupported, technical debt is extensive, or the cost of continued repair approaches the cost of starting clean. Many websites fall between those two choices and are better suited to broader improvement, redesign, or migration.

No backend access needed for the initial public-site review.

Four practical paths, not just repair or rebuild

DDS does not automatically recommend rebuilding every older website. Many small-business websites sit somewhere between a quick repair and a full rebuild.

Focused Fix

Suitable when

  • the issue is clear and contained
  • the platform still works
  • access is available
  • the site structure is generally sound
  • only a small group of related changes is needed

Examples

broken links or buttons; text or image updates; a form issue; a small mobile or layout correction.

Rescue & Improvement

Suitable when

  • unclear homepage messaging
  • weak calls to action
  • crowded navigation
  • inconsistent mobile layouts
  • outdated content

Examples

clearer service sections; simpler contact paths; better mobile flow; basic visibility cleanup.

Migration or Redesign

Suitable when

  • useful content should be preserved
  • the current platform or design limits progress
  • the website is difficult to maintain
  • the structure no longer supports the business
  • a cleaner foundation is needed

Examples

moving platforms; preserving useful pages; redesigning around existing content; cleaning up structure.

Clean Rebuild

Suitable when

  • the platform is unreliable or unsupported
  • account ownership or access is unclear
  • technical debt is extensive
  • plugins or integrations are fragile
  • repair cost approaches rebuild cost

Examples

new foundation; new structure; safer launch plan; clear ownership handoff.

Compare the likely direction

This table is a planning guide, not a diagnosis. The same visible problem can have different causes depending on platform, access, integrations, and history.

One broken form or link

Focused FixLikely

RescueMaybe

MigrationUsually no

RebuildUsually no

Outdated homepage messaging

Focused FixMaybe

RescueLikely

MigrationMaybe

RebuildUsually no

Weak mobile layout

Focused FixMaybe

RescueLikely

MigrationMaybe

RebuildDepends

Crowded navigation

Focused FixMaybe

RescueLikely

MigrationMaybe

RebuildUsually no

Useful content worth preserving

Focused FixMaybe

RescueLikely

MigrationLikely

RebuildMaybe

Platform difficult to maintain

Focused FixUsually no

RescueMaybe

MigrationLikely

RebuildMaybe

Repeated plugin or integration failures

Focused FixUsually no

RescueMaybe

MigrationMaybe

RebuildLikely

Ownership or hosting access unclear

Focused FixUsually no

RescueMaybe

MigrationMaybe

RebuildLikely

Major new functionality required

Focused FixUsually no

RescueMaybe

MigrationMaybe

RebuildLikely

Repair cost approaching rebuild cost

Focused FixUsually no

RescueMaybe

MigrationMaybe

RebuildLikely

What should determine the decision?

A good repair-versus-rebuild decision starts with practical facts, not a fixed rule about website age.

Platform condition

Is the platform still supported, stable, and maintainable?

Ownership and access

Can the business control the domain, hosting, platform, content, and important accounts?

Severity and number of problems

Are the issues contained, or do they affect the whole website?

Content and URLs worth preserving

Is there useful content, search value, trust information, or customer familiarity that should be kept?

Required functionality

Can the current platform support the forms, booking, e-commerce, integrations, or custom features the business needs?

Repair cost versus rebuild cost

Would continued repair create recurring expense without solving the underlying limitations?

Practical examples

These examples are illustrative situations, not guaranteed diagnoses.

Example 1: Focused Fix

A five-page Wix website has current branding and useful content, but the contact form is broken and several mobile sections are misaligned.

Likely direction

Focused Fix

Example 2: Rescue & Improvement

A WordPress website works, but the homepage is unclear, navigation is crowded, mobile layout is inconsistent, and calls to action are weak.

Likely direction

Rescue & Improvement

Example 3: Migration or Redesign

The content is worth keeping, but the current website builder is difficult to maintain and limits future changes.

Likely direction

Migration or Redesign

Example 4: Clean Rebuild

Hosting access is unclear, plugins are abandoned, forms repeatedly fail, and repairing the current setup would approach the cost of rebuilding.

Likely direction

Clean Rebuild or deeper technical review

How much might each path cost?

Use these public starting points for planning. Final scope and price are confirmed before work begins.

Free Website Quick Take

$0

A public-site first look to suggest the likely direction.

Focused Website Fix

From $197

For one clear, contained issue or a small group of closely related changes.

Rescue & Improvement Sprint

From $497

For broader cleanup involving structure, messaging, navigation, mobile layout, calls to action, content organization, or basic visibility foundations.

Larger rescue, migration, redesign, or rebuild

Quoted after review

For platform changes, extensive technical or structural issues, migration, major redesign, custom functionality, or cases where rebuilding may be more practical.

Price depends on platform and access, number of pages, issue complexity, content and migration needs, integrations, testing, risk, and custom functionality.

For current website and visibility starting points, see the Pricing page.

What should be preserved during a redesign or rebuild?

When a redesign, migration, or rebuild is the practical path, the goal is not to throw away everything useful. A careful plan should consider:

  • domain ownership
  • important URLs
  • useful content
  • page titles and metadata
  • internal links
  • redirects
  • analytics
  • Search Console
  • business information
  • forms and contact pathways
  • existing trust signals

A careful migration can reduce avoidable search and traffic loss, but rankings and AI visibility cannot be guaranteed.

When repair is not the right fit

Some situations require specialist support or referral. That can be the responsible recommendation when the issue falls outside a practical website rescue scope.

  • active malware or security incidents
  • server administration
  • large or complex e-commerce
  • custom databases
  • membership systems
  • regulated systems
  • proprietary legacy platforms
  • heavily customized integrations

DDS can help identify the likely direction, but does not overstate security, server administration, or complex systems expertise.

Frequently asked questions

Is an old website always better rebuilt?

No. Age alone is not enough to decide. If the platform is stable, access is clear, and the issues are contained, a focused repair or broader improvement may be more practical than rebuilding.

How old is too old for a website?

There is no universal age limit. A newer website can be poorly structured, and an older website can still be useful. The better question is whether the site is maintainable, mobile-friendly, clear, secure enough for its purpose, and aligned with the business today.

Can a non-mobile-friendly website be repaired?

Sometimes. A small mobile layout problem may be repairable. If the entire site was built on an old layout system or the platform limits responsive changes, redesign or rebuilding may be more practical.

Can I keep my domain during a rebuild?

Usually, yes, as long as you control the domain account or can regain access. Domain ownership should be confirmed before any rebuild or migration begins.

Can a website be rebuilt without losing SEO?

A careful migration can reduce avoidable search and traffic loss by preserving important URLs, content, metadata, redirects, internal links, analytics, and Search Console access. Rankings and AI visibility cannot be guaranteed.

What if I do not control the hosting or website account?

Access and ownership should be clarified before technical work begins. In some cases, recovery is possible. In others, a new setup may be cleaner and safer than trying to repair an account the business does not control.

Is WordPress worth repairing?

Often, but not always. WordPress can be a strong platform when it is maintained well. If the theme, plugins, hosting, or access situation is fragile, a cleanup, redesign, migration, or rebuild may be better.

How much does website repair cost?

Durham Digital Services currently lists a Free Website Quick Take at $0, Focused Website Fixes from $197, Rescue & Improvement Sprints from $497, and larger rescue, migration, redesign, or rebuild work quoted after review.

Do I need backend access for the first review?

No. The initial Free Website Quick Take is based on the public website URL and the details you provide. Backend access is only discussed if hands-on work is recommended later.

What if I am still not sure which option fits?

Start with the Free Website Quick Take. It is meant to provide a practical starting direction before you commit to paid repair, improvement, migration, redesign, or rebuild work.

About Durham Digital Services

Durham Digital Services helps small businesses and organizations across Durham Region and nearby Ontario communities build clear new websites and repair, improve, migrate, redesign, or rebuild existing ones. Supporting services include Local & AI Visibility foundations and practical interactive tools.

Published by Durham Digital Services

Location: Durham Region, Ontario

Last reviewed: July 22, 2026

Related reading: web design for Durham Region small businesses, Website Rescue & Improvement, and more resources.

Need a starting direction?

Send your website for a public-site first look.

No backend access is needed for the initial Quick Take. If paid work makes sense, scope and price are confirmed before work begins.