You are currently browsing comments. If you would like to return to the full story, you can read the full entry here: “3 Good Reasons Why Google Has Lost It On The Ajax Thing”.
3 Good Reasons Why Google Has Lost It On The Ajax Thing
New to the Search Marketing Standard Blog?
Subscribe to our blog via our RSS feed and receive updates and tips.
WHAT’S NEXT?
- Read more Organic articles.
- Subscribe to our weekly newsletter for practical how-to, industry stats and expert advice.
- All articles are available for republishing as long as you provide a link back to the original article.
- Become a premium member to get the print and digital magazine and premium content.
About the Author
Jaimie Sirovich (16 Posts)
Jaimie Sirovich is a search marketing consultant. Officially he is a computer programmer, but he claims to enjoy marketing much more. At present, Jaimie is focused on helping clients sell everywhere, and achieve multi-channel integration with major websites such as eBay, Amazon, and even Craigslist. He is the author of Search Engine Optimization With PHP. Jaimie can also be reached directly at jaimie@seoegghead.com.
6 Comments
Share Your Thoughts
GET PUBLISHED
Looking to promote your business and grow your industry credibility? Come write for us!
SIGN UP
[...] Guidelines – basic principles) is nonsensical. Especially when paired with the latest news of Google’s attempt to solve the AJAX issue – developers are left to struggle with increasingly outdated search engine technology in an [...]
[...] Guidelines – basic principles) is nonsensical. Especially when paired with the latest news of Google’s attempt to solve the AJAX issue – developers are left to struggle with increasingly outdated search engine technology in an [...]
[...] Guidelines – basic principles) is nonsensical. Especially when paired with the latest news of Google’s attempt to solve the AJAX issue – developers are left to struggle with increasingly outdated search engine technology in an [...]
Another and better alternative to Google approach: ItsNat
With ItsNat you develop a Single Page Interface (AJAX intensive) application and (almost) automatically the same is page based when JavaScript is disabled or ignored (like search engine crawlers see your site).
Take a look:
The Single Page Interface Manifesto
http://itsnat.sourceforge.net/php/spim/spi_manifesto_en.php
Single Page Interface Web Site With ItsNat
http://itsnat.sourceforge.net/index.php?_page=support.tutorial.spi_site
SPI web site online demo
http://www.innowhere.com:8080/spitut/
I think you have a bunch of misconceptions. Google does require you to have a headless browser. That is just a suggestion if you don’t want to write html for each request.
The way google does it is actually really simple, not confusing, and really the only way it can be done since browsers and spiders don’t send text after # to servers.
You just get the text after #! turned into _escaped_fragment_ get var… You parse it and add meta if you need.
I think Facebook might do that too… or they might be just plainly putting it in as a get var key…
It’s a lot of redundant work to do so, however.
Anything involving ‘escaping’ tends to cause problems for low-level programmers who don’t know what a grammar is. There is no misconception on that.
I predict Google AJAX will go the way of the dodo pretty soon, and if you do a quick Google search you’ll see I’m not the only one who thinks so. I just said it a year or two ago.