How Google Crawl the Content of your AJAX?
Search engine optimizers have experienced a dilemma in the past. In this post I will show how to use Google Ajax Crawl able proposed to allow Google to examine that your AJAX webpage improved and show examples of sites that already use. AJAX is excellent for users but not so good for search engines. Webpage that utilize AJAX to load the content page can be much faster and provide better user experience, but these sites can be challenging or extremely hard for Google to index, and using AJAX can harm the website.
Fortunately, Google has presented a proposal on how administrators can get the best of both worlds. Google has made this suggestion a year ago I do not think that has drawn much attention whether it would be particularly useful for SEO. This post is addressed to people that I have not explored the proposal for indexing by Google AJAX again - I try to be brief and not too technical!
Historically, developers have used the named anchor of the URL for AJAX-powered web sites. This is the 'hash' sign, #, and the following text. Instead of using a hash, #, the new proposal requires the use of a hash table and an exclamation mark: #! The #! combination has sometimes been called by the people hash bang geek than me, I like the sound of that word, so I am with him.
When you use the hash bang in a URL, Google understands that you are following its protocol, and interpret your URLs in a special way. They will take anything after the detonation of hash, and send it to the place as a URL parameter instead. The name parameter is used for: _escaped_fragment_
Then Google will rewrite the URL, and content of the request for static pages. To show that the URL has changed look, here are some examples:
www.demo.com/#!seattle/hotels becomes www.demo.com/?_escaped_fragment=seattle/hotels
www.demo.com/users#!name=rob becomes www.demo.com/users?_escaped_fragment_=name=rob
As long as you can get the static page (right URL in these examples) to see the same content as the user does not see (in the URL to the left), it works precisely as prepared.