How to Explain Website Hosting to a Client (In Plain English)
Ask a small business owner what hosting is and you will often get a polite blank look. Many think the website "just lives on the internet" and that the person who built it takes care of the rest. Then a renewal notice arrives, the site goes down, or a former designer holds the login, and everyone is upset.
Owners who understand three simple ideas at the start tend to have fewer scares later. You do not need to teach them technology. You need to give them a clear picture and a short page they can keep.
This guide gives you plain explanations, a few analogies that work, a one page handout to write, and answers to the questions owners ask most.
Why this conversation matters
Hosting, domains and email feel like back-office details, but they decide whether the business can be found and reached. If the owner does not know:
- who owns the domain,
- where the site is hosted,
- or who pays for it,
then a missed payment or a lost password can take the whole site offline. Explaining it early protects the owner and protects you from blame for things outside your control.
The three pieces in one sentence each
Start with three simple definitions. Say them out loud before you show any dashboard.
- The domain is the address people type, like yourbusiness.com. It is rented, usually by the year.
- Hosting is the place where the website files are kept so that anyone can visit. It is usually paid monthly or yearly.
- The website itself is the pages, pictures and words that make up the business online.
Many owners also use business email at their domain, such as name@yourbusiness.com. That is a fourth piece, often paid separately.
Analogies that help
Pick the one that fits your client.
The shop analogy
The domain is the street address. Hosting is the building and the rent on it. The website is the shop inside, with the signs and the shelves. If you stop paying rent, the shop closes even if it looks great. If you lose the address, customers cannot find you.
The phone book analogy
The domain is the name in the phone book. Hosting is the phone line the call actually goes to. If the line is cut, the listing does nothing.
The car analogy
The website is the car. Hosting is the garage and the road it needs. The domain is the license plate. You need all three for people to see the car, and each has its own renewal.
Use one analogy, not all three.
Who should own what
The rule that avoids most trouble is simple: the business owner should own the accounts, and you should have access to manage them.
- Domain: register it in the owner's name, with the owner's email. Add yourself as a helper if the registrar allows it.
- Hosting: the owner's account, or an account you manage clearly on their behalf with an agreement that says so.
- Business email: the owner's accounts, with the owner's recovery details.
- The site files and logins: documented and handed over when the project is done.
If you host sites on your own account for convenience, say so plainly and explain how the owner could move the site if they ever wanted to. For the longer version of this, read how to launch a client website: domain and hosting.
The table below sums up who should hold each piece of the setup.
| Piece | Whose account | What you keep |
|---|---|---|
| Domain | The owner's name and email | Helper access, if the registrar allows it |
| Hosting | The owner's account, or yours with a written agreement | Access to manage it |
| Business email | The owner's accounts and recovery details | Only what the deal covers |
| Site files and logins | Documented and handed over at the end | A copy of the handover sheet |
A short script you can use
Here is wording you can adapt for a call or an email:
"Your website needs three things to work: an address, a place to live, and the site itself. The address is your domain, which you rent each year. The place to live is hosting, which keeps the site online. I build the site. I will put the domain and hosting in your name so you always own them, and I will give you a one page sheet with the logins and renewal dates."
Then stop and ask: "Does that make sense? What would you like me to explain again?" Do not rush. A confused owner who nods politely is a future problem.
What owners ask, and how to answer
"What happens if I don't pay for hosting?" The site goes offline. The files are usually kept for a short time, but do not rely on that. Tell them the renewal date and who will remind them.
"Can I move my site later?" Yes, in most cases. Say how: the files and the database can be copied to another host. If you are the one managing it, explain that you will help or hand over what is needed.
"Why is my site slow?" Slowness can come from large images, too many add-ons, or an underpowered plan. Ask to look before you promise a fix.
"Is my site backed up?" Be precise about who does backups, how often, and where they are kept. If nobody does, say so and offer to set it up.
"Is it safe?" Explain the basics: a secure connection (https), updates kept current, strong passwords and limited access. Do not promise that nothing can ever go wrong.
"What about email?" Explain that email at the domain often needs its own service. Tell them what is included in your arrangement and what is a separate cost with a separate provider.
Be honest about costs and renewals
Prices vary by provider, so be clear in your own agreement about:
- What the owner pays directly to the domain registrar and host.
- What you charge, if anything, for managing it.
- When each item renews and how the owner will be told.
- What happens if a payment fails.
Owners hate surprises more than they hate costs. If you plan a monthly arrangement for updates and backups, website care plan: monthly for small business describes what to put in it, and your agreement should reflect it. The website contract basics for web designers covers where to write these terms down.
Build the one page handout
Give every client a single page, written in plain words, with:
- The business name and the site address.
- Where the domain is registered, the account email and the renewal date.
- Where the site is hosted, the account email and the renewal date.
- Where business email is managed, if relevant.
- Who to contact for changes, problems and emergencies, and how fast to expect an answer.
- A note on passwords: how they are stored and who can reset them.
Do not email passwords in plain text. Use a password manager or another safe way to share access, and tell the owner to change shared passwords when the project ends if that is appropriate.
Put the sheet in the same folder as the agreement so both are easy to find. Update it whenever something changes.
What to do when something goes wrong
Prepare a simple plan for the day the site goes down:
- Check whether the domain has expired and whether the host account is active.
- Look at the host's status page for outages.
- Restore from the latest backup if files are damaged.
- Tell the owner what happened in plain words, what you did and what is next.
Short, honest updates keep trust even when the news is bad. Do not blame the owner or the provider in the first message. Fix, then explain.
Keep the conversation short
A good first talk takes about five minutes: the three pieces, the analogy, the ownership rule and the handout. Follow up in writing so they can read it again later.
Where SiteRevive fits
SiteRevive finds local U.S. businesses with old or missing websites, checks each site, and takes the owner's email from the business's own website. You pick a trade and a U.S. state. With Run with your AI, you paste one prompt into your AI. It builds a one-page preview site for each business and drafts or sends a short first note from your own inbox. You can choose "drafts only," read each message and send it yourself.
Hosting and domain setup happen after the owner says yes, and they stay your work with the client. You still decide what to send, how to follow up and what to charge. SiteRevive plans start at $97 a month, plus your own AI plan. There is a 7-day money-back guarantee, no questions asked. It does not promise replies or sales. SiteRevive's servers never send email; your own AI sends from your own account, or saves drafts. Visit the SiteRevive home page or try the free website check.
Frequently asked questions
What is the simplest way to explain hosting?
Hosting is the place where your website files are kept so people can visit them. Think of it as the rent on the building where your shop sits.
What is the difference between a domain and hosting?
The domain is the address people type. Hosting is where the site lives. You need both, and each renews on its own schedule.
Who should own the domain and hosting accounts?
The business owner, in most cases, with you given access to manage them. It prevents lock-in and makes handover easy.
Should I host my clients' sites on my own account?
Some designers do. If you do, say so in writing, explain how the owner could move the site, and keep clear records. Owner-held accounts are simpler for most beginners.
What should the client keep after the project ends?
A one page sheet with the domain and hosting details, renewal dates, support contacts and how to get help, stored somewhere they can find it.
Does SiteRevive host the websites I build for clients?
No. SiteRevive finds and checks businesses and, with Run with your AI, helps your own AI build a one-page preview and a first note. Domain, hosting and launch are arranged separately with the client.