For sites nobody's touched in a long time

Your site hasn't changed in years. Where do you actually start?

A site that hasn't been updated in years usually has a handful of specific, priority issues — not everything needs fixing at once. Paste your URL and find out what actually matters first.

Free · 60 seconds · No signup · Scored across 10 commercial dimensions
Why this matters

A site that hasn't changed in years usually has a few urgent issues, not a hundred equal ones

Facing a site that's been untouched for years is genuinely overwhelming, and that overwhelm is often what stops any action being taken at all — if everything feels like it needs fixing, it's hard to know where to even start, so nothing gets started.

In practice, neglected sites tend to have a fairly consistent priority order. Whatever actively damages trust right now — stale content, wrong contact details, broken links — matters more than anything cosmetic, because it costs real credibility every single day it remains. Mobile experience is usually next, given how much has changed there specifically since many older sites were built.

It's also worth knowing what's genuinely changed in web standards since an older site was likely built: mobile-first is now the baseline rather than an extra consideration, HTTPS is expected rather than optional, and page speed expectations have risen substantially. None of this requires a full rebuild to address — but it does mean an old site is working against different, tighter expectations than it was originally built for.

The three areas below give a starting point, roughly in the order they tend to matter most.

What actually needs attention first

A neglected site's most common priority issues

📱 No real mobile experience
Sites built before mobile-first design was standard often just don't work properly on phones — usually the highest-priority fix.
📅 Stale content and outdated information
Old prices, discontinued services, or outdated contact details actively damage trust rather than just looking neglected.
🔒 Missing modern basics
No HTTPS, no mobile viewport tag, no basic schema markup — small technical gaps that have become standard expectations since the site was last touched.
Common questions

My Website Was Built Years Ago — FAQ

Where should I actually start with a neglected site?

Trust-damaging issues first (stale or wrong information), then mobile experience, then conversion path clarity — cosmetic modernisation matters, but has less immediate commercial impact than these three.

Do I need to rebuild everything, or can I fix it in stages?

Staged fixes are usually the more sensible approach — tackling the highest-impact issues first lets you see improvement without the cost and disruption of a full rebuild all at once.

What's actually changed in web standards since my site was built?

Mobile-first design is now the baseline, HTTPS is expected rather than optional, and page speed expectations have risen significantly — an older site is working against tighter standards than when it launched, even if nothing on it is technically broken.

Should I update content or design first?

Content first, generally — a beautifully redesigned site with outdated pricing or discontinued services underneath still actively damages trust, regardless of how current the design looks.

Go deeper

Related reading

How to Prioritise Fixes on a Neglected Website What's Actually Changed in Web Standards Since 2015 Auditing Old Content Before You Touch Design

Want the fixes implemented, not just listed?

The SiteMedic team can implement every recommendation directly.

Get it fixed →