Full-Site HTTPS

Full-Site HTTPS for storefront sites is important because it prevents intruders from being able to passively listen to communications between your website and your users. That's a huge benefit. Other benefits are as follows:

When you configure your Commerce Cloud site for full-site HTTPs, Salesforce B2C Commerce forces URL generation to use only the HTTPS protocol (no custom code changes required, except for hardcoded HTTP links). Incoming requests using HTTP are automatically redirected to HTTPS (with a 301 (permanent) redirect).

You can enable this feature only on a Development or Production instance whose configuration supports Full-Site HTTPS (that is, the instance is using either the Commerce Cloud eCDN or the Akamai Connector).

Migration and Configuration

So, how do you migrate? If you're already on Commerce Cloud eCDN, we'll do the migration for you. If you aren't, you must first migrate to Commerce Cloud eCDN.

Once you've migrated, you set the Enforce HTTPS site preference. This preference is also visible and configurable when an instance supports HTTPS-only. The feature toggle does not change the preference's visibility. The preference is instance specific and not included in the replication process. Static and Dynamic Mappings aren't effected by this preference. Make sure you change absolute URLs appropriately. Hard-coded - absolute URLs are also unaffected. Make sure you change absolute URLs in your HTML code appropriately.
Note: When the Enforce HTTPs preference is enabled, no changes to the URLUtils method are required. URLUtils.http generates URLs with the https protocol.

robots.txt file

HTTPS sites use the HTTPS robots.txt file, so check the following:

Online impact

You might be wondering how this change will impact your online presence. To start, there might be a drop in organic search traffic. According to Google, fluctuations in organic search traffic can occur with any large site change. Page rank, or link juice, however, should see no impact from HTTP to HTTPs redirects. According to Google, during 301 or 302 redirects from HTTP to HTTPS no PageRank will be lost.

Search keywords in Google Analytics won't change with HTTPS. You can still see the search queries in the Google Search Console.

To test how many HTTPs pages were indexed by Google, you can verify HTTP and HTTPs separately in the Google Search Console, use Index Status for a broad look, or chack the sitemaps indexed counts for sitemap URLs.

The time to move from HTTP to HTTPs within the Google Index depends on the size of your site and the speed of crawling. The move from HTTP to HTTPs URLs in Google's Search Index takes place on a per-URL basis. Google doesn't provide fixed crawl frequency data.