This post is important for all the bloggers, blogging on Googles Blogger platform. Whether you are presently using any post-truncating method or not, you should read this post at least once.
Truncating posts on homepage/archives/label-pages is a must for every blog. If you care for your readers and search engines, then you should know that truncating the posts will make both of them happy.
By showing only a small part instead of the complete post, you will save some bandwidth and time of your readers. And similarly search engines will load your pages quickly too. Moreover your readers will not miss the posts present at the bottom and when they click on the "read more" links to read the posts in detail, it will increase your pageviews too.
Truncating posts on homepage/archives/label-pages is a must for every blog. If you care for your readers and search engines, then you should know that truncating the posts will make both of them happy.By showing only a small part instead of the complete post, you will save some bandwidth and time of your readers. And similarly search engines will load your pages quickly too. Moreover your readers will not miss the posts present at the bottom and when they click on the "read more" links to read the posts in detail, it will increase your pageviews too.
If you are working on Blogger/BlogSpot platform, then you have at least 3 ways to truncate the posts. Two of them involve javascripting to truncate the posts and the third one (that is officially announced and suggested by Blogger) is non-javascript based. You would have seen all three of them being used by different bloggers. Some of the newly developed Blogger-Custom-Templates use the javascript based automatic-read more hack.
Sponsored Ads
What's the problem?
As the first two hacks, (viz. automatic read more hack, and manual read-more using <span class="fullpost">) use javascript to truncate the posts, so most of your readers (at least 90%) will be able to see the truncated posts, but search engines like Google/Yahoowithout javascript support in their browsers will not see your blog-pages with truncated posts. So, even though you are using the truncating (read-more) hack in your blog, they are of no help in optimizing your blog for search engines.
If you are also using one of those javascript based techniques to truncate your posts, then I will advice you to stop using that method and better switch to the third option (non-javascript based).
The solution
So I will suggest you to use the official method of truncating posts suggested by Blogger: i.e. use <!-- more --> anywhere in the blog-post to truncate it. Read the complete post here.
And if you are facing any problems in using this method, then read; how to fix errors in Blogger Read-More hack.
Benefits you will get by using this method:
1. Posts are truncated for both your readers and search engines.
2. Decreases loading time of your blog (you can check it in your Google Webmasters account), as posts are truncated for search-engine-bots too.
3. Increases page-views.
A suggestion to further optimize your blog:
Limit the non-truncated part of the posts to only 1 image (that means, show only 1 image per post in the homepage). Hide extra images in the hidden/truncated part, as it will decrease the loading time of your hompage/archive pages.
Check it yourself... - Immediately after implementing this hack in all the blog posts (being shown in the homepage), you can check and see the improvements your blog has made:
1. Go to Pingdom-Tools and note down the loading time of your blog.
2. Now apply this hack to all the posts present on your blogs homepage, and then again check the loading time of your blog at Pingdom.
You'll notice the difference;
- in the total HTML size of the blog (it will decrease) and,
- in the loading time (it will also decrease, that means your blog now loads faster).
Sponsored Ads
- The Art of SEO: Mastering Search Engine Optimization (Theory in Practice)
- Get to the Top on Google: Tips and Techniques to Get Your Site to the Top of the Search Engine Rankings -- and Stay There
- SEO Made Simple: Strategies For Dominating The World's Largest Search Engine
What's the problem?
As the first two hacks, (viz. automatic read more hack, and manual read-more using <span class="fullpost">) use javascript to truncate the posts, so most of your readers (at least 90%) will be able to see the truncated posts, but search engines like Google/Yahoowithout javascript support in their browsers will not see your blog-pages with truncated posts. So, even though you are using the truncating (read-more) hack in your blog, they are of no help in optimizing your blog for search engines.
If you are also using one of those javascript based techniques to truncate your posts, then I will advice you to stop using that method and better switch to the third option (non-javascript based).
The solution
So I will suggest you to use the official method of truncating posts suggested by Blogger: i.e. use <!-- more --> anywhere in the blog-post to truncate it. Read the complete post here.
And if you are facing any problems in using this method, then read; how to fix errors in Blogger Read-More hack.
Benefits you will get by using this method:
1. Posts are truncated for both your readers and search engines.
2. Decreases loading time of your blog (you can check it in your Google Webmasters account), as posts are truncated for search-engine-bots too.
3. Increases page-views.
A suggestion to further optimize your blog:
Limit the non-truncated part of the posts to only 1 image (that means, show only 1 image per post in the homepage). Hide extra images in the hidden/truncated part, as it will decrease the loading time of your hompage/archive pages.
Check it yourself... - Immediately after implementing this hack in all the blog posts (being shown in the homepage), you can check and see the improvements your blog has made:
1. Go to Pingdom-Tools and note down the loading time of your blog.
2. Now apply this hack to all the posts present on your blogs homepage, and then again check the loading time of your blog at Pingdom.
You'll notice the difference;
- in the total HTML size of the blog (it will decrease) and,
- in the loading time (it will also decrease, that means your blog now loads faster).