Click here to Skip to main content
15,891,253 members
Please Sign up or sign in to vote.
0.00/5 (No votes)
See more:
I've read on how one could have his ajax content crawl-able by Google bot using the #! (hashbang?) protocol which delivers HTMl to the bot.

Yet, I couldn't figure the point of having ajax indexed. IMHO the only relevant indexing one might want is HTML (container page) + AJAX as a whole.

If http://someexample.com#!value=top-sell outputs
JavaScript
{ "value" : "carrot" }
and google index it, what good it is to the user?

It has no meaning outside of a HTML page which could looks like this:
HTML
[...]
<script src="item-handler.js" />
</head>
<body>
Our store best selling item is <output id="top-sell"></output>!
</body>
</html>



Here's how I picture the every day use case of #!:

User: Searches "carrot" on Google
Google: Display http://someexample.com#!value=top-sell in the result
User: Clicks the link
Server/Browser: Renders
JavaScript
{ "value" : "carrot" }

User: "What kind of gibberish is that?!"
User: Sends a email to web-master: "You suck!"

And I definitively don't want to do the latter...
Posted
Updated 2-Apr-14 22:50pm
v3
Comments
Sergejack 7-Apr-14 3:18am    
Does nobody know?

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)



CodeProject, 20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8 +1 (416) 849-8900