Your Web Developer Stopped Answering. Do This First
Your web developer went quiet. Here's the order to work in: find who holds the domain, DNS, hosting and Google profile, get access, back up, then rebuild.

Three emails, two voicemails, nothing. The site is still up, so it doesn't feel like an emergency yet. Then you notice the contact form hasn't sent you anything in weeks, or a renewal notice arrives addressed to someone else, or you want to change your hours and there's nobody to ask.
This happens more than vendors admit. A freelancer takes a full-time job. A one-person shop folds. Someone gets sick. The work stops, but the accounts keep running in their name until something expires.
Work in order. The order matters more than the speed, because the wrong first move — an angry email, a chargeback, a public review — can get you locked out of accounts you still need.
Step one: find out if the clock is running
Before anything else, figure out how much time you have.
Check whether your domain is close to expiring. Go to ICANN Lookup (lookup.icann.org) for .com, .net and most others, or the CIRA WHOIS at cira.ca for a .ca. Type in your domain. You'll see the registrar name and the expiry date even if the contact details are hidden.
If expiry is months away, you have room to be patient and polite. If it's weeks away, you are on a deadline. A domain that lapses goes through a grace period, then a redemption period where getting it back costs many times the renewal price, and then it drops and anyone can take it. Businesses lose their domain this way — not to theft, to silence.
Also check: is the hosting bill on the developer's credit card? If it is, and their card is dead, your site goes offline without warning. If you can keep paying anything that keeps the lights on, keep paying it. Cancelling a subscription in protest is the fastest way to take your own site down.
Step two: list the four accounts, plus email
Almost every "I lost my website" story comes down to not knowing which of these is where.
Domain registrar. Where the domain name is rented. GoDaddy, Namecheap, Rebel, Google Domains migrated to Squarespace, Cloudflare. This is the single most important one. Whoever controls the registrar can point your domain anywhere.
DNS. The settings that say where the domain points — the website here, the email there. Often at the registrar, often at Cloudflare instead. Control of DNS is control of your email, which matters more than most owners realize.
Hosting. Where the actual website files and database live. Could be a WordPress host, could be Shopify or Squarespace, could be a server the developer rents and resells slices of.
Google Business Profile. Not part of your website at all, but it drives your map listing and your reviews, and developers routinely make themselves the owner.
Email. Google Workspace or Microsoft 365 with your domain on it. If the admin account belongs to your developer, every staff mailbox is downstream of a person who isn't replying.
Write these five down on paper and mark each one: I have the login, I don't, or I don't know. The unknowns are your work list.
Step three: find who holds what, without asking
Public WHOIS records are mostly redacted now, so you won't see a name. You will see the registrar, and that's enough — go to that registrar's site and start a password reset on your own email address. If a reset link arrives, you have the account.
For hosting, look at your credit card statements and your old email for receipts. Search your inbox for "invoice", "renewal", "receipt" and your domain name. A two-year-old welcome email often has the account number in it. If you paid the hosting bill directly at any point, you have a paper trail.
For email, a free MX record lookup tool will tell you whether you're on Google, Microsoft, or your host. Then try the admin recovery flow.
Our post on who owns your website domain walks through the lookups in more detail if you want to go record by record.
Step four: ask once, in writing, like an adult
Before escalating, send one clear message. Email and text. Keep it short and unemotional:
"I need to take over the accounts for [domain]. Please send me the registrar login or start a transfer to my account, confirm where the site is hosted, and transfer the Google Business Profile. Happy to settle any outstanding invoice first. If I don't hear back by [date one week out], I'll go through the registrar's ownership process."
Two reasons this matters. It sometimes works — plenty of ghosting is embarrassment, not malice, and a no-drama request gets answered. And if it doesn't work, you now have a dated record of a reasonable request, which is exactly what registrars and dispute processes want to see.
Do not threaten. Do not file a chargeback on the hosting yet. A chargeback can get the hosting account suspended, with your site inside it.
Step five: when the domain is in their name
This is the hard case, and it's recoverable more often than people think.
Contact the registrar directly — support ticket, not the chat bot. Tell them you are the business the domain represents, the listed registrant is unreachable, and you want to start a registrant change or ownership dispute. Ask what evidence they accept.
Gather what you have: your business registration or incorporation documents in the same name as the domain, invoices showing you paid for the domain or the site, emails where the developer refers to it as your domain, a trademark if you have one, and anything showing continuous use of the name. For .ca domains, CIRA has a formal process and the registrant must meet Canadian presence requirements, which can work in your favour if the developer is offshore. For .com and most others, ICANN's transfer and registrant-change policies sit behind the registrar's own procedure.
It takes weeks, not days. In the meantime, run a parallel plan: if the domain is genuinely gone, a close variant with your city in it beats being offline for two months. Don't let the dispute stop you from trading.
Step six: back up everything before you change anything
The moment you get into any account, copy things out. Access can disappear again.
Save the full text of every page — paste it into a document, page by page. Download every photo at the largest size available, especially food shots and staff portraits you paid for. Export your customer list, booking history and order history from whatever platform holds it. Screenshot the DNS records exactly as they are, including the email records, before you touch anything. Download any site backup the host offers.
If you have hosting access but no site builder login, your content is still there in the files. Even a crude copy beats recreating three years of menu descriptions from memory.
Step seven: Google Business Profile has its own path
If someone else owns your profile, sign in to Google with your own account, find your business, and use the "Request access" option. Google emails the current owner, who has a set window to respond. If they ignore it, you can be granted ownership. It's slow but it works precisely because unresponsive owners stay unresponsive.
While you wait, you can still reply to reviews only if you have access, so prioritize this one. Reviews are the asset you can never rebuild.
Step eight: rebuild or migrate, now that you own the pieces
Once the domain, DNS and content are yours, rebuilding is ordinary work. Move the site to hosting billed to your card, point the DNS yourself, and keep the domain at a registrar where you hold the master login.
This is the right moment to ask whether the old site was worth saving. If it was slow, never updated, and you couldn't change your own hours, you're not losing much. Before you hire the next person, read our questions to ask a web designer and the contract red flags worth arguing about — most of them exist because of exactly this situation. If you'd rather hand the whole recovery to someone local who has done it before, that's part of what a Toronto web agency should handle on day one, before anyone talks about design.
Set it up so it can't happen twice
The fix is boring and takes an afternoon.
Create one email address you control — something like admin@yourbusiness.ca, or a Gmail if you must — and use it as the account email for the registrar, the host, the Google profile and the email admin. Not your personal address, not your manager's, not the developer's.
Put your own credit card on the domain and hosting. The annual cost is small, and the card is the leash.
Turn on auto-renew for the domain and set a calendar reminder a month before expiry anyway.
Give your developer delegated access, not ownership. Registrars, Google Business Profile and most hosts all support adding a user. Add them as a manager. Remove them when the work ends.
Store the logins in a password manager, and tell one other person in the business where it is.
Then once a year, on a slow day, log into each of the five accounts and confirm you still can. Five minutes. It is the cheapest insurance you will ever buy on your business's online presence.