Securing Your Titan CMS Site With HTTPS

This guide will walk you through the process of securing your Titan CMS site with SSL. Once this is done, all pages on your site will be served via HTTPS.

The first step in this process is provisioning certificates and installing them on the web server. If your site uses Northwoods's shared hosting environment, we'll take care of this setup for you.

Titan CMS: Configure a Content Site to Use HTTPS

To instruct Titan to serve all pages on your site with HTTPS:

  1. Log in to the Titan Workstation and choose "Titan Administration".
  2. Expand "Content Sites" from the tree and choose the site on which you want to enable SSL.
  3. Under "Display Site Configuration" > "Site SSL Support", check the radio button next to "All pages must be https".
  4. Save your changes by clicking on the disk icon at the top of the screen.
  5. Within Titan Administration, perform a workstation refresh.

    On the refresh screen, include the workstation and all sites using domains that you switched to HTTPS.


That's it! If you have multiple content sites, you'll need to make this change to all of them.

SEO: Google Search Console, Sitemaps, & Fetch.

  1. Google Search Console treats HTTPS as a separate website, therefore you will need to create a new Property within Google Search Console. Click on “Add a Property” and continue with the claiming process.

  2. XML sitemaps are not required for Google to crawl and index your website, but they are a useful tool to tell Google – here are the important pages I want to show up in the Google search index. Once you have verified your new HTTPS property, you will need to resubmit the HTTPS version of your new sitemaps in the Google Search Console profile.
    • You can find the XML sitemap URL in your Titan Administration Module.

    • Remember to submit the XML sitemaps for your globes and your data sites

    • Your XML sitemaps may also be referenced in your robots.txt file.  To check if your sitemap is included, visit "". If your sitemap is included, please let Northwoods know and we will update the link with the HTTPS version of your sitemap.  Email to make this change (you must have an active Maintenance and Support Contract with Northwoods).

  3. Fetch and Crawl your new website to get things moving a little faster. Sometimes Google will take weeks to re-crawl your website correctly. Submitting your homepage to the Fetch feature in Google Search Console helps move things along.
    • Submit your homepage by clicking “Fetch” and then click on “Submit to Index”.
    • Choose “Crawl this URL and all its direct links”

    If you have some additional key SEO pages that are not connected to your homepage, you may consider submitting them individually too.
  4. If you previously used the disavow tool in Google Search Console, you will need to resubmit your file. Learn More about the Disavow Links tool.
  5. Update your Google Analytics profile URL. Although your website will continue to send data to Google Analytics, regardless of the URL in your Google Analytics property, it is good practice to make this change. Also include an annotation in your Google Analytics data that indicates when the HTTPS switch was made. This way you can track any changes based on the specific day the switch was made.

  6. Additional considerations.
    • Update your PPC URLs – make sure your ads are pointing to the HTTPS version of your site.
    • Update Email Marketing URLS
    • Update your social profile links to your site
    • Update as many external and backlinks as possible.

Fixing Mixed Content Issues

Even though your site is now using SSL, you might still notice some pages that browsers mark as insecure or that don't get the padlock in the address bar. This is usually caused by something called "mixed content". Check out our guide on finding and fixing mixed content issues on your site.

An error (Object reference not set to an instance of an object.) was encountered trying to format content from PageUrl=/SocialMedia.htm