<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: Parsing RSS Using Magpie and Ajax</title>
	<atom:link href="http://aarronwalter.com/2006/12/29/parsing-rss-using-magpie-and-ajax/feed/" rel="self" type="application/rss+xml" />
	<link>http://aarronwalter.com/2006/12/29/parsing-rss-using-magpie-and-ajax/</link>
	<description></description>
	<pubDate>Sun, 23 Nov 2008 13:47:14 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5</generator>
		<item>
		<title>By: entro</title>
		<link>http://aarronwalter.com/2006/12/29/parsing-rss-using-magpie-and-ajax/#comment-22211</link>
		<dc:creator>entro</dc:creator>
		<pubDate>Sun, 02 Dec 2007 13:08:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.aarronwalter.com/2006/12/29/parsing-rss-using-magpie-and-ajax/#comment-22211</guid>
		<description>This is a good example of clever ajax usage but still does not produce the desirable SEO effects. 
A perfect SEO solution would use the same page and render the same html results whether a client uses javascript or not.</description>
		<content:encoded><![CDATA[<p>This is a good example of clever ajax usage but still does not produce the desirable SEO effects.<br />
A perfect SEO solution would use the same page and render the same html results whether a client uses javascript or not.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aarron</title>
		<link>http://aarronwalter.com/2006/12/29/parsing-rss-using-magpie-and-ajax/#comment-630</link>
		<dc:creator>Aarron</dc:creator>
		<pubDate>Mon, 05 Feb 2007 18:52:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.aarronwalter.com/2006/12/29/parsing-rss-using-magpie-and-ajax/#comment-630</guid>
		<description>This is a good question that is addressed by building these sorts of JavaScript driven applications in an accessible manor. The solution is actually already built into the article. I use a noscript tag to show a link that manually loads in the RSS headlines if JavaScript is disabled/not available. Search engine spiders will trigger that link and get to the headlines all the same, refreshing the page with the headlines loaded. The PHP script looks to see if the RSS parsing request is coming from an Ajax call or a regular, JavaScript free call. The result is a slower load when done without the Ajax because all of the headlines have to be parsed before sending it to the browser, but the content is still the same. This is generically referred to as Progressive Enhancement.  

Jeremy Keith has a book that will be coming out this month called "Bulletproof Ajax" that explores other Progressive Enhancement techniques in more detail.</description>
		<content:encoded><![CDATA[<p>This is a good question that is addressed by building these sorts of JavaScript driven applications in an accessible manor. The solution is actually already built into the article. I use a noscript tag to show a link that manually loads in the RSS headlines if JavaScript is disabled/not available. Search engine spiders will trigger that link and get to the headlines all the same, refreshing the page with the headlines loaded. The PHP script looks to see if the RSS parsing request is coming from an Ajax call or a regular, JavaScript free call. The result is a slower load when done without the Ajax because all of the headlines have to be parsed before sending it to the browser, but the content is still the same. This is generically referred to as Progressive Enhancement.  </p>
<p>Jeremy Keith has a book that will be coming out this month called &#8220;Bulletproof Ajax&#8221; that explores other Progressive Enhancement techniques in more detail.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brian</title>
		<link>http://aarronwalter.com/2006/12/29/parsing-rss-using-magpie-and-ajax/#comment-629</link>
		<dc:creator>Brian</dc:creator>
		<pubDate>Mon, 05 Feb 2007 17:18:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.aarronwalter.com/2006/12/29/parsing-rss-using-magpie-and-ajax/#comment-629</guid>
		<description>Thanks for this code, Aarron.  I used it and it works great.

I have a question, though.  I was wondering if there was a way to make the displayed text more SEO friendly.  As you know, one of the benefits of having blog headings on a page is there is the potential for these headings to contain keywords, which could enhance the page's visibility.  Also, the changing content looks good to search engines, making the site look like it is updated frequently.

Since the headings are brought in dynamically they lose that SEO benefit.  I don't know enough about PHP/Ajax/Rss to evaluate any alternatives or solutions.  I was wondering if this is something you've thought about or had a solution for?</description>
		<content:encoded><![CDATA[<p>Thanks for this code, Aarron.  I used it and it works great.</p>
<p>I have a question, though.  I was wondering if there was a way to make the displayed text more SEO friendly.  As you know, one of the benefits of having blog headings on a page is there is the potential for these headings to contain keywords, which could enhance the page&#8217;s visibility.  Also, the changing content looks good to search engines, making the site look like it is updated frequently.</p>
<p>Since the headings are brought in dynamically they lose that SEO benefit.  I don&#8217;t know enough about PHP/Ajax/Rss to evaluate any alternatives or solutions.  I was wondering if this is something you&#8217;ve thought about or had a solution for?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
