Home
›
Articles
›

The agency that built your website has disappeared

The agency that built your website has disappeared

By Ibi Hasanli

·

·

4 min read

The agency that built your website has disappeared, and you now own a site nobody can log into. The fix isn't to keep chasing them. It's to take ownership: recover the access you can, move hosting and DNS into the business's name, then decide between a care plan for a sound site and a clean rebuild for one that's beyond rescue.

What an orphaned website looks like

An orphaned site still loads. That's what makes it easy to ignore. The trouble sits behind it, in accounts that belong to someone who no longer answers.

WHAT THE SITE NEEDSWHO HOLDS ITDomainAgency registrar accountDNSBuilder's CloudflareHostingBuilder's email loginCMS and licencesAgency licenceRenewals and SSLInbox nobody readsHeld by the business:none
An orphaned site: each part answers to someone other than the business.
  • Access: the WordPress admin works for one old login, or the Webflow project sits in the builder's workspace rather than yours.
  • Hosting: the SiteGround or GoDaddy account was opened with the builder's email, and the password reset goes to an inbox you can't see.
  • DNS: the domain points at nameservers on the builder's Cloudflare account, so a change to email or hosting needs their help.
  • Codebase: a WordPress theme with Elementor and a dozen plugins, half updated, with a premium licence registered to the agency.
  • Renewals: SSL, hosting and plugin renewal emails go to an address nobody reads, and Search Console is tied to a personal Gmail.

None of this breaks today. It breaks on the day a certificate lapses, a card expires or a plugin vulnerability lands, and then you're locked out of your own shopfront.

What you can salvage and when a rebuild is cheaper

Plenty of orphaned sites are worth keeping. If the content is right, the design still fits the business and the platform is current, the problem is ownership, not the site. Recover the accounts, put it under care and move on.

But some sites are archaeology. A WordPress install several major versions behind, an Elementor build left mid-project, page builder add-ons that are no longer sold, custom code with no repository: each fix means digging before you can change anything. At that point a rebuild against a clear brief costs less than paying someone to understand what was left behind. We covered the general trade-off in website care plan vs rebuild; the orphaned case just adds the cost of not knowing what you have.

The honest test is simple. Can an engineer update it safely in an afternoon? If yes, take it over. If nobody can say what updating it would break, rebuild.

A sensible takeover path

Do it in order. Jumping straight to a redesign while the domain still sits in someone else's account is how sites go dark during a launch.

STEP 1InventoryList each accountSTEP 2AccessRecover loginsSTEP 3Hosting and DNSUnder the businessSTEP 4Care or rebuildWritten plan
Take it over in order: nothing moves until you know what exists and who holds it.
  • Inventory: list the domain registrar, DNS provider, hosting, CMS, plugins and licences, email, analytics and Search Console. Note who holds each one.
  • Access: request transfers in writing. Where the builder won't reply, registrars and hosts have recovery routes for the named account holder, and Google lets a verified domain owner add Search Console access again.
  • Hosting and DNS under the business: move the domain and DNS into an account opened with a company email and company card, then move hosting once you have a full backup.
  • Care plan or rebuild brief: with access in hand, an engineer reviews the site and writes a plan. Either it goes under ongoing care, or the review becomes the brief for a rebuild.

Eight Mile can support websites it didn't build. That starts with a review of what the site does, where it's fragile and what it costs to run, followed by a written plan, so you know what needs changing before support is practical. For domain questions specifically, who actually owns your business domain name goes further.

How to stop your website being orphaned again

The agency that built your website has disappeared once. Set it up so the next supplier leaving is an inconvenience, not an emergency.

Business owner accountRegistrarSupplier seatDNSSupplier seatHostingSupplier seatCMSSupplier seatAnalyticsSupplier seatSupplier seats can be removed without touching ownership
The business owns each account; suppliers get a user you can revoke.
  • Logins: the business holds the owner account for registrar, hosting, CMS and analytics. Suppliers get their own user, which you can remove.
  • Billing: renewals go on a company card and land in a shared company inbox, never one person's Gmail.
  • DNS: nameservers live in an account the business owns, with a second person able to sign in.
  • Written handover: a short document listing each service, who has access and how to restore from backup, updated whenever something changes.

Or hand the whole stack to someone accountable for it. Our managed websites include domain registration, hosting, SSL, backups, security patches and a twelve-month warranty, with direct contact with the engineers who built the site.

If your site is in this state, don't spend another month waiting for a reply. Send us what you know about where it's hosted and who holds the domain, and we'll tell you whether it's worth taking over or rebuilding. Talk to an engineer.

Websites
Hosting

Uptime monitoring for a small business website

Uptime monitoring for a small business website only works with a named engineer and response path. What a care plan or managed hosting should cover.

·

3 min read

AWS
Infrastructure

Leaving a freelancer with your AWS root login

Leaving a freelancer with your AWS root login is a risk even after a good build. How to take back control with named IAM, MFA and a handoff.

·

4 min read

CRM
SaaS

CRM for a small firm off the shelf or built

CRM for a small firm off the shelf or built: when HubSpot-class tools fit, and when a system on your own job data serves trades and clinics better.

·

4 min read

TradeOps
SME

When WhatsApp is running your jobs

When WhatsApp is running your jobs, groups and voice notes become the job board. What a proper ops system replaces, without taking phones away.

·

4 min read

Software
Customer service

The info@ inbox nobody owns

The info@ inbox nobody owns is where a UK SME's enquiries sit with no named owner and no reply time.

·

4 min read

Field service
Mobile apps

From paper job sheets to a phone app

What changes when a trades business moves from paper job sheets to a phone app, including how the app copes with no signal.

·

4 min read

Security
Cyber Essentials

Cyber Essentials for small businesses

A plain-English guide to Cyber Essentials for small businesses, covering what the scheme checks and when a contract will ask for it.

·

4 min read

Email
SPF

Why your quotes land in spam

Why your quotes land in spam: SPF, DKIM and DMARC explained for business owners, and how to check your own domain with free tools.

·

3 min read

Networking
Office move

Office move IT checklist for London SMEs

Office move IT checklist for London SMEs: internet lead times, surveys, cabling, network design, servers and security before and after moving.

·

4 min read

Web design
Care plan

Website care plan vs rebuild

Website care plan vs rebuild: when maintenance is enough for a London SMB site, and when a full rebuild earns the spend.

·

3 min read

Networking
VPN

Multi-site office network

Multi-site office network design for London SMEs: site-to-site links, consistent segmentation, accounts you keep.

·

3 min read