{
  "id": 15128079,
  "title": "Who Should Own a Client's Domain and Hosting? A Handover Checklist",
  "url": "https://urgent.news/2026/10/17/who-should-own-a-clients-domain-and-hosting-a-handover-checklist",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-10-17T05:25:22.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/jainischalverma/who-should-own-a-clients-domain-and-hosting-a-handover-checklist-1be1"
  },
  "original_language": "en",
  "account": "When you create websites for clients, a clear handover is essential. This checklist outlines what should belong to the client and what the designer should retain.\n\nFirst, the domain name should be registered to the client's business. The business's contact email should be listed as the registrant. The designer should only have user access, not full control.\n\nNext, hosting should be in the client's name and billed to their credit card. The designer should get access to the hosting account, but this access should be removable at any time.\n\nThe designer should also have their own user access to both the domain and hosting. This allows them to make changes if necessary, but it also gives the client the ability to remove that access.\n\nIt's important to note that in the US, simply paying for a website doesn't automatically make the client the copyright owner. This should be clarified in writing before final payment.\n\nIf the client moves to another registrar, they'll need the authentication code (also known as an EPP or transfer code) to move the domain. Only the registrant can obtain this code.\n\nFor hosting, the client should pay for the service directly. The designer should have access through their own login, which can be removed once the project is over.\n\nLastly, the client should have control over all email, analytics, search console, and Google Business Profile accounts associated with the website. This includes the ability to show the site in the client's portfolio, if the client agrees. Premium theme and plugin licenses should be bought in the client's name, or at least listed under their name.",
  "summary": "If you build sites for clients, this is the setup I use on every project, and the one I'd want any client to insist on from any developer. It's written for small-business owners, so feel free to forward it to the client who still thinks \"the website\" is a file you email. Originally published at Sites You Own . Short answer: you do. Not your designer, and not your cousin who \"knows computers\".…",
  "key_points": [
    "Domain name should be registered to client's business",
    "Hosting should be in client's name and billed to their credit card",
    "Client should have control over email, analytics, and Google Business Profile accounts"
  ],
  "editors_take": "Assigning ownership of digital assets to clients protects businesses from vendor lock-in and ensures they maintain ultimate control over their online identity and intellectual property.",
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}