After many years of waiting, people who publish blogs using custom domains can provide HTTPS connectivity, to their readers.
Right now, HTTPS Availability / Redirect can be enabled, for custom domain published blogs, using Draft Blogger.
Since Draft Blogger is used by Blogger for beta testing new features and problem fixes, you will do best using it selectively.
Use Draft Blogger only to enable HTTPS Availability / Redirect.
In this case, you use draft Blogger only for enabling HTTPS for your custom domain URL. This is a good time to use a second browser - either a different browser on this computer, any preferred browser on another computer, or this browser with an Incognito / Private window.
Start by logging into Draft Blogger - using a second browser.
The Settings - Basic dashboard page, in Draft Blogger, now has a new option.
Select "Yes" for "HTTPS Availabiity" - and wait while the domain is setup with SSL.
With "HTTPS Availability" enabled, Blogger has to obtain an SSL Certificate for your domain. This is not a casual formality. With many domain registrations, you might pay extra for a certificate.
Once "HTTPS Availability" is activated, you'll have the "HTTPS Redirect" option.
Allow half an hour after enabling "HTTPS Availability", then refresh the display. You should have "HTTPS Redirect" available - and if you wish, you can enable it.
Success!
Blogger is not the last Internet service to provide "HTTPS" connectivity.
If you enable "HTTPS Availability", and later "HTTPS Redirect", you'll probably have accessories and services that don't support HTTPS.
Be selective when you use Page / Post / Template Editor, and see suggestions to "Fix" all links that continue to reference "HTTP" connectivity. If you routinely select "Fix" you will end up with broken links, for accessories and services that have not been upgraded.
If you can deal with the details though, you'll have a secure domain - and you can now offer your readers SSL connectivity, to your custom domain published blog.
If your #Blogger custom domain is setup properly, you can now offer HTTPS connectivity for your custom domain published blog.
You should consider the redirects, and the different URLs involved, carefully.
https://productforums.google.com/d/topic/blogger/RtzWu4CglrY/discussion
https://productforums.google.com/d/msg/blogger/B5tBKvv1FoE/n2Zv61G6CAAJ
Showing posts with label Settings - Basic. Show all posts
Showing posts with label Settings - Basic. Show all posts
Saturday, March 10, 2018
Wednesday, June 22, 2016
Blogger Magic - Disable The HTTPS Redirect
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.
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.
When I saved my post, I saw the error messageThis blog owner will be better off, with "HTTPS Redirect" disabled.This 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?
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.
Saturday, June 11, 2016
Recovering From A Corrupt Template - The Next Step
There are three possible dashboard wizards, used to recover a blog with a corrupt template aka "500 Internal Server Error".
Some blogs, unfortunately, cannot be recovered this way.
Some blogs have templates so badly broken, that no dashboard template wizard can be accessed - and used to restore the blog to operational status.
If there's no way to recover a broken blog by replacing the template, the next possibility is to recover the URL - and install a new blog at that URL.
Create a new blog - with a clean, working template.
Use the dashboard "New Blog" button, and create a new blog. You'll only create the new blog, in this case, to recover the URL of the broken blog - so just use a random, non valued URL.
Choose a template similar to the one on the broken blog, from the dashboard Template page - and get your new blog online. Use a Blogger standard template, until you are satisfied that the problem won't continue.
Swap URLs between the old and new blogs.
Hoping that you can access the Settings - Basic ("basicsettings") page - first rename the URL Of the broken blog, to a second random, non valued URL. Then you can rename your new blog - created above - to the URL previously used by the broken blog.

Just Edit "Blog Address", twice, to swap URLs.
First, for the broken blog, to free up the current URL - then, for the new blog, to recover the current URL.
Now, your broken URL is back online, with a clean template - though without content.
Export content from the broken blog - and Import to the new blog.
Use the "Import & back up" wizard at the Settings - Basic ("othersettings") page for the broken blog, and export comments, pages, and posts. Then use the wizard for the new blog, and import the content just exported.
Transfer / update Followers.
If the broken blog uses Blogger Followers for community building, and you had a significant Followers community, the community will remain on the old, broken blog. This is the one down side of recovering a broken template using this technique.
Fortunately, the only specific problem is the effect upon the Followers community. The other half of Following - the blog feed - will be re established with the new blog, which will now have the desired URL being recovered. And the sooner you get the blog back online, the sooner you can rebuild / recover your Followers.
Rebuild the template, and add gadgets.
If you periodically back up the template, as you tweak it, this will be the easiest step in the recovery. Of course, since you are here because the template is broken, maybe you should rebuild the template, one step at a time. Try to not repeat the previous mistake.
Then add gadgets back, one at a time - and test carefully.
Provide notice to your Followers, readers, and viewers.
If you care about your community - Followers, readers, subscribers, and other viewers - a new post, briefly admitting to your mistake might be a good idea. You can even display your new post, as a Featured Post.
Sometimes, it's not possible to recover a broken #Blogger blog, using any of the Template dashboard pages, with a blog sidelined by a "500 Internal Server Error" broken template. If the URL has any value to you - or your viewers - you can recover it, using a new blog.
target="_blank"
- The Template Designer page.
- The Template page.
- The Template Editor ("Edit HTML") page.
Some blogs, unfortunately, cannot be recovered this way.
Some blogs have templates so badly broken, that no dashboard template wizard can be accessed - and used to restore the blog to operational status.
If there's no way to recover a broken blog by replacing the template, the next possibility is to recover the URL - and install a new blog at that URL.
- Create a new blog - with a clean, working, Blogger supplied template.
- Swap URLs between the old and new blogs.
- Export content from the broken blog - and Import to the new blog.
- Transfer / update Followers.
- Rebuild the template, and add gadgets.
- Provide notice to your Followers, readers, subscribers, and other viewers.
Create a new blog - with a clean, working template.
Use the dashboard "New Blog" button, and create a new blog. You'll only create the new blog, in this case, to recover the URL of the broken blog - so just use a random, non valued URL.
Choose a template similar to the one on the broken blog, from the dashboard Template page - and get your new blog online. Use a Blogger standard template, until you are satisfied that the problem won't continue.
Swap URLs between the old and new blogs.
Hoping that you can access the Settings - Basic ("basicsettings") page - first rename the URL Of the broken blog, to a second random, non valued URL. Then you can rename your new blog - created above - to the URL previously used by the broken blog.

Just Edit "Blog Address", twice, to swap URLs.
First, for the broken blog, to free up the current URL - then, for the new blog, to recover the current URL.
Now, your broken URL is back online, with a clean template - though without content.
Export content from the broken blog - and Import to the new blog.
Use the "Import & back up" wizard at the Settings - Basic ("othersettings") page for the broken blog, and export comments, pages, and posts. Then use the wizard for the new blog, and import the content just exported.
Transfer / update Followers.
If the broken blog uses Blogger Followers for community building, and you had a significant Followers community, the community will remain on the old, broken blog. This is the one down side of recovering a broken template using this technique.
Fortunately, the only specific problem is the effect upon the Followers community. The other half of Following - the blog feed - will be re established with the new blog, which will now have the desired URL being recovered. And the sooner you get the blog back online, the sooner you can rebuild / recover your Followers.
Rebuild the template, and add gadgets.
If you periodically back up the template, as you tweak it, this will be the easiest step in the recovery. Of course, since you are here because the template is broken, maybe you should rebuild the template, one step at a time. Try to not repeat the previous mistake.
Then add gadgets back, one at a time - and test carefully.
Provide notice to your Followers, readers, and viewers.
If you care about your community - Followers, readers, subscribers, and other viewers - a new post, briefly admitting to your mistake might be a good idea. You can even display your new post, as a Featured Post.
Sometimes, it's not possible to recover a broken #Blogger blog, using any of the Template dashboard pages, with a blog sidelined by a "500 Internal Server Error" broken template. If the URL has any value to you - or your viewers - you can recover it, using a new blog.
target="_blank"
Friday, May 6, 2016
Verify BlogSpot And Domain URLs
Whenever dealing with any problem with a blog, you should verify the URLs involved.
Some of the most baffling problems, with blog connectivity, identity, or ownership, can start from simple typographical errors. This possibility will involve both native "blogspot.com" and custom domain URLs.
The Publishing wizard window, in the Blogger dashboard Settings - Basic page, is essential for identifying errors. Whether you paste or type a URL into the registrar's zone editor, the Publishing wizard, or the browser address window, you can make a mistake. Checking the Publishing wizard is as important as examining a Dig log extract - or as viewing an HTTP trace.
Verifying the URLs involved, in the dashboard Publishing wizard, is as important as examining a Dig log extract, or an HTTP trace.
This will be the case, when dealing with various "blogspot.com" connectivity problems, researching a custom domain problem, or a dashboard or ownership problem.
Both screen prints, and text copies, are very useful - and not redundant.
Both a screen print, and a text copy, of the Publishing window (and / or the browser address window) is very useful, when diagnosing connectivity problems - or possibly, researching ownership issues, or similarly vanished blogs. And with a custom domain, similar detail from the registrar zone editor is useful.
A text copy of the contents is needed, to avoid having to re type the URL - and maybe cause a different problem when comparing the URL. And a visual copy of the Publishing wizard is good, to identify the context of any problem.
Let's look at two blogs - and what we need to examine / verify.
My test blog, published as "nitecruzr-test-ssl.blogspot.com".
Here, we see a "blogspot.com" URL, in the browser address window.
Here, we see the Blogger dashboard Settings - Basic page, for a "blogspot.com" published blog.
The Publishing display, for a "blogspot.com" published blog.
Useful text details, from Publishing, for a "blogspot.com" published blog:
If you are requesting assistance with your native Blogger blog, the latter details, in both a screen print and text copy, will be useful.
My blog, published as "blogging.nitecruzr.net".
Here, we see a custom domain URL, in the browser address window.
Here, we see the Blogger dashboard Settings - Basic page. for a custom domain published blog.
The Publishing display, for a custom domain published blog.
Useful text details, for a custom domain published blog:
With a custom domain published blog, next click on "Edit", and make a second screen print.
The second page of the Publishing display - which only applies to a custom domain published blog.
You maybe have seen this display, similarly formatted, in an infamous "Error 12" or similar display.
The domain root redirection, properly selected.
More essential details, for a custom domain published blog:
If you are requesting assistance with your custom domain published Blogger blog, the latter details, in both a screen print and text copy, will be useful.
A zone editor display, for my domain "nitecruzr.co.uk".

A zone editor display, from GoDaddy. Every registrar will have a different display.
If you purchased the domain using a credit or debit account, the bank statement and / or charge advice will frequently have a description which details the purchase. In some cases, this will include the domain name.
Comparing the URLs in the browser window, and in the Publishing window - and in Dig logs and zone editor displays (for custom domains) - we can identify typographical errors, and other mistakes. Typographical errors can be a cause of various problems, when publishing blogs to custom domains - and to "blogspot.com".
Some problems result from failure to copy and paste, properly. They can be as challenging to diagnose, as failure to observe registrar name server syntax.
Having verified the URLs, in some cases, you will continue with an affinity diagnosis, and with a differential diagnosis. This is all part of my simple 12 link test set.
You, the blog owner, may consider "duplicate" and "redundant" to be synonyms. When we research a blog problem, "duplicate" != "redundant". Many confusing problems have been solved, by comparing combinations of various above details - and by finding inequality, in one or more displays.
Diagnosing problems with #Blogger blogs can require careful diagnostics, using details found in dashboard screen prints and detail text copies, in Dig logs, and in HTTP traces. All details must be carefully compared, both visually and using text extracts, to diagnose some problems.
Much of this may seem superficial, to experienced support analysts - yet be obscure to some blog owners.
Some of the most baffling problems, with blog connectivity, identity, or ownership, can start from simple typographical errors. This possibility will involve both native "blogspot.com" and custom domain URLs.
The Publishing wizard window, in the Blogger dashboard Settings - Basic page, is essential for identifying errors. Whether you paste or type a URL into the registrar's zone editor, the Publishing wizard, or the browser address window, you can make a mistake. Checking the Publishing wizard is as important as examining a Dig log extract - or as viewing an HTTP trace.
Verifying the URLs involved, in the dashboard Publishing wizard, is as important as examining a Dig log extract, or an HTTP trace.
This will be the case, when dealing with various "blogspot.com" connectivity problems, researching a custom domain problem, or a dashboard or ownership problem.
Both screen prints, and text copies, are very useful - and not redundant.
Both a screen print, and a text copy, of the Publishing window (and / or the browser address window) is very useful, when diagnosing connectivity problems - or possibly, researching ownership issues, or similarly vanished blogs. And with a custom domain, similar detail from the registrar zone editor is useful.
A text copy of the contents is needed, to avoid having to re type the URL - and maybe cause a different problem when comparing the URL. And a visual copy of the Publishing wizard is good, to identify the context of any problem.
Let's look at two blogs - and what we need to examine / verify.
My test blog, published as "nitecruzr-test-ssl.blogspot.com".
Here, we see a "blogspot.com" URL, in the browser address window.
http://nitecruzr-test-ssl.blogspot.com
Here, we see the Blogger dashboard Settings - Basic page, for a "blogspot.com" published blog.
The Publishing display, for a "blogspot.com" published blog.
Useful text details, from Publishing, for a "blogspot.com" published blog:
nitecruzr-test-ssl.blogspot.com EditIf you are requesting assistance with your native Blogger blog, the latter details, in both a screen print and text copy, will be useful.
My blog, published as "blogging.nitecruzr.net".
Here, we see a custom domain URL, in the browser address window.
http://blogging.nitecruzr.net
Here, we see the Blogger dashboard Settings - Basic page. for a custom domain published blog.
The Publishing display, for a custom domain published blog.
Useful text details, for a custom domain published blog:
blogging.nitecruzr.net Edit
bloggerstatusforreal.blogspot.com redirects
With a custom domain published blog, next click on "Edit", and make a second screen print.
The second page of the Publishing display - which only applies to a custom domain published blog.
You maybe have seen this display, similarly formatted, in an infamous "Error 12" or similar display.
The domain root redirection, properly selected.
More essential details, for a custom domain published blog:
Third party domain settings
http:// blogging.nitecruzr.net
X Redirect nitecruzr.net to blogging.nitecruzr.net.
If you are requesting assistance with your custom domain published Blogger blog, the latter details, in both a screen print and text copy, will be useful.
A zone editor display, for my domain "nitecruzr.co.uk".

A zone editor display, from GoDaddy. Every registrar will have a different display.
If you purchased the domain using a credit or debit account, the bank statement and / or charge advice will frequently have a description which details the purchase. In some cases, this will include the domain name.
Comparing the URLs in the browser window, and in the Publishing window - and in Dig logs and zone editor displays (for custom domains) - we can identify typographical errors, and other mistakes. Typographical errors can be a cause of various problems, when publishing blogs to custom domains - and to "blogspot.com".
Some problems result from failure to copy and paste, properly. They can be as challenging to diagnose, as failure to observe registrar name server syntax.
Having verified the URLs, in some cases, you will continue with an affinity diagnosis, and with a differential diagnosis. This is all part of my simple 12 link test set.
You, the blog owner, may consider "duplicate" and "redundant" to be synonyms. When we research a blog problem, "duplicate" != "redundant". Many confusing problems have been solved, by comparing combinations of various above details - and by finding inequality, in one or more displays.
Diagnosing problems with #Blogger blogs can require careful diagnostics, using details found in dashboard screen prints and detail text copies, in Dig logs, and in HTTP traces. All details must be carefully compared, both visually and using text extracts, to diagnose some problems.
Much of this may seem superficial, to experienced support analysts - yet be obscure to some blog owners.
Thursday, May 5, 2016
HTTPS Availability For All "blogspot.com" Blogs
The rollout of SSL, for "blogspot.com" published blogs, continues.
All "blogspot.com" published blogs will now offer HTTPS connectivity, to the reader. The choice, offered to the blog owner, is now whether to force every reader to use SSL - and the dashboard option is now labeled "HTTPS Redirect".
You can force your readers to use SSL, to access your blog - but will that make them more secure?
Every blog will offer SSL connectivity, to readers who use "HTTPS:" URLs.
The dashboard option is now "HTTPS Redirect".
The choice is now whether to force "HTTPS:" upon each reader - or allow some to continue to read, using "HTTP:".
If you select HTTPS Redirect, you will be limiting your reader population.
Some readers access our blogs, by using free proxy servers - and most proxy servers, when they offer HTTPS, offer it as a premium (with a paid subscription). You are entitled to require everybody to use SSL, if you wish - but you may see reader activity drop, as readers using free proxies find other blogs and websites to read.
Everybody will see the "HTTPS:" alias - with "HTTPS Redirect" set to "Yes".
My personal favourite connectivity diagnostic tool, Rex Swain HTTP Viewer, won't work with blogs that only support "HTTPS:" connectivity.
No "HTTP:" diagnostics, for "HTTPS:" redirected blogs.
The "www" alias of a "blogspot.com" published blog will not work, using SSL.
Using the "www" alias, of a "blogspot.com" URL, will not work - with "HTTPS Redirect" set to "Yes".
Forcing SSL will not make your blogs readers more secure.
Use of "HTTPS Redirect", while nominally making your readers more secure, will limit access to your blog.
Offering SSL connectivity is good for everybody - but understand the limitations.
Enjoy offering SSL connectivity - and improved search engine reputation. But keep it in perspective.
People who explicitly use "HTTP:" to access your blog, and are vulnerable to hijacking, will see an imposters blog - even if your blog forces them to use SSL. Only people who explicitly use "HTTPS:", to access your blog, will predictably see your blog - and they won't benefit from being forced to use SSL.
As #Blogger continues the rollout of SSL to "blogspot.com" published blogs, they have changed the HTTPS option. All blogs which support SSL will offer "HTTPS:" connectivity, and the option will be to allow explicit access, using "HTTP:".
You may do well to consider what benefits you get, from forcing your readers to use SSL to access your blog.
All "blogspot.com" published blogs will now offer HTTPS connectivity, to the reader. The choice, offered to the blog owner, is now whether to force every reader to use SSL - and the dashboard option is now labeled "HTTPS Redirect".
You can force your readers to use SSL, to access your blog - but will that make them more secure?
Every blog will offer SSL connectivity, to readers who use "HTTPS:" URLs.
The dashboard option is now "HTTPS Redirect".
The choice is now whether to force "HTTPS:" upon each reader - or allow some to continue to read, using "HTTP:".
If you select HTTPS Redirect, you will be limiting your reader population.
Some readers access our blogs, by using free proxy servers - and most proxy servers, when they offer HTTPS, offer it as a premium (with a paid subscription). You are entitled to require everybody to use SSL, if you wish - but you may see reader activity drop, as readers using free proxies find other blogs and websites to read.
Everybody will see the "HTTPS:" alias - with "HTTPS Redirect" set to "Yes".
My personal favourite connectivity diagnostic tool, Rex Swain HTTP Viewer, won't work with blogs that only support "HTTPS:" connectivity.
http://www.rexswain.com/cgi-bin/httpview.cgi?url=http://nitecruzr-test-ssl.blogspot.com/&uag=Mozilla/5.0+(X11%3B+CrOS+armv7l+7834.70.0)+AppleWebKit/537.36+(KHTML,+like+Gecko)+Chrome/49.0.2623.112+Safari/537.36&ref=http://www.rexswain.com/httpview.html&aen=&req=GET&ver=1.1&fmt=AUTO
No "HTTP:" diagnostics, for "HTTPS:" redirected blogs.
The "www" alias of a "blogspot.com" published blog will not work, using SSL.
Using the "www" alias, of a "blogspot.com" URL, will not work - with "HTTPS Redirect" set to "Yes".
Forcing SSL will not make your blogs readers more secure.
Use of "HTTPS Redirect", while nominally making your readers more secure, will limit access to your blog.
- Readers, using proxy servers, may not be able to access your blog.
- Diagnostics of blog problems, using proxy servers, will be limited.
- Readers who bookmarked your blog, using the "www" alias, will not be able to access it.
- Readers who are vulnerable to hijacking, when using "HTTP:", will not access your blog.
Offering SSL connectivity is good for everybody - but understand the limitations.
Enjoy offering SSL connectivity - and improved search engine reputation. But keep it in perspective.
People who explicitly use "HTTP:" to access your blog, and are vulnerable to hijacking, will see an imposters blog - even if your blog forces them to use SSL. Only people who explicitly use "HTTPS:", to access your blog, will predictably see your blog - and they won't benefit from being forced to use SSL.
As #Blogger continues the rollout of SSL to "blogspot.com" published blogs, they have changed the HTTPS option. All blogs which support SSL will offer "HTTPS:" connectivity, and the option will be to allow explicit access, using "HTTP:".
You may do well to consider what benefits you get, from forcing your readers to use SSL to access your blog.
Sunday, April 24, 2016
Blogger Magic - The Custom Domain Root Redirect
When you setup a custom domain, for a Blogger blog, the DNS addresses are the most important issue.
A close second in importance, to righteous DNS addressing, is redirecting the domain root to the published URL. We see frequent problem reports, in Blogger Help Forum: Get Help with an Issue.
With the proper DNS addresses in place, redirecting the domain root is a very simple process.
Start from Settings - Basic.
Start from the dashboard Settings - Basic page.
Click on "Edit" in the Publishing "Blog Address" wizard.
With this blog, I have the option to select "Redirect nitecruzr.net to blogging.nitecruzr.net."
You can only redirect the domain root - no virtual hosts.
Generally, you would publish to "www.mydomain.com" - then you would have the option to "Redirect mydomain.com to www.mydomain.com".
Note that you can only redirect the domain root - even if you publish to a virtual host, such as "www.blog.mydomain.com". "blog.mydomain.com" and www.blog.mydomain.com" are separate hosts - and cannot be aliased.
Whatever you have, the option will work best, when you start with righteous DNS addresses.
Given righteous DNS addresses, publishing a #Blogger blog to a custom domain will produce a more stable blog, with the domain root redirected to the published URL. As the blog owner, you need to be sure to select the redirect option.
A close second in importance, to righteous DNS addressing, is redirecting the domain root to the published URL. We see frequent problem reports, in Blogger Help Forum: Get Help with an Issue.
Why does my domain only work, with the "www" in the address?The domain root provides a backup to the published URL, in many domain setups. If the domain root is not redirected, and DNS for the "www" or other published alias is down, the domain is down.
With the proper DNS addresses in place, redirecting the domain root is a very simple process.
Start from Settings - Basic.
Start from the dashboard Settings - Basic page.
Click on "Edit" in the Publishing "Blog Address" wizard.
With this blog, I have the option to select "Redirect nitecruzr.net to blogging.nitecruzr.net."
You can only redirect the domain root - no virtual hosts.
Generally, you would publish to "www.mydomain.com" - then you would have the option to "Redirect mydomain.com to www.mydomain.com".
Note that you can only redirect the domain root - even if you publish to a virtual host, such as "www.blog.mydomain.com". "blog.mydomain.com" and www.blog.mydomain.com" are separate hosts - and cannot be aliased.
Whatever you have, the option will work best, when you start with righteous DNS addresses.
Given righteous DNS addresses, publishing a #Blogger blog to a custom domain will produce a more stable blog, with the domain root redirected to the published URL. As the blog owner, you need to be sure to select the redirect option.
Wednesday, April 13, 2016
Blogger Magic - Changing The Blog Title
Some blog owners start a blog - then discover that they gave the blog the wrong name.
Unlike changing the Blog Name (Address), changing the Blog Name (Title) is not complicated.
You can change the title of a blog, any time you wish.
The blog name (title) is an important blog component. Changing the title is not difficult.
Go to the dashboard Settings - Basic page.
Click on "Edit", for "Title".
Make the change, as necessary. Click "Save changes".
The next post you publish will display the right title, in any search engine lists, and shares. If the blog uses FeedBurner, to distribute by email or provide improved newsfeed subscriptions, you may want to check the feed title also.
What effect will this have, on search engine content?
When you change the title, all of the existing posts will still be indexed, under the old title. All of the SERP entries will show the old title - and the blog will be searchable using the old title.
As the blog is re indexed, the search engines will pick up the new title. This won't happen, immediately, though.
And the people who find the blog, when searching on the old title - and click on a SERP entry referencing the blog - will see the blog with the new title.
The #Blogger blog title is a key blog component, which can be changed any time convenient. This is a very simple change - and can be done without planning.
Unlike changing the Blog Name (Address), changing the Blog Name (Title) is not complicated.
You can change the title of a blog, any time you wish.
The blog name (title) is an important blog component. Changing the title is not difficult.
- Use the Blogger dashboard Settings - Basic page.
- Click the "Edit" link, next to "Title".
- Make the change, as necessary.
- Click "Save changes".
Go to the dashboard Settings - Basic page.
Click on "Edit", for "Title".
Make the change, as necessary. Click "Save changes".
The next post you publish will display the right title, in any search engine lists, and shares. If the blog uses FeedBurner, to distribute by email or provide improved newsfeed subscriptions, you may want to check the feed title also.
What effect will this have, on search engine content?
When you change the title, all of the existing posts will still be indexed, under the old title. All of the SERP entries will show the old title - and the blog will be searchable using the old title.
As the blog is re indexed, the search engines will pick up the new title. This won't happen, immediately, though.
And the people who find the blog, when searching on the old title - and click on a SERP entry referencing the blog - will see the blog with the new title.
The #Blogger blog title is a key blog component, which can be changed any time convenient. This is a very simple change - and can be done without planning.
Thursday, March 31, 2016
CloudFlare, Custom Domain Publishing, And HTTPS
A few blog owners, who publish blogs published to custom domains, are becoming impatient, waiting for Blogger Engineering to finish the Blogger upgrade to support HTTPS / SSL.
HTTPS is not available, for non BlogSpot published blogs.
Whether registered by eNom, GoDaddy, or Google Domains, it simply is not possible to publish a non BlogSpot URL as a supported custom domain, and make HTTPS / SSL available. CloudFlare, a supposed alternative, does not produce a supported custom domain.
A proxied CloudFlare domain looks like malicious redirection.
In some cases, a CloudFlare DNS "solution" tried by some blog owners, will look like dangerous / malicious redirection. Some blogs will show up as "Deceptive sites", aka "phishing".
Some blogs using CloudFlare, for custom domain publishing, will be classified as "Deceptive" sites.
Others will produce alarming warnings about malware.
"This blog is not hosted by Blogger and has not been checked for spam, viruses and other forms of malware."
Click on "Details".
Look at the warning.
And there is the typical Dig log, with a redirecting proxy service, like CloudFlare.
or
This is the basis for malware / phishing classification.
Any observed malware warning is generally a false positive - most custom domain published blogs do not contain malware. Even so, it's not likely that the "Deceptive site" classification will be easily corrected - or the malware warning interstitial display removed.
And this is one more blog owner, who must next be provided instruction to correct the DNS addresses.
Having corrected as instructed, DNS addresses will be asymmetrical, and righteous.
With DNS corrected, Google shows "Not dangerous" - but the warning still displays.
"Not dangerous".
Note "CloudFlare" is still seen as the host.
You can report an error, to SafeBrowsing.
False classification now requires time consuming site review.
Use "Report Incorrect Phishing Warning", if you believe the site is safe.
Finally, get the site reviewed, from the Security Issues page in Security Console (Webmaster Tools) - Security Issues.
And while the blog remains offline, search reputation - and the owner - will suffer.
Some #Blogger blog owners want to provide blogs published to custom domains - and offer HTTPS connectivity. Since Blogger cannot provide custom domains with HTTPS right now, the blog owners are using CloudFlare, which provides an HTTPS proxy.
Unfortunately, a CloudFlare proxy looks like malicious redirection - and blogs using CloudFlare are being labeled as "Deceptive" sites.
https://productforums.google.com/forum/#!category-topic/blogger/ApuJ58a4-kg
https://productforums.google.com/forum/#!category-topic/blogger/-LoJCeX6DEA
https://productforums.google.com/forum/#!category-topic/blogger/DhAFOtJFoCw
If I get a domain through Google Domains, will I be able to get HTTPS?Unfortunately, no. HTTPS / SSL is simply not available, to blogs published to custom domains.
HTTPS is not available, for non BlogSpot published blogs.
Whether registered by eNom, GoDaddy, or Google Domains, it simply is not possible to publish a non BlogSpot URL as a supported custom domain, and make HTTPS / SSL available. CloudFlare, a supposed alternative, does not produce a supported custom domain.
A proxied CloudFlare domain looks like malicious redirection.
In some cases, a CloudFlare DNS "solution" tried by some blog owners, will look like dangerous / malicious redirection. Some blogs will show up as "Deceptive sites", aka "phishing".
Some blogs using CloudFlare, for custom domain publishing, will be classified as "Deceptive" sites.
Others will produce alarming warnings about malware.
"This blog is not hosted by Blogger and has not been checked for spam, viruses and other forms of malware."
Click on "Details".
Look at the warning.
Phishing sites pretend to be other websites to trick you.
And there is the typical Dig log, with a redirecting proxy service, like CloudFlare.
kireisubs.id. 300 IN A 104.27.133.198
www.kireisubs.id. 300 IN A 104.27.133.198
or
topmovies21.biz. 300 IN A 104.28.0.106
www.topmovies21.biz. 300 IN A 104.28.0.106
This is the basis for malware / phishing classification.
Any observed malware warning is generally a false positive - most custom domain published blogs do not contain malware. Even so, it's not likely that the "Deceptive site" classification will be easily corrected - or the malware warning interstitial display removed.
And this is one more blog owner, who must next be provided instruction to correct the DNS addresses.
Having corrected as instructed, DNS addresses will be asymmetrical, and righteous.
kireisubs.id. 86400 IN A 216.239.32.21
kireisubs.id. 86400 IN A 216.239.34.21
kireisubs.id. 86400 IN A 216.239.36.21
kireisubs.id. 86400 IN A 216.239.38.21
www.kireisubs.id. 86400 IN CNAME ghs.google.com.
With DNS corrected, Google shows "Not dangerous" - but the warning still displays.
"Not dangerous".
Note "CloudFlare" is still seen as the host.
You can report an error, to SafeBrowsing.
False classification now requires time consuming site review.
Use "Report Incorrect Phishing Warning", if you believe the site is safe.
Finally, get the site reviewed, from the Security Issues page in Security Console (Webmaster Tools) - Security Issues.
And while the blog remains offline, search reputation - and the owner - will suffer.
Some #Blogger blog owners want to provide blogs published to custom domains - and offer HTTPS connectivity. Since Blogger cannot provide custom domains with HTTPS right now, the blog owners are using CloudFlare, which provides an HTTPS proxy.
Unfortunately, a CloudFlare proxy looks like malicious redirection - and blogs using CloudFlare are being labeled as "Deceptive" sites.
https://productforums.google.com/forum/#!category-topic/blogger/ApuJ58a4-kg
https://productforums.google.com/forum/#!category-topic/blogger/-LoJCeX6DEA
https://productforums.google.com/forum/#!category-topic/blogger/DhAFOtJFoCw
Saturday, October 11, 2014
If You Want To Keep A Secret, Don't Publish It
Have you ever heard the old saying
Occasionally we see signs of naivete, in Blogger Help Forum: Something Is Broken.
or
Not all blog owners know that neither the "disallow" statement, in "Robots.Txt" - nor the "noindex, nofollow" directives, in our blogs - are mandatory.
If you publish content on the web, chances are it is - or will eventually be - indexed somewhere, by some search engine.
Obedient search engines won't index content, when instructed.
Obedient search engine robots will observe the Google privacy directives, such as "noindex, nofollow" directives in HTML code, and the instructions in the "robots.txt" file. Not all robots are obedient, however.
There are many search engines besides Google - and not all search engines observe privacy directives.
The various robotic processes, which scan for abusive content, scan all blogs and websites out of necessity. Some archiving robots archive everything - not just content that's provided openly.
Many search engines share indexed content - obedient, or not.
Many search engines share data with other search engines, and / or retrieve data from other search engines. Even Google will index some sites, indirectly, that are not intended to be indexed.
Ownership and privacy laws vary - from country to country, and between Internet services. What you consider private (personal data), if you live in Germany, may be treated as common knowledge, by someone in Russia, or the USA. And if you report someone publishing your private data to Blogger / Google, you may get different treatment than from WordPress, or from an independent hosting service in China.
If you publish content, expect that it will be indexed.
If you want to keep a secret, do not publish your secret on the Internet. Regardless of whether you publish it to a blog with designated readers, using the Blogger dashboard Privacy settings, or even using a custom "robots.txt" file, your secret may be visible on any search engine - even on Google.
If you think the Internet is your friend, try publishing a secret there. You will learn the truth, eventually. And hiding your secret, after it gets out, will not be an easy task.
I had a friend, and I had a secret. I told my friend my secret - and now, I have neither a friend, or a secret.
Occasionally we see signs of naivete, in Blogger Help Forum: Something Is Broken.
I have a private blog! Why do I see my blog listed in Google?
or
I distinctly set my blog to be invisible! Why is my blog being indexed?
Not all blog owners know that neither the "disallow" statement, in "Robots.Txt" - nor the "noindex, nofollow" directives, in our blogs - are mandatory.
If you publish content on the web, chances are it is - or will eventually be - indexed somewhere, by some search engine.
Obedient search engines won't index content, when instructed.
Obedient search engine robots will observe the Google privacy directives, such as "noindex, nofollow" directives in HTML code, and the instructions in the "robots.txt" file. Not all robots are obedient, however.
There are many search engines besides Google - and not all search engines observe privacy directives.
The various robotic processes, which scan for abusive content, scan all blogs and websites out of necessity. Some archiving robots archive everything - not just content that's provided openly.
Many search engines share indexed content - obedient, or not.
Many search engines share data with other search engines, and / or retrieve data from other search engines. Even Google will index some sites, indirectly, that are not intended to be indexed.
Ownership and privacy laws vary - from country to country, and between Internet services. What you consider private (personal data), if you live in Germany, may be treated as common knowledge, by someone in Russia, or the USA. And if you report someone publishing your private data to Blogger / Google, you may get different treatment than from WordPress, or from an independent hosting service in China.
If you publish content, expect that it will be indexed.
If you want to keep a secret, do not publish your secret on the Internet. Regardless of whether you publish it to a blog with designated readers, using the Blogger dashboard Privacy settings, or even using a custom "robots.txt" file, your secret may be visible on any search engine - even on Google.
If you think the Internet is your friend, try publishing a secret there. You will learn the truth, eventually. And hiding your secret, after it gets out, will not be an easy task.
Wednesday, February 15, 2012
Cloning Your Blog
Occasionally, we see evidence of wistful thinking in Blogger Help Forum: How Do I?.
Before planning to clone a blog, using exact content, design, and layout, one should always bear in mind the search engines, and the possibility that both a clone may be subject to search engine duplicated content penalty - which may affect both blogs. Search engines want to index one copy of everything. When there are multiple copies of a given post on the Internet, all copies must be treated with suspicion.
When planning any cloning operation, we must consider the essential elements of a blog.
Some people, mindful of the inability to copy an XML based accessory / gadget, will suggest extracting the HTML rendered equivalent, from a blog source listing - then creating an HTML gadget in the target blog, using the extracted HTML from the source blog. This is a possible workaround, with several downsides.
One specific accessory, Followers, is a part of both the source blog, and the Followers community - the collective profiles owned by all of the Followers. The Followers gadget simply cannot be copied, from one blog to another.
Other than the exceptions of the Accessories, and of the Followers community and gadget, almost any Blogger blog can be cloned - with the proper planning and understanding.
>> Top
How do I make an exact copy of my blog, to another URL?This should be a simple enough task - but it's not.
Before planning to clone a blog, using exact content, design, and layout, one should always bear in mind the search engines, and the possibility that both a clone may be subject to search engine duplicated content penalty - which may affect both blogs. Search engines want to index one copy of everything. When there are multiple copies of a given post on the Internet, all copies must be treated with suspicion.
When planning any cloning operation, we must consider the essential elements of a blog.
- Accessories and Gadgets. There is currently no easy way to copy XML based accessories from one blog to another.
- Blog Address. This is unique for each blog, and cannot be cloned. All blog content, which refers to the blog address (URL) must be updated. Internal links must be edited, to point to other articles within the target blog. External references to the blog may or may not need to be updated, to point to the new address.
- Comments and Posts. Blog "articles" written by blog members and visitors can be copied from the source blog to the target blog, using the Export / Import wizards. Note one known caution, which should be observed when Importing content.
- Layout and Template. The blog template can be copied from the source blog to the target blog, using the Template backup and restore wizards.
- Blog Reputation. As with any new blog, this will start from scratch. All external links and references - whether the search engines, or the user community in general - must start from zero. This will be vaguely similar to the process of renaming a blog - with the exception of the reputation of both the source and target blogs, as noted above.
Some people, mindful of the inability to copy an XML based accessory / gadget, will suggest extracting the HTML rendered equivalent, from a blog source listing - then creating an HTML gadget in the target blog, using the extracted HTML from the source blog. This is a possible workaround, with several downsides.
- This will be a manual and repetitive process, one gadget at a time.
- Any gadgets, copied this way, will be based on HTML, and can't be maintained using an XML wizard.
- The content of any gadgets, copied this way, will be static.
One specific accessory, Followers, is a part of both the source blog, and the Followers community - the collective profiles owned by all of the Followers. The Followers gadget simply cannot be copied, from one blog to another.
Other than the exceptions of the Accessories, and of the Followers community and gadget, almost any Blogger blog can be cloned - with the proper planning and understanding.
>> Top
Monday, January 30, 2012
Custom Domain Publishing - Moving Back To BlogSpot, Using The New GUI, Isn't Obvious
The New Blogger GUI (2011) has been available for just over 6 months - and we see new confusion about using it, daily, in Blogger Help Forum: How Do I?.
The answer to that specific question is actually right there, in front of us - we just don't see it.
Blogger, like Google, likes to use overlay panels for some displays, such as how you see the picture below - when you click on it.
In the new GUI, if I look at the Blog Address settings for this blog, in Settings - Basic - Publishing, I see
See the "X"?
(Click on the picture, to better see the details.)
"Edit" is a link, that lets me "Edit" my custom domain settings. The "Edit" wizard (which simply pops up in the same display, when I click on "Edit") does not let me change the URL of the blog back to BlogSpot - and this is the start of some confusion.
To remove the custom domain redirect, and re publish the blog to the domain - or publish back to BlogSpot - one must click on the "X" in the top right. With the publishing shown as
When you click on the "X", you will get a verification popup.
So, click on the "X" (it's actually in black - I show it in red, above, to make it more obvious), to clear the custom domain redirect and publish back to the original BlogSpot URL. If you don't see the "X", click in the upper right corner of that window - to the right of "Edit" and just left of the window border. Apparently, not all browsers display the "X" properly.
How do I cancel my custom domain redirect, in the New GUI?This is one specific question, that's been asked, recently.
The answer to that specific question is actually right there, in front of us - we just don't see it.
Blogger, like Google, likes to use overlay panels for some displays, such as how you see the picture below - when you click on it.
In the new GUI, if I look at the Blog Address settings for this blog, in Settings - Basic - Publishing, I see
(Click on the picture, to better see the details.)
"Edit" is a link, that lets me "Edit" my custom domain settings. The "Edit" wizard (which simply pops up in the same display, when I click on "Edit") does not let me change the URL of the blog back to BlogSpot - and this is the start of some confusion.
To remove the custom domain redirect, and re publish the blog to the domain - or publish back to BlogSpot - one must click on the "X" in the top right. With the publishing shown as
blogging.nitecruzr.net Edit Xclicking on the "X" lets me remove the custom domain redirect. Clicking on "Edit" only lets me change specific custom domain settings, such as selecting the "naked domain" redirect option.
bloggerstatusforreal.blogspot.com redirects
When you click on the "X", you will get a verification popup.
Are you sure? This will remove the current custom domain.And you'll want to hit "Yes".
So, click on the "X" (it's actually in black - I show it in red, above, to make it more obvious), to clear the custom domain redirect and publish back to the original BlogSpot URL. If you don't see the "X", click in the upper right corner of that window - to the right of "Edit" and just left of the window border. Apparently, not all browsers display the "X" properly.
Thursday, April 8, 2010
Republishing A Custom Domain Blog
Sometimes, when you are publishing a blog to a custom domain, you'll have a problem with the settings. Some settings problems can only be solved by repeating the publishing process. But you can't repeat the process - once a blog is published to a URL, you can't just publish again, to the domain URL.
In some cases, you have to publish the blog back to BlogSpot, then re publish to the domain. In other cases, you have to return the blog to a BlogSpot publishing, so you can solve some problems now - and return to the domain publishing, at some unknown time in the future.
This is all done from the Settings - Publishing wizard, which you access from the Blogger dashboard - and it's as easy as 1 - 2 - 3 - 4.
For more details on the re publishing process, see Roberto's Report: Re-Publishing to blogspot.com, and back to a Custom Domain.
>> Top
In some cases, you have to publish the blog back to BlogSpot, then re publish to the domain. In other cases, you have to return the blog to a BlogSpot publishing, so you can solve some problems now - and return to the domain publishing, at some unknown time in the future.
This is all done from the Settings - Publishing wizard, which you access from the Blogger dashboard - and it's as easy as 1 - 2 - 3 - 4.
- Always start by getting a new ownership verification token, and adding it to the domain DNS address list. Pay careful attention to DNS address entry conventions! If you are instructed to add a "CNAME", you do have to add a "CNAME" - regardless of older instructions!
- If the blog is currently published to the non BlogSpot domain, you'll simply have to click on the "X", to re publish to the previous BlogSpot URL.
- Click on
Add a custom domain
- Now, you have several possibilities.
- In many cases, you will be republishing to an otherwise properly purchased domain. Click on
Switch to advanced settings
The previously used custom domain should be already displayed, in the Advanced settings window. Click on the Save button, and your domain should be online. - Occasionally, the domain was not successfully purchased, even though the BlogSpot URL redirects. Alternately, you may have let the domain expire - and you now have to buy a new domain. In either case, you have to purchase a domain, again.
- In many cases, you will be republishing to an otherwise properly purchased domain. Click on
- OK, it couldn't be quite that simple, could it? Don't forget to select
Redirect mydomain.com to www.mydomain.com
if desired - and if you are not publishing to the domain root.
For more details on the re publishing process, see Roberto's Report: Re-Publishing to blogspot.com, and back to a Custom Domain.
>> Top
Thursday, January 21, 2010
Want Your Blog Deleted Or The URL Freed Up? Do Not Delete Your Blogger Account
In March 2009, Blogger changed its blog deletion procedure, to let you recover a mistakenly deleted blog on your own, and to make a blog's URL available when the blog is deleted.
However, this process applies only to deletions using "Delete blog".
Please, don't make the mistake of deleting the account that owns a blog, purely to transfer control of a blog to another account. If you do that, you'll have to
>> Top
- When you use the "Delete blog" wizard in Settings - Basic, a deleted blog goes into a "Deleted But Recoverable" status.
- The blog is immediately visible on your dashboard, possibly behind the "View all blogs" link, and is displayed with an "Undelete this blog" link.
- 90 days after you use "Delete blog", the blog is truly deleted, and the URL is made available to the public, on a "first come, first served" basis.
However, this process applies only to deletions using "Delete blog".
- If you delete a Blogger or Google account, any blogs owned by that account are locked to that account. The URLs for those blogs will be permanently un available to the general public.
- If you want the blog URL to be immediately available to another individual Blogger account, you have to transfer control of the blog, properly.
- If you want the URL to be immediately publicly available, you have to rename the blog to publish to another URL.
Please, don't make the mistake of deleting the account that owns a blog, purely to transfer control of a blog to another account. If you do that, you'll have to
- Recover the owning account.
- Rebuild or undelete the blog.
- Transfer control of the blog, properly.
>> Top
Wednesday, November 4, 2009
Less Traffic To Our Blogs
One of the more active (and frequently controversial) subjects discussed in this blog is getting more traffic to our blogs, also known as getting the blog indexed by the search engines. Not everybody wants their blogs indexed, though.
Short of absolute effectiveness, the most obvious solution is the two Settings - Basic options. And there are other tweaks which you may find, in Google Webmaster Tools.
And, in the spirit of locking the barn after the horses have been stolen, there is the subject of Removing Your Blog From The Search Engines Caches. Search engine caches, like browser caches, won't clear overnight, if ever.
You'll need to note that the entries in "robots.txt", that result from the two Blogger options "Add your blog to our listings?" and "Let search engines find your blog?", are advisory only - not all search engines observe either setting. And the various search engines accept feeds from each other, in various relationships.
>> Top
How do I make sure my blog is NOT found by search engines?That question is asked, regularly. And, in truth, there is only one truly effective answer.
Don't publish your blog on the Internet.This is similar to the question (and answer)
How do I keep my blog private?
Short of absolute effectiveness, the most obvious solution is the two Settings - Basic options. And there are other tweaks which you may find, in Google Webmaster Tools.
And, in the spirit of locking the barn after the horses have been stolen, there is the subject of Removing Your Blog From The Search Engines Caches. Search engine caches, like browser caches, won't clear overnight, if ever.
You'll need to note that the entries in "robots.txt", that result from the two Blogger options "Add your blog to our listings?" and "Let search engines find your blog?", are advisory only - not all search engines observe either setting. And the various search engines accept feeds from each other, in various relationships.
>> Top
Sunday, October 25, 2009
Accepting Membership In Another Blog May Change Post Editor Settings
Recently, we've seen an occasional question about mysteriously changed post editor selections.
Right now, as part of the deployment of the new post editor, there are 3 selections, in Settings - Basic - Global Settings - Select post editor.
If you make this change under one blog, you'll find it true for all of your blogs. I've also noted, under some circumstances, that when you accept membership in someone else's blog, and the other person was using a different post editor selection, the other person's selection will now be yours, globally.
The next time that you accept membership in a blog, check your post editor setting. If the owner of the blog was using a different setting, your setting may have changed.
>> Top
Where did my options toolbar go?or
Why do I now see the new post editor?
Right now, as part of the deployment of the new post editor, there are 3 selections, in Settings - Basic - Global Settings - Select post editor.
- Updated editor
- Old editor
- Hide compose mode
If you make this change under one blog, you'll find it true for all of your blogs. I've also noted, under some circumstances, that when you accept membership in someone else's blog, and the other person was using a different post editor selection, the other person's selection will now be yours, globally.
The next time that you accept membership in a blog, check your post editor setting. If the owner of the blog was using a different setting, your setting may have changed.
>> Top
Wednesday, April 2, 2008
Controlling The Search Engine Spiders
Most, but not all, blog owners eagerly anticipate the arrival, upon their blog, by the search engine spiders.
The spiders come to index your blog, when the search engines recognise your blog's existence in the Blogosphere.
For those blog owners who don't want their blogs indexed, Blogger provides the settings, in Settings - Basic - Privacy, "Add your blog to our listings?" (for internal Blogger spiders, and Blogger links) and "Let search engines find your blog?" (for external spiders).
The privacy settings control the content of the "robots.txt" file in the blog.
The spiders, when well behaved, read "robots.txt" for instructions.
The spiders, when interested, read "robots.txt" for instructions. You can modify "robots.txt", using the dashboard "Search preferences" wizard.
You make the privacy settings changes, and let Blogger maintain "robots.txt" on your behalf. Alternately, you can use "Settings" - "Search preferences", if you are daring.
These settings are at the blog level - one setting affects the entire blog. If you would like only a part of the blog protected, make a second blog (blogs are free), and include one blog in the other. If you would like specific URLs protected, use the URL removal tool in Google Webmaster Tools.
Read "Search Console" reports carefully, and learn the meanings.
If you use Google Webmaster Tools / Search Console, maybe to add a sitemap or otherwise analyse or maintain your blogs search engine relationship, you may see some interesting details
Those restrictions are normal. All label searches are restricted, so the search engines won't detect the label searches as containing duplicate content. Your blog shouldn't depend upon label searches for your readers to find each post.
Some search engines will index private blogs.
Interestingly, I note that the search engines can have access to blogs that require permission to read. Private blogs can't have blog feeds, but the search engines can still index them. The "robots.txt" file is advisory only; search engines may honour the files directives, or they may ignore the directives.
The spiders come to index your blog, when the search engines recognise your blog's existence in the Blogosphere.
For those blog owners who don't want their blogs indexed, Blogger provides the settings, in Settings - Basic - Privacy, "Add your blog to our listings?" (for internal Blogger spiders, and Blogger links) and "Let search engines find your blog?" (for external spiders).
The privacy settings control the content of the "robots.txt" file in the blog.
The spiders, when well behaved, read "robots.txt" for instructions.
The spiders, when interested, read "robots.txt" for instructions. You can modify "robots.txt", using the dashboard "Search preferences" wizard.
You make the privacy settings changes, and let Blogger maintain "robots.txt" on your behalf. Alternately, you can use "Settings" - "Search preferences", if you are daring.
These settings are at the blog level - one setting affects the entire blog. If you would like only a part of the blog protected, make a second blog (blogs are free), and include one blog in the other. If you would like specific URLs protected, use the URL removal tool in Google Webmaster Tools.
Read "Search Console" reports carefully, and learn the meanings.
If you use Google Webmaster Tools / Search Console, maybe to add a sitemap or otherwise analyse or maintain your blogs search engine relationship, you may see some interesting details
URL restricted by robots.txt (http://myblog.blogspot.com/search/label/mylabel)and you'll generally have one of these notations for each label in the blog.
Those restrictions are normal. All label searches are restricted, so the search engines won't detect the label searches as containing duplicate content. Your blog shouldn't depend upon label searches for your readers to find each post.
Some search engines will index private blogs.
Interestingly, I note that the search engines can have access to blogs that require permission to read. Private blogs can't have blog feeds, but the search engines can still index them. The "robots.txt" file is advisory only; search engines may honour the files directives, or they may ignore the directives.
Subscribe to:
Posts (Atom)































