People who publish blogs which are relevant to a specific country may be able to focus search engine attention, for their blog, and better target readers in the country in question.
Google Webmaster Tools provides the "Geographical target" setting, which lets a blog owner select a single country. The setting increases search engine attention, for their blog, in the country selected.
If you are logged in to Google Webmaster Tools, for a given blog, find the "gear" icon in the upper right corner of the dashboard display.
From the drop down menu behind the "gear", select "Site Settings" - and "Geographical target" will be right there, in front of you. Click on "Target users in:", then select the appropriate country, in the pull down menu.
The list of countries, presented to you, appears to be rather complete. The list appears to be alphabetically sorted in the English language, as most of Webmaster Tools appears to be presented.
It's likely that your potential readers will be located using geolocation, so you should allow for some inaccuracies, in targeting specific readers. Readers who are located in regions close to national borders may appear to be located on either side of the border. Only one country can be targeted.
Note that this setting is not related to any Blogger dashboard settings, such as "Language" or "Time Zone", in "Language and formatting".
Also, note that the usefulness of this setting, like other search engine features, will depend upon your efforts in properly publicising the blog. Publicising the blog is still dependent upon your efforts - this setting, when used, simply focuses your efforts towards a single country.
>> Top
Showing posts with label Settings. Show all posts
Showing posts with label Settings. Show all posts
Sunday, 15 December 2013
Wednesday, 9 October 2013
Export / Import Requires Administrative Control Of Both Blogs
Occasionally, in Blogger Help Forum: How Do I?, we see the naive query
In order to avoid encouraging scraping of blog contents, both the Export and Import wizards are only available to blog administrators. Not everybody wishing to use "Export blog" has blog ownership, however.
Too many people, denied immediate recovery of control of their blog, just start another blog.
With a new blog, the first thing needed is the content from the old blog. This is not easily had, however - because both "Export blog" and "Import blog" are part of the Blogger dashboard - and can be accessed only by blog owners.
If anybody could use "Export blog", and export the comments and posts from any blog, "Export blog" would be a very popular wizard - to blog thieves. To encourage Export / Import to be used for legitimate purposes, Blogger made it part of the Blogger dashboard - where it is accessible only to blog administrators.
This does not provide a solution for people who have lost control of their Blogger accounts - and who naively figure to start a new blog, and move the contents of the old blog to the new blog. If you're in this situation, you have only two possibilities.
Sorry. Once again, you have to always retain control of your Blogger account.
>> Top
How do I merge my two blogs, using Export / Import?When given the simple advice
Use the "Export blog" and "Import blog" wizards, both in the dashboard Settings - Other menu.the immediate response is
I don't have that menu item!This person has, most likely, lost control of the Blogger account.
In order to avoid encouraging scraping of blog contents, both the Export and Import wizards are only available to blog administrators. Not everybody wishing to use "Export blog" has blog ownership, however.
Too many people, denied immediate recovery of control of their blog, just start another blog.
With a new blog, the first thing needed is the content from the old blog. This is not easily had, however - because both "Export blog" and "Import blog" are part of the Blogger dashboard - and can be accessed only by blog owners.
If anybody could use "Export blog", and export the comments and posts from any blog, "Export blog" would be a very popular wizard - to blog thieves. To encourage Export / Import to be used for legitimate purposes, Blogger made it part of the Blogger dashboard - where it is accessible only to blog administrators.
This does not provide a solution for people who have lost control of their Blogger accounts - and who naively figure to start a new blog, and move the contents of the old blog to the new blog. If you're in this situation, you have only two possibilities.
- Recover comments and posts using blog feeds and online cache.
- Cluster the new and old blogs - but asymmetrically.
Sorry. Once again, you have to always retain control of your Blogger account.
>> Top
Wednesday, 25 September 2013
Search Engines, And Private Blogs
Not every blog owner realises the relationships between private blogs, and search engine indexing.
Some blog owners think that private blogs can't be indexed, by the search engine robots. Given the way private blogs work, search engine access is not directly restricted - even though indexing activity is impeded.
People are prevented from viewing a private blog, only because Blogger displays the private blog interstitial in front of the blog display.
Search engines are not directly affected by the private blog status - though there are interesting details.
The interstitial notice is authoritative to people, when viewing the blog.
The notice does not block robots. Robots are stopped only when they voluntarily accept the relevant settings in "robots.txt".
The text content of the interstitial advice will replace the blog description, in SERP displays.
Private blogs do not publish newsfeeds. Since the newsfeed provides the Blogger equivalent of the sitemap, a typical private Blogger blog has no sitemap - and search engine indexing activity is not as regular.
The settings in the "robots.txt" file, which specifies bots and access, is not authoritative. Acceptance of the "robots.txt" settings is left to the discretion of each different robot - and a robot which does not observe the settings can access any website.
A private blog can be indexed - though without free access by readers to a private blog, there will be less links referencing the blog - and less indirect search engine activity.
Less links referencing the blog leads to less indexing, by the search engines. Less indexing leads to less entries in SERPs, poorer SERP positioning - and relative lack of success when using search engine cache, to search the blog.
With a private blog, you'll be much more successful using a direct blog search.
>> Top
Some blog owners think that private blogs can't be indexed, by the search engine robots. Given the way private blogs work, search engine access is not directly restricted - even though indexing activity is impeded.
People are prevented from viewing a private blog, only because Blogger displays the private blog interstitial in front of the blog display.
This blog is open to invited readers onlyOther than the presence of that display, access to the blog is not affected. This detail becomes important, for some potential readers who are accessing the Internet through some Local Area Networks.
It doesn't look like you have been invited to read this blog. If you think this is a mistake, you might want to contact the blog author and request an invitation.
Search engines are not directly affected by the private blog status - though there are interesting details.
- The blog description, when indexed, will contain the text of the interstitial notice.
- Private blogs do not publish newsfeeds - and with newsfeeds used to facilitate indexing, the indexing process is not as consistent as with public blogs.
- The dashboard Privacy setting, which generates an entry in the "robots.txt" file, is advisory only, to search engine robots.
The interstitial notice is authoritative to people, when viewing the blog.The notice does not block robots. Robots are stopped only when they voluntarily accept the relevant settings in "robots.txt".
The text content of the interstitial advice will replace the blog description, in SERP displays.
This blog is open to invited readers onlyWithout an actual blog description, potential blog readers won't feel very encouraged to view the blog. Even when clicking on the SERP entry, the would be blog reader is still taken to the interstitial, and goes no farther.
This blog is open to invited readers only
Private blogs do not publish newsfeeds. Since the newsfeed provides the Blogger equivalent of the sitemap, a typical private Blogger blog has no sitemap - and search engine indexing activity is not as regular.
The settings in the "robots.txt" file, which specifies bots and access, is not authoritative. Acceptance of the "robots.txt" settings is left to the discretion of each different robot - and a robot which does not observe the settings can access any website.
A private blog can be indexed - though without free access by readers to a private blog, there will be less links referencing the blog - and less indirect search engine activity.
Less links referencing the blog leads to less indexing, by the search engines. Less indexing leads to less entries in SERPs, poorer SERP positioning - and relative lack of success when using search engine cache, to search the blog.
With a private blog, you'll be much more successful using a direct blog search.
>> Top
Monday, 23 September 2013
BlogLovin, And Blogs Publishing Feeds Through FeedBurner
We're seeing a few reports, in Blogger Help Forum: Something Is Broken, about BlogLovin, and their inability to accept feeds from Blogger blogs.
When diagnosed, we frequently see a working posts feed, redirected through FeedBurner.
It appears that BlogLovin is not able to properly accept some (or all) FeedBurner redirected feeds. The most obvious solution here would be to setup BlogLovin properly, to use a non redirected feed, so they get the native Blogger posts feed.
Upon trying to test my diagnosis, using my test blog, it appears that adding a blog to BlogLovin requires publishing a new post, with their Follow button conspicuously located.
It does not appear to be easily possible to specify the blog feed, in this case. It appears that BlogLovin extracts the blog feed, using the feed autodiscovery meta code, in the blog template.
It appears that any solution to the problem with BlogLovin vs FeedBurner redirected feeds will require involvement with BlogLovin Engineering.
>> Top
My feed on Bloglovin is not updating correctly, so I emailed BlogLovin Support. They responded, and said it was because my RSS feed isn't working correctly.
When diagnosed, we frequently see a working posts feed, redirected through FeedBurner.
It appears that BlogLovin is not able to properly accept some (or all) FeedBurner redirected feeds. The most obvious solution here would be to setup BlogLovin properly, to use a non redirected feed, so they get the native Blogger posts feed.
Upon trying to test my diagnosis, using my test blog, it appears that adding a blog to BlogLovin requires publishing a new post, with their Follow button conspicuously located.
Paste this text into a new blog post:<a href="http://www.bloglovin.com/blog/10757427/?claim=ge8y4cfhqfx">Follow my blog with Bloglovin</a>
In some blogs it's necessary to put the code in the top of the blog post
It does not appear to be easily possible to specify the blog feed, in this case. It appears that BlogLovin extracts the blog feed, using the feed autodiscovery meta code, in the blog template.
It appears that any solution to the problem with BlogLovin vs FeedBurner redirected feeds will require involvement with BlogLovin Engineering.
- Convince BlogLovin Support to make their service accept FeedBurner feeds.
- Convince BlogLovin Support to make their service filter feed redirects.
- Discontinue FeedBurner from your feed redirect.
- Figure out how to specify a non redirected feed to BlogLovin.
>> Top
Wednesday, 11 September 2013
Click On The "X" (If You Can Find It - And If You Mean To Do It)
The custom domain publishing form, in the dashboard Publishing wizard, causes confusion.
Occasionally, we see evidence of the confusion, in Blogger Help Forum: Something Is Broken.
The custom domain overlay, in the dashboard Basic - Publishing wizard, is very elegant. The overlay design is similar to forms used by Blogger and Google+, to display photos.
The "overlay" form is appropriately designed, for its use. The form follows the function - and reflects the status of the blog. For all that, it's diabolically subtle.
The normal display, for a blog published to BlogSpot, is a simple box, containing the current BlogSpot URL - and an "Edit" link, used to change the published BlogSpot URL. If this blog were still published as "bloggerstatusforreal.blogspot.com", for instance, I would see
The display for a custom domain published blog overlays the normal BlogSpot URL box. With this blog published as "blogging.nitecruzr.net" (but still retaining the BlogSpot URL "bloggerstatusforreal.blogspot.com"), I see a simple box.
If I want to return the blog to the "bloggerstatusforreal.blogspot.com" published URL, I have to simply click on the "X", to the right of "Edit". The "overlay" box closes - as the blog is re published, to the BlogSpot URL.
It's that simple.
If you were to request assistance, in the forum.
To avoid causing more frustration, I provide some detail.
And, if you "accidentally" happen to click on the "X" without meaning to do so, your domain promptly (within limits of cache expiration) goes offline, as the blog only responds to a BlogSpot URL.
Oh yes, the "Edit" link, visible when the blog is published to the domain, does lead to an essential function - the ability to select the option.
>> Top
Occasionally, we see evidence of the confusion, in Blogger Help Forum: Something Is Broken.
I need to cancel my domain - but Blogger won't let me!or
I clicked on my dashboard, and now my blog isn't published to my domain!These blog owners, and more, are perplexed by the Publishing overlay form, displayed for a blog published to a custom domain.
The custom domain overlay, in the dashboard Basic - Publishing wizard, is very elegant. The overlay design is similar to forms used by Blogger and Google+, to display photos.
The "overlay" form is appropriately designed, for its use. The form follows the function - and reflects the status of the blog. For all that, it's diabolically subtle.
The normal display, for a blog published to BlogSpot, is a simple box, containing the current BlogSpot URL - and an "Edit" link, used to change the published BlogSpot URL. If this blog were still published as "bloggerstatusforreal.blogspot.com", for instance, I would see
bloggerstatusforreal.blogspot.com EditClicking on the "Edit" link, I would get the wizard, to re publish the blog under a different BlogSpot URL.
The display for a custom domain published blog overlays the normal BlogSpot URL box. With this blog published as "blogging.nitecruzr.net" (but still retaining the BlogSpot URL "bloggerstatusforreal.blogspot.com"), I see a simple box.
blogging.nitecruzr.net Edit XThis simple box "overlays" the previous box.
bloggerstatusforreal.blogspot.com redirects
bloggerstatusforreal.blogspot.com EditThis justifies the use of the "overlay" design, I suspect.
If I want to return the blog to the "bloggerstatusforreal.blogspot.com" published URL, I have to simply click on the "X", to the right of "Edit". The "overlay" box closes - as the blog is re published, to the BlogSpot URL.
It's that simple.
- When I can see the "X".
- When I understand what the "X" is intended for.
- When I intend to return the blog to the BlogSpot URL.
If you were to request assistance, in the forum.
How do I publish the blog back to BlogSpot?The answer should be very simple.
Click on the "X".How elegant - and how non useful. In strict online etiquette, it's rude. Since you are requesting assistance, it's possible that you don't see the "X" or do not understand its function.
To avoid causing more frustration, I provide some detail.
Click on the "X", to the right of the "Edit" link".To make sure that I am instructing you properly, I first must make sure that the blog is properly published to the domain. I request verification of what you are seeing.
Please provide a screen print, showing the Publishing wizard, in the dashboard Settings - Basic display.Later seeing the properly produced screen print, which indicates the blog properly published to the domain, I can then reply, confidently.
Click on the "X".Such is life, in the Blogger elegance.
And, if you "accidentally" happen to click on the "X" without meaning to do so, your domain promptly (within limits of cache expiration) goes offline, as the blog only responds to a BlogSpot URL.
Oh yes, the "Edit" link, visible when the blog is published to the domain, does lead to an essential function - the ability to select the option.
Redirect nitecruzr.net to blogging.nitecruzr.netAgain, not always a good idea.
>> Top
Tuesday, 10 September 2013
Automatic Sharing Of New Posts, To Google+, Is Here
Almost 3 years ago, Blogger introduced easy sharing of new Blogger posts, to Google+.
This week, they took the next step. For those blogs associated with a Google+ page or profile, you can share new posts, Publicly, automatically.
Just select "Automatically share after posting", and you're ready to share new posts, publicly, as soon as they are published.
When you share automatically, it's absolute and immediate.
We see in Google Help: Automatically share to Google+, some interesting advice.
>> Top
This week, they took the next step. For those blogs associated with a Google+ page or profile, you can share new posts, Publicly, automatically.
Starting today you can automatically share your blog posts publicly to Google+ — as soon as you publish them, with no additional clicks.
Just select "Automatically share after posting", and you're ready to share new posts, publicly, as soon as they are published. When you share automatically, it's absolute and immediate.
- Everything gets shared to Public - no Circles selection.
- No Comment addition.
We see in Google Help: Automatically share to Google+, some interesting advice.
Automatic sharing to Google+ is enabled by default on all public blogs linked to Google+ pages or profiles.If you setup a new blog, you might do well to check the setting, before publishing your first few posts.
>> Top
Saturday, 22 June 2013
Google+ Comments Lack Controls For Moderation And Notification
As more people choose Google+ Comments for their blogs, we're seeing concern from confused blog owners, mentioning lack of control.
With Google+ Comments, anybody can post - and share - a reference to any content, on the Internet, that they can view. If your blog is public, any post from your blog can be shared in Google+.
If someone shares a post from your blog, and you are in a Circle where the post is shared, you may see the shared post in your Google+ stream. You have no control over content in your stream - even if the content references your blog - which you do not share.
You have no control over content about your blog, which you, yourself, do not share.
If somebody comments on a post shared from your blog, and you are in a Circle where the post is shared, you may see the comment in your stream. Again, you have no control over a comment made against a post in your stream - even if the comment references your blog.
In no case will you have the opportunity to moderate either a post, or a comment against a post, if someone else shares a reference to a post from your blog. Nor will you get a notification, if someone shares a reference to a post from your blog. Your blog is just one object of interest, from the millions of shares published by people in Google+.
If you, yourself, share content from your blog, you will own that share - you can control the content in the share - and you can control any comments placed against that share.
If someone reshares what you share, that reshare becomes the property of the person resharing. If you are in a Circle where your share is reshared, you may see the reshared post in your stream. Again, you will have no control over the reshare - or any comments placed against the reshare.
If you are not in a Circle where your share is reshared, you won't even see the reshare. Even if your blog is referenced in a reshare, your blog is just one object of interest, in the millions of shares published by people in Google+.
Notifications work the same way. If you share content from your blog, you will get Notification when someone comments against your share - or when someone reshares what you share. If someone else shares - or reshares - content from your blog, which you did not originate, you won't get a notification.
With Google+ Comments, a post in your blog is treated like any time anybody shares a post from your blog. You own a post in your blog, just as you own a post which you share from your blog. You can control comments, when made directly against a post from your blog, as with a post shared from your blog.
If your blog uses Google+ Comments, you can moderate the comments by viewing comments on a post by post basis, and deleting what you don't like. You will get no ability to moderate comments before they are published - even if the comments are against your blog. Nor will you get notified when someone publishes a comment against a post in your blog.
Your blog has no comment moderation wizard, no settings for comment moderation, and no settings for comment notification, because you have no ability to moderate comments - nor do you get notifications.
Google+ is pretty much like real life. You can hear what people say about you, when you're in a real life conversation. You can't control what people say about you, behind your back - and you're generally better off not even knowing what people are saying about you, behind your back.
Concentrate on listening to what people tell you, or reading what they share with you. Ignore what you can't control, or hear. Get on with your life. Or, revert the blog, back to Blogger native comments.
>> Top
There is no option for comment moderation in my blog's settings. My Comments Settings only includes the option to change Location.and
I don't get notified about any comments published against my blog. There is no Setting for Comment Notification Email, either.These owners are discovering one of the design simplicities in Google+ Comments.
With Google+ Comments, anybody can post - and share - a reference to any content, on the Internet, that they can view. If your blog is public, any post from your blog can be shared in Google+.
If someone shares a post from your blog, and you are in a Circle where the post is shared, you may see the shared post in your Google+ stream. You have no control over content in your stream - even if the content references your blog - which you do not share.
You have no control over content about your blog, which you, yourself, do not share.
If somebody comments on a post shared from your blog, and you are in a Circle where the post is shared, you may see the comment in your stream. Again, you have no control over a comment made against a post in your stream - even if the comment references your blog.
In no case will you have the opportunity to moderate either a post, or a comment against a post, if someone else shares a reference to a post from your blog. Nor will you get a notification, if someone shares a reference to a post from your blog. Your blog is just one object of interest, from the millions of shares published by people in Google+.
If you, yourself, share content from your blog, you will own that share - you can control the content in the share - and you can control any comments placed against that share.
If someone reshares what you share, that reshare becomes the property of the person resharing. If you are in a Circle where your share is reshared, you may see the reshared post in your stream. Again, you will have no control over the reshare - or any comments placed against the reshare.
If you are not in a Circle where your share is reshared, you won't even see the reshare. Even if your blog is referenced in a reshare, your blog is just one object of interest, in the millions of shares published by people in Google+.
Notifications work the same way. If you share content from your blog, you will get Notification when someone comments against your share - or when someone reshares what you share. If someone else shares - or reshares - content from your blog, which you did not originate, you won't get a notification.
With Google+ Comments, a post in your blog is treated like any time anybody shares a post from your blog. You own a post in your blog, just as you own a post which you share from your blog. You can control comments, when made directly against a post from your blog, as with a post shared from your blog.
If your blog uses Google+ Comments, you can moderate the comments by viewing comments on a post by post basis, and deleting what you don't like. You will get no ability to moderate comments before they are published - even if the comments are against your blog. Nor will you get notified when someone publishes a comment against a post in your blog.
Your blog has no comment moderation wizard, no settings for comment moderation, and no settings for comment notification, because you have no ability to moderate comments - nor do you get notifications.
Google+ is pretty much like real life. You can hear what people say about you, when you're in a real life conversation. You can't control what people say about you, behind your back - and you're generally better off not even knowing what people are saying about you, behind your back.
Concentrate on listening to what people tell you, or reading what they share with you. Ignore what you can't control, or hear. Get on with your life. Or, revert the blog, back to Blogger native comments.
>> Top
Thursday, 20 June 2013
Custom Domains Purchase - "Buy a domain" Lacks The "Check Availability" Option
We're seeing a few reports from confused blog owners, in Blogger Help Forum: Something Is Broken, who want a non BlogSpot URL for their blog.
Several blog owners, in trying to use "Add a custom domain" to buy a domain, are observing that there is no "Check Availability" sequence.
Right now, the "Add a custom domain" link in the Publishing wizard simply goes straight to the "Advanced settings" option. This conflicts with Blogger supplied instructions.
Clicking on "Add a custom domain", we are immediately presented with "Advanced settings".
Right now, we're getting very terse advice from Blogger Support.
Until we hear more, I'll suggest use of eNom or GoDaddy, as advised. If you choose GoDaddy, you may be able to use the Blogger / GoDaddy DNS Setup wizard, to approximate the convenience of "Buy a domain". If you can't use the GoDaddy wizard, please note that the normal rules remain in full effect.
>> Top
I have tried to follow the guide, but my page does not say the same as the guide.
Several blog owners, in trying to use "Add a custom domain" to buy a domain, are observing that there is no "Check Availability" sequence.
Right now, the "Add a custom domain" link in the Publishing wizard simply goes straight to the "Advanced settings" option. This conflicts with Blogger supplied instructions.
In Blogger, locate the Publishing area under the Settings tab. Settings to Publishing.
Then, click the link to add a custom domain name, enter the domain name you'd like, and click Check Availability.
Clicking on "Add a custom domain", we are immediately presented with "Advanced settings". Right now, we're getting very terse advice from Blogger Support.
Blogger still supports custom domain hosting, though no longer offer an option to purchase domains within the product. To purchase a custom domain, please visit a third party registrar such as GoDaddy or eNom.
Until we hear more, I'll suggest use of eNom or GoDaddy, as advised. If you choose GoDaddy, you may be able to use the Blogger / GoDaddy DNS Setup wizard, to approximate the convenience of "Buy a domain". If you can't use the GoDaddy wizard, please note that the normal rules remain in full effect.
>> Top
Wednesday, 22 May 2013
The "Create a new blog" Wizard Is Not Prescient
We're seeing some odd problem reports in Blogger Help Forum: Something Is Broken, about blog creation.
What intrigues me here is not that people see
How do you explain that you have to type the entire name, and have that name checked, before giving up, disappointed?
Maybe the "Create a new blog" wizard is too good, for its own good.
Too much transparency actually makes it harder, for some people, to use it properly. Having the name checked for availability, as typed, one character at a time, may be a bit excessive.
Had I been creating this blog, long ago, as "bloggerstatusforreal.blogspot.com", I would have typed "bloggerstatusforreal" - and the "Create a new blog" would have checked, one by one
And I will bet good money, that I would have seen
Then again, even if "bloggerstatus" was taken, that does not say, for sure, that "bloggerstatu" was. Or "bloggerstat".
The bottom line here is that you have to type - and check - availability, one character at a time. And, you have to be persistent.
What would have happened, if I had given up, immediately.
Well, you would not be reading "bloggerstatusforreal.blogspot.com" now, would you?
>> Top
I entered just the first letter of the name which I wanted, and I immediately sawSorry, this blog address is not available.How am I supposed to create a blog, if all the names are taken?
What intrigues me here is not that people see
Sorry, this blog address is not available.It's that people don't ask the next question.
How did it know what name I was typing, before I finished?
How do you explain that you have to type the entire name, and have that name checked, before giving up, disappointed?
Maybe the "Create a new blog" wizard is too good, for its own good.
Too much transparency actually makes it harder, for some people, to use it properly. Having the name checked for availability, as typed, one character at a time, may be a bit excessive.
Had I been creating this blog, long ago, as "bloggerstatusforreal.blogspot.com", I would have typed "bloggerstatusforreal" - and the "Create a new blog" would have checked, one by one
- b
- bl
- blo
- blog
- blogg
- blogge
- blogger
- bloggers
- bloggerst
- bloggersta
- bloggerstat
- bloggerstatu
- bloggerstatus
- bloggerstatusf
- bloggerstatusfo
- bloggerstatusfor
- bloggerstatusforr
- bloggerstatusforre
- bloggerstatusforrea
- bloggerstatusforreal
And I will bet good money, that I would have seen
Sorry, this blog address is not available.during much of the typing.
- b Sorry, this blog address is not available.
- bl Sorry, this blog address is not available.
- blo Sorry, this blog address is not available.
- blog Sorry, this blog address is not available.
- blogg Sorry, this blog address is not available.
- blogge Sorry, this blog address is not available.
- blogger Sorry, this blog address is not available.
- bloggers Sorry, this blog address is not available.
- bloggerst Sorry, this blog address is not available.
- bloggersta Sorry, this blog address is not available.
- bloggerstat Sorry, this blog address is not available.
- bloggerstatu Sorry, this blog address is not available.
- bloggerstatus Sorry, this blog address is not available.
- bloggerstatusf
- bloggerstatusfo
- bloggerstatusfor
- bloggerstatusforr
- bloggerstatusforre
- bloggerstatusforrea
- bloggerstatusforreal
Then again, even if "bloggerstatus" was taken, that does not say, for sure, that "bloggerstatu" was. Or "bloggerstat".
- b Sorry, this blog address is not available.
- bl Sorry, this blog address is not available.
- blo Sorry, this blog address is not available.
- blog Sorry, this blog address is not available.
- blogg Sorry, this blog address is not available.
- blogge Sorry, this blog address is not available.
- blogger Sorry, this blog address is not available.
- bloggers Sorry, this blog address is not available.
- bloggerst Sorry, this blog address is not available.
- bloggersta Sorry, this blog address is not available.
- bloggerstat Sorry, this blog address is not available.
- bloggerstatu This blog address is available.
- bloggerstatus Sorry, this blog address is not available.
- bloggerstatusf This blog address is available.
- bloggerstatusfo This blog address is available.
- bloggerstatusfor This blog address is available.
- bloggerstatusforr This blog address is available.
- bloggerstatusforre This blog address is available.
- bloggerstatusforrea Sorry, this blog address is not available.
- bloggerstatusforreal Sorry, this blog address is not available.
The bottom line here is that you have to type - and check - availability, one character at a time. And, you have to be persistent.
What would have happened, if I had given up, immediately.
- b Sorry, this blog address is not available.
Well, you would not be reading "bloggerstatusforreal.blogspot.com" now, would you?
>> Top
Friday, 10 May 2013
Comment Moderation In Blogger Blogs, Using Google+ Comments
With more Blogger blogs being updated to use Google+ Comments, we're seeing a few questions in Blogger Help Forum: How Do I?, about comment moderation.
This is a question for which there is no easy answer - and this is one of the least appreciated feature limitations of Google+ Comments.
Native Blogger commenting allowed the option to moderate comments before or after they were published.
Google+ Comments, for Blogger blogs, provides no ability to moderate before publishing. All comments must be moderated after they are published. Moderation now simply consists of the ability to declare a comment as abusive - and this ability is shared equally by all users of Google+, who are in the right Circle to read and mark any comment.
With native Blogger Commenting, you (the blog administrator / owner) could moderate comments (before or after publishing), using either email, or the dashboard Comments section. With Google+ Comments, you have no such ability - and the dashboard won't even have a Comments section, listing comments made against the blog. You can view comments made - when you are able to view them - on a post by post basis, under each post.
As the blog owner, you do not have control over all comments, published against your blog. If you allow comments using Google+, anybody who is in one of your Circles can publish a comment against your blog. If you Share a blog post to the Public - or if someone else Shares a post from your blog to the Public - and a third person comments, you may not even see the comment made, against your blog.
You cannot see comments published by people who are not in your Circles, unless the comments are posted Publicly - even if the comments are published against your blog.
For these reasons, this blog remains with Blogger Commenting.
We have a Problem Rollup discussion where we are soliciting feedback from each blog owner, who sees this new feature - Google+ Comments - to be unacceptable as designed. If you are able to provide your opinion, in the rollup discussion, please keep your remarks brief and polite - and stay on topic.
>> Top
How do I moderate comments, with Google+ Comments enabled on my blog?
This is a question for which there is no easy answer - and this is one of the least appreciated feature limitations of Google+ Comments.
Native Blogger commenting allowed the option to moderate comments before or after they were published.
Google+ Comments, for Blogger blogs, provides no ability to moderate before publishing. All comments must be moderated after they are published. Moderation now simply consists of the ability to declare a comment as abusive - and this ability is shared equally by all users of Google+, who are in the right Circle to read and mark any comment.
With native Blogger Commenting, you (the blog administrator / owner) could moderate comments (before or after publishing), using either email, or the dashboard Comments section. With Google+ Comments, you have no such ability - and the dashboard won't even have a Comments section, listing comments made against the blog. You can view comments made - when you are able to view them - on a post by post basis, under each post.
As the blog owner, you do not have control over all comments, published against your blog. If you allow comments using Google+, anybody who is in one of your Circles can publish a comment against your blog. If you Share a blog post to the Public - or if someone else Shares a post from your blog to the Public - and a third person comments, you may not even see the comment made, against your blog.
You cannot see comments published by people who are not in your Circles, unless the comments are posted Publicly - even if the comments are published against your blog.
For these reasons, this blog remains with Blogger Commenting.
We have a Problem Rollup discussion where we are soliciting feedback from each blog owner, who sees this new feature - Google+ Comments - to be unacceptable as designed. If you are able to provide your opinion, in the rollup discussion, please keep your remarks brief and polite - and stay on topic.
>> Top
Friday, 19 April 2013
Problems Being Observed, In Blogs Now Using Google+ Comments
A few blog owners, eagerly opting to use the latest Blogger enhancement, Google+ Comments, are seeing some changes which they did not anticipate.
Even after checking all of the settings, some blogs, with Google+ Comments enabled, may not show the comment form - or may show the form, but comments may not be visible. Besides the visibility of the form, there are other changes which some blog owners don't appreciate.
In many cases, Google+ Comments, like other new features, require an updated post template. This will be seen in blogs with customised post templates, most frequently - although newer, less customised blogs also may need a post template reset.
After getting Google+ Comments working in general, some blog owners find other unexpected changes.
Fortunately, in most cases any prematurely made decisions are reversible. Go to the dashboard Google+ menu entry, and unselect "Use Google+ Comments on this blog". The blog will simply return to native Blogger based Comments. Any comments made under Google+ will not be visible to you, from the blog - but everything else should return to normal.
I've now added a Problem Rollup discussion, in Blogger Help Forum: Feature Suggestions and Feedback, where your opinion is appreciated. Please be objective.
See my test blogs Google+ Comments, Dynamic Template Test and Google+ Comments, Simple Template Test if you wish.
Click here, for instructions to revert back to Blogger based comments. Note that you will lose ability to view all Google+ based comments - though the comments will still exist.
>> Top
Even after checking all of the settings, some blogs, with Google+ Comments enabled, may not show the comment form - or may show the form, but comments may not be visible. Besides the visibility of the form, there are other changes which some blog owners don't appreciate.
In many cases, Google+ Comments, like other new features, require an updated post template. This will be seen in blogs with customised post templates, most frequently - although newer, less customised blogs also may need a post template reset.
After getting Google+ Comments working in general, some blog owners find other unexpected changes.
- Almost the entire "Comments" section, in the dashboard Settings - "Posts and comments" wizard, will disappear - though "Comment Location" will remain - and will default to "Embedded". None of these settings are relevant in Google+ Comments. On some blogs, there may be no "Comments" dashboard menu entry at all.
- There are no controls for moderation, or for notification, of comments.
- There is no ability to moderate comments, from the dashboard. Moderation is done under each post, one post at a time.
- As a blog owner, you have no special ability to moderate comments, made against your blog.
- There may be some comments, which you may not be able to moderate - but will publish against your blog.
- If you Block somebody from Following you, that person may still be able to post a Comment on your blog. When you look at the comments, you will only see
This post is hidden because you have blocked the author.
- People without Google+ accounts won't be able to make - or view - comments (since comments are Circle dependent).
- Visibility of the comment form, as with all embedded comments, is sensitive to cookie / script filters, on the client computers.
- Comments posted outside Google Comments may not be immediately visible, though the comments remain in existence. Resetting various sections of the template may resolve this, when observed.
- If you change the blog address - with either a simple BlogSpot address change, a non BlogSpot address republishing (aka "custom domain"), or export / import - existing Google+ Comments may not remain visible, with the blog. This may be a similar problem, with URLs subject to Country Code Aliasing.
- With a blog using Google+ Comments, the Comments newsfeed will not be published. Any "Recent Comments" gadgets will be useless.
- The "Export blog" wizard, which used to export both comments and posts, will only export posts.
- The comment count, as displayed in the blog main page display, may show "0 comments" - even with comments actually present, and visible when clicking on "0 comments".
- You may or may not get email notification of comments, when comments are not shared specifically with you - even if you own the blog. Other people, who do not own the blog, may get notifications when you do not.
Fortunately, in most cases any prematurely made decisions are reversible. Go to the dashboard Google+ menu entry, and unselect "Use Google+ Comments on this blog". The blog will simply return to native Blogger based Comments. Any comments made under Google+ will not be visible to you, from the blog - but everything else should return to normal.
I've now added a Problem Rollup discussion, in Blogger Help Forum: Feature Suggestions and Feedback, where your opinion is appreciated. Please be objective.
See my test blogs Google+ Comments, Dynamic Template Test and Google+ Comments, Simple Template Test if you wish.
Click here, for instructions to revert back to Blogger based comments. Note that you will lose ability to view all Google+ based comments - though the comments will still exist.
>> Top
Saturday, 23 March 2013
If You Use CAPTCHA Screening On Your Blog, Try Publishing A Comment, As A Guest
Not all Blogger blog owners, using CAPTCHA screening to reduce abusive comments on their blogs, know first hand what the typical CAPTCHA puzzle can be like.
We're seeing a few concerned blog owners, in Blogger Help Forum: Something Is Broken, asking why they're seeing fewer comments on their blogs.
Not all blog owners bother to test the CAPTCHA, on their blogs - or even know why they don't see one, when commenting.
Not all blog owners, enabling Word verification in their blog commenting settings, bother to read the tool tip behind the "?".
This leaves many blog owners unaware of how frustrating it may be, for their guests to comment, on their blogs.
If you're a blog owner, musing whether to add word verification to your blog, in an effort to cut down on the spamming and trolling going on in many blog comment threads, maybe you should try posting on your blog, as a guest. With "Show word verification" set to "Yes", logout from Blogger - or clear cache, cookies, and sessions (yes, all 3!) - then restart the browser, and try leaving a comment on your blog.
What you discover may not please you. Then ask yourself how many of your readers will have the patience, to solve a CAPTCHA, every time they wish to publish a comment?
As a blog owner, you have 3 settings which are used, in proper combination, to provide a safe environment for your readers to leave comments.
>> Top
We're seeing a few concerned blog owners, in Blogger Help Forum: Something Is Broken, asking why they're seeing fewer comments on their blogs.
I'm hearing from people that they can't post comments on my blog. I tested, and comments are working just fine. What is the problem, here?
Not all blog owners bother to test the CAPTCHA, on their blogs - or even know why they don't see one, when commenting.
Not all blog owners, enabling Word verification in their blog commenting settings, bother to read the tool tip behind the "?".
Show word verificationThe simple advice
This will require people leaving comments on your blog to complete a word verification step, which will help reduce comment spam. Learn more.
Blog authors will not see word verification for comments.
Blog authors will not see word verification for comments.does not sink in, to everybody.
This leaves many blog owners unaware of how frustrating it may be, for their guests to comment, on their blogs.
If you're a blog owner, musing whether to add word verification to your blog, in an effort to cut down on the spamming and trolling going on in many blog comment threads, maybe you should try posting on your blog, as a guest. With "Show word verification" set to "Yes", logout from Blogger - or clear cache, cookies, and sessions (yes, all 3!) - then restart the browser, and try leaving a comment on your blog.
What you discover may not please you. Then ask yourself how many of your readers will have the patience, to solve a CAPTCHA, every time they wish to publish a comment?
As a blog owner, you have 3 settings which are used, in proper combination, to provide a safe environment for your readers to leave comments.
- Authentication.
- CAPTCHA Screening.
- Moderation.
>> Top
Friday, 22 March 2013
Renaming Your Blog Requires Choosing An Available Blog Name
Like creating a blog, the task of renaming your blog involves one very important step - choosing an available blog name.
When you rename your blog - as in change the blog address - you have to pick a name (address) that's not in use. Both creating a blog, and renaming a blog, suffer from one key detail - you can't identify an available address before you get started.
When you create, or rename, a blog, you can only get to the task at hand, and start with the best choice.
Like "Create a blog", you'll only find out about an available URL after you have successfully chosen that URL for your blog. Unlike "Create a blog", the Blog Address wizard does not verify availability in real time.
If you want to do the rename with the least stress, you make a list of possible choices before you start, and sort the list in decreasing preference. Decide which names you like the most, before you start. Then start the above process with Step #1, and your top choice. If you end at Step #4, pick the next choice in the list, and go to Step #1, again.
As with "Create a blog", you should plan to go through your list as promptly as possible. Hesitate too long, when making the next choice, and your alternate choices could be unavailable.
If your choice of name will affect design work on the existing blog, yet you wish to change the blog design before renaming the blog, setup a stub blog - and pick the best available name for the stub blog, now. Once that's done, make the necessary design changes on your current blog - then swap names between the stub blog and your current blog. You'll likely use the stub blog, later.
As with creating a new blog, please note that addresses previously taken will not be reissued to you by Blogger - a 10 year old blog remains valid, whether published once daily for 10 years, or once 10 years ago and never again.
And as soon as you get the new name successfully chosen, be prepared to continue the renaming process, as promptly as possible.
>> Top
When you rename your blog - as in change the blog address - you have to pick a name (address) that's not in use. Both creating a blog, and renaming a blog, suffer from one key detail - you can't identify an available address before you get started.
When you create, or rename, a blog, you can only get to the task at hand, and start with the best choice.
Like "Create a blog", you'll only find out about an available URL after you have successfully chosen that URL for your blog. Unlike "Create a blog", the Blog Address wizard does not verify availability in real time.
- Paste or type the desired blog name (Only the "yyyyyyy" in "yyyyyyy.blogspot.com").
- Hit Save.
- If the name was available, you'll be looking at the initial Blog Address display, with the new address "yyyyyyy.blogspot.com" identified - and "yyyyyyy" will now be unavailable.
- If the name is not available, you'll get the sad news
Subdomain: yyyyyyy is not available.
And now, go back to Step #1, and try again.
If you want to do the rename with the least stress, you make a list of possible choices before you start, and sort the list in decreasing preference. Decide which names you like the most, before you start. Then start the above process with Step #1, and your top choice. If you end at Step #4, pick the next choice in the list, and go to Step #1, again.
As with "Create a blog", you should plan to go through your list as promptly as possible. Hesitate too long, when making the next choice, and your alternate choices could be unavailable.
If your choice of name will affect design work on the existing blog, yet you wish to change the blog design before renaming the blog, setup a stub blog - and pick the best available name for the stub blog, now. Once that's done, make the necessary design changes on your current blog - then swap names between the stub blog and your current blog. You'll likely use the stub blog, later.
As with creating a new blog, please note that addresses previously taken will not be reissued to you by Blogger - a 10 year old blog remains valid, whether published once daily for 10 years, or once 10 years ago and never again.
And as soon as you get the new name successfully chosen, be prepared to continue the renaming process, as promptly as possible.
>> Top
Saturday, 9 March 2013
Confusion About The Post Feed Redirect Feature
The world of Blogger blogs contains a lot of confusing terminology.
Some Blogger features don't even have names. Some names, which I use, are terms which I made up on my own, years ago - simply because Blogger did not provide a name, at that time. One term, which Blogger did give us, still causes confusion. The term "Post Feed Redirect" seems to describe an option, in Blogger, to redirect the post feed to a different URL.
The Post Feed Redirect feature is used by some confused blog owners, improperly. There are several specific cases, all too common.
This redirection, contrary to the term "Post Feed", also affects the comments feeds and the labels feeds, relevant to the blog where the setting is used.
Besides the fact that the option in question affects all feeds in the blog, the biggest confusion is that using the option does not actually redirect the feed - it redirects the references to the feed. People use this option in the expectation that it will change the URL of the feed. This option does not change the URL of the feed - it changes the URL used by references to the feed.
To change the feed references, successfully, you must have the URL mentioned by the setting already published, in a separate effort.
If you are reading this post, look down the page, after the "Newer Post Home Older Post" links.
There is an example of the original feed reference. The purpose of the post feed redirect feature, long ago, was to let the blog owners generate a different feed for the blog - maybe a FeedBurner republished post feed - and force that link to reference the FeedBurner republished feed.
If you use that link, and subscribe to the feed from this blog, you should get a subscription offer, using the FeedBurner feed for this blog.
The Post Feed Redirect simply lets people setup and use an alternate feed URL, without having to update the code for all links which reference the post feed - such as that link.
That's it - pure and simple.
If you have - even unintentionally - misused the post feed redirect in your blog, it's easy to correct the mistake. Just understand why you should correct the mistake.
>> Top
Some Blogger features don't even have names. Some names, which I use, are terms which I made up on my own, years ago - simply because Blogger did not provide a name, at that time. One term, which Blogger did give us, still causes confusion. The term "Post Feed Redirect" seems to describe an option, in Blogger, to redirect the post feed to a different URL.
The Post Feed Redirect feature is used by some confused blog owners, improperly. There are several specific cases, all too common.
- Change the URL of the feed. Redirecting the blog feed, to simply change the URL, causes the feed to redirect to non existent content - or a dead feed.
- Publishing the blog to a non BlogSpot URL. Custom domain publishing provides automatic redirection of the blog URL - and by extension, the blog feed URL. Adding a feed redirect causes an infinite loop.
- Randomly expose the blog to new audiences. Redirecting the blog feed to a random redirector causes the blog readers to report a hijacked Reading List - and later, to simply remove the blog, using a redirected feed, from the Reading List.
This redirection, contrary to the term "Post Feed", also affects the comments feeds and the labels feeds, relevant to the blog where the setting is used.
Besides the fact that the option in question affects all feeds in the blog, the biggest confusion is that using the option does not actually redirect the feed - it redirects the references to the feed. People use this option in the expectation that it will change the URL of the feed. This option does not change the URL of the feed - it changes the URL used by references to the feed.
To change the feed references, successfully, you must have the URL mentioned by the setting already published, in a separate effort.
- If you renamed the blog to a different BlogSpot URL, you can redirect the feed reference, from a stub blog, to the feed published under the new URL.
- If you used a different service, like FeedBurner, to create a reformatted feed replica, you can redirect the feed reference to the FeedBurner feed URL.
- In either case, the URL has to exist, from a separate effort.
If you are reading this post, look down the page, after the "Newer Post Home Older Post" links.
Subscribe to: Post Comments (Atom)
There is an example of the original feed reference. The purpose of the post feed redirect feature, long ago, was to let the blog owners generate a different feed for the blog - maybe a FeedBurner republished post feed - and force that link to reference the FeedBurner republished feed.
If you use that link, and subscribe to the feed from this blog, you should get a subscription offer, using the FeedBurner feed for this blog.
The Post Feed Redirect simply lets people setup and use an alternate feed URL, without having to update the code for all links which reference the post feed - such as that link.
That's it - pure and simple.
If you have - even unintentionally - misused the post feed redirect in your blog, it's easy to correct the mistake. Just understand why you should correct the mistake.
>> Top
Clear, Or Set, The Post Feed Redirect
One of the most mysterious settings, in our blogs, is the ability to redirect references to the blog feed.
Some people use the "Post Feed Redirect" setting improperly. When this is done, the problems created can be easily solved, by clearing the setting.
If you actually need this setting, it's similarly simple to set it.
Just understand what the setting does, how to enter the setting, and when you should use it.
>> Top
Some people use the "Post Feed Redirect" setting improperly. When this is done, the problems created can be easily solved, by clearing the setting.
- Go to the dashboard menu Settings - Other - Site feed.
- Look at the entry for "Post Feed Redirect URL".
- If that option is incorrectly set, click on "Remove".
- Click on "Save settings".
- You're done.
If you actually need this setting, it's similarly simple to set it.
- Go to the dashboard menu Settings - Other - Site feed.
- Look at the entry for "Post Feed Redirect URL".
- If that option needs to be set, click on "Add".
- Paste or type the correct URL, into the box.
- Click on "Save settings".
- You're done.
http://feeds.feedburner.com/Nitecruzr-Blogging
Just understand what the setting does, how to enter the setting, and when you should use it.
>> Top
Wednesday, 13 February 2013
Control The Email Settings, Relevant To Your Blog, Wisely
Some blog owners don't always think about the various email settings, which are part of their Blogger blogs, and the possible effects to their email - or somebody else's email.
There are several settings, where a blog owner may enter an email address.
There are several Blogger dashboard settings - related to post publication and to various commenting activities - with differing effect to one's own, or somebody else's, email.
Unlike various subscription services which use email, such as a FeedBurner Email Subscription service, an email address added to any of these three settings requires no formal acceptance. If a blog administrator should add an email address, whether their own (primary or additional personal email address), a willing friend or relative, or an unknown victim's address, there is no initial email sent to the recipient
The "Email posts to" feature, also known as "BlogSend", generates a minimally formatted text copy of each post, when published, to up to 10 email addresses. This setting has been used, in the past, to provide distribution of newly published posts for private blogs, as well as a simple distribution for posts from public blogs.
Since it's limited to 10 entries, BlogSend does not provide a suitable service for any blog with a reader population of any appreciable size. For a blog owner with any technical experience, FeedBurner Email Distribution is a much better solution for post distribution - when the blog in question is publicly accessible.
For distribution of a private blog to more than 10 readers, one may use Google+.
The "Comment Moderation" and "Comment Notification Email" settings, used together, can generate interesting duplication of email to one's own (or somebody else's) email service. If these settings are made without thinking, some interesting confusion can result. Email addresses can be added to each of these settings without consideration of the relationship or level of authority enjoyed by the owner of the email address, relative to the blog in question.
Comment Moderation Email is presumed to generally be a function performed by blog administrators - but email resulting from this setting will be sent to anybody addressed. A blog administrator / member - or other non administrator of the blog or an unwitting stranger - will receive email suggesting several options,
Comment Notification Email might be generally addressed to blog members - but is not necessarily limited. Since notification of comments is sent separately from moderation, recipients of a notification can become confused when they fail to find the comment, mentioned in the notification, present on the blog. A blog administrator, using either an email moderation message - or using the blog Comments wizard, may or may not decide to Publish - or to designate a comment as Spam - regardless of a notification message having been delivered to each designated recipient.
Comment notification email may look similar to comment moderation email, less the comment processing options - possibly causing more confusion. A blog owner, adding his own email address to both comment moderation and comment notification, may see the combination as unknown duplication. And blog owners may confuse the proper use of comment moderation and comment notification email.
A blog owner, transferring ownership of a given blog, may overlook updating of the email settings. A new blog owner, receiving a blog being transferred, may likewise overlook these settings, and may lack the associated email, until the omission is corrected.
Either the previous owner, or the new owner, may be confused temporarily - and may wonder why they are still getting email / not getting email, until they examine and correct the setting in question. Alternately, if someone's email address was added maliciously, by a blog owner intending to harass somebody, one can see interesting possibility for conflict.
>> Top
There are several settings, where a blog owner may enter an email address.
- Email posts to
- Comment Moderation.
- Comment Notification Email.
There are several Blogger dashboard settings - related to post publication and to various commenting activities - with differing effect to one's own, or somebody else's, email.
- Settings - "Mobile and email" - "Email posts to" generates a minimally formatted text copy of each post, when published, to up to 10 email addresses.
- Settings - "Posts and comments" - "Comment Moderation" generates a minimally formatted copy of each incoming comment, before the comment is published - and allows moderation of the comment, while reading the email message - when the recipient has the proper authority.
- Settings - "Mobile and email" - "Comment Notification Email" generates a minimally formatted copy of each incoming comment, before the comment is published or rejected.
Unlike various subscription services which use email, such as a FeedBurner Email Subscription service, an email address added to any of these three settings requires no formal acceptance. If a blog administrator should add an email address, whether their own (primary or additional personal email address), a willing friend or relative, or an unknown victim's address, there is no initial email sent to the recipient
You (or somebody else) has added this email address as a recipient of "Email posts to" / "Comment Moderation" / "Comment Notification Email". Do you approve of this additional traffic source to your email service?or a similarly worded notification / approval. Given a clueless or malicious blog owner, it's possible that one (or all) of these settings could be used to harass an unwitting third party.
The "Email posts to" feature, also known as "BlogSend", generates a minimally formatted text copy of each post, when published, to up to 10 email addresses. This setting has been used, in the past, to provide distribution of newly published posts for private blogs, as well as a simple distribution for posts from public blogs.
Since it's limited to 10 entries, BlogSend does not provide a suitable service for any blog with a reader population of any appreciable size. For a blog owner with any technical experience, FeedBurner Email Distribution is a much better solution for post distribution - when the blog in question is publicly accessible.
For distribution of a private blog to more than 10 readers, one may use Google+.
The "Comment Moderation" and "Comment Notification Email" settings, used together, can generate interesting duplication of email to one's own (or somebody else's) email service. If these settings are made without thinking, some interesting confusion can result. Email addresses can be added to each of these settings without consideration of the relationship or level of authority enjoyed by the owner of the email address, relative to the blog in question.
Comment Moderation Email is presumed to generally be a function performed by blog administrators - but email resulting from this setting will be sent to anybody addressed. A blog administrator / member - or other non administrator of the blog or an unwitting stranger - will receive email suggesting several options,
PublishIf the recipient is not an actual blog administrator, the links in the email provide confusion, and no result.
Delete
Mark as spam
Moderate comments for this blog.
Comment Notification Email might be generally addressed to blog members - but is not necessarily limited. Since notification of comments is sent separately from moderation, recipients of a notification can become confused when they fail to find the comment, mentioned in the notification, present on the blog. A blog administrator, using either an email moderation message - or using the blog Comments wizard, may or may not decide to Publish - or to designate a comment as Spam - regardless of a notification message having been delivered to each designated recipient.
Comment notification email may look similar to comment moderation email, less the comment processing options - possibly causing more confusion. A blog owner, adding his own email address to both comment moderation and comment notification, may see the combination as unknown duplication. And blog owners may confuse the proper use of comment moderation and comment notification email.
A blog owner, transferring ownership of a given blog, may overlook updating of the email settings. A new blog owner, receiving a blog being transferred, may likewise overlook these settings, and may lack the associated email, until the omission is corrected.
Either the previous owner, or the new owner, may be confused temporarily - and may wonder why they are still getting email / not getting email, until they examine and correct the setting in question. Alternately, if someone's email address was added maliciously, by a blog owner intending to harass somebody, one can see interesting possibility for conflict.
>> Top
Friday, 1 February 2013
How You Should Backup Your Blog Will Depend Upon How You Plan To Restore It
We see signs of naivete, in Blogger Help Forum: How Do I?, from blog owners concerned with malware / spam deletions, and with other unexplained disasters in Blogger.
Not many concerned blog owners realise the first principle of backups, known by any experienced network administrator.
One of the simplest solutions for a backup, which some Blogger experts will suggest, is to use the Export / Import wizard, in Settings - Other.
Similarly, some experts may suggest backing up the template.
There are many components of a Blogger blog - not just the comments, posts, and template.
The accessories (decorations, gadgets) is one component of the blog which is most frequently missed, after a deleted blog is recreated / restored using a "comments / posts / template backup" restore strategy. Both graphic decorations, and XML based gadgets, may not be easily backed up, and may present a challenge when the blog is restored, or recreated.
XML gadgets, such as bloglists and linklists, may contain a lot of detail, which is installed into the blog one entry at a time - and there is no known way to automate a backup or restore of these gadgets.
Recovering the URL is one of the most subtle details, that may not always be considered by many blog owners. The URL is relevant in two ways. Most blogs which are important enough, for the owner to want to backup, have acquired reputation - both with people (readers, subscribers, and viewers), and with search engines.
Some blogs will link the various posts to each other - as I do with this blog. In either case, the recovered blog is not as useful, unless the URL is also recovered.
If the blog is deleted by Blogger - or by the owner - the URL may not be available, for blog recovery. When Blogger deletes a blog as a suspected abusive content host, the URL is locked to the blog. The only way to recover the URL is to have the blog reviewed, and restored to availability.
When a blog is deleted by the owner, the blog must be restored by the owner - within 90 days after deletion. In either case, a backup is useless.
If you have a personal blog, containing just posts (and maybe comments from known family or friends), backing up the comments and posts makes sense. For a publicly known blog, containing various accessories, and having a known URL, you'll want to plan your backup / restore strategy using a bit more effort.
>> Top
How do I backup my blog, to protect the contents against unfair spam deletions?
Not many concerned blog owners realise the first principle of backups, known by any experienced network administrator.
- Never plan a backup, without first planning the restore.
- What problem do you expect, to require a backup?
- How do you plan to recover, from a problem?
One of the simplest solutions for a backup, which some Blogger experts will suggest, is to use the Export / Import wizard, in Settings - Other.
- Before disaster strikes, Export your posts and comments.
- After disaster strikes, simply Import your posts and comments, from a convenient backup.
Similarly, some experts may suggest backing up the template.
- Before disaster strikes, use the dashboard Template "Backup / Restore" wizard, to backup the template.
- After disaster strikes, use the wizard to restore the template.
There are many components of a Blogger blog - not just the comments, posts, and template.
- Accessories.
- Comments.
- Decorations.
- Gadgets.
- Posts.
- Layout.
- URL.
The accessories (decorations, gadgets) is one component of the blog which is most frequently missed, after a deleted blog is recreated / restored using a "comments / posts / template backup" restore strategy. Both graphic decorations, and XML based gadgets, may not be easily backed up, and may present a challenge when the blog is restored, or recreated.
XML gadgets, such as bloglists and linklists, may contain a lot of detail, which is installed into the blog one entry at a time - and there is no known way to automate a backup or restore of these gadgets.
Recovering the URL is one of the most subtle details, that may not always be considered by many blog owners. The URL is relevant in two ways. Most blogs which are important enough, for the owner to want to backup, have acquired reputation - both with people (readers, subscribers, and viewers), and with search engines.
Some blogs will link the various posts to each other - as I do with this blog. In either case, the recovered blog is not as useful, unless the URL is also recovered.
If the blog is deleted by Blogger - or by the owner - the URL may not be available, for blog recovery. When Blogger deletes a blog as a suspected abusive content host, the URL is locked to the blog. The only way to recover the URL is to have the blog reviewed, and restored to availability.
When a blog is deleted by the owner, the blog must be restored by the owner - within 90 days after deletion. In either case, a backup is useless.
If you have a personal blog, containing just posts (and maybe comments from known family or friends), backing up the comments and posts makes sense. For a publicly known blog, containing various accessories, and having a known URL, you'll want to plan your backup / restore strategy using a bit more effort.
>> Top
Thursday, 31 January 2013
Blogger Blogs And Commenting Permissions
Not all Blogger blog owners know that the ability to comment, like the ability to publish and read posts, is a privilege which they control - and a responsibility which they need to control, carefully.
Any blog owner who wishes to publish a blog, and not be subject to frequent deletion of the blog, as a suspected malware or spam host, needs to understand the responsibilities, and the risks.
There are levels of ability to post comments to a blog, which you select from the dashboard Settings - "Posts and comments" wizard. Protect yourself, if you allow comments.
If you allow comments by "Anyone", prepare to deal with the spam. Note that anonymous users can post either anonymously, or using "Name / URL" tags, at their discretion, with "Anyone" selected. "Name / URL" does not provide authentication. "Anyone" means anyone, period.
Besides "Who can comment?", you may also control comment publishing using CAPTCHA (aka "word verification") screening, and using comment moderation. These settings, like "Who can comment?", are part of the Settings - "Posts and comments" wizard.
Every blog owner, hoping for any visibility in the Blogosphere, needs to choose these settings carefully - or risk being buried by spam.
Comment Moderation, and Comment Notification Email, together, provide 2 settings which can bury your email Inbox, depending upon activity of commenting on your blog. Choose these settings wisely.
If you allow spam comments without control, you may later find yourself asking for help, in Blogger Help Forum: Something Is Broken
>> Top
Any blog owner who wishes to publish a blog, and not be subject to frequent deletion of the blog, as a suspected malware or spam host, needs to understand the responsibilities, and the risks.
There are levels of ability to post comments to a blog, which you select from the dashboard Settings - "Posts and comments" wizard. Protect yourself, if you allow comments.
- Anyone - includes Anonymous Users.
- Everybody with a Google, or an OpenID, account.
- Everybody with a Google account.
- Blog members only.
- Comments disabled.
If you allow comments by "Anyone", prepare to deal with the spam. Note that anonymous users can post either anonymously, or using "Name / URL" tags, at their discretion, with "Anyone" selected. "Name / URL" does not provide authentication. "Anyone" means anyone, period.
Besides "Who can comment?", you may also control comment publishing using CAPTCHA (aka "word verification") screening, and using comment moderation. These settings, like "Who can comment?", are part of the Settings - "Posts and comments" wizard.
Every blog owner, hoping for any visibility in the Blogosphere, needs to choose these settings carefully - or risk being buried by spam.
- Who can comment?
- Comment Moderation.
- Comment Notification Email.
- Show word verification
Comment Moderation, and Comment Notification Email, together, provide 2 settings which can bury your email Inbox, depending upon activity of commenting on your blog. Choose these settings wisely.
If you allow spam comments without control, you may later find yourself asking for help, in Blogger Help Forum: Something Is Broken
Help me! My blog was deleted by Blogger!Protect your blog, and your blog's future, by allowing comments, responsibly.
>> Top
Sunday, 27 January 2013
Blogger Magic - Republishing A Custom Domain Published Blog
Sometimes, when you have a Blogger blog, published to a non BlogSpot URL, you may need to repeat the publishing process.
Maybe, you want to change the BlogSpot or domain URL - or maybe the previous publishing did not complete, properly. If the blog is currently published to a non BlogSpot URL, you can't just publish it, again. You have to start by publishing the blog back to a BlogSpot URL, before you can again publish the blog to a non BlogSpot URL.
Given the right planning, and understanding of the tasks involved, you can do all of this in 5 minutes - less time than it will probably take you to read these instructions.
The republishing process is not complicated.
To publish the blog back to BlogSpot, you'll use the Blogger dashboard Publishing wizard, at Settings - Basic.
While the blog is (temporarily) published to BlogSpot, make any necessary changes. Maybe, change the BlogSpot URL.
To publish this blog (or another Blogger blog that you own) to a domain URL:
Use the available and working redirect setting, to enable the domain root redirect, if necessary.
When you publish to a domain URL, you may have to add domain ownership verification. In this case, you'll need access to the Zone Editor wizard, provided by the registrar. If you originally used "Buy a domain" to purchase the domain, you'll need access to Google Apps, to access the registrar login instructions.
Other than the domain ownership verification, the republishing process is just a matter of 1 - 2 - 3 (maybe - 4). Having done this, be aware of the possible search engine relationship issues.
>> Top
Maybe, you want to change the BlogSpot or domain URL - or maybe the previous publishing did not complete, properly. If the blog is currently published to a non BlogSpot URL, you can't just publish it, again. You have to start by publishing the blog back to a BlogSpot URL, before you can again publish the blog to a non BlogSpot URL.
Given the right planning, and understanding of the tasks involved, you can do all of this in 5 minutes - less time than it will probably take you to read these instructions.
The republishing process is not complicated.
- Publish the blog back to BlogSpot.
- If necessary, make any necessary changes in BlogSpot.
- Publish the blog to a domain URL.
- If necessary, enable the domain root redirect setting.
To publish the blog back to BlogSpot, you'll use the Blogger dashboard Publishing wizard, at Settings - Basic.
- Look at the Publishing display.
- If the blog is published to a custom domain, click on the "X".
- If the "X" is not visible, you'll need to know where it should be - and you can click where it should be visible.
- If the blog is currently published to a BlogSpot URL, you may skip this step.
- If the final objective was to return the blog to BlogSpot, you are now done.
While the blog is (temporarily) published to BlogSpot, make any necessary changes. Maybe, change the BlogSpot URL.
To publish this blog (or another Blogger blog that you own) to a domain URL:
- Return to the Publishing wizard, for the blog in question, and click on "Add a custom domain".
- Publish the blog back to an already purchased or used domain URL, by clicking on "Switch to advanced settings".
- Alternately, purchase a different domain, using "Buy a domain for your blog".
- If you use the most common DNS addressing, aka "asymmetrical DNS addresses", be sure to only publish to the "www" alias.
Use the available and working redirect setting, to enable the domain root redirect, if necessary.
When you publish to a domain URL, you may have to add domain ownership verification. In this case, you'll need access to the Zone Editor wizard, provided by the registrar. If you originally used "Buy a domain" to purchase the domain, you'll need access to Google Apps, to access the registrar login instructions.
Other than the domain ownership verification, the republishing process is just a matter of 1 - 2 - 3 (maybe - 4). Having done this, be aware of the possible search engine relationship issues.
>> Top
Saturday, 26 January 2013
Blogger Magic - Redirecting A URL In Your Blog
In 2012, Blogger gave us a suite of useful utilities to control how the search engines see our blogs. This includes the ability to redirect one URL in our blog to another URL in our blog.
The "Custom Redirects" feature is easy to use - but like many Blogger features, not immediately so. Neither its possibilities, nor its limitations, are obvious to everybody.
Custom Redirects, which is part of the dashboard Search Preferences wizard, is not difficult to use.
The possibilities are almost endless, when you reference any valid URL in a given blog. Thanks to the syntax of the "From" and "To" values in the wizard, Custom Redirects will only redirect within the blog itself, and is thus useless to spammers and others who would like to misuse it.
Just take any two URLs within the blog, strip the base URL from each, and enter the results as the "From" and "To" values. Always start "From" and "To" with a "/" (no leading spaces, or non visible control characters!), signifying the root of the URL, follow the above procedure, and you're done.
Click here, for examples of what you can do. Then, use your imagination. Just remember though - the actual URL - and what your readers see in the address window - will not change.
>> Top
The "Custom Redirects" feature is easy to use - but like many Blogger features, not immediately so. Neither its possibilities, nor its limitations, are obvious to everybody.
Custom Redirects, which is part of the dashboard Search Preferences wizard, is not difficult to use. - Go to Settings - Search preferences - Custom Redirects, and click on Edit.
- If you have existing redirects, click on "New redirect".
- Enter the correct "From" and "To" values.
- Select "Permanent".
- Click on "Save".
- Click on "Save changes".
The possibilities are almost endless, when you reference any valid URL in a given blog. Thanks to the syntax of the "From" and "To" values in the wizard, Custom Redirects will only redirect within the blog itself, and is thus useless to spammers and others who would like to misuse it.
Just take any two URLs within the blog, strip the base URL from each, and enter the results as the "From" and "To" values. Always start "From" and "To" with a "/" (no leading spaces, or non visible control characters!), signifying the root of the URL, follow the above procedure, and you're done.
Click here, for examples of what you can do. Then, use your imagination. Just remember though - the actual URL - and what your readers see in the address window - will not change.
>> Top
Subscribe to:
Posts (Atom)
