Activate HTTPS on Blogger third party Domain 100% Worked

 2017-05-25 /  Unknown

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

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!

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

(document).ready(function() {
$(“a”).each(function() {
var i =

(this).attr("href");<br>var n = i.replace( http://www.<strong>yourdomain</strong> , " https://www.<strong>yourdomain</strong>");&nbsp;

(this).attr(“href”, function() {
return n
})
})
});
</script>

Now here comes the coding part. Search for the following code
in your template:
<b:include data=‘blog’ name=‘all-head-content’/>
Remove it and below “<head>” paste the
following codes:

<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]–>

Now, see for any unsecured (without HTTPS) link in your
template and replace them with secured ones if you have found
or alternatively, upload them to your own host.
Last thing and the most tedious task- if your images are not
SSL certified or are not hosted on SSL compatible or secured
host, then please upload them to any free hosting services like
postimg.org that are SSL enabled and replace those images with
SSL certified images. Once you are done- congrats, you’re
80% done!

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

Go to Blogger > Settings > Search preferences >
Crawlers and indexing > Custom robot.txt
Edit it and use the following code instead of the one
you’re using currently to make it SSL Compatible:

User-agent: Mediapartners-Google
Disallow:
User-agent: *
Disallow: /search
Allow: /
Sitemap: https://www.web-development.cf/sitemap.xml

Now save it and head over Google Search Console.
Add your domain in all the following four ways:

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

Now after adding the first three and while adding the fourth
one, submit your sitemap. Please note that you are not required
to submit sitemap from every domain I’ve listed above.
Just while adding the last one (https://www.yourdomain.com) submit the sitemap.XML file.
Now you’re ready, and your blog is fully SSL compatible.
😃

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:

After moving, you’ll not be able to forward any of your
subdomains to any URL –SOLUTION – Suppose you want to redirect fb.yourdomain.com
to facebook.com/yourdomain, then, navigate to CloudFlare DNS
manager and their, add a CNAME with “Name”
subdomain (for fb.yourdomain.com, it will be “FB”)
and with “Value” ghs.google.com. Then, link it to a
blogger blog and redirect that blogger blog to any
blog/website. For example, see contact.bloggerguider.com.
We’ve used this simple trick to redirect
contact.bloggerguider.com to support.bloggerguider.com.

SOLUTION 2 – Use “Page Rules” to forward but
they’re too limited in numbers.
You’ll not be able to move back, and when you try to,
you’ll lose traffic. No solution, this will happen with
any domain.

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

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

it will be change the icon to YELLOW CLOUD FORWARD. Like this: Activate HTTPS on Blogger third party Domain 100% Worked

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!

Activate HTTPS on Blogger third party Domain 100% Worked
PermaLink: https://www.webmanajemen.com/2017/05/activate-https-on-blogger-third-party.html
Google Rich Snippets | Schema Markup Validator | Google Pagespeed Insight