Who Owns Your Website After You Fire Your Agency?

You send the email on a Monday: contract's ending, please send over the login. Tuesday, nothing. Wednesday, a reply that opens with "per our internal policy" and closes with a new invoice for "account transfer services" you never agreed to pay. Your site is still up. You just cannot get into it, and neither, as it turns out, can anyone but them.

That is not a rare story. It is the default outcome of a contract that never said, in writing, who owns what once the relationship ends. Most agency agreements are written around getting the work done, not around handing it over, and that gap is not an accident. A vague ownership clause costs the agency nothing to leave out and pays out the moment you try to leave.

Who owns the website if you leave your marketing agency?

Ownership comes down to four things, and none of them is a feeling: who holds the domain registrar account, who controls the DNS, who has admin access (not editor access) to the CMS or hosting, and whose name is on the license for the custom code and paid assets. If your contract is silent and the agency's name sits on all four, you can be functionally locked out of a site you paid to build, even though you almost certainly own the copyright to the content and design under standard work-for-hire principles.

That "almost certainly" is the trap. Work commissioned and paid for generally belongs to the client who paid for it, unless the contract says otherwise, and plenty of agency contracts do say otherwise, quietly, in a clause about the agency retaining rights to its "proprietary systems and code." But copyright is a claim you would have to go enforce. Access is immediate. An agency holding the registrar login and the hosting account does not need to win an argument about who owns the site. It just needs to not answer the email. Practical control beats legal ownership every time you need the site to keep working today, this week, long before your legal position would even matter.

The four assets that actually decide the fight

Everything else in this dispute is detail. These four accounts are the whole negotiation, because each one is a different kind of lock.

1. The domain registrar account. Whoever holds this can point your domain anywhere: at your site, at a parking page, at a competitor, at nothing. If it is registered in the agency's name, you do not own your own address on the internet, no matter what the contract says about the website itself.
2. DNS. Even with the domain registered in your name, if DNS is managed through the agency's account, they control where every request for your domain actually resolves: your site, your email, all of it.
3. CMS or hosting admin access. An editor role lets you change a headline. An admin role lets you export the database, add an integration, and remove the agency's own login. Agencies that hand out editor access while keeping admin for themselves are not being cautious. They are keeping the door.
4. Source files and licensed assets. The custom code, the design files, and every stock photo, font, plugin, or icon set bought for the build. If those licenses were purchased under the agency's account, the license itself may not transfer to you at all, regardless of who actually built the site.

Losing any one of these turns "we own our website" into a theoretical claim you would need a lawyer to enforce. It is the same asset-inventory logic we walk through in when to fire your agency: the accounts, not the invoices, are what tell you who actually owns anything.

Can your marketing agency take down your website?

Yes, mechanically, if they control the registrar, the DNS, or the hosting account, regardless of who legally owns the copyright in the content. A domain repointed or a hosting account suspended takes minutes; disputing it afterward takes weeks, and your site is dark the whole time.

This is not a scare tactic, it is just how the infrastructure works. A registrar transfer, a DNS change, a hosting deactivation: each one is a five-minute action by whoever holds the login, with no requirement to ask you first. Agencies rarely do this out of spite. It happens for mundane reasons: a disputed final invoice, a "we'll turn it back on once you settle up," a staffer running a routine account cleanup who does not know the relationship is contested. The result reads the same either way. Your site goes dark, your email tied to that domain stops working, and your leverage in the argument collapses because now you need them more than they need you.

A vague ownership clause costs the agency nothing to leave out and pays out the moment you try to leave.

This is the mirror image of the argument in why we left Wix: a platform that will not let you export is the same problem as an agency that will not hand over the keys. Either way, the thing you paid to build was never fully yours, and you find out on the one day it matters most.

What the ownership clause needs to say before you sign anything

Get four things in writing before any work starts, whether you are signing with a new agency or renegotiating one you are already in.

• Domain in your name, from day one. Register or transfer the domain into an account you control, with your billing card on it, before the agency touches anything. If they offer to register it "to save you the hassle," that is the clearest signal in this whole post to say no.
• Admin access for you, always. You get an admin login to the CMS and hosting from the start, not at the end. The agency can hold its own admin login alongside yours. There is no legitimate technical reason you cannot have one too.
• An explicit assignment-of-work clause. Language stating that custom code, designs, and deliverables become your property upon final payment, not "upon request" and not "available for a transfer fee."
• Licensed assets in your name. Stock photography, fonts, plugins, and any paid tool used in the build should be licensed to you directly, or the agency should hand over a documented list of what needs relicensing the day you leave.
• A written handoff checklist tied to the final invoice. Not a verbal promise. A named list of accounts, logins, and files that transfer the day the last payment clears.

None of this is adversarial. A healthy agency does all five without being asked, because it is not trying to make itself load-bearing. That is the same test we describe in the retainer trap: an arrangement that only works while the vendor stays attached was built that way on purpose, before you ever signed. If you are still choosing which agency to hire, cross-reference this against how to hire a marketing agency without getting burned, since the ownership clause is one line item on a longer list you should be checking before any money changes hands.

Agency won't give you access to your website? Here is the order of operations

Send a written request first, naming the specific accounts, before you announce that you are leaving. Give a short deadline, escalate to the registrar or host directly if that deadline passes, and treat a lawyer as the last resort rather than the first move, since most of these disputes resolve once the agency realizes you already know exactly what to ask for.

Work the escalation in this order:

1. Email the request, specifically. Not "please send our stuff." Name the domain registrar transfer (or the authorization code, if you are only moving registrars and the name on the domain is already yours), the DNS zone, the CMS admin login, and the source files. Vague requests get vague, slow answers.
2. Set a real deadline and put it in writing. Ten business days is standard and defensible. State what happens if it passes: you will contact the registrar or host directly, and if the contract includes an assignment clause, you will treat continued denial as a breach of it.
3. Go to the registrar or host once the deadline passes. Domain registrars have a formal dispute process for exactly this situation, and hosting providers can usually verify account ownership through billing records even when login credentials are being withheld.
4. Bring in a lawyer only once the damage is real money or real time. If the downtime is costing you actual leads or revenue, a short letter from counsel referencing the contract's assignment language moves faster than most people expect, precisely because most agencies do not want that letter on file.

If you are mid-dispute right now and the site is already dark, that sequence is the fastest path back to control, even if it is not the most satisfying one. Skipping straight to a lawyer feels justified and is usually slower than the registrar's own process.

The version that never has this problem

This entire negotiation exists because so many agencies design it to exist. When ownership sits with the client from the first invoice, the exit is a non-event: you already hold the domain, you already have admin, the code was already licensed to you, and there is nothing left to hand over because nothing was ever held back. We saw the alternative up close rebuilding a legacy site whose entire archive had quietly accrued its search authority to a platform, not to the person who wrote every word of it. The fix was not clever. It was handing every asset back to the person who created the value in the first place, which you can see the shape of in the John Lantos rebuild.

If you are staring at a contract right now trying to decide whether the ownership language actually protects you, or you are already locked out of a site you paid for and need the fastest way back in, book a call. We will read the clause, or help you write the request, before you spend another month renting access to your own website.