Website maintenance, fixes and redesigns

Honest 2026 bands: independent care plans $30–150/month (updates, backups, monitoring, small edits), agency plans $150–500/month adding content work and reporting, hourly fallback $40–100 when something needs real attention. Annual plans price below monthly. The honest framing: maintenance is insurance plus gardening — the cheapest plan from someone who answers email beats the richest plan from someone who does not.

If the site runs on a CMS or store platform: yes, non-negotiably — updates, backups and security patches are how sites stay live and unhacked. A truly static hand-coded site needs almost none. The test: what happens if the site goes down Friday night? If the answer is "nothing, nobody notices", skip maintenance. If the answer involves revenue, do not.

A proper plan: platform and dependency updates with a staging check first, verified backups (tested restores, not just saved files), uptime monitoring, security patching, small content edits within a monthly allowance, and a quarterly report. What it excludes until agreed: new features, redesigns, marketing. The itemised version is the maintenance checklist.

Yes — monthly retainers are the standard shape of care work: a defined allowance of updates, fixes and edits plus monitoring, rolling monthly. Most sites fit a light plan; commerce and membership sites need the heavier tier. What to verify before signing: response-time promises in writing and who actually does the work.

Any competent developer working in your stack can — diagnosis is the first billable hour, and most fixes land 1–4 hours after the cause is found. Honest bands: routine fixes $50–300, hack cleanups $200–1,000 including hardening, recovery-from-no-backups scenarios pay more and succeed less. Active emergencies triage faster: emergency work.

Platform and security updates: as released, applied within days after a staging check. Content: weekly-to-monthly depending on how the site earns; stores and publishers live on freshness. Full audits: quarterly. The failure pattern is not too-few updates — it is years of none followed by an emergency. Rhythm beats intensity.

Usually 60–100% of a comparable new build — the design work is equivalent, and careful content/SEO migration adds its own workstream. Template-refresh redesigns run $1,500–5,000; full redesigns $5,000–20,000+ from independents. Anyone quoting "redesign" at logo-refresh prices is reskinning, not redesigning — sometimes that is actually fine, but know which you are buying.

Redesign when the site measurably underperforms: conversions falling, mobile experience poor, Core Web Vitals red, brand visibly outgrown, or the platform end-of-life. Do not redesign from boredom or competitor envy — those projects pay back nothing. The signals checklist is the redesign guide.

Visual refresh: every 3–5 years. Continuous improvement: always — the better pattern is steady quarterly upgrades against analytics rather than five-year big bangs. Technology migrations happen when the platform forces them, not the calendar. Sites that improve continuously rarely need dramatic redesigns; that is the entire strategy.

Both, when done with continuity discipline: redirects mapped before launch, schema preserved, content strategy intact, speed improved — rankings usually hold and rise, conversions follow the UX work. Done carelessly, redesigns are the classic way businesses destroy rankings overnight. The safety procedure: the redesign checklist and SEO migration work.

Yes — dramatically in most cases: image pipeline fixes, caching layers, code and asset diet, hosting moves, and the plugin/app audit that removes the slow ones. Realistic outcome: most neglected sites can cut load time by half or more. The workstream is performance engineering.

Yes: isolate, clean, patch the entry point, harden, and restore confidence with monitoring. The professional sequence is documented in security work; the after-hack hardening checklist is the security checklist. Speed matters after a hack: every day infected hurts search and trust.

Yes — routine work: replicate to the new host, rehearse the cutover, switch DNS during low traffic, verify and roll back if needed. Pricing runs on site complexity, not distance. When it is more than hosting — platform moves — that is the migration section.