tags:

views:

166

answers:

4

on my site ive got a search box in center with google, when you search for something it displays all threads that matched the search criteria.

so these threads are all ajaxad in, but when you click on a thread it will go to the thread content with usual href link and the page will refresh.

now i have to let google find these threadlinks that link to every thread in the usual way, so if i put a 'show all threads'-link in my first page on the upper right corner that shows every thread in my site, does it solve the SEO part?

google is able to index them all, but the users will just use the ajax search box?

i've read that "as long as google can find all your contents from the first page (index.php) its fine". so this will be a good solution?

+1  A: 

This will work - up to a point - and you'd be better off putting the links on a different page. You can trust that your users will go with the path of least resistance. If your search works better than your listing, you'll be fine there.

Regarding Google, what you described sounds a lot like a sitemap. That'll work OK, but consider breaking it up into multiple pages if you exceed around 150 links (that's about the time the searchbot gives up). The page should also be something else than index.php, and then just provide a link to it on the home page. A lot of news sites categorize by day or week, but you could also use alphabetical or other. Use whatever system works best for your site.

Mike Robinson
+1  A: 

Turn of javscript on your site. Can you navigate to the threads in some fashion? If so, you can assume Google can as well.

I ahve to assume that your site isn't solely dependant on search to find threads. There should be some sort of traditional category-based way to get to the forums. If so, that should be all Google needs.

Worse case? Yes, a single link to some sort of index of all posts should work as well.

DA
its the latter one:) so why do a lot of people complain about ajax + seo struggling when you can solve it this easily? or have i missed something?
weng
+3  A: 

One of the downsides of AJAX is that it breaks a fundamental aspect of the net: that anyone visiting a given URL will get the same page view. This means bookmarking doesn't work right (or at all) for you and link sharing doesn't work right. It also means that bots (even very smart bots) may miss whole sections of your site.

One way to approach this is to make sure that all of your content is reachable via non-AJAX means. Graceful degradation is an important design concept, but it can be difficult to implement after the fact. My rule is to make the site work correctly without any JS magic, and then make it snazzier if JS is enabled. This is also good from an accessibility point of view since many people with handicaps can't benefit from (or are actually further disadvantaged by) AJAX and other JS wizardry.

Peter Rowell
but cant you solve the URL part with really simple history or google ajax webkit?
weng
Short answer: No. If all of the information needed to get to a particular place in your site is not in the URL then you have broken the REST contract. See http://en.wikipedia.org/wiki/Representational_State_Transfer. It's fine to build a site (e.g. Google maps) that does not pretend to be RESTful, but doing so means that you have violated fundamental assumptions made by all spiders/search engines. This also includes using cookies to store state - most indexing bots do not acknowledge cookies.
Peter Rowell
A: 

I use jQuery and this site was very helpful: restoring-conventional-page-navigation-to-your-javascript-application-with-jquery-history-plugin