This is important to creating search friendly websites because ensurng search engines are able to crawl and index your content is necessary to acquiring search traffic and market share. By not embracing these approaches, you are leaving yourself in a handicap for SEO efforts and leaves you at a competitive disadvantage. In fact, it should not even just be designed on a project per project basis, but should be built into code that takes advantage of web standards and progressive enhancement.
The AJAX Dilemma for SEO
Notice something different? Of course you do, it is VERY blatently obvious that the entire content within the tabs is completely missing. This is a large opportunity that is missed by ifoodstv.com at getting content not only indexed, but great internal links to deep content.
Do you notice a difference here at all? No?! Well, thats right, because there isn’t one.
Also, to add to that, iMedix is rewriting URLs so that there are no hash tags in the URLs:
Resources to help with AJAX and SEO
Google Webmaster Central: A spiders view of Web 2.0
Dom Scripting: Hijax
Progressive Enhancement with AJAX
Follow me on Twitter for more info @tonyadam or subscribe to my feed to keep up to date!
There are 8 comments
Nice… I wrote about this awhile back on my personal blog here.
Or.. they could just include a sitemap.xml file….
@popo that is completely untrue…sitemaps.xml only provides pages on a site, not the content within them.
I know a good AJAX framework to make it SEO friendly and has a demo on http://www.ajaxoptimize.com/
I may have missed something on the imedix.com example but it works because it is not doing any Ajax stuff with the tabs. The only Ajax stuff seems to be to reload the tab images and data. When you click on a tab it reloads the entire page, which is why the URL is correct in the address bar (btw I traced all this using wireshark).
The tab example seems complicated with Hijax. Taking the progressive enhancement approach
i. The baseline code would have different versions of the page for each tab.
ii. You could use CSS/DOM to have a single page with different content shown depending on the tab that is clicked. From an SEO perspective you would have one big page will all the content in something like individual list elements. However this would not be possibly to hijaxify.
You would have to return to i) and rather than load the entire page reload just the tab data but I’m not sure this is possible either with the hijax approach.
In short it seems like you would have to do this at the server side. Either server a CSS/DOM version of the page if the browser doesn’t support JS or an Ajax version of the page.
I’d be interested in comments though.
[…] be indexed or crawled by a “search engine spider.” There are tips and tricks on on how to build Ajax SEO Friendly websites out […]
[…] issues by developing Progressively Enhanced code. While, I’ve written about how to address crawling and indexing with AJAX and SEO. I wanted to take a little bit of a deep dive into this again, along with the bigger issue, […]