Site Launch Best Practices

Getting ready for the big launch can be exciting and nerve-racking. This guide will help you make sure you are ready for lift off!

Summary

The purpose of this document is to outline the steps for a successful, low-risk site launch process on Flywheel. If you are only looking for the quick steps to point your DNS and take a simple site live here on Flywheel, please refer to our standard Go Live help doc.

The following process will take place after the initial migration, or after your site has been built on Flywheel.

If you have any questions, our Happiness Engineers are available 24/7.

Pre-launch

1. Check and adjust TTL (time to live) for Name Servers and DNS records if needed.
   1. Change TTL of A record and www CNAME record as soon as possible (changing TTL doesn’t affect the site).
   2. If you do need to change Name Servers before taking a site live at Flywheel, we strongly recommend that you do that at least 3 days prior to launch.
      

      Note

      Here’s a quick conversion guide for TTL values if your registrar uses seconds:

      TTL value in seconds	Converted
      300	5 minutes
      900	15 minutes
      1800	30 minutes
      3600	1 hour
      43,200	12 hours
      86,400	24 hours
      604,800	1 week

2. If you plan on purchasing your own SSL certificate, you’ll want to install that prior to launch.
   If you’ll be using Simple SSL, you’ll add that from the Overview tab after the site has been made live on Flywheel.
3. If your site is eCommerce, LMS, forum, Membership or has other user-generated content, disable anything that allows that user-generated content (ordering, comments, posts, etc.).
4. Have changes been made to the live/old site? If so, follow the steps in this handy help doc on refreshing your site’s content.
   
5. Prior to the day of launch, update all plugins and themes on the migrated site, including the premium ones.
   
   

   Note

   Note: it may not be possible to update premium themes or plugins directly through the WordPress dashboard. Updating those often requires direct contact with the theme/plugin developer. It’s extremely important to update premium themes and plugins, as they are often overlooked sources of out-of-date code that can cause potentially fatal errors and security vulnerabilities.
6. Test each page of the site and any functionality (third party embeds, shopping cart, feeds, widgets, etc.) to make sure all is working as expected.
7. Use a broken link checker to check for any broken links or missing images. A few tools/services we can recommend (do not use a plugin):
   1. Mac: Integrity
   2. Windows: Xenu’s Link Sleuth
   3. All: Online Broken Link Checker

Launch Day

1. Confirm Development Mode is turned OFF on the Advanced Tab for the site.
   
2. If you installed Simple SSL on the temp domain or a test domain before go-live, make sure Force HTTPS is turned OFF on the Advanced tab.
   
3. Work through the steps of the go live help doc.
4. Once DNS has fully propagated, clear cache in any page builder plugins, themes, and/or caching plugins, then clear cache in your Flywheel dashboard.
   
5. If using Simple SSL, add that to the site (skip this step if you purchased and installed a third-party SSL certificate).
6. Once Simple SSL has been added, allow 20 minutes minimum (but can be up to one hour) for the SSL certificate to fully propagate to all of our Cloud infrastructure before forcing HTTPS.
   
7. If applicable, clear cache in any page builder plugins, themes, and/or caching plugins, then clear cache in your Flywheel dashboard once more.
8. Don’t see the padlock in your browser’s address bar? Check out our handy help doc for how to get the padlock in the browser bar.
   

Things to keep in mind

• It’s best to take sites live Tuesday – Thursday during low traffic times.
• TTL (time to live) applies to Name Servers and individual DNS records.
• If you prefer to use Simple SSL, that can only be done once DNS has fully propagated and privacy mode is off.
• When installing Simple SSL, we recommend waiting 20 minutes minimum (but can be up to one hour) for the SSL certificate to fully propagate to all of our Cloud infrastructure before forcing HTTPS in your Flywheel dashboard. You can verify this is done by manually typing in the HTTPS URL in your browser to visit the site. If the site loads, you can force HTTPS; if it doesn’t load, wait a little longer and try again.

Need help?

If you have any questions our Happiness Engineers are here to help!