<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: How to Parse the Google Results Page using Regular Expressions Even if You&#8217;re a Total PHP n00b</title>
	<atom:link href="http://hackingsearch.com/2009/10/how-to-parse-google-serp-results-page-using-regular-expressions/feed/" rel="self" type="application/rss+xml" />
	<link>http://hackingsearch.com/2009/10/how-to-parse-google-serp-results-page-using-regular-expressions/</link>
	<description>Technical SEO Ryan Smith</description>
	<lastBuildDate>Wed, 31 Mar 2010 22:27:45 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=abc</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
	<item>
		<title>By: Ryan Smith</title>
		<link>http://hackingsearch.com/2009/10/how-to-parse-google-serp-results-page-using-regular-expressions/comment-page-1/#comment-3781</link>
		<dc:creator>Ryan Smith</dc:creator>
		<pubDate>Wed, 31 Mar 2010 22:27:45 +0000</pubDate>
		<guid isPermaLink="false">http://hackingsearch.com/?p=26#comment-3781</guid>
		<description>Yeah, there&#039;s definitely more than one way to skin this particular feline.  This method attempts to be comprehensive in the amount of information it harvests from the SERP while still trying to maximize resilience against minor tweaks (e.g., Google switching from h2 to h3 tags).

I think it&#039;s easier to use the tags as delimiters rather than stripping them before the parse, but I&#039;m open to your code if you&#039;d like to share it.

Thanks!</description>
		<content:encoded><![CDATA[<p>Yeah, there&#8217;s definitely more than one way to skin this particular feline.  This method attempts to be comprehensive in the amount of information it harvests from the SERP while still trying to maximize resilience against minor tweaks (e.g., Google switching from h2 to h3 tags).</p>
<p>I think it&#8217;s easier to use the tags as delimiters rather than stripping them before the parse, but I&#8217;m open to your code if you&#8217;d like to share it.</p>
<p>Thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ryan Smith</title>
		<link>http://hackingsearch.com/2009/10/how-to-parse-google-serp-results-page-using-regular-expressions/comment-page-1/#comment-3780</link>
		<dc:creator>Ryan Smith</dc:creator>
		<pubDate>Wed, 31 Mar 2010 22:22:46 +0000</pubDate>
		<guid isPermaLink="false">http://hackingsearch.com/?p=26#comment-3780</guid>
		<description>Thanks, try again with the latest version above, unless all you&#039;re really after are the URLs, in which case a much simpler regexp would of course be preferable.  I was attempting to be a bit more comprehensive (but not by much). :-)</description>
		<content:encoded><![CDATA[<p>Thanks, try again with the latest version above, unless all you&#8217;re really after are the URLs, in which case a much simpler regexp would of course be preferable.  I was attempting to be a bit more comprehensive (but not by much). <img src='http://hackingsearch.com/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ryan Smith</title>
		<link>http://hackingsearch.com/2009/10/how-to-parse-google-serp-results-page-using-regular-expressions/comment-page-1/#comment-3779</link>
		<dc:creator>Ryan Smith</dc:creator>
		<pubDate>Wed, 31 Mar 2010 22:21:09 +0000</pubDate>
		<guid isPermaLink="false">http://hackingsearch.com/?p=26#comment-3779</guid>
		<description>Thanks, I updated the code snippet above to reflect recent SERP changes.</description>
		<content:encoded><![CDATA[<p>Thanks, I updated the code snippet above to reflect recent SERP changes.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Vladimir</title>
		<link>http://hackingsearch.com/2009/10/how-to-parse-google-serp-results-page-using-regular-expressions/comment-page-1/#comment-3529</link>
		<dc:creator>Vladimir</dc:creator>
		<pubDate>Wed, 10 Feb 2010 14:59:45 +0000</pubDate>
		<guid isPermaLink="false">http://hackingsearch.com/?p=26#comment-3529</guid>
		<description>Your regexps didn&#039;t work for me at the moment of writing this comment. I have used s simpler regexp to extract URLs: preg_match_all(‘/&lt;a&gt;]+)/’, $content, $matches);</description>
		<content:encoded><![CDATA[<p>Your regexps didn&#8217;t work for me at the moment of writing this comment. I have used s simpler regexp to extract URLs: preg_match_all(‘/<a>]+)/’, $content, $matches);</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: LAMPdocs: Linux, Apache, MySQL, PHP</title>
		<link>http://hackingsearch.com/2009/10/how-to-parse-google-serp-results-page-using-regular-expressions/comment-page-1/#comment-3528</link>
		<dc:creator>LAMPdocs: Linux, Apache, MySQL, PHP</dc:creator>
		<pubDate>Wed, 10 Feb 2010 14:48:51 +0000</pubDate>
		<guid isPermaLink="false">http://hackingsearch.com/?p=26#comment-3528</guid>
		<description>&lt;strong&gt;Simple Google SERP Parser in PHP...&lt;/strong&gt;

Script to parse google search results. Works on all hosting services.......</description>
		<content:encoded><![CDATA[<p><strong>Simple Google SERP Parser in PHP&#8230;</strong></p>
<p>Script to parse google search results. Works on all hosting services&#8230;&#8230;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jason @ Searchologie</title>
		<link>http://hackingsearch.com/2009/10/how-to-parse-google-serp-results-page-using-regular-expressions/comment-page-1/#comment-3474</link>
		<dc:creator>Jason @ Searchologie</dc:creator>
		<pubDate>Thu, 04 Feb 2010 05:39:39 +0000</pubDate>
		<guid isPermaLink="false">http://hackingsearch.com/?p=26#comment-3474</guid>
		<description>Hi Ryan - love this post, but I have a question for you - is there any way you can simplify parsing Google search results by creating a RE to pull all the a tags in the Google source code, then filter out/eliminate all the links based on their target (or another criteria)?

In my head, it seems simpler than trying to tackle the whole thing with a giant regular expression - then again, when things usually seem simpler, that&#039;s when i get into a lot of trouble</description>
		<content:encoded><![CDATA[<p>Hi Ryan &#8211; love this post, but I have a question for you &#8211; is there any way you can simplify parsing Google search results by creating a RE to pull all the a tags in the Google source code, then filter out/eliminate all the links based on their target (or another criteria)?</p>
<p>In my head, it seems simpler than trying to tackle the whole thing with a giant regular expression &#8211; then again, when things usually seem simpler, that&#8217;s when i get into a lot of trouble</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scott</title>
		<link>http://hackingsearch.com/2009/10/how-to-parse-google-serp-results-page-using-regular-expressions/comment-page-1/#comment-3356</link>
		<dc:creator>Scott</dc:creator>
		<pubDate>Sat, 23 Jan 2010 22:43:03 +0000</pubDate>
		<guid isPermaLink="false">http://hackingsearch.com/?p=26#comment-3356</guid>
		<description>I think google changed there page, or your regex is not working, any chance of an update?</description>
		<content:encoded><![CDATA[<p>I think google changed there page, or your regex is not working, any chance of an update?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
