For those not yet familiar with the new "Responsive" class themes, I offer my demo 4 "Responsive" blogs - one blog per exciting theme.
You can see the links to the 4 demo blogs, at the top of the sidebar.
You have to make an effort, to find the sidebar, however. The effort is necessary, to help the "Responsive" class templates replace the "Layout" / "Designer" class templates - and their special "Mobile" template.
See the linklist "Responsive Templates Tests", in the pop out sidebar?
Whether you are viewing this blog as The Real Blogger Status, or as Now, Ya See It - Now, Ya Don't, or even as Custom Domain Redirection, And "A" Referral Servers, you probably are not looking at the sidebar.
If you do want to see the sidebar, just click on the "hamburger" icon, in the upper right corner of the screen.
Click on the "hamburger" icon, to open the sidebar.
The "hamburger" icon is in the upper right corner.
The sidebar, normally hidden, to let the post content be more readable on a tiny "phone" display.
The "pop out" sidebar is one majorly innovative design feature, that helps the "Responsive" class templates replace the "Layout" / "Designer" class templates, and their special "Mobile" template.
The pop out sidebar is only visible, when you want to access sidebar content - by clicking on the "hamburger" icon.
Now, you see it.
Now, you don't.
Click on the tiny "right arrow" icon, to hide the sidebar, when the sidebar is open.
So yeah, if finding the sidebar is now an effort for your readers, I sympathise. But the hidden sidebar has a practical origin - it's not purely cosmetic.
If you recently upgraded your #Blogger blog to use an exciting new "Responsive" theme, and you can't find the sidebar, with its wonderful complement of gadgets, that's because the sidebar is now hidden.
Just click on the "hamburger" icon, and all will be seen.
After years of waiting, this blog is now readable, using HTTPS.
This blog, and others published using properly setup custom domains, now provides optional HTTPS connectivity - joining BlogSpot published blogs.
I looked at the Settings - Basic page of my Blogger dashboard, a couple hours ago.
Previously, I might see the HTTPS options "Availability" and "Redirect" when accessing my Draft Blogger dashboard. Now, both are there, in Production Blogger.
If you publish a blog, using a custom domain URL, you should see the new option too. It took 5 minutes, with my blog, to activate "HTTPS Availability".
RBS is now secure!
A couple hours ago, "HTTPS Availability" was offered, on my Blogger dashboard.
There are two options - HTTPS Availability, and HTTPS Redirect.
- HTTPS Availability lets your readers access your blog, using HTTP or HTTPS, as they choose. HTTPS Availability is now an option, for all blogs.
- HTTPS Redirect automatically requires all readers use HTTPS, to access your blog. HTTPS Redirect is an option, with HTTPS Availability enabled.
HTTPS Availability is now an option!
"HTTPS Availability" lets your readers, who use only HTTPS, connect to your blog. It's the first step in upgrading the web.
So, it's selected - and now we wait.
When you enable "HTTPS Availability" for a custom domain published blog, Google will setup an SSL certificate for the domain - free of charge. Just enable the option, and wait a few seconds - and your domain will be secure, with certificate.
Less than 5 minutes later, and I see the display updated.
"HTTPS Redirect" is now available, for this blog. "HTTPS Redirect" automatically requires all of your readers to use HTTPS, when reading your blog. It's the second step in upgrading the web.
So "HTTPS Availability" is now a reality. Common sense - and Blogger advice - tells me to take things slowly. I'll still allow HTTP connectivity, for readers who can't use HTTPS.
I next need to setup Search Console entries for this blog, using HTTPS.
For best results, the domain needs to be properly setup. Both the BlogSpot to domain redirection, and the domain root ("naked domain") to published URL redirection, can be complicated, with HTTPS offered for an improperly setup domain.
Also, remove any other custom installed redirecting code. Both code blocking local country redirection, and code blocking (or enabling) HTTPS redirection, will interfere with the HTTPS Redirect option.
And check your non Blogger accessories and features carefully. Blogger is not the last Internet service to provide this upgrade - and your blog will provide the best experience, for your readers, if all accessories and features also support HTTPS.
Test the blog and domain, in the many URLs.
With the blog published to the domain, and offering HTTPS connectivity, you'll have 6 URLs - all pointing to the blog. Make sure that all 6 work properly.
Right now, my test blog does provide HTTPS connectivity / redirect - though this blog does not, since I don't want broken links to third party services. Using my test blog, I have 6 URLs to check. Note that this blog is published as "blogging.nitecruzr.net" - not "techdict.nitecruzr.net", or "www.nitecruzr.net".
- http://myspaceandmore.blogspot.com
- http://nitecruzr.net
- http://techdict.nitecruzr.net
- https://myspaceandmore.blogspot.com
- https://nitecruzr.net
- https://techdict.nitecruzr.net
Your readers will be happiest, if all 6 URLs work - and all redirect to your blog. Again, your domain will probably use "www", in place of "blogging" or "techdict", in #3 and #6.
Be prepared to re publish the blog, for best results.
If you were using "HTTPS Redirect" for the BlogSpot URL, #2 and / or #5 many be "404". You may need to re publish the blog, and remove the BlogSpot "HTTP" to "HTTPS" redirect. The domain root redirect, and "HTTPS Redirect" for the domain, may conflict.
Activate "HTTPS Redirect" for the domain, with the BlogSpot URL having "HTTPS Redirect" enabled - and you may see this.
You will have 3 redirects, with HTTPS Redirect added.
- The BlogSpot to domain redirect.
- The domain root to published URL redirect.
- The "HTTP" to "HTTPS" redirect.
All 3 redirects need to be addd in proper sequence - if you want the BlogSpot URLs, the domain root, and the published domain URL to all redirect to the blog.
With both the BlogSpot redirect, the domain root redirect, and the HTTPS redirect enabled, you may see an error when addressing the domain root. In that case, you'll have to re publish the blog to the domain.
- Login to production Blogger ("www.blogger.com").
- Publish the blog back to BlogSpot, by clicking on the "X".
- Disable “HTTPS”, if necessary.
- Re publish the blog to the "www" domain host.
- Select the domain root redirect.
Be careful when editing the pages / posts / template.
One of the reasons why HTTPS took so long to be available with Blogger - and contrarily, why the entire web did not upgrade over night - is that other blogs and websites have not yet upgraded.
If your blog is to provide useful HTTPS connectivity, any accessories and features, that you depend on, must also offer HTTPS connectivity. If a non HTTPS link is present, your readers will see scary advice about "mixed content", and "unsafe" web pages.
Blogger provides "mixed content" warnings, in page / post / template editor, when appropriate - but read their warning very very carefully. Before you change a link from HTTP to HTTPS, you have to verify that the accessory linked will provide HTTPS connectivity.
The "Fix" option in the page / post / template editor "mixed content" warning will break accessories that don't yet provide HTTPS connectivity. Don't change links from HTTP to HTTPS, without verifying that they will support the change.
Understand the details, to ensure an effective migration.
If you can deal with the details, you'll have a secure domain - and you can now offer your readers SSL connectivity, to your custom domain published blog, using all 6 links above.
HTTPS Availability is now an option for all #Blogger blogs. I'll continue to offer HTTP, for readers who can't use HTTPS - but those who require HTTPS can now use it, to access this blog - and other custom domain published blogs.
Making a blog searchable is the first step in getting search traffic, and readers, for our blogs - when we want them visible to the public.
Not all blog owners want their blogs visible to everybody. Complementing the ability to publish a blog, and have it visible only to invited readers, Blogger gives us the ability to make the blog invisible, to the search engines.
If we want readers for a blog, and do not have a private reader audience in mind, we first make it visible to the search engines.
The Privacy wizard, on the Blogger dashboard, lets us choose whether to make a blog visible to the search engines.
Start with the dashboard Settings - Basic page, and Edit the Privacy setting.
Select "Yes" for both options - if you want the blog indexed.
Select "Yes" for both options, if you want the blog indexed. This is how you start getting search traffic, and readers, for your blog.
- Add your blog to our listings?
- Let search engines find your blog?
And click "Save changes".
Having made the blog visible to the search engines, continue by publishing lots of informative, interesting, and unique content. Make it a blog that people will read - and that search engines will index.
If you prefer the blog to be invisible or private, on the other hand, select "No" for both options. Then continue by developing your private audience, as you like.
There are more settings - for owners who want to fine tune search engine access. Both the Blogger dashboard Settings - "Search preferences" page, and the "Google Search console" (previously known as "Webmaster Tools"), have a rich collection of settings, complementing "Privacy".
If you really want to fine tune these settings, look at the Settings - "Search preferences" page, and the "Crawlers and indexing" section - but read and heed the serious advice.
Warning! Use with caution. Incorrect use of these features can result in your blog being ignored by search engines.
You can read more advice in Blogger: Help people find your blog on search engines - and Webmasters: Search Engine Optimization (SEO) Starter Guide. And you'll find Webmaster Central: Crawling, Indexing, and Ranking and Webmaster Central: Search Console useful for personal advice, complementing Blogger Help Forum.
Since Webmaster Forums supports owners of static websites, as well as owners of Blogger blogs (and other blogs), not all Search Console / Webmaster advice and tools will be useful for Blogger blogs. Be selective when considering Webmaster instructions - and ask questions in Blogger Help Forum, any time you feel the need.
The "Privacy" wizard is where you start - and similarly where some blog owners should stop.
The Blogger "Privacy" wizard, on the "Basic" Settings page, provides the start to getting a blog indexed by the search engines - when we want a blog indexed. Not all blog owners want their blog indexed - and that need makes the "Privacy" settings relevant.
Several months ago, I took a leap into the future, and upgraded this blog to use a "Responsive" class template.
There are four "Responsive" templates - Contempo, Soho, Emporio, and Notable. The differences between the four include more than merely the visible design.
My serious opinion about template choice is that two people, each starting a blog about the same subject, and using the same source of content, will still have different perspectives - and each will probably choose a different template.
Anybody who asks me, bluntly
Which template is a better choice, for my blog?
Gets my facetious reply
Whatever template encourages you to write more original and quality content, in your blog, is best for your blog.
It's your blog. Your blog is valuable, because of the content.
Our clean, exciting new look.
Our boring previous look.
If you want more advice, I'll offer you my four "Responsive" class test templates - Contempo Test, Soho Test, Emporio Test, and Notable Test. You can examine this post, and compare the visible differences, on each of the four.
The navbar is gone.
Where's the navbar?
It's possible that the navbar contains details that are not compatible with hosting on the Google CDN. Is this why Blogger started providing a "Report this blog". gadget?
The sidebar is now hidden - unless you need to see it.
See the linklist "Responsive Templates Tests", in the pop out sidebar? You need to click on the "hamburger" icon, in the upper right corner of the screen, to see the sidebar.
The "pop out" sidebar is one majorly innovative design feature, that helps the "Responsive" class templates replace the "Layout" / "Designer" class templates, and their special "Mobile" template.
The pop out sidebar is only visible, when you want to access sidebar content, by clicking on the "hamburger" icon.
There are more, undocumented improvements, too.
Besides the "Mobile" template that is now redundant, there are significant differences between the four "Responsive" templates, that may encourage choice of one or the other. As I continue to upgrade the older posts in this blog, to look better using "Notable", I'll start discussing the advantages and disadvantages of each.
If this interests you, move your blog forward, by choosing an exciting "Responsive" class template, from the dashboard "Theme" page.
Pick one of the new and exciting "Responsive" class templates - Contempo, Soho, Emporio, Notable.
You can setup your own demo / test set, easily enough.
If necessary, setup your own test blog set, with your own test posts - and compare your content on the different templates, to see what your blog will look like. Or, you can use my sidebar menu "Responsive Templates Test" - and look at my four test blogs.
My personal choice of the "Notable" Responsive template, was not immediate - it took several days, and some experimentation using various tests - and my 4 test blogs. You can take your time - and change your template, as you feel the need.
The Real Blogger Status has moved into the future - and is now using a new #Blogger supplied "Responsive" class template. It's going to take some work, to make the blog truly look good under "Notable" - but progress always has a price.
One of the simplest ways to make a blog useful is to add label searches.
Adding label searches, in page / post text, is not easy - unless you know how to build the URLs. Here's a label search from this blog.
http://blogging.nitecruzr.net/search/label/Blogger%20Magic
All that I want, when using that label search, is to add another reference to my "Blogger Magic" post series.
"Blogger Magic" emphasises how easy it is, to use Blogger. How easy is it, to remember that syntax - to add a label link? Maybe, a "Blogger Magic" reference, in this post?
When you read a blog post, that has label references, look at the bottom of the post.
Please note the advice, at the bottom of the post.
Look in the post footer, for the "Labels" section.
Here's the bottom of another post, from this blog.
Here's the bottom of this post.
Note that not all blogs will provide a "Labels" posts section. That is an owner choice.
Look at a label link, in the "Labels" section of the post - when provided.
There's the bottom of two of my "Label Search" posts - "Blogger Magic - A Blog Within A Blog", followed by this post "Blogger Magic - Adding Label Search URLs". Now, look at the Labels links.
In most blogs, the Labels links would be labeled "Labels". I call mine "Topics". As owner of this blog, that is my personal choice.
Also, in most blogs, the "Labels" section will be found, in the post footer. Some blog owners have chosen to position their "Labels" in the post header. This, too, is their choice - and carries with it, some risk.
See "Label Search"?
Look in the browser status area, when hovering over the link caption.
Look at the "Topics" section. See "Label Search"? Hover the mouse cursor, over the "Label Search" link.
See the label search URL, in the browser status area?
Look in the browser status area, when hovering over the link caption.
Hover the mouse over "Label Search", and look in the browser status area.
blogging.nitecruzr.net/search/label/Label Search
For a blog using an HTTPS redirect, you might see a slightly different URL.
If this blog uses the "HTTPS: Redirect" option, you might see it slightly differently.
https://blogging.nitecruzr.net/search/label/Label%20Search
Click on either of the above 2 links. OK, I cheated with the second link - since this blog, right now, does not support HTTPS - and I obviously don't want you looking at an HTTPS Error display.
Whether HTTP - or HTTPS - is in use, there is the label search link.
Whichever you see - and decide to use - with your blog, there is a label search URL. Now, get a label search URL from your blog - and use the URL, in another page or post in your blog.
This post opens many links in new tabs / windows, intentionally.
BTW - and if you have clicked on any of the links above - and since you have apparently read to this point - I have to warn you that many of the links, above, are intentionally coded to open in a new tab / window. That is necessary, based on the nature of the links in this post.
Many of the links in this post are clickable, simply to illustrate to you the content in label searches - as opposed to links which lead you to additional information in the blog. So as not to lead you away from this post, you should not lose context after clicking on a link - as long as you simply close the new (illustrative) tab / window.
My sincere apologies, if my seemingly gratuitous opening of new tabs / windows inconveniences or offends you.
Some #Blogger blog owners want to use label search URLs, in page or post text. Getting a label search URL is easy enough, when you look in the post label search section - which is generally in the post footer.
SSL has been an option, for BlogSpot published blogs, since late last year - and we still see occasional questions, in Blogger Help Forum: Get Help with an Issue, about its use.
When I saved my post, I saw the error messageThis page contains HTTP resources which may cause mixed content affecting security and user experience if blog is viewed over HTTPS.
I clicked "Fix" - and the error message went away. Should I have to go back and "fix" all my old blog posts, this way?
This blog owner will be better off, with "HTTPS Redirect" disabled.
Until HTTPS availability, for all Internet content and services, becomes a consistent reality, there will be problems with Blogger blogs - and confusion, as in the example.
Custom domain publishing is the most vulnerable Blogger feature, with blogs using "HTTPS Redirect". It's not the only possible complication, though.
Some blog owners will be better off, not enabling "HTTPS Redirect" - or if enabled, they will need to disable it.
HTTPS Redirect can be easily disabled.
"HTTPS Redirect" is not difficult, to disable. Go to the dashboard Settings - Basic page.
Click on "Yes".
Select "No".
And, the option is disabled.
And the owner won't see the confusing "Fix" / "Dismiss" options.
Now, you can publish the blog, to a custom domain. With "HTTPS Availability" not optional, blogs, with essential features that don't provide SSL, will still have unsatisfied readers who will demand HTTPS.
Some blogs would be better off with "HTTPS Availability" as an option.
You cannot eliminate all confusion, until SSL is uniformly available.
I will note, however, that disabling the redirection will not eliminate reader concern, from "Mixed Content" alerts - nor will it prevent owner confusion, from Post Editor warnings. As long as SSL is (may be) involved - automatic redirect or not - and until every Internet feature and service uses SSL consistently - there is going to be some confusion.
Some #Blogger blog owners will need to disable the "HTTPS Redirect" option, to publish their blogs as they need. Right now, "HTTPS Redirect" is an option - and "HTTPS Availability" needs to be an option also.
With Blogger now providing (optional) HTTPS, on all blogs, we're seeing a few anxious reports in Blogger Help Forum: Get Help with an Issue.
I'm getting an error, on one of my plugins.This content is not yet available over encrypted connections.
What can I do?
The answer won't be encouraging.
Don't enable "HTTPS Redirect", on your blog.
Not enabling "HTTPS Redirect" won't mean that every plugin or service will work - if your readers choose to use SSL, to access your blog, unfortunately.
One of the reasons why it is taking Blogger so long to get SSL working, is that they have to allow for our blogs, using non Blogger code.
Too many Blogger blogs use non Blogger code that does not support SSL.
One of the reasons, why all websites don't have HTTPS yet, is they have to wait for other websites to provide it.
Rex Swain does not plan to upgrade - ever.
It's similar to the game of Pickup Sticks. You can't (shouldn't) upgrade your blog, until your accessories and plugins support SSL.
I use the Rex Swain HTTP (yes "HTTP:"!) trace, for diagnostics, frequently. HTTPS is not a zero cost upgrade!
Note re HTTPS: I often get requests to provide support for HTTPS. But I'm afraid I have no financial incentive to enhance the viewer. Despite thousands of hits a day, virtually nobody clicks on ads. So, I have this request on my to-do list, but frankly I doubt I'll ever get to it.
Somebody else may depend upon content from your blog - and his website can't be upgraded, because his website displays a Mixed Content alert ("Not secure"), because of his link to your blog. And a third website must wait, for him to upgrade his website.
Your blog may use a plugin that does not provide SSL access.
For plugins that don't support SSL, you may have to choose between having a broken plugin - or dropping use of those services, until they, too, can upgrade. Or don't force HTTPS.
Don't enable the "HTTPS Redirect" option, if you use plugins in your blog, that don't support SSL.
Be patient - and work on blog content.
Be patient. Encourage the websites, that you depend upon, to enable SSL on their service - then you can do the same, with your blog. And keep publishing your blog.
Encourage Blogger to restore the "HTTPS Availability" option. Make SSL access optional, for each blog - not forced SSL optional.
With #Blogger having enabled HTTPS on all BlogSpot published blogs, blog owners are seeing problems caused by non Google websites that don't offer SSL yet. The "HTTPS Redirect" option really should be "HTTPS Availability", again.
https://productforums.google.com/forum/#!category-topic/blogger/2HV3zzclGCg
https://productforums.google.com/forum/#!category-topic/blogger/9rp4vZhBAhQ
https://productforums.google.com/forum/#!category-topic/blogger/p3DlfKBszTM
https://productforums.google.com/forum/#!category-topic/blogger/QMFbAsOvvdc
Some blog owners decide to include music, to accessorise their blogs - and the first thing they ask for is instructions.
Please give me step by step instructions, to add music.
They don't consider that adding music, for any blog, will be their personal choice - and a music player will be personal too.
The choice of music player needs to be based on the music library provided.
You will probably want your music choice to match the blog content.
Some one who wants to provide classical music won't want to add a music player, published by a disco / techno website. Similarly, if you want to decorate your blog with country music, you will not be pleased by a player provided with a jazz website.
Each music website will provide their own player, to accompany their music library - and their own installation instructions, to install their player. You will probably be provided HTML / JavaScript code, by the website - so you will want to add an HTML / JavaScript gadget.
Position the player so it is convenient and visible, to your readers.
You will want the player controls to be visible - so you should position the new gadget, in a convenient and visible location, on the blog.
The one suggestion, that is consistently provided, is that you should choose a player that lets your readers choose whether to listen to the music. Please, don't use any player that only provides "autoplay".
The choice of music will be yours - and some readers will choose to view your blog. But some will choose to not listen to your music - and unless you want to limit reader population to those who can listen as they view, you will want to make the music optional.
Some #Blogger blog owners want to decorate their blogs with music - and they request detailed instructions for adding a music player. Music players are individual to the website providing the music - and the smart blog owner will choose the website, for one offering an appropriate music library.
One question, that I have never seen specifically asked, is about our following, reading lists, and blog subscriptions in general.Why do I have to login to Blogger, to maintain my Reading List?
The blog follower / owner has asked a question that is involved in various problems, in Blogger Help Forum: Get Help with an Issue - but with this question so easily overlooked.
The Blogger dashboard Reading List, which so many use transparently, is unique to each of us.
Similar to the confusion about the email address, mysteriously displayed on our Blogger dashboard, is the unstated detail that each of us has our own personal set of followed blogs - and consequently, our own Reading List.
If you want to maintain the (Blogger Following / Google Friend Connect) Followers community, on your blog, you are forced to do this, as part of the Followers GUI. When you are able to access the Reading List "gear" icon, and "Manage Blogs I'm Following", you have already logged in - possibly, without realising.
Sometimes, blog owners have learned of various dashboard shortcuts - and use them transparently. All blog dashboard access requires a login - to simply prove, to Blogger, that you are the owner of the blog in question.
Most blog owners understand, instinctively, that they must login to access each blog dashboard. Not everybody realises, however, that they have their individual Reading List - also accessed by their own login, on the dashboard "home" page.
Along with having your own Reading List, you have your own reading list maintenance wizard (aka "Manage Blogs I'm Following" - or possibly the Google Friend Connect equivalent, for Blogger accounts that use Google+ profiles). To access your own wizard, you must identify yourself, by logging in to Blogger.
Failure to use the right Blogger account, or using a computer that prevents proper identification, leads to an empty Reading List - or to a list with just one entry. This is one reason for some people claiming that the Reading List is unreliable.
