Signs your web developer is holding your site hostage

The short answer: you own your website only if you hold the login to your own hosting account, your own domain registrar and your own analytics. If any of the three sits with a developer, you are renting access. A lot of business owners find out they don't own their website at the worst possible time: when they want to switch developers, make an urgent change, or the relationship with whoever built it turns sour. If you've never had to log in to your own hosting account, there's a real chance you don't actually control your site, you're renting access to it from the person who built it.

The three-question test

• Do you have your own hosting login? Not one your developer set up and manages on your behalf, one where you're the account owner, with your own email and payment method on file.
• Do you have your own domain registrar access? The domain should be registered in your name (or your company's), at a registrar you control, not sitting in your developer's account "on your behalf."
• Do you have your own analytics account? Google Analytics, Search Console, whatever you use, should be owned by you, not viewed through a dashboard your developer controls and can revoke.

If you answered no to any of these, you don't fully own your website, whatever the contract says.

Why this happens, and why it's a red flag

It's not always malicious. Some developers set things up under their own accounts because it's faster, and never hand it over because nobody asked. But the pattern that should worry you is different: being told you'll get access "once you renew," being charged again for something you already paid for once, or getting vague answers when you ask directly who owns the hosting account. That's not an oversight, that's leverage.

What happens when it goes wrong

The moment you need an urgent change, a bug fixed, a page added before a launch, and your developer doesn't answer, ownership problems turn from theoretical to real. Some business owners have had a site held back entirely after a contract dispute or a non-renewal, with the developer treating access as something to negotiate rather than something that was always the owner's to begin with.

What full ownership should look like

• Your own hosting account, in your name, that you could cancel or move at any time without asking permission.
• Your domain registered to you, renewable by you, transferable if you ever want to move it.
• Your own analytics and Search Console access, so your data stays yours even if you change developers.
• The actual code and design files, not just a live site you can look at but never export.

None of this means you have to manage your own hosting day to day, most business owners are happy to have a developer handle the technical side. The difference is whether you could take it back if you needed to. If the honest answer is no, that's worth fixing before it becomes urgent.