Apart from making your eBook the best in content, grammar,proof reading and editing you have to be careful about its exteriors. Usually it is believed that one should never judge a book by its cover but in the world of eBooks trend is completely different more over when you are selling your eBooks on eBay you need to be more careful.

The cover of your book is as important as its content. As on eBay the most striking thing any customer looks for is the free image which eBay provides with every listing. And hence they will usually make a decision to keep reading your sales page within 3 seconds of viewing your eBook cover.

So you should always have an eBook cover created for each one you write and don’t forget to use this as the 1st image on your eBay listing. As this will be the 1st thing any potential buyer sees it is essential that your cover looks the part.

There is software available that will help you to create your own covers but if you can afford it to invest a few dollars and get your cover professionally created by some artist. There are several professional cover artists who will create a cover for you. A simple google search can also bring up a ton of results. Which will cost you be anything from $10 onwards.

We can give you some smart tips to reating a quality cover that will help sell your eBook.

If you are planning to appoint some professional to create a cover go through his work and portfolio.

Try to use your own graphics or have them created from scratch. Don’t try to copy your images from another website. otherwise you can be in trouble. If you have appointed an artist make sure your he also understands this.

Dont forget to Include the title of your eBook on the cover. If your eBook has resale rights include as many different variations of your cover as possible. You should also include different sizes, colours and angles.

You should Include your cover at least once in your sales page. so that the works is a large cover on the left of the page with text to the right explaining the merits of your eBook.

Last but not the least never forget ebooks are always judged by outlooks so be very careful and attentive before writing one.

Spread the word: related/readit

by: Philipp Lenssen

SUP stands for Simple Update Protocol (officially, anyway, though it’s perhaps an acronym or backronym for “what’s up” aka “’sup”). It’s a JSON-based meta format for RSS/ Atom feeds useful for websites that deliver a large number of feeds, like a blogging platform, so that services subscribing to that site’s RSS feeds only need to download a single file to check for updates, and then download the other individual feeds as needed. SUP was invented by the ex-Google employees Paul Buchheit and Gary Burd of (recently redesigned) social feed aggregator Friendfeed. There is no official documentation at the moment outside of the Python source.

Friendfeed’s aim in introducing the format is to decrease the load in polling so many feeds from all over the web all the time (a polling that’s typically done whether or not the feed changed since last time). After all, that’s one of Friendfeed’s problems, too. “FriendFeed’s user base has grown quite a bit since launch, and our servers now download millions of feeds from over 43 services every hour,” Paul Buchheit writes in a blog post announcing SUP. A SUP feed can thus serve as first stop for feed readers to see if a feed changed, and the SUP file will only include the changes since the last SUP in a specified frequency – like 3 minutes – was published. (I remember Google’s Blogger once had such a “what’s new” file in XML format, but I’m not sure they ever attempted to turn it into something like a standard.)

So, all of this means SUP is not a competition to RSS feeds, but rather it’s a level above “watching” over it to make site updates be known faster and easier to other sites, due to a lowered load for publisher and reader programs. For sites with only a single feed or two (like Blogoscoped.com for instance) there seems to be no immediate need to support SUP (I’m not sure if it would be a speed win with Friendfeed). “[T]he benefits are most significant when the SUP feed covers a large number of other feeds,” Paul says. On the other hand, from an aggregator’s point of view the SUP format also requires you to set up a system that doesn’t miss out on its polling in the defined frequency, or else your program may miss feed update information (a look at the SUP’s time stamp could help find out about this). Paul in an email says, “SUP consumers must be somewhat intelligent when consuming feeds in order to poll at the appropriate frequency, but our goal was to make things as simple as possible for SUP producers in the hopes that most sites will be able to quickly implement a SUP feed.”

As for the syntax itself, why the choice of JSON over, say, XML? In popular browsers, XML can be checked for well-formedness and also displays somewhat formatted when directly opening it. Paul comments that JSON (JavaScript Object Notation) “is a very simple and common data format that is now supported by just about every common language … It is also very compact, which is a real advantage for SUP feeds that may have thousands of entries. An XML-based SUP feed could be easily generated, but it’s not clear that there would be any advantage (and it could easly end up being 3-5 times as large).”

At this time, not even Friendfeed itself has SUP reading support (they do have a SUP feed), but Paul says “it should be ready soon.” As SUP is so new it’s hard to tell who else will adopt the format. Paul states:

I’ve spoken with several sites, but we’re not yet ready to make any announcements.

We would like for everyone to support SUP, however Blogger already pings several blog ping services, so the benefit may not be as significant as it is with other non-blog services. One other issue with blog feeds is that many people send their feeds through Feedburner, which introduces additional delay (meaning that even after a new blog post is published, it may not appear in the RSS feed for some time).

A great example of a service that would really benefit from SUP is Google Reader. The Reader shared items feeds have “secret” urls that Google does not want to publish, so a traditional blog pinging service is not viable for them. Using SUP, they could easily notify feed consumers such as FriendFeed of which feeds have been updated without having to disclose any of the secrety urls.

Spread the word: related/readit

Source: Blogo Scoped

Adding ‘noindex, follow’ tags

What can you do to avoid this problem? You can tell the search engines what URL to index by using ‘noindex, follow’ meta tag, robots.txt exclusions or 301 redirects. Let’s say you want Google to index your front page, posts, single pages and category pages and forbid the spiders from crawling the content of archives, feeds and ‘next entries’ pages - page/2, /3, … To do this you have to add to your header.php the following code:

Code Is :
if((is_home() && ($paged < 2 )) || is_single() || is_page() || is_category()){
echo ‘< meta name="robots" content="index,follow" />‘;
} else {
echo ‘< meta name="robots" content="noindex,follow" />‘;}

For those not familiar with editing templates in WordPress: in your dashboard click Presentation menu item and after the new page is opened – click Theme Editor. In the Theme Editor choose ‘header.php’ and then paste the above code into the editor form. This code has to be inserted anywhere between head tags .

Here the tag is added to the home page but not the ‘next entries’ page (is_home() and ($paged<2)), to your posts (is_single()); to solo pages, like ‘About me’, if you created any (is_page()); and to category pages (is_category()). If you don’t want your categories to be indexed just delete || is_category(). All the other pages will get . They will not be indexed, but this will not prevent crawlers from following their outgoing links.

Adding unique meta description

For this purpose I use Head Meta Description plugin. This plugin can be configured to use an excerpt of your post as a meta description – this is especially useful if you have to add this tag to hundreds of existing pages. Or you can add your own manually as a custom field, which is my personal preference.

Using more tag

By using this tag you tell WordPress to display only the first few lines of your post. This greatly reduces the similarity of home page and your articles. If you have too many existing posts to edit, you can use an ‘excerpt’ plugin, such as this one from Semiologic

Redirect to a canonical URL

You should edit your .htaccess file to perform 301 redirects. Non-www addresses like yoursite.com should be redirected to www.yoursite.com. URL without trailing slashes like www.yoursite.com/category should be rewritten to include it: www.yoursite.com/category/ This can be done by inserting the following code into your .htaccess file:

RewriteEngine On
RewriteCond %{HTTP_HOST} !^www\.yoursite\.com$ [NC]
RewriteRule ^(.*)$ http://www.yoursite.com/$1 [R,L]
RewriteBase /
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]

For more details read this: the process or rewriting the URL layout.

Preventing spiders from crawling feeds and auxiliary pages

For this purpose you should edit your robots.txt file by inserting the following code

User-agent: *
Disallow: /wp-
Disallow: /search
Disallow: /feed
Disallow: /comments/feed
Disallow: /feed/$
Disallow: /*/feed/$
Disallow: /*/feed/rss/$
Disallow: /*/trackback/$
Disallow: /*/*/feed/$
Disallow: /*/*/feed/rss/$
Disallow: /*/*/trackback/$
Disallow: /*/*/*/feed/$
Disallow: /*/*/*/feed/rss/$
Disallow: /*/*/*/trackback/$

Spread the word: related/readit

Source: Seo Searchers