How To Get HTTPS In Custom Domain In Blogger? - SE Optimized

Activate HTTPS on Blogger third party Domain 100 Worked | WMI - https://3.bp.blogspot.com/-bOCTNQhWzYA/WBmcYZFKW8I/AAAAAAAAAw0/V1juMdd-VWw8AUrPb8b7Wz8jDYdm1Vi0gCLcB/s400/HTTPS_for_custom_domains-min.png

Yes, it’s been quite a while since I distributed my last post, yet here, I have something interesting for you!
The thing I am today going to share worth your important minutes. Too, oh my goodness that I have a few bits of new substance to compose in the up and coming days. In this way, on the off chance that you haven’t yet.
So yes, how about we go to the thing that I will disclose to you today, the most anticipated thing for which bloggers have held up a considerable measure.

Along these lines, clients of BlogSpot have their blessing. That is to say, clients of BlogSpot space who haven’t purchased any custom area. The blessing is: SSL Declaration for their area. Be that as it may, shouldn’t something be said about blogger websites with the custom area? Will they need to hold up additional? No remark. All things considered, see the address bar and you’ll see that Blogger Guider has SSL Authentication, and it is fueled by CloudFlare and along these lines, our blog’s stacking speed has additionally diminished!

Activate HTTPS on Blogger third party Domain 100 Worked | WMI - https://3.bp.blogspot.com/-1zh7ShICd4Q/WBmcaHeE2UI/AAAAAAAAAxc/MPx11FMNkOk-6f33DduAwufj0-F0xQHMACLcB/s1600/screenshot_71-min.png

Activate HTTPS on Blogger third party Domain 100 Worked | WMI - https://3.bp.blogspot.com/-FeXB3KNT3h4/V7BYs49T-kI/AAAAAAAAALc/Hpe8OQFxK3QLPXKIHeRMZwyyg1vy2mrCACLcB/s1600/screenshot_72.png

Along these lines, 1.46s for a 4.6 MB is not terrible. Contrast this and different online journals or sites with comparative page size and you’ll see that they stack slower. That is the impact of, yes, right-CloudFlare. CloudFlare is a CDN benefit which is Allowed to utilize, and will utilize this administration just, with some JavaScripts to move your blogger blog from HTTP to HTTPS and in reward, you’ll get a lift in your blog’s stacking time.

Presently, I’d get a kick out of the chance to make this unmistakable in beginning, that, I don’t prescribe utilizing the thing I will share. No, don’t take it that contrarily. I intend to state, I’ve utilized CloudFlare’s free arrange in this post yet, I exceptionally prescribe you utilizing their Ace Arrangement which costs just $20 every month. All things considered, when you have a decent blog + great wage, then interest in right things is likewise imperative.

Along these lines, without squandering your time, how about we begin!

Everybody know Google gives a slight lift to the rank of locales which are HTTPS empowered. In any case, slight increment. That is insignificant on the off chance that you inquire me. In any case, the contort most likely is, in future, as indicated by what I have perused up until now, Google will build the impact of this “lift” and that time, you’ll be desirous of WordPress locales.
So, you’ve got the reason to follow this guide but, let’s
first read some important points:

  1. Your traffic will be down for few days until Google correctly
    indexes all your URLs with HTTPS.

  2. During this all process, if you made any mistake, then your
    blog can go down for few hours (so, consider doing this all
    after 12 AM if you get most of your traffic from India)

  3. You’ll have to remove all the widgets that are
    hosted/attached to non-SSL hosts.

If it’s not too much trouble Note: In case you’re not that techy or are new to blogging or terms like “Facilitating,” “CDN,” then I’ll not suggest you going further. Rather, take a gander at this segment. Additionally, I’m not going to expound every one of the things. I’ll clarify as it were primary principle things to keep this short guide, short.

Moving From HTTP To HTTPS

So, let’s start the process. Firstly, we’ll change the
default nameservers. In my case, my domain registrar was GoDaddy and
so, in this post, I’ve shown the settings of GoDaddy only. If
your domain registrar is not same, then see this section of the post.

Activate HTTPS on Blogger third party Domain 100 Worked | WMI - https://1.bp.blogspot.com/-zQjHiOVCwR8/WBmofwUOHRI/AAAAAAAAAz8/TleaE-GLuv4D12wUKHszIDmO92vZZJizgCLcB/s640/screenshot_81.png
Activate HTTPS on Blogger third party Domain 100 Worked | WMI - https://4.bp.blogspot.com/-Mr0WweJu_Dc/WBmca6yeHwI/AAAAAAAAAxo/hkZFRbBIBq40n9KXaPnDfv3QAQvHoQTwQCLcB/s640/screenshot_82-min.png

Till now, what you’ve done, or we’ve done is the setup of CloudFlare on our TDL space, and now, the genuine motivation behind this guide starts.

Activate HTTPS on Blogger third party Domain 100 Worked | WMI - https://3.bp.blogspot.com/-yr_H3qHXrhI/WBm8qosgGBI/AAAAAAAAA2E/8cBepbZpTOstJOgqoMQeGV9tp9mG5rcJACLcB/s1600/screenshot_83_min-min.png
*
Congratz! You’ve successfully enabled SSL on your Blogger
blog. Try visiting your blog with “https” followed
by your domain.

Activate HTTPS on Blogger third party Domain 100 Worked | WMI - https://2.bp.blogspot.com/-sghiR2-cNYo/WBmcbP3073I/AAAAAAAAAxs/yxO5cBkQAUktkvjwjGy14ZES-FdIwhXGwCLcB/s640/screenshot_84-min.png Activate HTTPS on Blogger third party Domain 100 Worked | WMI - https://3.bp.blogspot.com/-LM5prrwPEvg/WBmcbfcrIVI/AAAAAAAAAxw/m9ttsbB8pwUAtmpzIZYcov28OPIUY8Z8gCLcB/s640/screenshot_85-min.png Activate HTTPS on Blogger third party Domain 100 Worked | WMI - https://1.bp.blogspot.com/-phg046qimAs/WBmcbn8mIwI/AAAAAAAAAx0/8qM03atvP1AkLv2Ior9JpdgfH__vWTGxQCLcB/s640/screenshot_86-min.png
*
Be sure that these Page Rules are in the same order.

Now visit your blog. You’ll see that your blog is being
redirected to HTTP all the time whether is it a subdomain or the main
domain and keeping the directory (characters after the domain). Now,
what’s next? You should not forget that the links in your blog do
not have “HTTPS” in their starting and to let Google know
that you’ve moved to HTTPS and get your new URL indexed faster,
you should change all your blog links from HTTP to HTTPS. But, how?
It’s a hectic task! But we’ve made it simple.

<script>
  $(document).ready(function () {
    $("a").each(function () {
      var i = $(this).attr("href");
      var n = i.replace("http://www.yourdomain", " https://www.yourdomain");
      $(this).attr("href", function () {
        return n;
      });
    });
  });
</script>
<link href='https://www.yourdomain .com/favicon.ico' rel='icon' type='image/x-icon'/>
<meta content='blogger' name='generator'/>
<link href='https://www.yourdomain .com/feeds/posts/default' rel='alternate' title='Blogger Guider - Atom' type='application/atom+xml'/>
<link href='https://www.yourdomain .com/feeds/posts/default?alt=rss' rel='alternate' title='Blogger Guider - RSS' type='application/rss+xml'/>
<link href='https://www.blogger.com/feeds/ BLOGID/posts/default' rel='service.post' title='Blogger Guider - Atom' type='application/atom+xml'/>
<!--[if IE]><script type="text/javascript" src="https://www.blogger.com/static/v1/jsbin/2591933621-ieretrofit.js"></script>
<![endif]-->
<meta expr:content='data:blog.url' name='og:url:domain'/>
<!--[if IE]> <script> (function() { var html5 = ("abbr,article,aside,audio,canvas,datalist,details," + "figure,footer,header,hgroup,mark,menu,meter,nav,output," + "progress,section,time,video").split(','); for (var i = 0; i < html5.length; i++) { document.createElement(html5[i]); } try { document.execCommand('BackgroundImageCache', false, true); } catch(e) {} })(); </script> <![endif]-->

Remaining 20% is settings you’re going to do in Google Search
Console and Robot.txt.

User-agent: Mediapartners-Google
Disallow:
User-agent: *
Disallow: /search
Allow: /
Sitemap: https://www.webmanajemen.com/sitemap.xml

http://yourdomain.com
https://yourdomain.com
http://www.yourdomain.com
https://www.yourdomain.com

Don’t want to do this all and make your hands dirty?

Hm…so this was a long and techy process. Why you’re willing
to do all this when a professional can do this for you? I’ve
collected people who will do this work for you at a very reasonable
cost. Plus, if you want any kind of information about SSL or about any
other things, you’re welcome to our try our service. You can
contact me here and get your work done within some minutes.

Cons Of This Early Adaption

There are some disadvantages (plus, the solution of them) of using this
method to move your blog from HTTP to https. These are giving below
followed by their solutions:

Simple way -> Short way if you wrong in any steps. Following this my simple guides:

1. Login cloudflare -> https://cloudflare/a/login (register if you not have cloudflare accounts). -> HeRe Tutorial For Registering Blogger Thirdty Domain to Cloudflare <-

2. Go to https://cloudflare.com/a/crypto/YOURDOMAIN.TLD -> Choose SSL FLEXIBLE

3. Go to https://cloudflare.com/a/firewall/YOURDOMAIN.TLD -> Set Security level to LOW

4. Go to https://cloudflare.com/a/page-rules/YOURDOMAIN.COM -> add third rules below ->

4.1. RULES OPTION (Source --> Rules --> Target)

4.1.1. http://*yourdomain.com/* --> ALWAYS USE HTTPS --> https://*yourdomain.com/*

4.1.2. http://yourdomain.com/\* --> 301 Permanent Redirect --> https://yourdomain.com/$1

4.1.3. https://yourdomain.com/\* --> 301 Permanent Redirect --> https://yourdomain.com/$1

Fix Issues: 525 SSL HANDSHAKE FAILED on Cloudflare

1. Go to https://cloudflare.com/a/dns/YOURDOMAIN.COM -> See Failed/Wrong DNS Option here
Activate HTTPS on Blogger third party Domain 100 Worked | WMI - https://encrypted-tbn1.gstatic.com/images?q=tbn:ANd9GcQHq-sYEQ0GH-IRiuBxBqF01Wn2u4DCZUjX2acdHc8SpJhflvL9f2DlbtNb0A Change to valid cloudflare dns with the following tutorial below:
Double click icon below or open the settings dns one by one and doubleclick the icon : Activate HTTPS on Blogger third party Domain 100 Worked | WMI - https://lh4.googleusercontent.com/proxy/kqV9uHVHYtVeKvHgVvJscuzK42lc35c4Xm3izZuT0BB0UZ1615EueZnaC3WM5UAeyfzDrDkLgD30wExn02_lMuUJgzYYKula-_cWK3TDtcafKNGk=w478-h308-nc it will be change the icon to YELLOW CLOUD FORWARD. Like this: Activate HTTPS on Blogger third party Domain 100 Worked | WMI - https://encrypted-tbn3.gstatic.com/images?q=tbn:ANd9GcTHCAy08DKiNzySz0D2QZhBip4whPJJbwvTsWD03-9cMtItTz7PbUjSu6fb  CHANGE all your dns or spesific dns LIKE ABOVE IMAGE (Yellow icon). Save.
Done.
Reload Your website.

Final Words

I trust you’ve preferred this guide and gladly, I can state that we’re the first on the web to uncover this trap which works like for hell’s sake. On the off chance that you have any issue, make certain to get in touch with us. Share this blog entry to tell more individuals about this phenomenal guide, much appreciated!