Skip to main content

You Cannot Index Label Searches, Productively

The subject of indexing of label searches comes up, from time to time, in Blogger Help Forum: Learn More About Blogger.
I want the label content to appear, in search engine hit lists.
Some blog owners cannot understand what gets indexed, by the search engines.

Label searches are not unique content - and should not be indexed. Posts are content - and posts are best indexed, as post pages - directly from the automatically generated sitemap.

Post content indexed both using a normal post page URL, and using one (or many) label search URLs, will be detected as duplicated content.

Duplicated content penalties will be applied to content simultaneously indexed using both label search URLs, and post page URLs. We've seen this happen - and it was not a time of enjoyment, for many blog owners.

A few months after labels were added to our blogs, in 2007, blog owners were complaining about lack of search engine activity. Blogger blog owners, in massive amounts, reported that page rank had dropped to zero - and search engines had stopped indexing their posts.

Investigation revealed that Blogger blogs, with newly added label search indexes, were being indexed twice - one using the normal, post page URLs, and a second, using the label search URLs. Blogs with multiple labels / post were rampantly indexed.

And all of the indexing was for nothing. Why? Because the search engines were detecting the duplicated indexing - and applying penalties to both the post page indexed content, and the label search indexed content. And nobody was happy.

Blogger Engineering installed an emergency update, to our "Robots.Txt" files.
User-agent: * Disallow: /search Allow: /
Since a label search has the URL "/search/label/whatever", "Disallow: /search" blocks obedient robots from searching, using label search URLs - and "Allow: /" permits all other access.

And there we are. Everybody who understands search engine indexing leaves the "Robots.Txt" code intact, and publishes informative, interesting, and unique content.

If you wish, you may remove that portion - or any other portion - of your file. It's your blog, and your file.

However, if you do remove the necessary entries, and you come later to Blogger Help, or maybe Webmaster Central, complaining of reduced search engine activity, or of no visitors, you'll be instructed to restore to a standard "Robots.Txt" file. And, to spend more time publishing content, in your blog.

Comments

Fit Studs said…
Very helpful. :)

Popular posts from this blog

Custom Domain Migration - Managing The Traffic

Your blog depends upon traffic for its success.

Anything that affects the traffic to your blog, such as any change in the URL, affects the success of your blog. Publishing the blog to a custom domain, like renaming the blog, will affect traffic to your blog. The effects of the change will vary from blog to blog, because of the different traffic to every different blog.Followers. People who find your blog because of recommendations by other people.Search engines. Robotic processes which methodically surf your blog, and provide dynamic indexing to people who search for information.Subscribers. People who read your content from their newsfeed reader, such as the dashboard Reading List.Viewers. People who read your content from their browser.No two blogs are the same - and no two blogs will have the same combinations of traffic sources.

Stats Components Are Significant, In Their Own Context

One popular Stats related accessory, which displays pageview information to the public, is the "Popular Posts" gadget.

Popular Posts identifies from 1 to 10 of the most popular posts in the blog, by comparing Stats pageview counts. Optional parts of the display of each post are a snippet of text, and an ever popular thumbnail photo.

Like many Stats features, blog owners have found imaginative uses for "Popular Posts" - and overlook the limitations of the gadget. Both the dynamic nature of Stats, and the timing of the various pageview count recalculations, create confusion, when Popular Posts is examined.