AJAX and Search Engines
In the light of the immense popularity AJAX has received and the emerging tools like Atlas and AJAX.NET, I thought it was the right time to talk about the implications on search engine behaviour on AJAX enabled websites.
In this post I’ll split websites into two categories – the public and the protected. A public website is accessible to all people and does not require login of any kind. It’s the most common type of website out there. The protected website could be an intranet site or a password protected membership site. In other words, the search engines index the public sites and not the protected sites.
When developing a protected site, you can do just about anything without the concern of search engine ranking. When developing a public website, you do not have that kind of liberty. The public site has to be search engine friendly.
So, when AJAX enabling a public website you have to make sure to keep the search engines happy at all times. If they aren’t happy with your website, neither should you be.
That’s why I’ve made a quick little list of Do’s and Don’ts about AJAX enabling your public website without loosing the search engines in the process.
Do use AJAX for user specific actions
Set cookies, track sessions and log actions as long as the content isn’t dependant of it. Search engines will have no trouble indexing your content.
Do use AJAX to save content
When a user enters information in a form field and hits the save button, you can use AJAX as much as you like. Search engines will never push the save button anyway and is therefore unaware of the use of AJAX.
Do use AJAX to do form field validation
When validating form fields, you can use AJAX to validate the input without disturbing the search engines. Search engines do not fill out forms so that won’t be a problem.
Do use AJAX to display status messages
Don’t use AJAX for displaying static text content
By static content I mean the main text content of a page and not simple information like the number of current active session or something like that. The main text content of a page is the single most important thing for search engines, so never use AJAX for this purpose.
Don’t use AJAX for paging a table or list
If the table is filled with numbers with no search engine relevancy, you can skip this point. If your table or list contains book reviews, chances are that you want them indexed correctly. If your paging is AJAX enabled, the search engines will only index the first page of the table.
Don’t use AJAX for navigational purposes
The list isn’t complete, but I think it covers the basics and will help you to avoid the biggest caveats.
Mads Kristensen currently works as a Senior Developer at Traceworks located
in Copenhagen, Denmark. Mads graduated from Copenhagen Technical Academy with a multimedia degree in
2003, but has been a professional developer since 2000. His main focus is on ASP.NET but is responsible for Winforms, Windows- and
web services in his daily work as well. A true .NET developer with great passion for the simple solution.