<?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: Google&#8217;s &#8220;Scalable&#8221; Solution</title>
	<atom:link href="http://www.jlh-design.com/2008/01/scalable-solution/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.jlh-design.com/2008/01/scalable-solution/</link>
	<description>Terrible writing and mere conjecture</description>
	<pubDate>Fri, 16 May 2008 02:30:21 +0000</pubDate>
	<generator>http://wordpress.org/?v=abc</generator>
		<item>
		<title>By: Craig</title>
		<link>http://www.jlh-design.com/2008/01/scalable-solution/#comment-5541</link>
		<dc:creator>Craig</dc:creator>
		<pubDate>Wed, 13 Feb 2008 11:59:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.jlh-design.com/2008/01/scalable-solution/#comment-5541</guid>
		<description>I like the "Web search certified engineer" thingy, where do I sign up?  :-()

Actually, here is an idea, although maybe not any more scalable than anything else but here goes anyway,,,

A webmaster's site tanks, they come to the Google Webmaster Help forum and pose the problem. If after everyone diligently working on the problem, no one finds anything obvious, which I think most of us would find things with spammers' or black-hat sites, the problem is escalated to someone who can peer into Google's algo crystal ball and give ideas as to what areas are problematic.

An example of this that I think worked well, although maybe took longer than maybe it should have, is Sam I Am's website.  We all wracked our brains looking for anything and everything and the real problem turned out to be something that almost no one had imagined.

A Googler then steps in and gives a general overview of the problems, Sam I Am and his brother then go off and do the work that is needed.  In the trade off we end up with a new and valuable member of the GWMH forum in Sam I Am who may not be the forum whore that some of us are but often seems to help out at just the right time.

Could something like this work?</description>
		<content:encoded><![CDATA[<p>I like the &#8220;Web search certified engineer&#8221; thingy, where do I sign up?  :-()</p>
<p>Actually, here is an idea, although maybe not any more scalable than anything else but here goes anyway,,,</p>
<p>A webmaster&#8217;s site tanks, they come to the <strong style="color: rgb(0, 0, 255);">G</strong><strong style="color: rgb(255, 0, 0);">o</strong><strong style="color: rgb(255, 255, 77);">o</strong><strong style="color: rgb(0, 0, 255);">g</strong><strong style="color: rgb(0, 128, 0);">l</strong><strong style="color: rgb(255, 0, 0);">e</strong> Webmaster Help forum and pose the problem. If after everyone diligently working on the problem, no one finds anything obvious, which I think most of us would find things with spammers&#8217; or black-hat sites, the problem is escalated to someone who can peer into Google&#8217;s algo crystal ball and give ideas as to what areas are problematic.</p>
<p>An example of this that I think worked well, although maybe took longer than maybe it should have, is Sam I Am&#8217;s website.  We all wracked our brains looking for anything and everything and the real problem turned out to be something that almost no one had imagined.</p>
<p>A Googler then steps in and gives a general overview of the problems, Sam I Am and his brother then go off and do the work that is needed.  In the trade off we end up with a new and valuable member of the GWMH forum in Sam I Am who may not be the forum whore that some of us are but often seems to help out at just the right time.</p>
<p>Could something like this work?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stumped</title>
		<link>http://www.jlh-design.com/2008/01/scalable-solution/#comment-5536</link>
		<dc:creator>Stumped</dc:creator>
		<pubDate>Mon, 11 Feb 2008 00:51:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.jlh-design.com/2008/01/scalable-solution/#comment-5536</guid>
		<description>"We’ve certainly debated giving that sort of status back, but the problem is that hardcore spammers would probe to see just exact how much they could “get away with” and still get reincluded."

No disrespect Matt but that's a bit of a cop out, there's nothing stopping a black hat or spammer setting up a network of sites and adding a dash of cloaking, .edu spam etc and probing how much they could "get away with" before being shot down.

No difference, by not having some sort of re inclusion feedback it effects legitimate people trying to do the right thing more than anyone.

I just submitted a re inclusion request after my site vanished 2 weeks ago for an unknown reason. It went from xx,xxx visitors per day mainly from Google powered search to about 10 a day in a matter of 5 minutes.

The worst part is, i finished my last day of my offline job on the Friday to become a full time webmaster solely because my site just started breaking the $400 per day mark via Google Adsense. On the Sunday my traffic was killed off completely leaving me with no source of income what so ever.

Now i'm left sitting here praying my re inclusion message in a bottle i sent out gets to someone before i cannot afford to eat.

I don't sell/exchange text links and i couldn't give a hoot about PageRank and nobody can find anything wrong with my site and it's believed to be a glitch.

So i feel sick after reading the Adsense "Success Stories" and how it changes peoples lives... Well i can definitely say it changed my life just 48 Hours after becoming a full time publisher.

Anyhow back to the topic.. Please Matt something needs to be done about the re inclusion process, put yourself in my shoes. Something eventuating from this re inclusion request means the difference between loosing things like my house and internet connection or being able to live my life as it was before all this happened.

It's breaking me scouring the net all day long trying to work out "what else can i do".</description>
		<content:encoded><![CDATA[<p>&#8220;We’ve certainly debated giving that sort of status back, but the problem is that hardcore spammers would probe to see just exact how much they could “get away with” and still get reincluded.&#8221;</p>
<p>No disrespect Matt but that&#8217;s a bit of a cop out, there&#8217;s nothing stopping a black hat or spammer setting up a network of sites and adding a dash of cloaking, .edu spam etc and probing how much they could &#8220;get away with&#8221; before being shot down.</p>
<p>No difference, by not having some sort of re inclusion feedback it effects legitimate people trying to do the right thing more than anyone.</p>
<p>I just submitted a re inclusion request after my site vanished 2 weeks ago for an unknown reason. It went from xx,xxx visitors per day mainly from <strong style="color: rgb(0, 0, 255);">G</strong><strong style="color: rgb(255, 0, 0);">o</strong><strong style="color: rgb(255, 255, 77);">o</strong><strong style="color: rgb(0, 0, 255);">g</strong><strong style="color: rgb(0, 128, 0);">l</strong><strong style="color: rgb(255, 0, 0);">e</strong> powered search to about 10 a day in a matter of 5 minutes.</p>
<p>The worst part is, i finished my last day of my offline job on the Friday to become a full time webmaster solely because my site just started breaking the $400 per day mark via <strong style="color: rgb(0, 0, 255);">G</strong><strong style="color: rgb(255, 0, 0);">o</strong><strong style="color: rgb(255, 255, 77);">o</strong><strong style="color: rgb(0, 0, 255);">g</strong><strong style="color: rgb(0, 128, 0);">l</strong><strong style="color: rgb(255, 0, 0);">e</strong> Adsense. On the Sunday my traffic was killed off completely leaving me with no source of income what so ever.</p>
<p>Now i&#8217;m left sitting here praying my re inclusion message in a bottle i sent out gets to someone before i cannot afford to eat.</p>
<p>I don&#8217;t sell/exchange text links and i couldn&#8217;t give a hoot about PageRank and nobody can find anything wrong with my site and it&#8217;s believed to be a glitch.</p>
<p>So i feel sick after reading the Adsense &#8220;Success Stories&#8221; and how it changes peoples lives&#8230; Well i can definitely say it changed my life just 48 Hours after becoming a full time publisher.</p>
<p>Anyhow back to the topic.. Please Matt something needs to be done about the re inclusion process, put yourself in my shoes. Something eventuating from this re inclusion request means the difference between loosing things like my house and internet connection or being able to live my life as it was before all this happened.</p>
<p>It&#8217;s breaking me scouring the net all day long trying to work out &#8220;what else can i do&#8221;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Forrest</title>
		<link>http://www.jlh-design.com/2008/01/scalable-solution/#comment-5503</link>
		<dc:creator>Forrest</dc:creator>
		<pubDate>Wed, 30 Jan 2008 02:55:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.jlh-design.com/2008/01/scalable-solution/#comment-5503</guid>
		<description>I agree what you described isn't very scalable ... but I honestly don't see anything wrong with it.  I get the sense you don't, either?

Your proposed, more-scalable solution says when a reinclusion request is denied, Google should say "no," and refer the user to their guidelines ... but you aren't actually suggesting that the onus is on Google to research the site page by page to find each violation of their rules for inclusion.  It sounds like the main difference between that and what actually happened is that Google assumes anyone asking to be reincluded probably already knows about their guidelines...?

Also, Google is a private, for-profit company, and not a public utility.  Page rank ( especially the toolbar variety ) isn't something we're owed for having web sites.  Google would be within its legal rights to reset a site's PR to zero because one of their employees doesn't like its template;  their stance on paid links and such hasn't been a secret for the past several years.

It's unfortunate it took several weeks and a public spectacle for your friend to get her ad value back.  But does Google really owe a site that's broken their terms of service repeatedly more haste than they would have for any other web site?</description>
		<content:encoded><![CDATA[<p>I agree what you described isn&#8217;t very scalable &#8230; but I honestly don&#8217;t see anything wrong with it.  I get the sense you don&#8217;t, either?</p>
<p>Your proposed, more-scalable solution says when a reinclusion request is denied, <strong style="color: rgb(0, 0, 255);">G</strong><strong style="color: rgb(255, 0, 0);">o</strong><strong style="color: rgb(255, 255, 77);">o</strong><strong style="color: rgb(0, 0, 255);">g</strong><strong style="color: rgb(0, 128, 0);">l</strong><strong style="color: rgb(255, 0, 0);">e</strong> should say &#8220;no,&#8221; and refer the user to their guidelines &#8230; but you aren&#8217;t actually suggesting that the onus is on <strong style="color: rgb(0, 0, 255);">G</strong><strong style="color: rgb(255, 0, 0);">o</strong><strong style="color: rgb(255, 255, 77);">o</strong><strong style="color: rgb(0, 0, 255);">g</strong><strong style="color: rgb(0, 128, 0);">l</strong><strong style="color: rgb(255, 0, 0);">e</strong> to research the site page by page to find each violation of their rules for inclusion.  It sounds like the main difference between that and what actually happened is that <strong style="color: rgb(0, 0, 255);">G</strong><strong style="color: rgb(255, 0, 0);">o</strong><strong style="color: rgb(255, 255, 77);">o</strong><strong style="color: rgb(0, 0, 255);">g</strong><strong style="color: rgb(0, 128, 0);">l</strong><strong style="color: rgb(255, 0, 0);">e</strong> assumes anyone asking to be reincluded probably already knows about their guidelines&#8230;?</p>
<p>Also, <strong style="color: rgb(0, 0, 255);">G</strong><strong style="color: rgb(255, 0, 0);">o</strong><strong style="color: rgb(255, 255, 77);">o</strong><strong style="color: rgb(0, 0, 255);">g</strong><strong style="color: rgb(0, 128, 0);">l</strong><strong style="color: rgb(255, 0, 0);">e</strong> is a private, for-profit company, and not a public utility.  Page rank ( especially the toolbar variety ) isn&#8217;t something we&#8217;re owed for having web sites.  <strong style="color: rgb(0, 0, 255);">G</strong><strong style="color: rgb(255, 0, 0);">o</strong><strong style="color: rgb(255, 255, 77);">o</strong><strong style="color: rgb(0, 0, 255);">g</strong><strong style="color: rgb(0, 128, 0);">l</strong><strong style="color: rgb(255, 0, 0);">e</strong> would be within its legal rights to reset a site&#8217;s PR to zero because one of their employees doesn&#8217;t like its template;  their stance on paid links and such hasn&#8217;t been a secret for the past several years.</p>
<p>It&#8217;s unfortunate it took several weeks and a public spectacle for your friend to get her ad value back.  But does <strong style="color: rgb(0, 0, 255);">G</strong><strong style="color: rgb(255, 0, 0);">o</strong><strong style="color: rgb(255, 255, 77);">o</strong><strong style="color: rgb(0, 0, 255);">g</strong><strong style="color: rgb(0, 128, 0);">l</strong><strong style="color: rgb(255, 0, 0);">e</strong> really owe a site that&#8217;s broken their terms of service repeatedly more haste than they would have for any other web site?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joe Hunkins</title>
		<link>http://www.jlh-design.com/2008/01/scalable-solution/#comment-5499</link>
		<dc:creator>Joe Hunkins</dc:creator>
		<pubDate>Mon, 28 Jan 2008 23:53:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.jlh-design.com/2008/01/scalable-solution/#comment-5499</guid>
		<description>This is an *excellent* set of observation, and with all due respect to my pal Matt I've always been totally unmoved by Google's suggestion that making the reinclusion and webmaster information process more transparent would somehow jeopardize Google's ability to kill spammers.  

In fact from my observations over the years I think the lack of transparency, along with initally vague webmaster guidelines (now fixed), have caused many if not most of the spam problems as both spammers and regular web folks vie to push the limits of the rules while staying in Google's good graces.   The big problem now is the profound inconsistency in the way sites are indexed, and the fact that it's very difficult for webmasters to get much feedback from Google.    Google would be well advised to consider better automated or customer pays routines to examine websites for problems and allow reinclusion, because the frustration is building more than they realize in the webmaster and small business community.</description>
		<content:encoded><![CDATA[<p>This is an *excellent* set of observation, and with all due respect to my pal Matt I&#8217;ve always been totally unmoved by Google&#8217;s suggestion that making the reinclusion and webmaster information process more transparent would somehow jeopardize Google&#8217;s ability to kill spammers.  </p>
<p>In fact from my observations over the years I think the lack of transparency, along with initally vague webmaster guidelines (now fixed), have caused many if not most of the spam problems as both spammers and regular web folks vie to push the limits of the rules while staying in Google&#8217;s good graces.   The big problem now is the profound inconsistency in the way sites are indexed, and the fact that it&#8217;s very difficult for webmasters to get much feedback from Google.    <strong style="color: rgb(0, 0, 255);">G</strong><strong style="color: rgb(255, 0, 0);">o</strong><strong style="color: rgb(255, 255, 77);">o</strong><strong style="color: rgb(0, 0, 255);">g</strong><strong style="color: rgb(0, 128, 0);">l</strong><strong style="color: rgb(255, 0, 0);">e</strong> would be well advised to consider better automated or customer pays routines to examine websites for problems and allow reinclusion, because the frustration is building more than they realize in the webmaster and small business community.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: dockarl</title>
		<link>http://www.jlh-design.com/2008/01/scalable-solution/#comment-5497</link>
		<dc:creator>dockarl</dc:creator>
		<pubDate>Sun, 27 Jan 2008 04:16:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.jlh-design.com/2008/01/scalable-solution/#comment-5497</guid>
		<description>I think that if Google really decided to put the axe to the grindstone they could find a solution to this problem - I've personally thought about possible solutions to the prob from just about every angle and (with brain cells sufficiently knotted) I still can't find one that doesn't potentially open the algorithm to the kind of abuse Matt refers to above.

I do, however, think that obvious and well known issues such as simple HTML hidden text could be notified without threatening the integrity of the spam detection algorithm, but I guess even that would then possibly give the blackhats info about the approx time it takes an infraction to be detected.. sigh..

This is a particularly tricky problem for Google.</description>
		<content:encoded><![CDATA[<p>I think that if <strong style="color: rgb(0, 0, 255);">G</strong><strong style="color: rgb(255, 0, 0);">o</strong><strong style="color: rgb(255, 255, 77);">o</strong><strong style="color: rgb(0, 0, 255);">g</strong><strong style="color: rgb(0, 128, 0);">l</strong><strong style="color: rgb(255, 0, 0);">e</strong> really decided to put the axe to the grindstone they could find a solution to this problem - I&#8217;ve personally thought about possible solutions to the prob from just about every angle and (with brain cells sufficiently knotted) I still can&#8217;t find one that doesn&#8217;t potentially open the algorithm to the kind of abuse Matt refers to above.</p>
<p>I do, however, think that obvious and well known issues such as simple HTML hidden text could be notified without threatening the integrity of the spam detection algorithm, but I guess even that would then possibly give the blackhats info about the approx time it takes an infraction to be detected.. sigh..</p>
<p>This is a particularly tricky problem for Google.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dave L</title>
		<link>http://www.jlh-design.com/2008/01/scalable-solution/#comment-5494</link>
		<dc:creator>Dave L</dc:creator>
		<pubDate>Sat, 26 Jan 2008 20:18:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.jlh-design.com/2008/01/scalable-solution/#comment-5494</guid>
		<description>First, Google needs to indicate the area causing the site to be penalized if a site owner requests it. They don't have to share specifics, but they should give an overview, ESPECIALLY when Google has changed its policy and something that was okay yesterday is not ok today. There should be a generic report of some kind available through webmaster tools.

Second, no one with a clear-cut issue should be left guessing. Did they simply overlook something? Google should make that information available. If it's a case of borderline violations, or borderline detection methods, Google can be more obscure so that spammers don't abuse the feedback.

Third, there are Google AdWords certified professionals, why not Google SERPs reinclusion certified professionals? Google can provide them more advanced tools or have the relevant Google employees interact with them. Part of ongoing certification could be to help an assigned case a few times per year pro bono.

And when Google changes their policy, they need to provide a single, clear document on the policy, and tools and to allow compliance, all in ADVANCE. No one should be left interpreting and interpretation of something Matt Cutts said on video in order to determine details of Google's policies.

And last, on Google should not provide methods or tools that CAUSE sites to be penalized. Explanation:

My least read blog (on blogspot) recently lost all Google traffic when I changed the blogspot template. Almost certainly a duplicate content penalty, as I didn't have any posts sorted by topic before, and now do (and not using any suspicious page elements, etc.) Google traffic dropped to zero within a couple hours of changing the template, and has remained at zero for weeks since. So Google killed my Google results. Pages are still "indexed," so reinclusion is not an issue, but sending 0-0-0 for traffic.</description>
		<content:encoded><![CDATA[<p>First, <strong style="color: rgb(0, 0, 255);">G</strong><strong style="color: rgb(255, 0, 0);">o</strong><strong style="color: rgb(255, 255, 77);">o</strong><strong style="color: rgb(0, 0, 255);">g</strong><strong style="color: rgb(0, 128, 0);">l</strong><strong style="color: rgb(255, 0, 0);">e</strong> needs to indicate the area causing the site to be penalized if a site owner requests it. They don&#8217;t have to share specifics, but they should give an overview, ESPECIALLY when <strong style="color: rgb(0, 0, 255);">G</strong><strong style="color: rgb(255, 0, 0);">o</strong><strong style="color: rgb(255, 255, 77);">o</strong><strong style="color: rgb(0, 0, 255);">g</strong><strong style="color: rgb(0, 128, 0);">l</strong><strong style="color: rgb(255, 0, 0);">e</strong> has changed its policy and something that was okay yesterday is not ok today. There should be a generic report of some kind available through webmaster tools.</p>
<p>Second, no one with a clear-cut issue should be left guessing. Did they simply overlook something? <strong style="color: rgb(0, 0, 255);">G</strong><strong style="color: rgb(255, 0, 0);">o</strong><strong style="color: rgb(255, 255, 77);">o</strong><strong style="color: rgb(0, 0, 255);">g</strong><strong style="color: rgb(0, 128, 0);">l</strong><strong style="color: rgb(255, 0, 0);">e</strong> should make that information available. If it&#8217;s a case of borderline violations, or borderline detection methods, <strong style="color: rgb(0, 0, 255);">G</strong><strong style="color: rgb(255, 0, 0);">o</strong><strong style="color: rgb(255, 255, 77);">o</strong><strong style="color: rgb(0, 0, 255);">g</strong><strong style="color: rgb(0, 128, 0);">l</strong><strong style="color: rgb(255, 0, 0);">e</strong> can be more obscure so that spammers don&#8217;t abuse the feedback.</p>
<p>Third, there are <strong style="color: rgb(0, 0, 255);">G</strong><strong style="color: rgb(255, 0, 0);">o</strong><strong style="color: rgb(255, 255, 77);">o</strong><strong style="color: rgb(0, 0, 255);">g</strong><strong style="color: rgb(0, 128, 0);">l</strong><strong style="color: rgb(255, 0, 0);">e</strong> AdWords certified professionals, why not <strong style="color: rgb(0, 0, 255);">G</strong><strong style="color: rgb(255, 0, 0);">o</strong><strong style="color: rgb(255, 255, 77);">o</strong><strong style="color: rgb(0, 0, 255);">g</strong><strong style="color: rgb(0, 128, 0);">l</strong><strong style="color: rgb(255, 0, 0);">e</strong> SERPs reinclusion certified professionals? <strong style="color: rgb(0, 0, 255);">G</strong><strong style="color: rgb(255, 0, 0);">o</strong><strong style="color: rgb(255, 255, 77);">o</strong><strong style="color: rgb(0, 0, 255);">g</strong><strong style="color: rgb(0, 128, 0);">l</strong><strong style="color: rgb(255, 0, 0);">e</strong> can provide them more advanced tools or have the relevant <strong style="color: rgb(0, 0, 255);">G</strong><strong style="color: rgb(255, 0, 0);">o</strong><strong style="color: rgb(255, 255, 77);">o</strong><strong style="color: rgb(0, 0, 255);">g</strong><strong style="color: rgb(0, 128, 0);">l</strong><strong style="color: rgb(255, 0, 0);">e</strong> employees interact with them. Part of ongoing certification could be to help an assigned case a few times per year pro bono.</p>
<p>And when <strong style="color: rgb(0, 0, 255);">G</strong><strong style="color: rgb(255, 0, 0);">o</strong><strong style="color: rgb(255, 255, 77);">o</strong><strong style="color: rgb(0, 0, 255);">g</strong><strong style="color: rgb(0, 128, 0);">l</strong><strong style="color: rgb(255, 0, 0);">e</strong> changes their policy, they need to provide a single, clear document on the policy, and tools and to allow compliance, all in ADVANCE. No one should be left interpreting and interpretation of something Matt Cutts said on video in order to determine details of Google&#8217;s policies.</p>
<p>And last, on <strong style="color: rgb(0, 0, 255);">G</strong><strong style="color: rgb(255, 0, 0);">o</strong><strong style="color: rgb(255, 255, 77);">o</strong><strong style="color: rgb(0, 0, 255);">g</strong><strong style="color: rgb(0, 128, 0);">l</strong><strong style="color: rgb(255, 0, 0);">e</strong> should not provide methods or tools that CAUSE sites to be penalized. Explanation:</p>
<p>My least read blog (on blogspot) recently lost all <strong style="color: rgb(0, 0, 255);">G</strong><strong style="color: rgb(255, 0, 0);">o</strong><strong style="color: rgb(255, 255, 77);">o</strong><strong style="color: rgb(0, 0, 255);">g</strong><strong style="color: rgb(0, 128, 0);">l</strong><strong style="color: rgb(255, 0, 0);">e</strong> traffic when I changed the blogspot template. Almost certainly a duplicate content penalty, as I didn&#8217;t have any posts sorted by topic before, and now do (and not using any suspicious page elements, etc.) <strong style="color: rgb(0, 0, 255);">G</strong><strong style="color: rgb(255, 0, 0);">o</strong><strong style="color: rgb(255, 255, 77);">o</strong><strong style="color: rgb(0, 0, 255);">g</strong><strong style="color: rgb(0, 128, 0);">l</strong><strong style="color: rgb(255, 0, 0);">e</strong> traffic dropped to zero within a couple hours of changing the template, and has remained at zero for weeks since. So <strong style="color: rgb(0, 0, 255);">G</strong><strong style="color: rgb(255, 0, 0);">o</strong><strong style="color: rgb(255, 255, 77);">o</strong><strong style="color: rgb(0, 0, 255);">g</strong><strong style="color: rgb(0, 128, 0);">l</strong><strong style="color: rgb(255, 0, 0);">e</strong> killed my <strong style="color: rgb(0, 0, 255);">G</strong><strong style="color: rgb(255, 0, 0);">o</strong><strong style="color: rgb(255, 255, 77);">o</strong><strong style="color: rgb(0, 0, 255);">g</strong><strong style="color: rgb(0, 128, 0);">l</strong><strong style="color: rgb(255, 0, 0);">e</strong> results. Pages are still &#8220;indexed,&#8221; so reinclusion is not an issue, but sending 0-0-0 for traffic.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Doug Heil</title>
		<link>http://www.jlh-design.com/2008/01/scalable-solution/#comment-5491</link>
		<dc:creator>Doug Heil</dc:creator>
		<pubDate>Fri, 25 Jan 2008 23:13:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.jlh-design.com/2008/01/scalable-solution/#comment-5491</guid>
		<description>Hi John, I thought you said that Google would reply back saying all was fine or all was still not fine? It's also Matt Cutts doing a post by post and telling the owner what the issues still were, etc.

I just don't see how things would scale at all in any type of situation. I'm also not understanding the idea of giving a blackhat all the tools they need in order to get re-included...(NOT talking about this particular case at all), but talking about this issue in general of Google giving correspondence like this to everyone.</description>
		<content:encoded><![CDATA[<p>Hi John, I thought you said that <strong style="color: rgb(0, 0, 255);">G</strong><strong style="color: rgb(255, 0, 0);">o</strong><strong style="color: rgb(255, 255, 77);">o</strong><strong style="color: rgb(0, 0, 255);">g</strong><strong style="color: rgb(0, 128, 0);">l</strong><strong style="color: rgb(255, 0, 0);">e</strong> would reply back saying all was fine or all was still not fine? It&#8217;s also Matt Cutts doing a post by post and telling the owner what the issues still were, etc.</p>
<p>I just don&#8217;t see how things would scale at all in any type of situation. I&#8217;m also not understanding the idea of giving a blackhat all the tools they need in order to get re-included&#8230;(NOT talking about this particular case at all), but talking about this issue in general of <strong style="color: rgb(0, 0, 255);">G</strong><strong style="color: rgb(255, 0, 0);">o</strong><strong style="color: rgb(255, 255, 77);">o</strong><strong style="color: rgb(0, 0, 255);">g</strong><strong style="color: rgb(0, 128, 0);">l</strong><strong style="color: rgb(255, 0, 0);">e</strong> giving correspondence like this to everyone.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Honeck "JLH"</title>
		<link>http://www.jlh-design.com/2008/01/scalable-solution/#comment-5490</link>
		<dc:creator>John Honeck "JLH"</dc:creator>
		<pubDate>Fri, 25 Jan 2008 22:39:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.jlh-design.com/2008/01/scalable-solution/#comment-5490</guid>
		<description>Doug, where did I say that Google was to email the owner back and forth?</description>
		<content:encoded><![CDATA[<p>Doug, where did I say that <strong style="color: rgb(0, 0, 255);">G</strong><strong style="color: rgb(255, 0, 0);">o</strong><strong style="color: rgb(255, 255, 77);">o</strong><strong style="color: rgb(0, 0, 255);">g</strong><strong style="color: rgb(0, 128, 0);">l</strong><strong style="color: rgb(255, 0, 0);">e</strong> was to email the owner back and forth?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Doug Heil</title>
		<link>http://www.jlh-design.com/2008/01/scalable-solution/#comment-5489</link>
		<dc:creator>Doug Heil</dc:creator>
		<pubDate>Fri, 25 Jan 2008 22:32:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.jlh-design.com/2008/01/scalable-solution/#comment-5489</guid>
		<description>My, oh my. I don't know what to say. When has any search engine in history had back and forths with people who filed a re-inclusion request of any kind, even though they had not fixed all violations totally?

Hasn't it always been the case that if a site owner knows they did something against the guidelines, that the site owner is responsible for a "total" cleanup?

I just don't know what to say. How does our SEO industry expect Google or any employee to email back and forth with any type of owner who did not follow the guidelines?

I'm at a loss with this. I really am. It shouldn't matter who did what and when; if you violate guidelines you should fix things first.

Second, third, and even fourth and fifth chances?

My, oh my.</description>
		<content:encoded><![CDATA[<p>My, oh my. I don&#8217;t know what to say. When has any search engine in history had back and forths with people who filed a re-inclusion request of any kind, even though they had not fixed all violations totally?</p>
<p>Hasn&#8217;t it always been the case that if a site owner knows they did something against the guidelines, that the site owner is responsible for a &#8220;total&#8221; cleanup?</p>
<p>I just don&#8217;t know what to say. How does our SEO industry expect <strong style="color: rgb(0, 0, 255);">G</strong><strong style="color: rgb(255, 0, 0);">o</strong><strong style="color: rgb(255, 255, 77);">o</strong><strong style="color: rgb(0, 0, 255);">g</strong><strong style="color: rgb(0, 128, 0);">l</strong><strong style="color: rgb(255, 0, 0);">e</strong> or any employee to email back and forth with any type of owner who did not follow the guidelines?</p>
<p>I&#8217;m at a loss with this. I really am. It shouldn&#8217;t matter who did what and when; if you violate guidelines you should fix things first.</p>
<p>Second, third, and even fourth and fifth chances?</p>
<p>My, oh my.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: DazzlinDonna</title>
		<link>http://www.jlh-design.com/2008/01/scalable-solution/#comment-5488</link>
		<dc:creator>DazzlinDonna</dc:creator>
		<pubDate>Fri, 25 Jan 2008 16:45:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.jlh-design.com/2008/01/scalable-solution/#comment-5488</guid>
		<description>John, I agree with you 100%.  Heck, I agree with you 500%.  And I hope that my post eventually leads to that sort of solution.</description>
		<content:encoded><![CDATA[<p>John, I agree with you 100%.  Heck, I agree with you 500%.  And I hope that my post eventually leads to that sort of solution.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Honeck "JLH"</title>
		<link>http://www.jlh-design.com/2008/01/scalable-solution/#comment-5487</link>
		<dc:creator>John Honeck "JLH"</dc:creator>
		<pubDate>Fri, 25 Jan 2008 16:40:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.jlh-design.com/2008/01/scalable-solution/#comment-5487</guid>
		<description>Once again I agree with you.

Feedback has to be given in such a way that it can't be used in an iterative process to decipher where the lines are.  Obviously there is some human element to it as well as I've seen people who've gotten very specific messages telling them where hidden text was located, which surprised me. 

I don't have the exact answer but I just feel like there is more that could be done.  I'm trying to step away from the forums, blogs, and SEM social sites and look at the issue through the eyes of a site owner of a single site owner, and for them the current process is akin to sending a message in a bottle, you don't know if it got anywhere.

On the other side of it I know the troubles of trying to deal with spammers.  In my own personal experience I've learned that you cannot judge a site solely on the information given on the site.  Often people post with problems for a given site that on the surface seem quite benign, but before helping them out I'll check the history.  With my limited tools I'll often find that the site owner has A LOT of experience pushing the envelope on other properties, at that point I have to make a judgement call of my own.  Do I help them get this one particular site back in or do I resist so as to not further their shadier tendencies?  False link profiles, dozens of thin affiliate sites, scraper aggregators, etc. are just some of the rather obvious stuff I can find, and I don't have the wonderful data mining tools that Google has.

I was hesitant to post this at first as I don't want to give the impression that I don't want to have Matt out there helping people, as I do, but it's an issue that I feel strong about.  For me helping the silent majority who isn't quite as vocal and doesn't have a voice in the blogosphere or the search engine circles because frankly, they don't know they exist, is a cause worth forwarding.  

In the end, hopefully Matt continues his public efforts, but also I hope I at least registered a vote for the cause to find a way to help the non-hardcore spammers and those without many connections.  Great strides have been made in that direction but I don't think we are quite there yet.

Thanks Matt for adding to my discussion.</description>
		<content:encoded><![CDATA[<p>Once again I agree with you.</p>
<p>Feedback has to be given in such a way that it can&#8217;t be used in an iterative process to decipher where the lines are.  Obviously there is some human element to it as well as I&#8217;ve seen people who&#8217;ve gotten very specific messages telling them where hidden text was located, which surprised me. </p>
<p>I don&#8217;t have the exact answer but I just feel like there is more that could be done.  I&#8217;m trying to step away from the forums, blogs, and SEM social sites and look at the issue through the eyes of a site owner of a single site owner, and for them the current process is akin to sending a message in a bottle, you don&#8217;t know if it got anywhere.</p>
<p>On the other side of it I know the troubles of trying to deal with spammers.  In my own personal experience I&#8217;ve learned that you cannot judge a site solely on the information given on the site.  Often people post with problems for a given site that on the surface seem quite benign, but before helping them out I&#8217;ll check the history.  With my limited tools I&#8217;ll often find that the site owner has A LOT of experience pushing the envelope on other properties, at that point I have to make a judgement call of my own.  Do I help them get this one particular site back in or do I resist so as to not further their shadier tendencies?  False link profiles, dozens of thin affiliate sites, scraper aggregators, etc. are just some of the rather obvious stuff I can find, and I don&#8217;t have the wonderful data mining tools that <strong style="color: rgb(0, 0, 255);">G</strong><strong style="color: rgb(255, 0, 0);">o</strong><strong style="color: rgb(255, 255, 77);">o</strong><strong style="color: rgb(0, 0, 255);">g</strong><strong style="color: rgb(0, 128, 0);">l</strong><strong style="color: rgb(255, 0, 0);">e</strong> has.</p>
<p>I was hesitant to post this at first as I don&#8217;t want to give the impression that I don&#8217;t want to have Matt out there helping people, as I do, but it&#8217;s an issue that I feel strong about.  For me helping the silent majority who isn&#8217;t quite as vocal and doesn&#8217;t have a voice in the blogosphere or the search engine circles because frankly, they don&#8217;t know they exist, is a cause worth forwarding.  </p>
<p>In the end, hopefully Matt continues his public efforts, but also I hope I at least registered a vote for the cause to find a way to help the non-hardcore spammers and those without many connections.  Great strides have been made in that direction but I don&#8217;t think we are quite there yet.</p>
<p>Thanks Matt for adding to my discussion.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matt Cutts</title>
		<link>http://www.jlh-design.com/2008/01/scalable-solution/#comment-5486</link>
		<dc:creator>Matt Cutts</dc:creator>
		<pubDate>Fri, 25 Jan 2008 16:14:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.jlh-design.com/2008/01/scalable-solution/#comment-5486</guid>
		<description>We've certainly debated giving that sort of status back, but the problem is that hardcore spammers would probe to see just exact how much they could "get away with" and still get reincluded.

But I should have added in my comments on Donna's situation something like "The webmaster help group is more scalable to identify problems that I am."</description>
		<content:encoded><![CDATA[<p>We&#8217;ve certainly debated giving that sort of status back, but the problem is that hardcore spammers would probe to see just exact how much they could &#8220;get away with&#8221; and still get reincluded.</p>
<p>But I should have added in my comments on Donna&#8217;s situation something like &#8220;The webmaster help group is more scalable to identify problems that I am.&#8221;</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.379 seconds -->
