How To SEO Optimize Your Blogger Blog Titles For Higher Search Results

Today I Show You How To  SEO Optimize Your Blogger Blog Titles For Higher Search Results
This is called "Blogger/blogspot Title Swapping". Swapping blogs title can help boost your position in search engine results page listing and also increase clickthroughs. From an SEO (Search Engine Optimization) perspective, page title is the most important element in your blog in terms of ranking well in search engines. If you look at your browser's title bar you will notice that Blogger's default templates display your blog title in front of each page or post title. So page title would normally be displayed as:

After swapping the blog title, it will be appearing like this:

This kind of placement will be also appearing in google search results. The reason why you should put post titles at the beginning is because users are more likely to search for specific post content rather than the actual name of your blog. So having the post titles at the beginning increases your chances of being found.

How to optimize blogger post titles

Step 1. Log in to your Blogger Dashboard and go to Template > Edit HTML

Step 2. Check the "Expand Widget Templates" checkbox

Step 3. Find (CTRL + F) this code:

<title><data:blog.pageTitle/></title>

Step 4. Replace the code above with this one:

<b:if cond='data:blog.pageType == "item"'>
<title><data:blog.pageName/> |<data:blog.title/></title>
<b:else/>
<title><data:blog.pageTitle/></title> </b:if>

Step 5. Click Save Template and you are done.

Any Question Write In Comment Section

How to Make Smartphone Sites Load Fast?

 How to Make Smartphone Sites Load Fast?
According to the latest researches, it is estimated that around 15% of all internet users are mobile users who typically use smartphones or tablets to browse the internet. And a large majority of those mobile users need to find instant results. Indeed, the whole point of using internet on a smartphone is it's quick mobility and its convenience. Hence, site load speed makes all the difference in the mobile web. The average mobile page takes around 7 seconds to loads. But wouldn't it be great if you could greatly reduce that time to under 1 second for a decreased bounce rate? Today, we'll talk about how Google is helping webmasters optimize their website for mobile, and decrease their load time.

Google has provided some latest guidelines, and has introduced a new tool as well called the PageSpeed Insights Tool. These two aim at providing webmasters with all the help they need to increase their page speed for mobile pages.

Tips for improving load-time

The 1 second time budget is incredibly hard to achieve. But for mobile sites, it is essential. Therefore, a different-than-conventional approach has to be used. The ideas is to deliver the Above-The-Fold content very quickly, so that users can start interacting with the website as soon as possible. The rest of the content can then be loaded in the background in the meantime.

Here are a few approaches that can be taken to achieve a sub-second rendering.

Quick server response - The quicker the web server takes to return the initial HTML and content, the better. Ideally, server response should be below 200 milliseconds, And this does not count network transfer speed. So port to a faster web hosting server to enhance mobile load speed.

Avoid HTTP redirects - Each redirect requires an addition roundtrip to the server, two if an addition DNS lookup is needed. This wastes a lot of time, and often times accounts for times over one second.

Keep ATF data below 14k - The nature of TCP is such that when a client makes a request, it doesn't immediately start sending out as many data packets as is allowed by the bandwidth. This phenomenon is called TCP Slow Start, and it initially sends out only a few (for e.g. 10) packets until it receives acknowledgement from the client and fills up the bandwidth in response. Due to this behaviour, it is important that your initial, Above-The-Fold content fits under 14 KB. This will minimize the roundtrips needed to get the initial data. Also make sure your server is running the latest version of TCP, because older versions only send out 3-4 packets on a Slow Start!

Avoid external blocking JS and CSS - JavaScript and CSS renders that require clients to download an external resource not only take up download time, they also increase the number of roundtrips made, hence slowing down the page load-up. A better approach is to use inline JS and CSS for ATF content, and use external blocking JS and CSS later.

Optimize your code - Complex and inefficient JavaScript codes can take up hundreds of milliseconds. Always make sure you use the best practices, and try to avoid doing complex JS computations, at least on the ATF content.

Reserve time for browser rendering - Client machines also take time to render the HTML, CSS and JS content. The rendering time depends upon the specific machine a user is using. But reserve a minimum of 200 milliseconds when optimizing your mobile site, and trying to achieve the 1 second target.

After you've made these optimizations, you can test them out in the Google PageSpeed Insights Tool. We'll leave it as an exercise for you for now to use this tool, and understands the insights it generates for improving your load speed. And as always, if you have questions, please feel free to ask in the comments section below. Cheers :) Regarding Mustafa Ahmedzai For Nice Post

SEO Settings for rel=prev and rel=next

Sites often tend to paginate their content into several, smaller logical chunks that make it easier for readers to navigate through and keep track of. You can often see this type of thing in in-depth product reviews, where there are different sections divided into different pages. Similarly, news and other such publishing sites often tend to divide a very long article into several smaller chunks. Discussion forums also often break threads into sequential URLs. People have often asked us about how to handle such type of Pagination from a SEO point of view, because you want search engines to be able to associate all the related 'pages' together. Well, today, we'll tell you about the correct SEO Settings to paginate large content on your site.

When paginating, you can do two things to help search engines understand your content structure. You could either specify a view all page, or you could use rel="prev" and rel="next" to describe the associativity.

A View-all Page

You can create two versions of your content. One View-all page, which has all of the content on the same page. Some readers prefer this, since it doesn't require additional page loads. Google tries to show this page in search results. However, you can also create paginated version of the same content, and then use rel="canonical" on each component page, pointing to that View-all page, so as to avoid content duplication.

Check out the following post to find out more about using rel="canonical"

• Best SEO Practices for rel="canonical"

Using rel="prev" and rel="next"

You can use the next and prev attributes in HTML links, so as to describe the relation between two page. For example, suppose your content is broken up into three separate pages.

• example.com/part1.html
• example.com/part2.html
• example.com/part3.html

Now, on the first page, you simply need to define a "next" page only, since there's no "prev" page. Similarly, for the last page, there's no "next" page; only a "prev" page.

• For the first page, you can simply add a link to the next page using the <link> tag inside the <head> tag.
  
  <link rel="next" href="http://example.com/part2.html">
  
• Similarly, the last page (part3) needs a link tag in its <head> section as follows
  
  <link rel="prev" href="http://example.com/part2.html">
  
• Since all the middle parts have both previous and next counterparts, you need to include two links in such parts.
  
  <link rel="prev" href="http://example.com/part1.html">
  <link rel="next" href="http://example.com/part3.html">

Things to remember

The rel="prev" and rel="next" attributes are just hints to Google. They're not absolute directives. Meaning that they don't define the content or anything. They just tell Google what comes before and after this content.

URL parameters that don't change a page's content should also be included in the prev and next links. Examples of such parameters include session IDs, tracking number etc. Suppose you have a page example.com/article?page=2&id=123. It should contain the following link tags.

• <link rel="prev" href="http://example.com/article?page=1&id=123">
• <link rel="next" href="http://example.com/article?page=3&id=123">

Google itself does a very good job of recognizing such content. So even if you make a mistake with the prev and next attributes, it'll continue to index your pages, and rely on its own heuristics to understand the content. So you needn't worry about getting it wrong. But just make sure you don't make a mistake while using rel="canonical" (discussed above). Otherwise, you should be fine. Thanks For Reading