Avoiding Interruptions during Publishing

When the website is ready to be published, it's time to update the DNS records. This will be done by changing the DNS so that the domain (example.com) begins to point to the new server. The global Domain Name System has it's own caches, which causes a short period (an hour for example) during which part of the visitors will be directed to the old site and part to the new. For this reason we recommend doing these DNS updates at night if possible, and if it's important that a possible interruption or disturbance is not visible for visitors.

If the customer has given the control over domains to Seravo there's no particular need to worry about matters concerning DNS. If the DNS changes are handled by the customer, the customer should take care that the changes are done correctly and that the IP addresses that were given in the site's delivery message are used. You can find additional info in our knowledgebase under Domains.

The Address of the WordPress (siteurl, home)

Right after redirecting the domain (within an hour for example) it should be taken care that the proper new domain is implemented on the newly developed site. In most cases Seravo's automation will take care of this and changes the address of the site that was in the form example.fi.seravo.com to the proper form example.fi. If the address is changed from the form example.fi to the form example.com at the site, Seravo's automation can't deduce it in anyway that the change was desired, and therefore such changes are to be done manually. A good tool is a command from wp-cli called 'search-replace' with which you can change all the addresses from the database from one to another in one go.

HTTPS certificate

Another procedure to be done right after redirecting the domain is to implement a HTTPS certificate. This is something that the customer can't do, and instead Seravo will take care of this. Sometimes there might be a delay acquiring the HTTPS certificate if the DNS change has been made incorrectly (e.g. if www.example.com and example.com are accidentally directing to different servers). Also sometimes when publishing a site completely unexpected matters might occur simply because the functionality of the site with a given new address can't be tested beforehand. For this reason it's better to do the DNS changes during night time – the time to update might take 1-2 hours – so there's more room to react to possible disturbances.

When You Can't Afford Failure, Leave it to the Experts

If the functionality of the site is crucial, it's better to leave the publishing to the hands of someone who does it routinely for a living. In the Seravo pricing there is publishing service called Launch Team especially for these situations. Publishing done by a Seravo expert is tested for functionality beforehand in a test environment, which helps to minimize surprises.

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.

Still need help? Contact Us Contact Us