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.

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.

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".

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.

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.

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.

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.

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?

Some blog owners are becoming confused by the AdSense activation process, and are applying directly to AdSense.

If you apply directly to AdSense, you will be applying for an AdSense For Content account. AdSense For Content requires a properly qualified top level domain website.

If you have a fully qualified top level domain website - or a Blogger blog already published to a custom domain, again, fully qualified - you can add a Blogger blog published to BlogSpot, as an additional ad host. If, like many Blogger blog owners, your blog is your first step in Internet activity, you cannot accomplish anything by applying directly to AdSense.

We have a few blog owners, reporting problems with sharing their blogs to FaceBook.When I share my blog on FaceBook, the photo from the blog doesn't appear. Some blurry pencil appears instead.What the blog owner is seeing, is the effect of the FaceBook Share wizard, grabbing an unwanted photo, from the page being shared.

You have 2 choices, if you want to share blog content to FaceBook - and have it all look attractive.Publish every post, containing a photo that FaceBook will want to use.Add FaceBook Open Graph code, to your blog.

Normal backup uses the "Backup" wizard, on the dashboard Template page. When backed up, an XML file, containing the template code, is extracted and saved locally. To restore, the "Restore" wizard is used and a previous Backup XML file selected.

That's how Backup / Restore should work - but it isn't always that easy.

The term "contextual" means that the ads, which display on each different blog, are chosen to match the subject in the posts. This assures the ad companies, which pay for the ads hosted on the blogs, that their ads will be seen by people who appreciate the products.

With the ads carefully chosen, AdSense can confidently charge appropriately - and the blog owner can be paid to host the ads.

When you use the BlogLovin supplied instructions to claim your blog, you will get a BlogLovin link, with an embedded token, which you install in your blog.Paste this text into a new blog post ... In some blogs, it's necessary to put the code at the top of the blog post.
BlogLovin would have you publish a new post, and put the link / token at the top of the post. This ensures that the claim link displays at the top of the page, in the blog.

A Blogger account is simply a Google account, used to publish or read blogs. If you want to delete a Blogger account, you need to delete the Google account.

If you are using your Google account for other services, maybe GMail, Google+, and / or YouTube, you won't want to delete your Google account. But you can make the Blogger portion of your Google account invisible, to the public.

We see occasional reports, in Blogger Help Forum: Get Help with an Issue, from Blogger blog owners who want to share their blogs using BlogLovin.Why can't I claim my blog? BlogLovin is somewhat monolithic. They use the blog feed, and a BlogLovin URL with embedded token, to process / validate blog claims - and their diagnostics, when a claim is a problem, are not always effective.

Some blog feeds can be validated, yet not be found by BlogLovin. And other feeds won't validate.

We're seeing a few reports from blog owners, in Blogger Help Forum: Get Help with an Issue, with blogs being inaccessible.My blog can't be seen at all, it just says error when I'm trying to open my blog. I also can't edit anything, like HTML or Template. When the blog is viewed, it will issue one of several bX codes. So far, I've identified bX-3o92c2, bX-ppgc07, bX-tqn3zr, bX-v2vqfh, bX-vg1g6a. When the blog is viewed, using an HTTP trace, the trace will terminate, showing an old friend.Error 500 Internal Server Error

We've recently seen a few blog owners, in Blogger Help Forum: Get Help with an Issue, report their blogs being classified for phishing.Today my blog was locked due to "phishing":Hello, Your blog at http://xxxxxxx.blogspot.com/ has been reviewed and confirmed as in violation of our Terms of Service for: PHISHING. In accordance to these terms, we've removed the blog and the URL is no longer accessible.No, there was no phishing in this blog - and no, I didn't change or add anything to it recently, that could trigger a false detection or report.

Not all blog owners can successfully add a conditional display of a template object, to their blog.

Some owners carefully copy the conditional code that I provide, add it to their blogs - and it does not work (for them). In some cases, it may work, for me, when I check their work.

Conditional code, that involves people in countries subject to the country specific domain redirect, won't always be comparing against "blogspot.com". People in the UK may see their blog as "blogspot.co.uk", for instance.