Register your hosting package yourself
|
If you are not in control of this whoever did it for you can take your site down if they feel like it and if they go out of business your site will disappear when they stop paying their bills.
It's also important to choose a hosting company that charges a fee that you are happy with and provides a site that responds quickly enough. As a horrible over-simplification the cheaper the hosting, the more sites there will be sharing limited resources.
|
|
Register your domain name yourself
|
Whoever registers the domain name is pretty much in control of it, they say yes/no to renewals and control which company hosts the site. Moving a website without the consent of the person who registered the domain name is pretty close to impossible. Transferring a domain name to yourself is possible but if the transfer is opposed or ignored it can be a long process, possibly so long that the domain name expires!
|
|
Get the original site and updates from your supplier but learn how to upload them yourself.
|
This can be a bit time consuming at first but it means that you can always recreate your site elsewhere.
Depending upon the technology used to build the site you may also need "source files" for some parts of it. If your supplier refuses to give them to you now, when the relationship is good, imagine what it will be like later on.
If you do this and keep your passwords to yourself it also means that if things go wrong nobody can log in and delete your site, replace it with porn or rude messages.
|
|
Check licencing and copyright.
|
Are the stock photos used on you site licenced, is an API being used that charges fees, is there any generic text that might be an issue?
Even now there are still active sites that display the message This page can't load Google Maps correctly, which is a hangover from when Google offered maps for free without the need to create an account to when it was still free but an account is needed.
Also get an explicit statement on who owns the copyright on the text and images, without one you may find that that you have a licence to use but no right to change.
|
|
Understand any frameworks used.
|
Understand how your website is created, does it use prewritten frameworks or much, much worse a proprietary framework?
If you go to another supplier will they have access to the framework and will they know it or not want to work with it?
This gets complex really fast, even simple things like a login page is going to share elements that are copied between sites so you can't be granted ownership, just a right to use and change.
|
|