Hi Bjarne,
The SEO Framework handles SSL automatically by detecting the current site’s state.
In the future (I assume 2.8.0 or through an extension), I’ll add ways to add priority to certain schemes.
The most important thing is the Canonical URL in this case.
This URL will change dynamically to the set scheme, which is expected behavior (but not recommended).
So it’s a high-priority update :), because those myths are true to a certain extend.
For now, you’ll simply have to change the site’s URL at WordPress General Settings (the second website URL entry).
I recommend HTTPS, as Google favors secure websites over non-secure.
If WordPress doesn’t redirect the user automatically to HTTPS, you can do several things.
a. Adjust .htaccess
.htaccess adjustments are the fastest way to force website interaction. As this handles things right into the Apache/Nginx core prior to loading the website. So no (slow) PHP handling is needed. This is at least 1000x faster, up to a few million, compared to PHP redirects.
The code you’ll need:
RewriteCond %{HTTPS} off
RewriteCond %{HTTP_HOST} ^oldrup\.dk [NC]
RewriteRule ^(.*)$ https://oldrup.dk/$1 [R=301,L]
Be sure to adjust the WordPress site URL before, otherwise you might encounter a loop.
b. Adjust the Canonical URL:
If you’ve forced the scheme within .htaccess, this is not needed. As The SEO Framework detects the scheme automatically.
When Google encounters a canonical URL that’s different from the current website, Google will abort crawling the current page and will follow that URL and continue from there.
Within The SEO Framework, there’s a filter available so it’ll canonicalize all URLs to a certain scheme:
add_filter( 'the_seo_framework_canonical_force_scheme', 'my_scheme_filter' );
function my_scheme_filter( $new_scheme = null, $current_scheme = '' ) {
//* Only adjust on front-end. You might need to fiddle a bit.
if ( 'https' !== $current_scheme && ! is_feed() ) {
$new_scheme = 'https';
}
return $new_scheme;
}
That’s it :).
I hope this all clears things up!
