Social Sharing Popularity, And URL Changes

As both custom domain publishing, and social sharing networks, become normal with many blogs, we see anguish when blog owners change the URLs of their blogs, without planning for the effects of the change.

What happened to my Likes?

This blog owner - and many others - do not realise that FaceBook counts Likes, based on the URL, not the blog.

FaceBook Likes, and Google+ +1s, are counted by URL - and are not controlled by DNS redirection, or simple name changes. If you rename your blog, you get a new URL with a new popularity counter, in FaceBook and Google+.

Some social sharing services allow for URL changes.

BlogLovin lets you transfer Followers from one URL to another.

BlogLovin, for instance, provides for transfer of Followers, to a new URL - as long as the blog owner owns both the old and new URL.

First, make sure that you've claimed both of your blogs.

Once both blogs are claimed, navigate to "My blog" and select the "Edit Blog Info" option next to your original blog.

From the "Move Followers" dropdown menu, select the blog you'd like to move your followers to and click "Move". This will remove your original blog and move your followers to your new blog of choice.

Start from any BlogLovin page.

Select "Blog analytics" from the drop down menu.

Click "Edit blog info".

Select a blog, from the drop down blog menu, in the "Edit blog info" wizard - and click on "Move Followers".



Whether you have a blog with a new URL, or a blog with multiple feeds and groups of Followers, BlogLovin lets you consolidate / move Followers so you can address your Followers, conveniently.

Blogger Followers stay with the blog, automatically.

With a Blogger blog, and Blogger Following / Google Friend Connect, your Followers Follow the blog - not the URL. You can rename the blog, and change the URL - but as long as you don't change the BlogID, your Followers remain with your blog.

FaceBook and Google+ give you a new counter, for each URL.

Neither FaceBook or Google+ provide a similar option. To both FaceBook and Google+, if you change the URL of the blog, you have a new blog. Google+ Followers - unlike Blogger Followers - Follow the URL.

With custom domain publishing, and the BlogSpot to domain redirect, the attention of your Followers may end up on your redirected blog - but the +1 counter and Followers community, that was based on the BlogSpot URL, stays with the BlogSpot URL. With the blog published to the domain, your blog gets a counter and community for the domain URL - and starts over.

With a BlogSpot to BlogSpot URL change, and a domain to BlogSpot URL change, everything starts over.

FaceBook Likes are counted, within FaceBook - and Google+ +1s are counted, within Google+. Both are based on the URL of the blog which accrues the Likes and +1s. If you change the URL of the blog, you get a new counter - and a new Followers community.

A URL change is effective for different changes, to a Blogger blog.

• BlogSpot to BlogSpot name change.
• BlogSpot to custom domain republishing.
• Custom domain to custom domain change.
• Custom domain to BlogSpot republishing.

All of these are URL changes - and are treated as a different blog, for most social sharing services.

BlogLovin supports URL changes. Neither FaceBook, Google+, or LinkedIn provides this ability. You change the URL, you start over with +1 / Like count, Followers community, and sharing reputation.

---

With most social sharing services, if you change the URL of a #Blogger blog, you start over accumulating +1s, Followers, and Likes. BlogLovin appears to be alone, in letting you transfer Followers from one blog to another - if you create a new blog, or change the URL of an existing blog.

https://productforums.google.com/forum/#!category-topic/blogger/ZiozKZOS07Q

https://productforums.google.com/forum/#!category-topic/blogger/gkmBV6s03Ck

Blogger Magic - Using Sitemaps To Diagnose Problems

Knowing how to read, and follow, sitemap entries is a useful skill in diagnosing many Blogger problems.

The Blogger generated sitemaps, which apply to each blog, index both pages and posts. This blog, like every other blog, has two sitemaps, automatically generated.

"sitemap.xml" (posts) roughly duplicates the "Archives" gadget - but has advantages, over the gadget. "sitemap-pages.xml" (static pages) is not redundant, to any Blogger accessory.

The two Blogger generated sitemaps provide possibilities for content and problem analysis, unequaled by any Blogger accessory.

• http://blogging.nitecruzr.net/sitemap.xml
• http://blogging.nitecruzr.net/sitemap-pages.xml

The posts sitemap is valuable.

• The Archives gadget, which provides a canonical list of posts, is not included on all blogs.
• The Archives gadget, for most blogs, must be examined one month at a time - and does not provide a search option.
• Manually searching for a post, using "Older Posts", is time consuming.

The pages sitemap is especially valuable.

• There is no canonical accessory, that lists pages.
• The Pages gadget only lists pages that the owner wants to index.

You can view pages, and posts, using either sitemap. Note only a published page or post will be listed. Draft status pages and posts will not be listed.

This blog, like many, has a paged posts sitemap.

Each posts sitemap page will list up to 150 entries. Any blog with over 150 posts will have a paged sitemap.

http://blogging.nitecruzr.net/sitemap.xml

The posts sitemap, for this blog.



Page 1 of the posts sitemap contains the 150 most current posts.

http://blogging.nitecruzr.net/sitemap.xml?page=1

Page 1 of the posts sitemap, for this blog. It's a very simple display - just URL and "last edited" date / time, for each post.



Here is the pages sitemap.

http://blogging.nitecruzr.net/sitemap-pages.xml

I don't have a lot of pages published, in this blog, that are of public interest.



You can access pages and posts, from the sitemap.

Using browser features, you can access any listed page or post, directly from either display.

Highlight the URL that you need to examine.

Right click, select "Go to http://blogging.nitecruzr.net /p/what-are ...".

And there is the page in question.



You can access "http://blogging.nitecruzr.net/p/what-are-differences-between-pages-and.html" from the pages sitemap - or "http://blogging.nitecruzr.net/2013/12/what-are-differences-between-pages-and.html" from the posts sitemap.

Most browsers have a right click context menu, and a "Go to (URL)" selection - and provide direct access to any page or post, using a properly formatted URL.

One practical case, diagnosed using the sitemaps.

One of the intriguing uses of the sitemaps, that we find useful, involves a blog with content - yet when viewing it, we see

No posts.

in the blog "status message" section. Why do I see "No posts." - instead of blog content?

People who confuse "pages" (aka "static pages") and posts (aka "dynamic pages") may publish a blog, using nothing but static pages. The blog main page will normally only display posts - and show "No posts.", when viewed.

You can, however, redirect the home page to a given static page - and add links between the static pages. Or, republish the pages as posts, if convenient.

---

The recently added #Blogger generated pages and posts sitemaps offer canonical access to all published pages and posts, in every publicly accessible blog. These sitemaps are useful to people - as well as to search engines and other indexing processes.

Duplicate Post URL Prevention, And Yearly Archiving

We see an occasional suggestion, in Blogger Help Forum: Learn More About Blogger, about archive convenience.

Some blog owners, presumably ones who do not publish so often, would like to archive posts on a yearly basis.

It would be great, if you would add the option of "Yearly" under the Archive gadget "Archive Frequency".

This blog owner may not know why posts are archived on a weekly or monthly schedule.

One of the most challenging tasks in the post editor has to involve post URL creation.

Post URLs absolutely must be unique.

Besides having to create a URL from the post title, the post editor has to ensure that no post title causes a previous URL duplication - after removal of unnecessary words. One unbreakable rule of Blogger posts (Internet life, in general) is that two posts can not have the same URL.

Post URLs use a structure that includes the Year and Month, as "/yyyy/mm". That is how the Archive gadget opens the post list, for the "Monthly" archive option.

My previous post, on this subject - and the Archive gadget ("Contents") opened, to the month of its publishing.



The Archives gadget opens the post index to the proper year and month.

The Archive gadget display opens to the year and month of the first post on the page. It does that, by using the URL of the post displayed.

The Post:

Blogging - The Directory and URL Structure

The URL:

http://blogging.nitecruzr.net/2009/08/blogging-directory-and-url-structure.html

The Archives gadget can't show a year - or infinity - of posts.

See how the Archives gadget opens up, to the year / month ("/2009/08") of the post?

Can you imagine the performance issues, if the Archives gadget were to open up an entire years worth of posts? Then there is the resulting sidebar length increase - causing main page length increase.

The archives list for this blog, for 2009/08. I'm not going to try to display the entire list for 2009.



Every Blogger feature has to have limits, to make the Blogger service usable by everybody.

Like the oft misunderstood auto pagination feature, Blogger features should display only so much, at one time. One display limit includes retrieval of content - and archiving is an important component in limiting content retrieval.

---

Some #Blogger blog owners would like to archive posts on a yearly basis, so they could open the Archives list for an entire year, at once.

Not all blog owners understand how the Archives display follows the post URL structure - which includes the year and month, to prevent URL duplication. Like auto pagination, monthly archiving limits mass content retrieval - and makes the Blogger service more useful, for everybody.

Change A Post To Draft, To Change The Post URL

Long ago, a renamed blog post would automatically receive a new URL, to match a change in date or title.

Blog owners would happily rename posts - and see a new URL, with no problem. Those blog owners who monitored search engine activity, however, later became concerned by the "404"s, shown in the search engine activity logs, in Webmaster Tools - or from various test searches.

Blogger later gave us dashboard and post editor options, to let us intentionally change a post URL, when necessary - and stopped allowing incidental changes to the date or URL, when editing post content.

Settings - Search preferences has the "Custom Page Not Found" and "Custom Redirects" wizards, for dealing with existing posts with changed URLs - and the Post Editor "Post settings" has the "Permalink" wizard, to change URLs of new posts.

This gives blog owners the ability to Edit and Publish posts, and to adjust URLs, independently - and makes it harder for owners to accidentally generate "404"s with existing posts.

You can change a post to Draft status, to change the date or URL.

Recently, people discovered that changing a Published post, to Draft status, would reset a post. A Published post, changed to Draft, and later Published again, would act as a new post would have, when Published.

Blog owners wishing to change the URL of an existing post would change a post back to Draft status, change the Date and / or Title, then Republish - and the post would have a new URL to match the new Date / Title.

This worked great - for owners intentionally wanting a new URL for their renamed posts.

You can also publish a post to Draft, to re use the URL of that post.

If you delete a post, then publish a new post with that same title, you will get a post with a URL containing a duplication prevention suffix - because deletion of a post does not let you re use a URL. If you publish a post to Draft, that resets the URL - and lets you publish a new post to that same URL.

Saving a post as Draft, to edit, can allow URL change - and cause broken links.

Some blog owners use Draft status, for previously Published posts, differently

You can take a published post offline, as a Draft post - then change the Title, and various other settings. This will not change the URL - unless you also change the Permalink, before you Publish.

If you do change the URL, be mindful of the links that may refer to the old URL.

If you want the URL to change, you will have to change the permalink.

While the post is in Draft status, find "Permalink" in "Post settings", in the right sidebar of post editor. Select "Custom Permalink", and change the title section of the post URL. Then select "Done".

Note you will only be able to change the title section of the permalink. You can't change the year, month, or extension ("html") any more.

If I wanted to, I could rename this post, when in Draft status.

Change Posts To Draft, To Change The Post URLs

I could change the post URL, to match.

change-posts-to-draft-to-change-post-urls

The most obvious change that I could get, then would be

http://blogging.nitecruzr.net/2015/01/change-posts-to-draft-to-change-post-urls.html

Fix broken links, by adding a custom redirect.

We can use the same tools to correct mistakes, as we can to make changes.

If you change the URL - and cause broken links, and / or "404" entries in Search Console / Webmaster Tools, when re Publishing a Draft post, just add a Custom redirect from the old URL, to the new URL. One new redirect takes but a few seconds to add - and will keep your readers, the search engines, and you happier.

Blogger Terminology - Blogs Vs Posts

Sometimes, we see odd confusion in Blogger Help Forum: Get Help with an Issue.

I deleted my blog - can somebody help me restore it? I worked so many days writing it!

or alternately

I am trying to write a new blog, but it says my url has already been taken (by me).

If the first owner is kind enough to include the URL of the deleted "blog", we may use our favourite online diagnostic tool - and discover that the blog is still online, and not deleted! In the second case, we may find a new blog, with one post.

Investigating further, we discover that the problem here involves terminology. This article that I am writing, "Blogger Terminology - Blogs Vs Posts", is a post, which is part of my blog, "The REAL Blogger Status" (which right now is actually The ONLY Blogger Status - but that is another tale).

The terminology here is pedantic, to us - but it's very real, to the blog owner who has just deleted an important post. Or to the owner who has published one post - and now wants to publish a second (not blog, post).

A Blogger blog is a collection of pages and posts, under a common root URL.

A Blogger blog contains pages and posts.

You publish new posts (and pages), to a blog, to add indexable content. Both pages and posts will add value, given informative, interesting, and unique material.

So why do some people confuse blogs, and posts?

So what is the confusion, between blogs and posts? I've seen some helpers muse that social networks, like FaceBook, may offer the option to create a "blog" as part of your Wall. A FaceBook "blog", which is equivalent to one Blogger "post", becomes one more article that's part of the FaceBook experience - which is passed on by one's acquaintances.

People used to writing on FaceBook walls may be used to creating a "blog", which we simply call a "post". It's a simple mistake. Similar to "blog" vs "post", some blog owners confuse "pages" and "posts".

Call it a "blog" - or a "post" - your choice - just please don't work on it, unpublished!

Whatever you wish to call it, please don't spend days editing it, before Publishing. Terminology aside, losing days of work is not a trivial concern. The lament described above is very real, for too many blog owners.

Also, don't create a "duplicate" blog, to publish a new article - add a post (or a page) to the existing blog.

I Promise You, This Blog Exists

I almost hesitate to start this post, because of the date. However, I promise you, this is no joke. Recently (and before today, so I don't see this as a joke), Blogger made a change to their servers, and to how they display "404 Address Not Found". And, I've seen some confusion resulting from the change.

Here, for instance, is a link to this blog. And here is a link to this post.

Simple enough? How about a link to a non existent web site. See the display?

Server not found
Firefox can't find the server at nitecruzr-non-existent-blog.

Duh. What's a server?

OK, "Chuck's Non Existent Blog" doesn't exist. Or, it exists in my mind, purely to make this point. Don't think about this too hard though.



How about a just deleted blog?

Blog has been removed

Sorry, the blog at nitecruzr-non-existent-blog.blogspot.com has been removed. This address is not available for new blogs.

This blog did exist - for a few minutes. It doesn't exist now, and the name isn't available to anybody else either. And no, you can't have it.



Or maybe a (previously) non existent blog?

Blog not found

Sorry, the blog you were looking for does not exist. However, the name nitecruzr-second-non-existent-blog is available to register!

This blog didn't exist, until I registered it. Now, it does exist.



Clear so far?

OK, now get this - a link to a non existent post, in this blog. Bloggers will, from time to time, delete posts that they have linked elsewhere. Or maybe they will mistype a post name when setting up a link, as I did (intentionally). And pity their readers, who don't know all of this technical mumbo jumbo.

The blog you were looking for was not found.

And, what's a blog?

But, "The Real Blogger Status" does exist. The post "This Post Does Not Exist", however, again exists only in my mind. Too many bloggers confuse the concepts of "blog" and "post", and this display is only going to enhance that confusion.



Looking at the last two examples shows that Blogger does recognise the difference between a "404 Blog Not Found" (the example second above) and a "404 Post Not Found" (the example immediately above). And if we know what each error display looks like, we can tell the difference too. But how about our readers, or the newbie blogger?

Can you see the confusion there? I've seen confusion here and there with some bloggers, referring to this post, as a blog - so I wrote this post. If I didn't understand web servers just a little, I'd be wondering if my blog was now gone. But, this blog exists. Really.

>> Top

Your Blog Is Like You - Unique

The title of this blog is "The Real Blogger Status".

This blog contains many posts. The name of this blog is "bloggerstatusforreal", and its URL is now "blogging.nitecruzr.net" (it's also known as "bloggerstatusforreal.blogspot.com"). There can be only one BlogSpot blog with the name "bloggerstatusforreal", though there can also be "bloggerstatusforreal.com", and "bloggerstatusforreal.net", and each can be separate web sites, if desired. And any blog can have the title of "The Real Blogger Status".

You can create another blog, if you wish.

You can create as many blogs as you need, and they are all free. Use the Dashboard link "Create a Blog", to create another - but you will have to use another blog name - if you wish to publish to "BlogSpot.Com". If you want to create another blog in a custom domain cluster, that's easy enough, after you create a BlogSpot blog.