redesign or rebuild? matrix, paths, equity safety

web · 2026-10-13 · 7 min

redesign guides (hubspot's classic) sell process; nobody helps owners choose between refresh and restart. wrong choice wastes both directions: redesign on rotten foundations (preserved rot, fresh paint) or rebuild for cosmetic problems (months and thousands for new fonts). the decision matrix, then each path done right.

redesign when (refresh the living)

structure sound (URLs, content depth, rankings healthy). problems cosmetic (dated look, weak trust signals, poor mobile polish). platform adequate (CMS current, integrations fit). content mostly right (needs editing, not rewriting). history valuable (years of links/rankings to preserve — moves risk them: site moves). redesign keeps equity, costs less, ships faster.

rebuild when (restart the dead)

platform wrong (ceilings hit: builder limits, unmaintainable stack). technical debt terminal (hacked repeatedly, updates impossible, speed unfixable). structure rotten (URL chaos, duplicate sprawl, penalties). rebrand fundamental (new business, new audience, new model). migration math positive (rebuild cost < redesign-workaround cost × years). rebuilds reset equity — budget the SEO transition (redirects, monitoring, fluctuation weeks) as part of the quote, not an afterthought.

each path done right

redesign: audit first (what converts now — preserve it), change in stages (measure between), preserve URLs (redirects only where necessary), retest everything (launch checklist). rebuild: content inventory, URL map, staging, redirect matrix, console monitoring both properties, patience through fluctuation. both: backups before, analytics during, reviews after. neither fixes content voids — words first in both paths (service pages).

FAQ

how often redesign?

design ages 3-5 years; businesses change faster. redesign on evidence (conversion decay, brand drift, mobile pain) — calendar redesigns are agency revenue plans, not owner needs.

keep rankings through either?

redesign: yes, if URLs/content preserved + speed maintained. rebuild: temporarily dips, recovers with correct redirects + equal-or-better content. traffic loss is a process failure, never fate.

smallest-fix-first ladder

if URLs/structure change: inventory, map 301s, keep titles, retest search console. after-launch: after publish.