Envious Digital offers dedicated hosting, along with supporting care plans for after the site is launched. If our hosting is used, we would just need to point the IP address of our server to the DNS settings of the domain name. If our client’s own hosting solution is to be used, we would need to migrate the new website to their hosting instead.
Access to the domain name is really only needed if Envious Digital is going to be hosting the new website, piece of software, or application. This is so we can add our IP address to the domain name so it displays the new files, rather than what was there previously.
When the new website is replacing a previous one, there could be pages that have already been ranking well with Google. If the URL structure has needed to change, or old content is being archived, we will need to put 301 redirects into the site. This means that when someone visits the old URL, it will take them to a page on the new website containing content that is most relevant to what the previous page contained.
Depending on the type of migration needed (whether it is a site replacement on existing servers or whether the DNS needs to be changed) – there can be a time period of propagation. This is the time it takes for different servers and ISPs across the world to ping the new IP address and it update – displaying the new website. Due to this, it may be worth planning the launch for a time when the website is typically the least visited.
During development, it may not be possible to use live API keys, especially when the dev domain was different from the live environment or the system the API works with doesn’t allow for multiple domains to be active. Once the site is launched and on its new/final domain and hosting environment, we will ensure that API keys are updated accordingly. A typical example of this would be e-commerce stores where Stripe (a payment gateway for facilitating card payments) is being used.