Optimizer are often faced with a dilemma: on the one hand, by using AJAX loading content on a page can be done much faster and more convenient user interface, but on the other hand, these Web sites Google is difficult (or impossible) to index, and the use of the protocol index AJAX can significantly interfere poikovom promotion website. To everyone's happiness, almost a year ago, the Google search engine offered a solution to this problem. First of all, this article is for those webmasters who are not fortunate enough to get a deal from Google. We will try to explain the principle of this method is accessible language and explain it on the example of a well-known site.
So, to start Google offers to make two versions of the content of the site - one for JS-users with the URL in the style of AJAX and the second - the content for search engines to a "normal" urlom.
Traditionally, the web developers used "concrete anchor" as part of the Internet address to AJAX websites (this is # - hash symbol and the text after it). If you click on one of the menu, you will notice changes in the address bar of your browser, the content with the page loads instantly. Of course, it's not bad for a user, but the search engines are experiencing some difficulties. To solve this problem, Google suggests using #! instead of #.
Protocol indexing AJAX
As soon as you or any other webmaster nachninaete use traditional heshbeng (#!) In the Web sites, Google search engine robot detects that you're using his protocol and interprets URL-address in a special way - the bot uses all that is after heshbenga as a parameter URL with the name _escaped_fragment_. Google then rewrites URL and request content from a static page. Below are some examples of protocol index AJAX:
• www.ldi.ru/ #! optimizaciya-saitov/prodvishenie-saita becomes www.ldi.ru/?_escaped_fragment = optimizaciya-saitov/prodvishenie-saita
• www.ldi.ru / users #! Name = AlexanderAnisimov becomes www.ldi.ru/users?_escaped_fragment_=name=AlexanderAnisimov
As you've probably realized if the static pages (in this example, the address on the right) display the same content, which will see an Internet user (the address on the left), then everything will work as it should.
It turns out that Google returns the index static URL, which is the right thing to do, because they do not want to hurt people who do not use Javascript, redirecting them to the page where the Javascript needed. For this purpose, the sites most likely will want to add Javascript, which will determine the users with Java and sends them to a page with improved AJAX.Vozmozhno, you will not like indexed URL-address parameter will contain "_escaped_fragment_". In fact, this can be avoided and make URL-address more attractive with a 301 redirect. Take for example the first of the options discussed above: www.ldi.ru/?_escaped_fragment = optimizer -saitov/prodvishenie-saita becomes www.ldi.ru / directory / optimizer -saitov / prodvishenie-saita
The "live" example
One of the best examples of this new technique can be a fairly large website - new version Twitter.Esli you are a registered user of microblogging service Twitter and you have Javascript , you can view the profile by clicking the following link: http://twitter.com / #! / AlexanderAnisimov
However, the Google search engine robot detects an Internet address in the new format and instead enters this: http://twitter.com/?_escaped_fragment_=/ AlexanderAnisimov
However, Twitter wants to maintain compatibility, and at the same time be attractive indexed URL-address, and therefore uses a 301 redirect: http://twitter.com/AlexanderAnisimov
If you are logged in user Twitter, the latter of the above as an example URL-address will redirect you to the first.
0 comments:
Post a Comment