PC Dekstop, Notebook, Point of Sale

Breaking

2.09.2012

How to verify Technorati claim token

Verify Technorati Token


Technorati will give you email contain unique token number like EKYCYiWuyYknoec9BFTQp0MYhfw  (new) D95AS6YN3836 (old) for this blog.

Next step is you need to write about something on your blog where you can put your token there and publish it, for example you can write a post like i did in this post, it need to show to Technorati system that you are the real owner of this blog.

Remember to put the exact token as you've get from Technorati email. You could place the code anywhere in the post (generally it is preferred to keep within the first few lines or within excerpt).

Or you can put in your html page ( just in < head > area ). Login and go to


Once you have published the post with the token in it, visit http://technorati.com/account/. Sign in to your Technorati account. Under your profile page, you should notice Technorati claim status and a button to verify claim token.

Verify Technorati Claim Token


Click on ‘verify claim token’ and Technorati will go and look for unique code in your blog. If all goes well, Technorati will visit your blog, find the token and verify it.

You may sometimes get an error message with Technorati mentioning that “we have encountered a problem reading your site’s data.” If that occurs, make sure your claim code is correct (as it mentioned on http://technorati.com/account/ on your claimed blog) and is reflected in your blog’s RSS feed.

For blogs, having feed excerpts enabled, make sure the code appears in excerpt. It's important to be noted that token that you got from email not always as it want on http://technorati.com/account/ so read carefully on error message beside your blog picture.

There are a number of possible causes of claim failures. Here are some pointers to help make your claim successful: 1) Don't redirect A redirect is a mechanism for telling a browser, or anyone trying to find content at a given URL that they should look at a different URL.

For example, some who used to have a blog at http://myOldOldBlogSite.zzz and now has a blog at http://mySnazzyNewSite.zzz might set up a redirect so that anyone going to the old site gets automatically sent on to the new site.

This can be quite useful, but if you do this, please do NOT try to claim the old site URL. When it tells us there's nothing there and we should look elsewhere, we believe it, so we don't want to add the old URL to our system.

If you want to claim the new site, please do, but use the new URL. Of course, we don't have a problem with minor redirects that are essentially the same location, such as redirects that add or remove www or a slash at the end of the URL, or to go from http://mySnazzyNewSite.zzz to http://mySnazzyNewSite.zzz/index.php

2) Make sure the claim code (also called the claim token) is in a post and is visible in your feed.

Technorati relies very heavily on feeds for all of our processing, so make sure we can find the code there. And the code needs to be in a post -- there are too many ways to get text onto someone else's blog page, so we require that you demonstrate that you can actually make or edit a post to claim a blog.

We realize that putting this odd code text into your feed means that all of your feed followers (and perhaps Twitter, Facebook, and other sites) will see it, but it's the best method we've found so far to demonstrate to us that you control the blog. You can remove the code once the claim is complete. It's probably best to put the code at the beginning of an existing post, and then remove it after claiming.

Many feeds do not include the full post, so putting it at the start of a post ensures it gets into your feed. Then when you're done, you can remove it and it's gone.

If you create a new post for the code and then delete the entire post, many systems cannot tell if the post was deleted or just aged off of the feed like an old (but still valid) post, so may not remove it when you do. 3) Do not block Technorati using the robots.txt access control mechanism.

Web sites can host a file named robots.txt that specifies what automated software ("robots") are allowed to access. Not all software obeys these directions, but Technorati does, so if you have a robots.txt file that doesn't allow us to read your site, we won't. If you use a blogging service such as BlogSpot or LiveJournal, this is likely controlled via your blog settings for privacy.

Look for settings relating to allowing search engines to index your blog. If you are hosting your own site, make sure to permit access to TechnoratiBot (currently our UserAgent is TechnoratiBot/8.1). You can learn more about using robots.txt and the Robots Exclusion Standard at robots.org or Wikipedia.

How to verify Technorati claim token, read more: http://technorati.com/blog-claiming-faq/

No comments:

Post a Comment