I have a WordPress site which uses WordPress HTTPS to enable SSL when users access it via that protocol. However, currently the menu links point back to the HTTP version.

I want users to be linked to HTTPS pages while accessing the site over HTTPS, but not when accessing it over HTTP. Is this possible?

Note: I have tried changing the menu options to use // and / for the links, but in both cases they are just rendered as HTTP links.

  • 1
    See "How do I make my whole website secure?" here. – dan Jan 18 '14 at 6:38
  • Actually all the links are wrong in Wordpress. It's a big nightmare if you ask me... I tried to use it once, although it has nice capabilities (with lots of AJAX) the fact that links are completely broken made me leave that product. – Alexis Wilke Jan 19 '14 at 4:01
  • Have you tried using the official guide – eyoung100 May 15 '14 at 2:07

Do you have the Yoast SEO plugin? I was just actually doing this on my client's site. If so, try going to SEO > SEO Settings > Permalinks > Canonical Settings > Leave Default. (I know canonicalization isn't what you're looking for, but the other two options are "force HTTP" or "force HTTPS.")

Earlier today, I was staying on the secure versions of the pages (when default was set) and staying on the non-secure versions of the page, depending on where I first started.

Also, depending on what kind of server they're on, you could probably do some URL rewriting.

| improve this answer | |

I think, if you are enabling to force the user to use SSL links in settings, that will make all the pages use HTTPS, but not in HTTP. Make sure that your site should be in either HTTP or HTTPS, because only one is possible.

However, we can make some default pages like payment transaction pages or login/register pages HTTPS because they are really secure pages.

One more tip is, if you are enabling HTTPS on all your pages, your site will not be cached by Google robots, so use HTTP in that case.

| improve this answer | |
  • 2
    This isn't what I'm trying to do. Also, the last paragraph is incorrect. – Gelatin Jan 20 '14 at 14:19
  • @Gelatin The link in your comment is in regards to browser caching, whereas the OP was referring to caching by Google (without confirming or dis-confirming that). – dan Jan 21 '14 at 1:53
  • Alternative evidence: GitHub uses HTTPS on all pages and it appears in Google's cache. – Gelatin Apr 22 '14 at 4:56

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.