UK Website Ownership: What You Keep After a Web Agency Exit

TL;DR: Under UK law, your agency owns your website’s code and design by default — not you — unless your contract explicitly assigns IP on final payment. Before any agency exit, check who holds your domain, hosting, CMS logins and licences. Without written assignment and direct account control, you risk losing access or facing disputes costing UK businesses between £20,000 and £100,000 a year.

Introduction

UK website ownership sounds like a formality until the agency relationship sours and the invoices stop being paid. At that point, SME owners often discover they don’t actually own the thing they spent two years and tens of thousands of pounds building. The domain sits in someone else’s account. The hosting bill goes to the agency’s card. The code lives in a repository you’ve never seen.

This isn’t rare. Poorly drafted contracts and vague handover arrangements can cost UK businesses between £20,000 and £100,000 annually in IP disputes alone, according to the research behind this guide. As more SMEs invest in sophisticated digital presences — fast, well-built sites rather than templated placeholders — the gap between what you paid for and what you legally hold has become more expensive to ignore. 2026 adds a further wrinkle: the rules governing .uk domain transfers are changing, and agencies that have grown used to loose handover practices will need to adapt.

This guide sets out exactly what you should own, what you’re entitled to ask for, and how to check before you ever give notice to an outgoing supplier.

Who owns your website code and content under UK law?

Under the Copyright, Designs and Patents Act 1988, the default position is straightforward and often unwelcome: the developer or agency that created your code, designs and content is the first owner of copyright in it. Paying the invoice doesn’t change that. You only gain full ownership if your contract contains a written clause explicitly assigning those rights to you, usually triggered on final payment, as Sprintlaw’s guide to web development contracts sets out. Without that clause, you hold a licence to use the site — a permission, not a possession — which can be weaker, conditional, or revocable depending on the wording.

What drives the cost of getting this right (or wrong)

Securing proper ownership isn’t free, but it’s far cheaper than the alternative. The real cost driver is whether IP assignment, domain registration and access control are handled upfront in the contract, or patched together after a dispute has already started.

The pattern is consistent: the earlier ownership is formalised, the lower the cost. Artificer Legal’s analysis of IP clauses in software agreements notes that assignment should be explicit, not implied — vague phrases like “client owns the final product” are not the same as a proper assignment clause naming the rights transferred and the trigger event.

Pro tip: Ask your solicitor to review the IP clause specifically, not the whole contract in general. A five-minute read of one paragraph can save five-figure sums later.

There’s also a licensing cost most SMEs overlook. Open-source components and third-party tools used in your build remain under their own licences — you can use them, but you never “own” them the way you own custom code. Your contract should require the developer to list every open-source component used and confirm licence compliance, so you know exactly what you’re responsible for if the agency disappears.

What good looks like vs red flags when comparing providers

When you’re choosing a new agency, or auditing your current one, the difference between good practice and a red flag is usually visible in the first conversation.

What good looks like:

• A written IP assignment clause, triggered on final payment, naming the code, design and content explicitly.
• The domain registered in your business’s name, with your business as registrant and administrative contact, on your own billing — never the agency’s account.
• Direct, top-level administrator access to hosting, CMS, Google Business Profile and analytics, using your own individual logins rather than shared agency credentials.
• A documented list of third-party services, licences and account details, handed over as standard, not negotiated as a favour.

Red flags:

• The agency registers domains in its own name “for convenience.” Gurve Legal’s domain name protection guidance flags this as a common cause of businesses being effectively held hostage over transfer fees.
• Vague contract language like “the client may use the website” instead of ownership or assignment wording.
• Reluctance to provide full database and code exports, or to document the deployment process.
• Hosting billed to the agency’s card with no client-visible control panel access.

If you’re evaluating a new build, this is also where to check delivery quality, not just paperwork. A good technical partner — building, for instance, high-performance Astro websites — should be just as transparent about repository access and deployment pipelines as they are about design mock-ups.

When should you not switch agencies (or not build a new site yet)?

Sometimes the right call is to wait. If your current contract has no IP assignment clause and the relationship is otherwise functional, it may be cheaper to negotiate an amendment now than to terminate and risk a dispute over unclear ownership. If you don’t yet have a documented list of your own accounts — domain registrar, hosting, CMS, analytics — audit that first, before giving any notice. According to the research behind this guide, Google Business Profile transfers alone can carry a seven-day wait, so timing your exit around these delays matters more than rushing it.

Similarly, if your current site works, loads reasonably fast, and converts, a full rebuild purely to “own it properly” is usually unnecessary. Fix the contract and access first; only commission by new build if the underlying technology is genuinely holding the business back.

What this means for Astro & Performance Websites in 2026

From 9 February 2027, .uk domain transfers move from the existing “tag” system to an authorisation code system aligning with .com domains — a change that may introduce renewal charges on transfer that aren’t currently applied consistently. SMEs planning an agency switch in 2026 should factor this timeline into their planning, particularly if a transfer is likely to straddle the changeover. For growth-stage businesses across the Thames Valley commissioning new performance-focused builds, including website development in Slough, this is the moment to insist on clean contracts from the outset rather than retrofitting them later. Fast, well-built Astro sites are only a good investment if the business behind them actually owns what’s been built.

Key takeaways

• Insist on a written IP assignment clause that transfers code, design and content rights on final payment — a default copyright position favours the agency, not you.
• Register your domain in your own business name, on your own billing, with your business as registrant and administrative contact.
• Demand direct administrator access to hosting, CMS, analytics and Google Business Profile using individual logins, not shared agency credentials.
• Require a documented list of all open-source components, third-party licences and account credentials as a standard contract deliverable.
• Audit your digital assets and access permissions before giving notice to an outgoing agency, allowing time for transfers that carry built-in delays.

Conclusion

Website ownership in the UK isn’t assumed — it’s negotiated, documented and verified. The businesses that avoid five-figure disputes are the ones that treat IP assignment, domain registration and access control as standard contract terms, not afterthoughts. If you’re planning a rebuild or a switch in 2026, start with the paperwork before the design brief. Zorinto builds fast, Core Web Vitals-ready Astro sites with ownership terms made clear from the first conversation — worth a look if your next project needs both speed and a clean exit path.