Website redesigns and rescues
Something you inherited, something that broke, or something a developer stopped replying about.
First, an honest answer
Not every site needs replacing. Sometimes the problem is three oversized images and a plugin doing something silly, and that is a morning's work rather than a project.
So the first thing you get is a straight answer about whether a rebuild is worth paying for. If it isn't, I'll say so — a rescue I talked you out of is a better outcome for both of us than a rebuild you didn't need.
The usual suspects
A site an AI builder produced, with fifty-odd dependencies and a database nobody will ever log into. A theme abandoned by whoever wrote it. A hosting account in a previous employee's name. A contact form that has been quietly failing for months.
That last one is more common than it should be, and it's the expensive one: the site looks fine, and the enquiries simply stop arriving with nothing to show that they ever tried.
Keeping what you have earned
If the old site ranks for anything, that ranking is an asset and it is easy to throw away. URLs get mapped and redirected properly, existing content is preserved rather than quietly dropped, and the new site goes up with its sitemap and structured data in place from the first day.
What's included
- A plain-language assessment of what you currently have
- A recommendation, including "keep it" where that is the right answer
- Old URLs mapped and redirected so existing rankings survive
- Content migrated rather than rewritten from memory
- Every account moved into your name
- A before-and-after on speed and accessibility, measured
If your current developer is unreachable but the accounts are in your name, the work is straightforward. If the accounts are in theirs, that is the first thing to sort out and I can talk you through it.