Latest News

Stats And "Don't track", And Custom Domains

Blog owners have been trying to block tracking their own Stats pageviews, for a few years.

This option has long been unusable, for blogs published to custom domains. Recently, Blogger Engineering updated the option - and the dashboard page with the link.

The new Stats option to "Manage tracking your own pageviews" is a start.

Unfortunately, it provides no obvious help, to people who publish their blogs to custom domains.

Start from the Stats dashboard page.

Click on "Manage tracking your own pageviews".

And you get an HTTPS link.

As we all know, blogs published to custom domains won't provide HTTPS access.

Change "https" to "http".

And you can make it work.

If you manually remove the "s", you can make it work.

You can't access the "Manage tracking your own pageviews" for a custom domain published blog, by simply clicking on the dashboard link.

This suggests an interesting detail. Now that "Manage tracking your own pageviews" runs under the blog URL, it will be subject to script filtering - for "", any applicable country local domains, and / or a custom domain URL.

You may need to correct your browser script filter, to make "Don't track" work, now.

Owners of custom domain published #Blogger blogs have been wanting to block Stats from counting their own pageviews, for a few years. This option is now available - but not in an obvious way.

With AdSense, Ads Are Not Based On The Minimum

One sign of confusion, in AdSense Help Forum: Blogger / Host Partners, involves new blog publishers, who want to immediately add ads, after starting their blogs - and need reassurance, about how soon they will be seeing income.
What is the actual qualification level, for AdSense?
This is a question, from somebody who probably does not understand the AdSense approval process.

If AdSense is run properly, final approval is not based on any fixed minimum. There are too many different blog / website subjects, and advertising targets, to have a consistent minimum across all product lines.

I've seen too many blogs with very little content - significantly below the often stated "minimum" of 50 posts, 100 - 200 words / post, showing ads - to believe that there really is one common minimum qualification level.

Some of the experienced helpers in the forum seem to suggest a very restrictive "qualification level".

100 posts, 500 to 1,000 words / post.

There are more blogs that will never get ads - even after being given approval.

Qualification is based on supply vs demand, for each blog subject.

My suspicion is that the qualification level is based on what ads are being sold (by the ad managers) vs what blogs and websites are being offered for ads (by the owners).

It would make no sense to qualify a blog about automobiles, based on current standards for selling ads about bicycles.

  • At any time, these may be more blogs about bicycles, than about automobiles.
  • Automobiles cost more than bicycles, so it's likely that one automobile ad click is worth more than one bicycle ad click.
  • Next month, there may be more advertisers selling ads about bicycles (in San Francisco), than about automobiles (in Los Angeles).

Approval is based on blog and post size - ads are sold, based on a variety of details.

Qualification is based on a combination of details.

At minimum, I would bet eligibility for ads is based on a combination of metrics - including current demand.

  • Post count.
  • Post length.
  • Post subject.
  • Blog language.
  • Blog location.
  • Demand for ads of a given language, location, and subject.

If a given ad manager is prepared to pay for 5 blogs about automobiles in Los Angeles, the best 5 blogs, based on current metrics, will be "qualified". This week, some blogs with 50 posts may be chosen to host ads.

Next month, with the Tour de France scheduled for San Francisco, there will be more market for ads about bicycles there. With more ad managers paying for ads about bicycles in San Francisco, blogs about automobiles in Los Angeles will have less demand.

Automotive blogs may be chosen based on 75 posts / blog and 200 words average / post - and some blogs about bicycling in San Francisco, being more in demand, may be chosen with 25 posts / blog and 100 words average / post.

Work on your blog more - and your blog will host ads sooner.

To anybody asking

What post count, post length, traffic level is required, for qualification?

I would suggest a different approach.

Work on your blog - and don't spend time asking about qualification level.

What you need, to make serious bucks, is going to be more that mere qualification level. And ad managers want to pay for ads hosted on blogs that will be in business longer, and deliver relevant traffic consistently - because that's where more paying customers originate.

And blogs that make more money have owners who are better motivated to publish more - and stay in business longer.

Better / more content --> More earnings --> Better future --> Preferred for ads

That's your qualification levels.

Some #Blogger blog owners want to host AdSense ads on their blogs - with their blogs immature, and lacking content. They ask about qualification levels, rather than look at how valuable their blog may be (or not) for hosting ads of a given subject.

They ignore the concept of supply and demand - even though that's very likely as important as blog subject - or size.

Comments "Lost", With Google+ Comments Selection

Besides the confusion about being in the right Circles, some Google+ comments can be overlooked, because of the comment view selector.

We see odd problem reports, in Blogger Help Forum: Get Help with an Issue.
When a friend mentioned she'd commented, I found that odd - because I couldn't find the comment anymore. It had shown up previously - but it was now gone.
The view selector is not so obvious, either. It's similar to the "Compose" / "HTML" buttons, in Post Editor.

Besides the view selector, we see another possibility for third party cookies, unwisely filtered, to cause confusion.

Displaying comments for a blog, with Google+ comments involved, requires determining the identity of the individual viewer. Viewer identity - much more specific than "blog owner" / "blog guest" - is required, to determine visibility of specific comments, published against a given blog.

Here's an example, using a post from my recipes blog.

12 comments - from Circles + Public.

Circles + Public, selected.

6 comments - from my Circles.

Circles only, selected.

Can you see the difference? Other viewers of the blog will see a completely different set of comments.

Here's a different example, from a forum topic.

The blog owner, signed in, sees a count of 27 comments.

The blog owner, not signed in, sees a count of 42 comments.

There's actually 3 possible different displays - each showing a different comment count, and a different list of comments.

  1. Not signed in.
  2. Signed in, looking at "Public" + "Circles".
  3. Signed in, looking at "Circles" only.

One might expect #1 and #2 to be the same. In some cases, it appears that #1 displays a total comments count - though #2 and #3 display a count specific to the blog owner or reader. And I would not expect that one will actually see a precisely equal number of individual comments, displayed.

And if blog owner / reader access is affected by a third party cookie filter, both the comment count - and the list of comments displayed - will be smaller than what really should be displayed.

We now have a Rollup Discussion, in Blogger Help Forum: Get Help with an Issue, where we are requesting details from anybody experiencing mysterious loss of comments, If you are losing comments, please provide your details.

Owners of #Blogger blogs that use Google+ Comments don't realise how much more important their personal identity is, when looking for comments, that should be displayed with the individual posts. Personal identity is further relevant, with the "Circles" / "Public" comment selector, a feature of Google+ Comments.

And determining personal identity is affected, when cookie filtering becomes involved.

Custom Domain Publishing, And Alias Blocking

Some blog owners setup their new custom domain, check all settings carefully (and correctly) - then find that it does not work.

We see the confusion, in Blogger Help Forum: Get Help with an Issue.
The addresses were right - and all the DNS servers updated correctly. But when I open the website, it does not open. It continuously reloads for 5 minutes and after 5 minutes it shows an error.
It's frustrating, when everything is setup properly - but still no results.

It's also frustrating, when you forget about unsupported tweaks that you made, to the blog - then have to ask for help.

Whenever changing the URL, check for - and remove - any redirecting scripts.

Before you publish a blog to a new URL, you need to check the template, for any redirecting scripts, that you may have previously installed.


Scripts which redirect - or block redirecting, when the blog is published to BlogSpot - will not work for you, when you publish to a non BlogSpot URL.

You will need to connect URLs, when possible - without scripts interfering.

Any time you change the URL of the blog, you're going to need some ability to link from the old URL to the new URL. Before you change the URL - either BlogSpot to BlogSpot, or BlogSpot to custom domain - check the template, for redirecting scripts.

Any redirecting scripts, that might have helped you with the blog originally published, will be a problem, when you change the URL. Remove any scripts, before changing the URL.

Better yet, don't add redirecting scripts. If you got this far, without having the blog classified as a malware host, consider yourself lucky.

Some blog owners install mysterious scripts, to "protect" against unwanted Blogger features - and forget about their unwise tweaks. When they change the URL of the blog - and the blog, under the new URL reacts to the previously installed tweaks - they are clueless.

If you make unsupported tweaks to your blog, only you can correct problems that arise, later.

"Export / Import" Is Now "Import & back up"

Blog owners who need to export blog content are reporting confusion, in Blogger Help Forum: Get Help with an Issue.
I'm trying to export my blog, but when I click "Settings > Other", there is no "Export" option!
Not all blog owners realise that the "Export" wizard is now "Back up".

Changes in functionality may perplex blog owners, too.

There are various ways to use "export" and "import" features, that may involve Blogger, and non Blogger content hosts.

Not all content will transfer, equally well - whether a Blogger or non Blogger host is involved, as either the source or target. The Blogger blog owner, using "Import & back up", will be responsible for resolving any differences.

"Import & back up" is now used to export and import Content (pages, posts & comments).

"Import Content" is used, as previously.

"Back up Content" is the former Export wizard.

"Import Content" is used, as previously.

When you import content, consider the multiple possibilities of XML files.

  • Archive / Backup comments, pages, and posts.
  • Archive / backup templates.
  • Publish newsfeeds in Atom and RSS.

Observe the nature and source of any XML file, whenever importing. "Import Content" will work best, with comments, pages, and posts backed up from Blogger.

  • It may, or may not, work with content Backed up ("Exported") from other content hosting services.
  • It may, or may not, work with templates, Backed up from Blogger or from a third party source.
  • It won't work, with newsfeed content - or other XML data files.

And, as always, be careful when using the "Automatically publish ..." option, any time you import content.

"Back up Content" is the former Export wizard.

"Backup Content" will be most useful, when used to Import content to another Blogger blog. It may, or may not, work to Import content to another content hosting service.

"Backup Content" is most useful, when you plan how to use the content being backed up. And you will benefit, from regular use.

When moving content from, or into, another hosting service, note limitations.

Every content hosting service - Blogger, Tumblr, WordPress, and many many others - will have their own data management policies. A backup / export file, created under any one service may, or may not, work under another service.

If you experience problems, you'll be arbitrating diagnostics provided by the source and target tech support groups - whatever you can find. You will be the point person, in dealing with any problems that involve multiple hosts.

Moving content between services is not a project for the beginning Blogger blog owner. It's similar in complexity to using a Blogger custom domain outside Blogger.

The recent redesign of the #Blogger dashboard "Export / Import" wizard, at Settings - Other, has perplexed some blog owners.

Not everybody knows that "Backup" is the same task as "Export". And few blog owners understand the complexities of using XML type files, with different sources and targets.

Recovering From The Corrupt Template / "Error 500"

We're seeing a few reports, this week, in Blogger Help Forum: Get Help with an Issue, about blogs with broken templates.
I tried to log on to my blog, and it shows up an error message. I've done it several times on different browsers, but no change: the error code is bX-uukqqu.
It appears that the "bX-uukqqu" is from the owner attempting dashboard access. Trying to view the same blog, I see the ubiquitous "bX-v2vqfh".

Both codes reference blogs which show up, in an HTTP trace, with the monolithic message "500 Internal Server Error" - and tells us that this is one more blog with a broken template.

If you, the owner of a blog with a broken template, can access the Template dashboard page, you may be able to recover the template.

Some blog owners report that adding a Template Backup / Restore has helped to resolve their own bX code / "Error 500".

  1. Backup the template ("Download full template").
  2. Get a clean Blogger standard template.
  3. Restore the template ("Upload" the template that you just downloaded).

If you're lucky, your version of the "bX-uukqqu" (dashboard) / "bX-v2vqfh" (public) can be resolved, by a quick template download then upload.

You may need direct access to the Template page, bypassing the dashboard menu - though if you can view the blog, the "Design" navbar link will provide you that ability. If you can't access the Template page at all, you may be able to clear some bX codes, by using the Template Editor aka "Edit HTML".

If any of this works, your blog will be back in service. If not, you will at least have a backup copy of the template.

If the template is still broken, you now have three choices.

  1. Leave the blog as it is now, broken - until Blogger Engineering finishes diagnosing and fixing the actual cause of the template corruption.
  2. Get a fresh new template. When Blogger Engineering finishes diagnosing and fixing the actual cause of the template corruption, you can try restoring the template copy that you just backed up.
  3. Try a persistent solution.

And whether this works - or not - or even if you can't use it, right now, you can have a template backup. And one day, this backup may be useful.

A few Blogger blog owners, reporting bX codes when trying to access their dashboards, have found that accessing the Template page directly, then doing a quick back / restore, may clear the bX codes. This suggests that Blogger Engineering is beginning to test solutions to the ubiquitous "Error 500" broken template problem, that have been afflicting blog owners for some time.


Verifying Blog Ownership, In BlogLovin

In BlogLovin, the ownership verification process is termed "claiming your blog".

Claiming your blog involves installing a BlogLovin link, with embedded token, on your blog where it can be seen, by the BlogLovin claim verification process. Getting the claim link, from the BlogLovin dashboard, is not an obvious process.

Not every blog owner is able to get the BlogLovin blog claiming link, for their blog.

  1. Some folks can't find the "Claim blog" button.
  2. Others don't provide the right URL, into the "Claim blog" window.

If you have either problem, you end up unable to "claim your blog".

Finding the "Claim" button is not obvious.

You start the Claim process from the "Blog analytics" display. In some instructions, this is referred to as "My blogs". There is no menu selection to "Claim your blog".

From the home page, click "View all in Analytics".

From "Blog Analytics", click on "Edit blog settings".

Find the blue "Claim blog" button.

BlogLovin needs the blog published URL - not the blog feed URL.

Observe the caption in the "Claim blog" window.

When you provide the URL, only provide the published URL - not the blog feed. This works best if the blog publishes a feed, and if the blog has a standard Blogger header. BlogLovin gets the feed URL from the blog header - when the URL is there.

Paste the published URL of the blog - not the blog feed - into the window, and hit "Search".

Select your blog.

And, there is the BlogLovin link, with an embedded token.

Now, you install the token on your blog - and that is another source of confusion.

Not every #Blogger blog owner is able to verify ownership of their blog, to BlogLovin. Some folks can't find the "Claim blog" button - and others don't know what URL to provide, in the "Claim blog" process.

And the term "claim blog" is not obvious, to everybody, either.

Plan The Custom Domain Upgrade, With AdSense

Too many blog owners take their Blogger blogs, successfully hosting AdSense ads using a Blogger Hosted account, and decide to get a non BlogSpot URL.

Having survived the challenge of getting the custom domain published blog working, they settle back and look for lots more traffic, because of the new non BlogSpot URL - and more income, from AdSense. Then, they discover harsh reality.

Not only do they not get lots more income, their ads are now blank.

When AdSense is involved with a Blogger blog, a custom domain upgrade becomes more than a mere formality, or technical challenge.

When AdSense is involved, a custom domain upgrade is exponentially difficult.

Besides the challenge of getting the domain setup correctly, one has the suspense of getting AdSense approval, for the new domain.

You do need to start with a Blogger blog, published to "", and applying for Blogger Hosted AdSense. Starting with a custom domain published blog, and applying for AdSense for Content, is not a good idea.

A verified address, with an AdSense PIN, is a specific requirement.

Note that if you haven't already verified your address via a Personal Identification Number (PIN), then you'll need to do this before you can apply to show ads on your own site. Learn more about PIN verification.

With the PIN being a requirement, you'll need to have earned at least $10 (or non USA equivalent) from the ads already - which you'll only get with a properly qualified Blogger Hosted account.

Getting AdSense working, on a custom domain published blog, requires AdSense For Content - and AdSense For Content is more selective, when approving blogs to host ads.

Work on your blog - and don't stop adding content.

I constantly advise blog owners

When your blog is successfully reviewed, ads will become visible. Until then, work on the blog. You will need a lot more content - and traffic - than what is required to simply make ads appear.

A blog, to become eligible to apply, needs lots of content - and you are wasting time asking

How much content do I need?

To be actually approved for Hosted AdSense, a blog needs more content than simply to be eligible. And, to be approved for AdSense For Content, a blog needs still more content.

And after all of that, a blog needs even more content, to get traffic, and to make money.

Make the content informative, interesting, and unique. And well written.

So, stop asking, and start publishing - and don't stop. Remember that what you publish must be informative, and interesting to your readers - and it must be original;. AdSense requires unique content, that's well written - and useful to your readers.

And make sure that the domain is properly setup, and remains online.

And, for the unique content to be read by AdSense, if you're going to publish to a custom domain, make sure that the domain is properly setup. You do not want a refusal because the blog appears to be offline.

Setup Search Console - and watch reports, daily. A Search Console report, warning you of a problem, could provide the difference between approval and rejection, from AdSense.

And learn the policies, regulations, and rules.

And learn the rules of AdSense Accounts. Read these references, as you would a bible. Learn them, before applying.

Finally, plan the upgrade and approval process - and allow for the ads outage.

Be aware that the approval process will examine your blog even more critically than the Hosted AdSense approval. And hopefully, with the blog at least 6 to 12 months older, there will be more content to be examined, than when you applied for Hosted AdSense.

Allow for 2 to 4 weeks of no ads, while the blog is examined again. Don't start this process, then post anxiously, in AdSense Help Forum: Blogger / Host Partners.
How long does it take? My family is hungry and we need the income!
That will not speed up the approval by even one day.

So plan the upgrade, and be patient.

Too many #Blogger blog owners, enthusiastic about their new blog now showing AdSense ads, decide that the road to riches lies with an immediate upgrade to a non BlogSpot URL - which will get them more traffic, and even more ad income.

Having upgraded and gotten the domain setup correctly - and seeing more traffic - they discover that the blog is now not serving ads. Upon asking for advice in AdSense Support, they find that they must wait another 2 to 4 weeks - and even so, it is not certain that they will ever see ads, again.

Get Free Sample Of Vatika Brave & Beautiful

Hello Friends. Vatika Has Launching Free Sample for Their Lovers, Here You Will Get Free Vatika Brave & Beautiful Sample for Free, With Free Shipping, It is Free Of Cost, So Order It Now
How to Get Free Sample Of Vatika Brave & Beautiful Sample :-

1) First Of All Goto Offer Page
2) Click On “Request Sample” at Left Side
3) Fill Your Delevery Details
4) And Submit Your Details, You Will Receive It Within 10 Working Days,

Freebies Offer :- Get A Pack Of Fortune Rice

Freebies Offer :- Get A Pack Of Fortune Rice – Get A free sample of fortune 1kg pack official site. and 100% delivery
You will experience the taste and texture of fine rice.

How to Claim This Deal
1) Firstly Visit Deal page
2) Follow The Steps Given There And Invite them For Free Rice (Steps Given)
3) Invite From Login Or Register In Facebook Social Media Site
4) Finally They Ask Your Name And Number Enter And Wait For Call
Stay Tuned With us

(Live Now) Shilpkart Free at Three – Buy Bags In Just Rs.0

Shilpkart Free at Three – Buy Bags In Just Rs.0 – Hi Friends I am Back Again With an Another Freebies Offer, Shilpkart Has Completed Their First Year On Internet And Celebrating Their First Anivarsary, They Are Offering Free Bags Like Hand Bags, Jhola Bags etc You Just need to Pay Shipping Charges Only, So Friends Just Claim It Now
This Offer Will be Live at 3:00 PM (21th Feb)
How to Claim This Amazing Offer?

1) First Of All Goto Shilpkart Offer Page
2) Click On “Add to Cart”
3) Login/Register to Your Account
4) Proceed and Apply This Promo Code :- FREEAT3
5) Fill Shipping and Billing Details and Proceed
6) Pay Shipping Charges, And Complete Your Order

Using The Meta Search Description In Your Blog

There is some confusion, about including "search description" meta content, in blog template code, to provide source for data shares to social sharing sites.

In various topics in Blogger Help Forum: Get Help with an Issue, I've seen references to "data:post.metaDescription", "data:post.snippet", and "data:post.pageTitle" used, in providing the blog post source for the FaceBook "og:description" tag. As far as I can tell, none of these exist.

The Layout data tag "data:blog.metaDescription", which provides "og:description", does exist - though it seems to be referenced, ambiguously.

Some FaceBook Open Graph content references different Blogger tags, depending upon page type. The FaceBook "og:title" references "data:blog.pageName" with an "item" (post) page, and "data:blog.title"; with other pages.

"og:description", on the other hand, only references one Blogger tag - "data:blog.metaDescription". The latter appears to change its source, depending upon whether the main page, or a post page, is being viewed.

  • In main page mode, the per blog "Description", from Settings - Search preferences, is referenced.
  • In post page mode, the per post "Search Description", from the Post Editor "Post settings", is referenced.

Source listing for this blog, in main page view.

"What Blogger won't (or can't) tell you. Blogger features and problems explained, using real life examples."

Source listing for this post, in post page view.

"Blogger provides the meta tag "data:blog.metaDescription", which seems to vary in source. Learn how it varies."

There is no mention of "data:blog.metaDescription", in the reference Blogger Help: Layouts Data Tags - as either a per blog, or per post, data element.

In my earlier post, my reference to "'data:blog.metaDescription' name='description'" was simple. But simplicity can lead to confusion.

<meta expr:content='data:blog.metaDescription' name='description' property='og:description'/>

Some tags are universal, others vary depending upon page type ("item" being post page).

<!-- BEGIN Open Graph tags -->
<meta expr:content='data:blog.metaDescription' name='description'' property='og:description'/>
<meta expr:content='data:blog.pageTitle' name='keywords'/>
<b:if cond='data:blog.pageType == "item"'>
<meta content='article' property='og:type'/>
<meta content='' property='article:author'/>
<meta expr:content='data:blog.canonicalUrl' property='og:url'/>
<meta expr:content='data:blog.pageName' property='og:title'/>
<b:if cond='data:blog.postImageUrl'>
<meta expr:content='data:blog.postImageUrl' property='og:image'/>
<meta content='http://xxxxxxxxxxxxxxxxx/xxxxxxxxxxxx/xxxxxxxxxxx/xxxxxxxxxxx/xxxxxxxxxxx/S1600-R/yyyyyyyyyyyyy.gif' property='og:image'/>
<meta expr:content='data:blog.title' property='og:title'/>
<meta expr:content='data:blog.canonicalHomepageUrl' property='og:url'/>
<meta content='blog' property='og:type'/>
<meta content='http://xxxxxxxxxxxxxxxxx/xxxxxxxxxxxx/xxxxxxxxxxx/xxxxxxxxxxx/xxxxxxxxxxx/S1600-R/yyyyyyyyyyyyy.gif' property='og:image'/>
<meta expr:content='"en_US"' property='og:locale'/>
<!-- END Open Graph tags -->

'data:blog.metaDescription' name='description' is referenced once, in the template code - and the source is apparently determined, based on the context.

If you find this confusing, I have to agree with you.


#Blogger provides the Layout data tag "data:blog.metaDescription", which is used for the FaceBook meta ag "og:description" - for both blog main page, and post pages, when shared. This is in contrast to the FaceBook meta tag "og:title" and others, which use different Blogger data tags for the main page and post pages.

This variation has caused some confusion - and attempted use of different non existent Blogger data tags.

(Giveaway) Get Free Credit Cards With 10$ Balance To Buy .Com Domains !!!

We are here presenting giveaway of credit cards with 10$ Balance.The Cards Will Be Given Between 8:00am to 10:00pm At Hourly Basis. So Please Read Steps To Participate

Steps :-

1.Share This Post On Facebook

Click Here To Share

2. Wait For Cards To Be Posted At 8:00am,9:00am,10:00am And So On Till 10:00Pm Tonight ..(Hourly Basis)

3. Now Open And Use Usa Ip And Buy Domain With Our Given Credit Cards.

4.Enjoy Domain

(Note- Share This Post On Fb Is Necessary)

Click Here To Share

1ST CARD (8:00AM)

Card no. :-4264289581683580




(First Time On Internet)How To Get 300 Rs Freecharge Cash From Snapdeal In Just 1 Minute (Unlimited Times) !!

We Are Always Posting Best Tricks For you and today we are posting (First Time On Internet)How To Get 300 Rs Freecharge Cash From Snapdeal In Just 1 Minute (Unlimited Times) !!

This Trick Is 1st Time On Internet And Created By Us :-


1. 1st Make A New Snapdeal Account 

2. Now Order Any Thing With Price Error

3.Now Your Order Will Be Canceled

4.Now Go To COnsumer Complaint Complaint About Cancellation

5. Now A Call Will COme From Snapdeal And They Will Give You 300 Freecharge Cash As Penalty 

This trick is 100% working and created by us !!! 

Soon We Are Posting domain trick so stay tuned !!

Blogger, And Home / Small Business Blog Clusters

One topic of frustration, occasionally seen in Blogger Help Forum: Get Help with an Issue, involves home based business blogs, that may be victims of their own success.
We are not spam - we are a network of blog owners, in select cities all over the country. I am tired of hearing the apologies, this needs to be resolved.
The blog owner is being quite polite, but insistent.

Blog clusters, whether developed by home / small business owners, or malicious spammers, create problems for all Blogger blog owners. Home / small business blogs are clearly not intentional spam - but their structure makes them easy to mistake for spam blog farms.

Blogger values the creation of blogs with original content. Replicating original content across multiple blogs however, violates the Blogger Spam policy.

Blogger Content: Spam provides a good definition of the Blogger Spam policy.
Spam: Spam takes several forms in Blogger, all of which can result in deletion of your account or blog. Some examples include creating blogs designed to drive traffic to your site or to move it up in search listings, posting comments on other people's blogs just to promote your site or product, and scraping existing content from other sources for the primary purpose of generating revenue or other personal gains.

The most recently observed home / small business blog cluster, which generated traffic in the Spam Review section of the forum, was a USA based coupon sharing club, that had expanded into other areas - such as dining, entertainment and local events.
We are MORE than a coupon group. Our network works with Disney, Nickelodeon, local restaurants, reviews and products and events locally.

Other blog clusters have involved an Australian blog franchise of electronic / tech products and services - and a California / Florida carpet / home cleaning business.

Home / small business blogs can be mistaken for spam blogs.

Each of these three examples appear to have started as home / small businesses, possibly with one blog - and grew exponentially, as franchises. And each of the examples present problems, with automated spam classification.

  • Aggregation of blogs produces unfair advantage, over other small businesses using Blogger.
  • Aggregation of blogs skews spam classification, by tweaking the heuristic spam filters.
  • Aggregation of blogs makes detection of actual spam blog farms more difficult.

These three concerns produce side effects, in the Blogger spam mitigation program - and lead to periodic spurious spam classification of home / small business blog clusters.

As the size of the clusters increase, so does the chance of repeated classification.

  • Blogger policy prevents whitelisting the blogs in the cluster.
  • The more blogs in the cluster, the greater chance that one or more blogs will be classified, at any given time.
  • The more blogs in the cluster, the longer it will take to review a blog, when classified.

Understand your role, in the spam classification / review process.

If you operate a home / small business, which involves blogs clustered on a geographic and / or product - service relationship - and your business is impeded by spurious spam classification, we'll work with you, and try to get your blogs reviewed.

Please, understand that your home / small business may be pushing the limits of the Blogger spam mitigation program. Try to minimise content which replicates through multiple blogs in the cluster - and content which is scraped from various commercial websites.

Some owners / operators of home / small businesses, which use #Blogger as a backbone for their business, produce clusters of blogs, organised on a geographic / product / service basis. Rapid growth of the businesses may lead to blogs which share content too heavily - and may lead to repeated spurious spam classification.

Owners of the blogs should learn to expect occasional spam classification, and try to minimise blog features which lead to spam classification.

Zoook Selfie Stick - Black In Just Rs.0 With 12 Months Warranty on Snapdeal

Hi guys now a days Snapdeal is offering many Loot offers but today Snapdeal is offering Zoook Selfie Stick - Black In Just Rs.0 With 12 Months Warranty on Snapdeal

Instructions To Get This Product →

1. Click Here To Visit offer page

2. Add product to bag / Cart

3. Login/ Signup

4. Enter Shipping details

5. Make Final payment

Features of this Products →

  • Type : Selfie Stick
  • Brand : Zoook
  • Bluetooth Version : Others
  • Warranty : 12 Months
  • Color : Black

(Must See) (Live Now) Book Freedom 251 Smartphone By Ringing Bells At Just Rs.251 (Proof added)

Hi guys we are back with a maha Loot that you never seen. This is biggest Loot Ever in india. Gyus this is exclusive smartphone launched by narendra modi and Ringing bells LTD. Follow Simple Instructions To Loot →

  • Try Only In Google Chrome Web. In Mobile Version Its Redirecting to homepage.

Must see →

Get Free Products Of Rs.400 On Rewardme

Original Image →

Background Look →

Product Image →

Proof →


1- Click here To visit & for Booking
Update → There is Rs.40 shipping charges
2- Click on Add to cart

3- Enter Your Full details. Like- Name, Address Mobile no. etc.

4- Now You will Get a confirmation message like this →

Time →

  • Booking Open on Thursday 18th Feb, 2016 From 06:00 Hrs.
  • Delivery Date Complete upto 30th June, 2016.
  • Booking close Sunday 21st Feb, 2016 at 20:00 Hrs.


  • 4″ WVGA IPS
  • 1.3 GHz Quadcore Processor
  • 1GB RAM
  • 8GB Internal Memory (ROM)
  • 3.2 MP Back Camera
  • 0.3 MP Front Camera for Selfi
  • 1450 mAh Battery
  • 2G/3G Network
  • Dual SIM
  • 1 Year Warranty
  • 650+ Service Centres across India

Ringing Bells Pvt. Ltd Address and Contact number:

B-44, Sector 63, Noida-201301
08822232323, 0120 4313097

Video By NDTV

About Ringing Bells Pvt Ltd →

Established in 2015, Ringing Bells Pvt. Ltd. is one of the fastest growing smartphone company in India. We design and produce smart phones with smartness. BELL Smartphones give an intuitive mobile experience for people who spend their valuable time in doing multiple tasks using their devices, instead of figuring out the way of using them.

Terms & Conditions of Warranty:-

1) This warranty of the Product extends for a period of 12 months for the Host unit, 6 months for Battery and Charger, and 3 months for Earphone commencing from the date of purchase- Freedom251 phone booking
2) Any defect arising due to misuse of the unit, damages due to liquid ingress, or physical abuse, or normal wear and tear will not be covered by this warranty. Plastic components like front & back cover plus rubber component like key pads; antenna will not be treated under warranty coverage- Freedom251 phone booking
3) The warranty is void if the unit is tampered with, altered or repaired by unauthorized persons- Freedom251 phone booking
4) The defective unit along with the sales invoice must be brought or sent to the Authorized Service Centre, during normal working hours, by end customer at his own expense.- Freedom251 phone booking
5) The warranty is void if the serial number of the unit is deleted, defaced or altered rendering it difficult to identify the instrument

Comments With HTML Code Confuse Blog Owners

Some blog owners see encoded special characters, in Blogger dashboard displays - and do not understand why they are there.
I recently noticed that the comments, that I view in my Blogger dashboard page, have like a series of numbers and symbols in some of the comments.
This owner is looking at comments, displayed in the Dashboard Comments pages ("Published", "Awaiting moderation", and "Spam"), which right now may contain strange character sequences.

The "HTML entity codes" for special characters, like ampersand, apostrophe, and quote marks, are HTML code - that will probably be with us, forever. Blogger blog content (like many other blogs and websites) uses HTML - and those characters have syntactical importance. Using them in blog content, unencoded, causes problems with browser operation.

Blogger has had various problems with displaying special characters, like ampersand (&), apostrophe ('), and quote marks ("), for many years.

Long ago, I published my recipes blog, titled "Chuck's Kitchen".

Seeing the blog title displayed a few times, in comments, in the dashboard - and even in the blog header - as "Chuck&#39;s Kitchen" confused my readers, with the apostrophe displayed as an HTML entity. I figured the simplest solution was simply to compromise - and accept a non grammatical title of "Chucks Kitchen".

What I saw, in the dashboard Comments wizard, recently. Look at my comment, of "10:17 AM".

What we now see, in the post comment. Compare the above, with my published comment, of "10:17 AM"

You are allowed to use special characters, like ampersand (&), apostrophe ('), greater than (>), less than (<), and quote marks ("), and others, if you like, in your blog - but you will occasionally see confusion from your readers - as the confusion recently seen in Blogger Help Forum: Get Help with an Issue.
I recently noticed that the comments that I view in my Blogger Design page have like a series of numbers and symbols. I don't know why they are there or how to get rid of them.
You can't really get rid of them, you need to just learn to ignore them. Right now, only you see them.


Some #Blogger blog owners see comments, displayed in the dashboard Comments pages, displayed with HTML entity coded characters. They are odd looking - but right now, they only display this way, in the dashboard pages.

When published, the blog will display the special characters properly.

(Exclusive)(Buy Now) Buy Sony Earphones At 0Rs (Freebie) + Order Proof Added

Here We Are Giving 0rs Sony Earphones !

1: Visit The Offer Page From Here

2. Checkout and do the payment

3) Enjoy Free Earphones ! :)

(Must See)(Live Now)Buy Freedom 251 Mobile At Rs 251 + Trick To Buy This Phone Without Any Overload Error (Must See)

Freedom 251 by Ringing Bell In Just Rs.251 (Booking Starts From 18th Feb) – Freedom 251 Is the New Phone Launched In India by Ringing Bells Company, This Is an Good Feature Phone With Android 5.1Supported In Very Lowest Price About Less Than Rs.500The Ringing Bells ‘Freedom 251’ launch is in line with PrimeMinister Narendra Modi’s visionfor “empowering India to the last person, transforming India’s growth story”, the Noida-based company said.

Features :-

* This Phone Have Good Features And Good Looking With 4 INCHES HD Display Screen

* Freedom 251 Has 5.1 Android Lollipop Support

* It Have 1 GB Ram And 8 GB Internal Capacity

* It Have 3 MP Front Camera With 0.3 Secondary

* Freedom 251 is Duol Sim Support And 3G too

* It Have 1.3Ghz Processior, And 1450 MAZ Battery

How to Book Freedom 251 Online :-This Phone Will Launch On 17thFeb And Booking Will Start On 18th Feb at 6:AM (Live Now)

1) First Of All Click Here And Goto Offer Site

2) Add Product On Your Shopping Cart.

3) Now Goto Your Shopping Cart And Proceed to Checkout

4) Fill Your Delevery InformationAnd Proceed to Payment

5) At Last Make Payment And Complete Your Order

Trick to open website without any error :-

1. Use Droid Vpn Netherlands Server
2. And open with uc speed mode

Share if You Care :-D

Third Party Templates - Not Always Free

Some third party templates come with extra features - that not everybody appreciates.
How do I get rid of the "lorem ipsum" nonsense, that's part of my signature?
This blog owner just got a shiny "free" third party template, for her blog.

Some custom template providers publish free templates that contain odd, irrelevant details.
When I click on the "Read more" link on my blog, it opens up the post - but has added in a odd kind of signature. It displays my name but is using an image that isn't me, and the "lorem ipsum" text. I have no idea where to edit this?

The typical response, by experienced forum helpers, will be a simple suggestion.
Hopefully, the template publisher can sort the problem. If not, a standard Blogger template, or a different third-party template, may be your best solution.
That's a reply, based on experience.

This particular template oddity has been mentioned, in Blogger Help Forum: Get Help with an Issue, a few times - each time with mention of the "lorem ipsum" babble, in the signature.

In one case, the blog owner did contact the template developer - and was kind enough to follow up in her forum thread.
She told me that she would be glad to provide a clean template - for a fee.
It's likely that the "bogus photo" / "lorem ipsum" bit is there, to motivate the blog owner into paying for the template.

In a way, this sort of "fee based" customisation makes sense. The blog owner has 3 choices.

  1. Pay extra for the template cleanup.
  2. Get a different third party template, from a different provider.
  3. Learn to live with the irrelevant babble.

Neither the bogus photo, or the babble, damage the blog. The content is there, as desired - and pleasantly displayed. Not too many blog readers will know that the photo is bogus, or care so much about "lorem ipsum", either.

In a way, it's similar to the legendary photos of imaginary family, that one gets when buying a fancy picture frame, or a new wallet. Some (single, and very lonely) people like the photos - and supposedly, keep them when using the wallets.

Maybe new blog owners won't care, either. They are, after all, rather attractive templates - and popular with women, anyway.

The apocryphal signature section.

The source code for the signature section.

Enjoy the new templates. Pay, when the need arises. Or, refresh the post template (possibly, lose a lot of custom formatting, if you do) - but this should get rid of the "lorem ipsum" nonsense.


Some non #Blogger supplied templates are provided for a price - and payment is optional, though cleverly motivated. Minor irrelevant content is included, which is most noticeable to blog owners who are publishing blogs with a large and observant reader population.

Conversely, the unwanted content is not important to new blog owners who would appreciate the free templates, which are not noticeably damaged by the irrelevant content.

Contact Us

24x7 online , we happy to answer you , ,
skype: greeenchip


This Blog and its TUT's are intended for educational purposes only, no-one involved in the creation of this TuT may be held responsible for any illegal acts brought about by this Blog or TuT.

Featured Post

Custom Domains And HTTPS Redirection Code