You paid someone to build your website. They took your money, delivered something that barely works, and now they’re not answering your calls. Or maybe they did answer, quoted you another £2,000 to fix problems that shouldn’t exist in the first place.
I hear this story at least twice a month. Business owners who got burned by developers who promised the world and delivered a liability.
The good news: your situation is almost always recoverable. The bad news: you need to make some clear-headed decisions before throwing more money at the problem.
Step 1: Assess the Actual Damage
Before you make any decisions, you need to understand exactly what you’re dealing with. Not all “terrible” websites are terrible in the same way.
Technical Health Check
Run these checks yourself (or have someone technical do it):
Security scan - Use Sucuri SiteCheck or similar. If it shows malware, outdated software, or security warnings, that’s a red flag for deeper problems.
Speed test - Run Google PageSpeed Insights. Anything under 50 on mobile suggests serious performance issues.
Mobile test - Open your site on your phone. Does it look broken? Are buttons too small to click? If basic mobile usability is missing, the developer skipped fundamentals.
Uptime check - Is your site actually online consistently? Use UptimeRobot to monitor for a week. Frequent downtime means hosting or configuration problems.
Functional Reality Check
Go through your site like a customer would:
- Can you find contact information easily?
- Do all forms actually send you emails?
- Do images load properly on all pages?
- Does the site work in both Chrome and Safari?
- Is there an SSL certificate (https, not http)?
Write down every broken thing you find. This list becomes your assessment baseline.
Access Audit
This is critical. What do you actually own and control?
If the developer owns your domain name or won’t give you hosting access, that’s not just a bad website problem. That’s a hostage situation.
Step 2: The Salvage vs Rebuild Decision
I’ve seen both approaches work, but the decision comes down to three factors: foundation quality, technical debt, and business impact.
When Salvage Makes Sense
Consider fixing what you have if:
The foundation is solid - Built on WordPress, modern HTML/CSS, or a legitimate platform. The structure is there, just poorly executed.
Issues are mostly cosmetic - Design looks dated, images are wrong, copy needs work. These are surface-level fixes.
You have access to everything - Admin login, hosting, source files. You’re not fighting for control.
Timeline is critical - You need the site working properly in 2-3 weeks, not 2 months.
Budget is tight - You can’t afford £5,000+ for a rebuild right now.
When Rebuild Is Smarter
Start over if:
Built on dead technology - Flash, ancient PHP, a custom CMS the developer invented, broken WordPress installation from 2018.
Security is compromised - Evidence of hacking, malware, or exposure of customer data. You can’t patch your way out of fundamental security problems.
Missing core functionality - The site was never actually finished. Forms don’t work, pages are placeholders, the checkout process crashes.
Mobile is fundamentally broken - Not “needs tweaking” broken, but “completely unusable on phones” broken.
You’re locked out - Developer owns the domain, won’t provide access, or the site is on their proprietary platform.
Step 3: Extract What You Can
Whether you’re salvaging or rebuilding, you need to save everything recoverable from the current site.
Content Extraction
Text content - Copy all your service descriptions, about page content, blog posts. Paste into Google Docs or similar. Even if the site is terrible, you probably spent time on that copy.
Images - Download all photos, logos, graphics. Right-click and save, or use a tool like HTTrack to mirror the site locally.
Customer data - If you have a contact form that worked at some point, export the leads/inquiries. Same with email subscribers, customer accounts, etc.
SEO assets - Note which pages ranked for anything in Google. Use Google Search Console if you have access. You’ll want to preserve good URLs and redirect old ones.
Technical Extraction
If you have any access at all:
Database backup - WordPress sites, Shopify data, anything stored in a database. Export it even if you’re not sure you’ll use it.
Source code - Download everything via FTP or hosting panel. It might be messy, but it’s yours.
Analytics data - Export Google Analytics reports showing traffic patterns, popular pages, referral sources. This informs the rebuild.
Email list - If email marketing is connected to the site, export your subscriber list before changing anything.
Step 4: Migration Strategy
Once you’ve decided on salvage or rebuild, you need a plan that doesn’t break everything in the meantime.
The Staging Approach
Never work directly on your live site. Set up a staging version:
For salvage - Most hosts let you clone your site to a staging URL (staging.yourdomain.co.uk). Make fixes there, test thoroughly, then push live.
For rebuild - Build the new site on a temporary domain or subdomain (new.yourdomain.co.uk). Only switch over when it’s actually finished and tested.
This means your broken site stays online (at least it’s something) while you fix or rebuild without public-facing disasters.
The Cut-Over Plan
When you’re ready to launch the fixed or new site:
- Pick a low-traffic time - Sunday evening or early Monday morning for most UK businesses
- Backup everything - One final backup of the old site before you touch anything
- Set up redirects - Map old URLs to new ones so you don’t lose Google rankings
- Update DNS if needed - If you’re moving hosts, point your domain to the new server
- Test immediately - Check forms, mobile, key pages within the first hour
Communication Plan
Tell people what’s happening:
Email list - “We’re improving our website. If you notice any issues over the next week, please let us know.”
Social media - Brief update that improvements are coming.
Key clients - Direct heads-up if you’re working with repeat customers who use your site regularly.
This manages expectations and turns potential complaints into understanding.
Step 5: Protect Yourself This Time
The reason you’re in this mess is because something went wrong the first time. Here’s how to avoid repeating it.
Ownership Documentation
Before you pay anyone:
- Domain ownership - You must own the domain registration. Not the developer, not the agency. You.
- Hosting in your name - The account should be under your business email, with you as the billing contact.
- Written agreement - What’s being delivered, when, and what happens if it’s not done properly.
- Handover checklist - List of every login, password, and access credential you’ll receive at the end.
Payment Structure
Never pay 100% upfront. A reasonable structure:
- 30% deposit to start work
- 40% when you can preview the working site
- 30% on completion and handover
This keeps the developer motivated to actually finish and protects you if they disappear midway.
Red Flags to Watch For
If you hear these phrases, proceed with extreme caution:
- “You don’t need access to the hosting, I’ll manage it for you”
- “The domain should be in my name for technical reasons”
- “You wouldn’t understand the code, just trust me”
- “I need full payment upfront to get started”
- “It’s built on my proprietary platform”
These are not industry standards. These are control tactics.
The Recovery Timeline
Realistic expectations for getting back on track:
Assessment phase - 1-2 days to inventory damage and extract data
Decision phase - 3-5 days to get quotes, evaluate options, make the salvage vs rebuild call
Salvage timeline - 2-4 weeks for fixes, testing, and launch
Rebuild timeline - 4-8 weeks for a proper job, depending on complexity
Post-launch monitoring - 2 weeks of close attention to catch any issues
Yes, this means you’re looking at 1-2 months total to properly recover from a bad website situation. Trying to shortcut this usually means creating another bad website.
What This Actually Costs
Budget expectations for UK service businesses:
Assessment and extraction - £300-600 if you need technical help
Salvage and fix - £1,500-3,500 depending on how broken it is
Full rebuild - £3,000-8,000 for a professional job done properly (our business website service offers full rebuilds with ownership and access guaranteed)
Migration and setup - Usually included, but budget £500 if complex
These numbers assume a typical 5-15 page service business website. E-commerce or custom functionality costs more.
Moving Forward
The worst part of a terrible website isn’t the money you lost. It’s the time you spent worrying about it, the customers who bounced, and the business opportunities that slipped away because your online presence was broken.
Recovery is possible. I’ve helped dozens of businesses get out from under bad websites. Most are online with something they’re actually proud of within 6-8 weeks.
The key is making clear-headed decisions based on what you actually have and what you actually need, not what the last developer promised or what you wish had happened.
Start with the assessment. Know what you’re dealing with. Then make the salvage or rebuild decision based on reality, not hope.
