Answer in brief
A domain registered to your agency turns every future conversation into a hostage negotiation. Which decisions here are genuinely irreversible, which are not, and what to check before you pay.
Two five-minute decisions you live with for years
Domain and hosting for a website get chosen right at the start, usually in one evening and usually on price. Then you live with that choice for years, and undoing it costs more than getting it right first time.
Not because it is technically hard. Moving between hosts takes a day. It is expensive because over the years a domain accumulates search positions, email, links from other sites, business cards and signage.
Below: which decisions here are genuinely irreversible, which are not, and what to check before paying.
Start with the single point that matters more than all the others put together.
Whose name the domain is registered in
This is the most important question in the article, and it is almost never asked.
The domain has to be registered to you or to your company. Not to the agency, not to the friend who built the site, not to the employee who happened to handle the internet at the time.
A domain held by an outside party turns every later conversation into a hostage negotiation. A change of supplier, a payment dispute, a falling-out, or simply somebody who stops replying — and you are left without the asset everything else is attached to.
It takes a minute to check: open the public registration record and see who is listed. If the data is hidden, log in to the registrar account — and if you have no access to that account, you already have your answer.
Recovering control of a domain registered to somebody else is possible, but it is slow, needs documents and does not always succeed. Easier not to let it happen.
Choosing the name
There are few rules, and they all come down to being able to dictate the name over the phone.
Shorter is better, but not at any cost. A clear two-word name beats an unclear one-word name.
Avoid hyphens, digits and letters that are read differently in different languages. Every one of those adds a how do you spell that to every time the address is passed on.
Check how the name looks run together and whether it reads a second way. The classic story about words merging happens more often than people expect.
And check whether the name is free in other zones and on social platforms. You do not have to claim everything, but knowing a competitor holds a near-identical address is worth learning before the cards are printed.
The domain zone
The zone affects two things: how much people trust it, and how a search engine reads your geography.
A country zone signals that you work in that country. For a local business that is a plus: both people and search engines pick up the attachment immediately.
An international zone is geographically neutral. If you work across several countries that is the right choice, and geography is then set by the site's structure and its language versions.
New thematic zones look modern and are harder to remember by ear. For a business that dictates its address aloud often, that is a minus.
In practice: a local business takes a country zone; an international one, or one planning to expand, takes an international zone. Mixing makes no sense — two domains with the same content create a duplication problem rather than doubling reach.
If a domain already exists
A separate case: the site is new but the domain stays, or the other way round.
An old domain is an asset accumulated over years: the search engine knows it, other sites link to it, customers remember it. Swapping it for a new one without a strong reason means starting over.
If it does have to change, the old domain is not released. You keep it, and it moves people and crawlers to the new one with permanent redirects. You will be renewing it for several more years.
We have written about what carelessness here costs: after changing platform we were left with six hundred and seventy-three addresses the search engine had known for years and which stopped existing. That was within one domain; changing the domain would produce as many such addresses as the old site had pages.
And check a domain's history if you are buying it second-hand. A domain previously used for spam comes with a reputation, and that reputation becomes yours.
Hosting: three kinds
They differ not in power but in what happens as load grows and when something breaks.
Shared hosting: many sites on one machine, resources divided. Cheap, fine for a brochure site or a blog. The downside is that your neighbours on the machine affect you, and you affect them.
A virtual server: a dedicated share of resources, your own access, your own configuration. A sensible choice for most working sites with a catalogue, an account area or integrations.
A dedicated server or cloud: the whole machine is yours, or resources are issued on demand. Needed when load is heavy or uneven, and when downtime costs more than the server.
A practical rule: take one level above what you need now if the site is growing, and one level below if it is a five-page brochure. Moving is always possible, but it takes a day better spent on something else.
Where the server physically sits
A point people skip, and it affects speed more than half the optimisations do.
Data travels along wires at a finite speed. A server on another continent adds a delay to every request that no amount of compression removes.
The rule is simple: the server belongs where your visitors are. Not where it is cheapest, and not where you are.
If the audience spans several countries, a content delivery network solves it: copies of the site are served from the point nearest each visitor. That is a separate service, worth adding when the geography really is wide.
And check the choice does not create legal complications about where your customers' data is stored — requirements differ by country, and that is a question for a lawyer rather than a hosting provider.
What to check before paying
Six points, each answered in five minutes and each saving weeks later.
Whether you get direct access to files and the database, not only through the provider's panel. Without it, moving becomes a problem.
What restoring from a backup looks like and how long it takes. Ask directly: how many hours to bring the site back if I break everything today?
Which software versions are supported and how often they are updated. A host stuck on an old version limits what you can run on it.
Whether there is a staging area — a copy of the site where changes can be checked before going live.
And how to reach support at three in the morning on a Saturday. Not is there support, but that exact question.
Certificates, email and the small things that break
Three things that look like details and stop a site outright.
The security certificate. It is free now and renews automatically almost everywhere. It breaks in exactly one situation — when auto-renewal quietly stopped working, and one day the site starts frightening visitors with a warning. Set yourself a quarterly reminder to check.
Email on the domain. It usually gets set up on the same host by default, which is unfortunate: when the site moves, the mail moves with it and disappears for several hours. Mail is better kept as a separate service.
And the records that connect the domain to the server. Changes to them propagate over hours, not instantly. When planning a move, allow a day during which some visitors see the old site and some the new one.
Backups are not a hosting feature
This is worth being categorical about, because the cost of being wrong is high.
A backup sitting on the same server as the site is not a backup. It protects you from your own mistake and from nothing else.
Two things are needed: a copy at the provider and a copy of your own, somewhere else. The second is made automatically and downloaded regularly.
And crucially: a backup that has never been restored does not count as working. Restoration should be tested at least quarterly by deploying a copy to a staging area.
On our own site every release takes a copy of the previous version and can roll back to it automatically if the post-launch checks fail. That is not a luxury: it is exactly what makes shipping changes possible without fear.
A checklist before you pay
Domain and hosting for a website, in eight points on one page.
The domain is registered to you or your company, and you have access to the registrar account.
The name can be dictated over the phone without clarification.
The zone matches the geography of the business.
An old domain, if there was one, stays with you and redirects to the new one.
The server sits in the region your audience is in.
There is direct access to files and the database beyond the provider's panel.
There is a staging area and a clear restore procedure.
Email is set up separately from the site's hosting.
Practical checklist
- Check who is listed as the domain's registrant and whether you have account access.
- Confirm the domain name can be dictated over the phone without clarification.
- Match the domain zone to the geography of the business.
- Ask the provider how many hours a restore from backup takes.
- Confirm there is direct access to files and the database beyond the panel.
- Set up a second copy of the site outside the provider's server.
- Deploy that copy to a staging area to prove it actually works.
Questions and answers
Whose name should the domain be registered in?
Yours or your company's. A domain held by an agency or a former employee turns any later dispute into a hostage negotiation: search positions, email and inbound links are all attached to it. Check whether you have access to the registrar account.
Which domain zone should I choose?
A local business suits a country zone: both people and search engines pick up the country attachment immediately. A business working across countries suits an international zone, with geography set by site structure. Two domains with identical content are not needed — they create duplication.
What hosting does an ordinary site need?
Shared hosting is enough for a brochure site or blog. A virtual server is sensible for a site with a catalogue, an account area or integrations. A dedicated server or cloud is needed when load is heavy or uneven and when downtime costs more than the server.
Does server location affect speed?
Yes, more than half the optimisations do. Data travels at a finite speed, and a server on another continent adds delay to every request. The server belongs where your visitors are; for wide geography a content delivery network solves it.
Are the host's own backups enough?
No. A copy on the same server protects only against your own mistake. You need a second copy outside the provider's server, and it has to be deployed to a staging area periodically — a backup that has never been restored does not count as working.