<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Daniel Skinner: News and Articles on Web Development &#187; ajax</title>
	<atom:link href="http://www.daniel-skinner.co.uk/tag/ajax/feed" rel="self" type="application/rss+xml" />
	<link>http://www.daniel-skinner.co.uk</link>
	<description>Daniel Skinner&#039;s Blog: Web Development news and articles</description>
	<lastBuildDate>Wed, 18 Mar 2009 15:11:23 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Key points when considering SEO in an AJAX application</title>
		<link>http://www.daniel-skinner.co.uk/key-points-when-considering-seo-in-an-ajax-application/04/08/2007</link>
		<comments>http://www.daniel-skinner.co.uk/key-points-when-considering-seo-in-an-ajax-application/04/08/2007#comments</comments>
		<pubDate>Sat, 04 Aug 2007 16:58:26 +0000</pubDate>
		<dc:creator>Daniel Skinner</dc:creator>
				<category><![CDATA[Web Development]]></category>
		<category><![CDATA[ajax]]></category>
		<category><![CDATA[javascript]]></category>
		<category><![CDATA[seo]]></category>

		<guid isPermaLink="false">http://destiny.xeaura-host.co.uk/blog/key-points-when-considering-seo-in-an-ajax-application /03 /11/2007</guid>
		<description><![CDATA[A collection of notes based on the SEO implications of AJAX applications.]]></description>
			<content:encoded><![CDATA[<ul>
<li>Minimise the payload &#8211; put all javascript in external files, consider using a lightweight javascript loader which loades the meatier js files in only if javascript is enabled. Google does not seem to like reams of uncomprehensible code.</li>
<li>Always have a non-javascript fallback to all pages &#8211; this includes forms, dialogs and most importantly pages.</li>
<li>Endevour as much as possible to separate style from layout, code from content, logic from interface&#8230; pretty much everything from everything if time and resources permit.</li>
<li>Try to consider all the possible ways in which a user can interact with your AJAX application &#8211; as AJAX applications tend to be more like desktop applications than traditional web applications. The MVC and HMVC patterns adapt well to AJAX applications.</li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://www.daniel-skinner.co.uk/key-points-when-considering-seo-in-an-ajax-application/04/08/2007/feed</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>
