Why SSL on one page?
If you don’t want to move to SSL entirely because you’re afraid to lose your ranking, don’t worry. If you redirect your site with 301 permanent redirects, this does not happen.
Sometimes your site become a bit slower when on SSL. This might be especially noticeable when you have a lot of resources loading from external domains. Or your site might use a service that doesn’t support SSL. Trying to get that service to start supporting SSL would be the best solution of course. But if you’ve got your mind set on enabling SSL on just one page, you can.
The plugin solution: Really Simple SSL per page
To be able to offer a solution that supports this, I’ve developed a plugin that handles this for you. You’ll have to deactivate the free plugin, and then install Really Simple SSL per page.
The manual solution
You could do this manually as described below. This won’t give you the mixed content fixer, though.
- Go to your FTP program
- Look for the root of your website
- Find the .htaccess file. Sometimes you have to enable the “Show hidden files” option
- Open the .htaccess file in a text editor
Then add the following lines above the WordPress redirect rules in your .htaccess file:
Remember, if you are in a subdirectory (website/subsite) you have to add the subsite before the page. RewriteEngine on RewriteCond %{HTTPS} !=on [NC] RewriteCond $1 /your-page-on-ssl/ RewriteRule ^(.*) https://%{HTTP_HOST}%/$1 [R=301, L]
If you change it to this:
RewriteCond %{REQUEST_URI} !/your-page-on-ssl/
The redirect will not take place on that URL.
If your site is still redirecting you might have to leave the homeurl and siteurl on http, using safe mode.