What is a good example of a strategy to achieve advertising convenience in a javascript-enabled application?

Question

Introduction

I know this was asked before, but the questions I found were either specific or generals to provoke the answer I was looking for. The best possible answer I can imagine would be an example using a backbone and the least amount of server logic (there is no preferred language / structure there).

Problem

I am planning a javascript / ajax-heavy application (backbone + most-json backend) that implements a faceted search. Take, for example, the faceted search for a simple app for a shoe store that lets you filter the color, brand and type of shoe and sort by price and size or something else.

Suppose I use a backbone or similar structure on the client and the json service as the backend.

What would be a good (compromise between effort and outcome) strategy to achieve friendliness, as well as a fast interface?

Resources

The solution that caught my attention was Hijax, reusing server-side client templates, as described here: http://duganchen.ca/single-page-web-app-architecture-done-right

Resources I digested without a final conclusion

• http://code.google.com/intl/de-DE/web/ajaxcrawling/
• stack overflow
• http://www.quora.com/Search-Engine-Optimization-SEO/If-I-have-data-that-loads-using-json-JavaScript-will-it-get-indexed-by-Google?q= seo + javascript

Answer 1

Common sense in SEO friendliness: It should work without JavaScript .

It is also good for accessibility, so you should do it this way, if the user does not have JavaScript enabled (for example, in a search engine), it will work.

If it has JavaScript enabled (like any sane person), it will work with all the great JavaScript features you have added.

As a general rule of usability: If it works, it should also work without JavaScript!

Answer 2

The solution to your first link sounds right. The main problem of a single-page application is that you have to display your templates on both sides, the backend and the interface. Using a Mustache or Google closure template would be a good solution for this.

The same solution that was used for google +, where initially the side will be displayed on the server and you load a static html page, after which the page will be displayed on the client side, but with the same templates as on the server.

Answer 3

Also remember that search engines most often link to links than they (ever?) Fill out forms.

This problem, which allows scanners to see your db content, is called a dark web, an invisible network, a deep web, or a hidden network. Blog post

So your expression about the problem:

an aspectual search for a simple app for a shoe store that allows you to filter the color, brand and type of shoe and sort by price and size or something else.

I would suggest that you include a search in the link hierarchy in addition to searching through forms with selection fields.

For example, in the additional menu there are all different brands as separate links. Then each link should lead to a list of products sold by this brand. The trick is to arrange things so that the link to individual shoes returns you to the first page (an application with a rich one page), but shows specific shoes. - And the page should implement the Google Ajax workarounds that you link to in OP.