If it’s possible to judge a book by its cover, why not a blogger by their blog?
Look at the statements below and choose the FOUR that you think most closely describe your blog. Each statement is numbered. Match the numbers to the words in the table at the bottom of this post to find out what your blog says about you….
- Your blog includes a blog roll or list of other book blogs you admire
- You frequently take part in tags, blog hops or feature ‘who’s that blogger’ type posts
- Your blog has been going for more than a year
- You display your stats – views, followers, etc – prominently on your blog
- Your most frequent posts are discussion pieces
- Your blog features lots of custom-made graphics
- Your blog has an archive, lists of reviews by category/genre/author, reading list pages or challenge pages
- On your blog you feature books from a number of different genres
- Your blog focuses on one main book genre
- Your blog is linked to at least four of the following social media channels: Twitter, Facebook, YouTube, Instagram, Pinterest
- You frequently feature books with some of the following characteristics: LGBT; gender diversity; people with disabilities; characters from ethnic, cultural, and religious minorities; banned books; literature in translation
- Your blog has used several different design themes
- You post at least five times per week
- You post less than five times per week
- Book reviews on your blog are most likely to be for ARCs or recently published books
- You often feature author interviews/Q&As
Why not share in four words what your blog says about you in a comment below.
One of my pet hates is books with loads of typos, such as spelling and punctuation errors, or other editing issues. (I’m aware this means people will now be scouring this blog post for errors – but I’m not an author trying to sell you their book!) I make a point of stating in my review policy that books which haven’t been proofread properly (or at all) will get a poor review, if indeed I actually finish them.
From time to time, I still come across books with lots of typos and it got me wondering – what is the best response in those circumstances?
- Provide a few examples of the typo’s you’ve noticed to the author and suggest they have the book professionally proofread and/or copy-edited (or ask for their money back if they reckon it already has!).
- Give the author a list of all the errors you’ve noticed. However, this means you’re doing a proofreader out of a job and, unless you’re a professional proofreader yourself, you’ll probably have missed some anyway.
- Don’t inform the author but reflect the issues in your rating of the book and mention it in your review.
- Ignore (or in my case, try to) the errors and concentrate on the plot, characters and other aspects of the book.
- Chuck the book away unfinished and move on. However, this means leaving unsuspecting future readers to experience the same issues.
I’ve probably done all of the above at one time or another but what’s your view?
A few weeks ago, I wrote about some of the temptations I’ve encountered as a novice book blogger. You can read my original post here. Confession time: I’ve been better at warning others of temptations than I have at resisting them.
In particular, the temptation I referred to as The Author’s Best Friend Temptation – that seemingly irresistible urge (for me, anyway) to say ‘Yes’ to review requests from authors when you really should glance at your TBR pile and say ‘No’. As a consequence, I’ve amassed quite a stack of books from indie authors needing review, some going back several months.
In an effort to make amends, I’ve decided to devote July to reading and reviewing as many of these books as I possibly can. In order to do that, I’ve made a deliberate effort to limit my other commitments next month and read ahead as much as possible for blog tours or publication dates in July.
And what about some of the other temptations I identified, like The NetGalley Frenzy Temptation? Ah well, best draw a veil over that one for the time being. One confession is enough for now.