<?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: Holy Grail: SEO Model for Flash and Flex Content</title>
	<atom:link href="http://www.metah.ch/blog/2008/04/holy-grail-seo-model-for-flash-and-flex-content/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.metah.ch/blog/2008/04/holy-grail-seo-model-for-flash-and-flex-content/</link>
	<description>Ahmet Gyger&#039;s web log.</description>
	<lastBuildDate>Fri, 11 Nov 2011 23:05:59 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: flex bi dashboards</title>
		<link>http://www.metah.ch/blog/2008/04/holy-grail-seo-model-for-flash-and-flex-content/comment-page-1/#comment-12400</link>
		<dc:creator>flex bi dashboards</dc:creator>
		<pubDate>Thu, 12 May 2011 09:22:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.metah.ch/blog/2008/04/02/holy-grail-seo-model-for-flash-and-flex-content/#comment-12400</guid>
		<description>It is entirely new information and seems i can use it to make my flex files index in searches. going to give a try.</description>
		<content:encoded><![CDATA[<p>It is entirely new information and seems i can use it to make my flex files index in searches. going to give a try.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aplicaciones web multiplataforma con XSL y XML: un reto SEO &#124; Programador PHP .ORG</title>
		<link>http://www.metah.ch/blog/2008/04/holy-grail-seo-model-for-flash-and-flex-content/comment-page-1/#comment-12376</link>
		<dc:creator>Aplicaciones web multiplataforma con XSL y XML: un reto SEO &#124; Programador PHP .ORG</dc:creator>
		<pubDate>Thu, 24 Mar 2011 22:07:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.metah.ch/blog/2008/04/02/holy-grail-seo-model-for-flash-and-flex-content/#comment-12376</guid>
		<description>[...] muy fácil de leer, esto es bueno para la web semántica (web 3.0!), bueno para el posicionamiento (SEO),claro, de hecho Google anunció que una página en XML y XSLT iría a la cabeza antes que otra en [...]</description>
		<content:encoded><![CDATA[<p>[...] muy fácil de leer, esto es bueno para la web semántica (web 3.0!), bueno para el posicionamiento (SEO),claro, de hecho Google anunció que una página en XML y XSLT iría a la cabeza antes que otra en [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Randolph Carter</title>
		<link>http://www.metah.ch/blog/2008/04/holy-grail-seo-model-for-flash-and-flex-content/comment-page-1/#comment-12372</link>
		<dc:creator>Randolph Carter</dc:creator>
		<pubDate>Fri, 25 Feb 2011 21:31:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.metah.ch/blog/2008/04/02/holy-grail-seo-model-for-flash-and-flex-content/#comment-12372</guid>
		<description>Interesting post, thanks for sharing great information.</description>
		<content:encoded><![CDATA[<p>Interesting post, thanks for sharing great information.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ahmet</title>
		<link>http://www.metah.ch/blog/2008/04/holy-grail-seo-model-for-flash-and-flex-content/comment-page-1/#comment-11870</link>
		<dc:creator>Ahmet</dc:creator>
		<pubDate>Mon, 11 May 2009 19:35:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.metah.ch/blog/2008/04/02/holy-grail-seo-model-for-flash-and-flex-content/#comment-11870</guid>
		<description>Hi Tony,

I had a short mail exchange with Matt, he confirmed me that the methods in itself does NOT breach any of Google guides lines.

I asked him:
&quot;I understand that you cannot reveal the algorithms of anti spam but still I&#039;m very interested to understand how any search engines (that cannot understand dynamic driven content) can know if &#039;stuffed keywords&#039; are used or not.&quot;

He answered:


&lt;blockquote&gt;If we load a page and it&#039;s got a ton of rare, misspelled, or unusual variants on a single word or phrase, that can be a pretty good signal. The only point I wanted to make is that there are ways to show Flash on a page that has text content that search engines can index. Google&#039;s main litmus test for cloaking is whether the page that the user saw is the same that Googlebot saw. The easiest test is whether the md5 sum of the two pages are the same. Even if the hashes are identical though, it&#039;s possible that someone is hiding keyword-stuffed text behind an image or Flash. That&#039;s where the keyword stuffing detection comes in. In addition to high keyword density, you could imagine looking at the words in sequence and seeing that those sequences are quite unusual compared to &quot;normal&quot; text that we see around the rest of the web.&lt;/blockquote&gt;

Now obviously doing an MD5 on vectorized texts can be resources consuming. So I assume that if the exposed texts you have does not seems to be too SEO oriented (typically high keyword density) then you should be safe. 

P.S: That was a year ago, do things may have a changed and I must admit that I haven&#039;t been watching at this particular issue too much. 

Cheers,
Ahmet
</description>
		<content:encoded><![CDATA[<p>Hi Tony,</p>
<p>I had a short mail exchange with Matt, he confirmed me that the methods in itself does NOT breach any of Google guides lines.</p>
<p>I asked him:<br />
&#8220;I understand that you cannot reveal the algorithms of anti spam but still I&#8217;m very interested to understand how any search engines (that cannot understand dynamic driven content) can know if &#8216;stuffed keywords&#8217; are used or not.&#8221;</p>
<p>He answered:</p>
<blockquote><p>If we load a page and it&#8217;s got a ton of rare, misspelled, or unusual variants on a single word or phrase, that can be a pretty good signal. The only point I wanted to make is that there are ways to show Flash on a page that has text content that search engines can index. Google&#8217;s main litmus test for cloaking is whether the page that the user saw is the same that Googlebot saw. The easiest test is whether the md5 sum of the two pages are the same. Even if the hashes are identical though, it&#8217;s possible that someone is hiding keyword-stuffed text behind an image or Flash. That&#8217;s where the keyword stuffing detection comes in. In addition to high keyword density, you could imagine looking at the words in sequence and seeing that those sequences are quite unusual compared to &#8220;normal&#8221; text that we see around the rest of the web.</p></blockquote>
<p>Now obviously doing an MD5 on vectorized texts can be resources consuming. So I assume that if the exposed texts you have does not seems to be too SEO oriented (typically high keyword density) then you should be safe. </p>
<p>P.S: That was a year ago, do things may have a changed and I must admit that I haven&#8217;t been watching at this particular issue too much. </p>
<p>Cheers,<br />
Ahmet</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tony</title>
		<link>http://www.metah.ch/blog/2008/04/holy-grail-seo-model-for-flash-and-flex-content/comment-page-1/#comment-11867</link>
		<dc:creator>Tony</dc:creator>
		<pubDate>Fri, 08 May 2009 20:25:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.metah.ch/blog/2008/04/02/holy-grail-seo-model-for-flash-and-flex-content/#comment-11867</guid>
		<description>Interesting.

I note the &quot;Matt Cutts&quot; comment and a quick look at Google&#039;s webmaster guidelines (not complete here - check the full version at Google) seems to suggest that the method indicated is already ba breach of Google&#039;s own guidelines.

Quality guidelines - basic principles

    * Make pages primarily for users, not for search engines. Don&#039;t deceive your users or present different content to search engines than you display to users, which is commonly referred to as &quot;cloaking.&quot;

    * Avoid tricks intended to improve search engine rankings. A good rule of thumb is whether you&#039;d feel comfortable explaining what you&#039;ve done to a website that competes with you. Another useful test is to ask, &quot;Does this help my users? Would I do this if search engines didn&#039;t exist?&quot;

   

Quality guidelines - specific guidelines

    * Avoid hidden text or hidden links.

    * Don&#039;t use cloaking or sneaky redirects.

    * Don&#039;t load pages with irrelevant keywords.

    * Don&#039;t create multiple pages, subdomains, or domains with substantially duplicate content.</description>
		<content:encoded><![CDATA[<p>Interesting.</p>
<p>I note the &#8220;Matt Cutts&#8221; comment and a quick look at Google&#8217;s webmaster guidelines (not complete here &#8211; check the full version at Google) seems to suggest that the method indicated is already ba breach of Google&#8217;s own guidelines.</p>
<p>Quality guidelines &#8211; basic principles</p>
<p>    * Make pages primarily for users, not for search engines. Don&#8217;t deceive your users or present different content to search engines than you display to users, which is commonly referred to as &#8220;cloaking.&#8221;</p>
<p>    * Avoid tricks intended to improve search engine rankings. A good rule of thumb is whether you&#8217;d feel comfortable explaining what you&#8217;ve done to a website that competes with you. Another useful test is to ask, &#8220;Does this help my users? Would I do this if search engines didn&#8217;t exist?&#8221;</p>
<p>Quality guidelines &#8211; specific guidelines</p>
<p>    * Avoid hidden text or hidden links.</p>
<p>    * Don&#8217;t use cloaking or sneaky redirects.</p>
<p>    * Don&#8217;t load pages with irrelevant keywords.</p>
<p>    * Don&#8217;t create multiple pages, subdomains, or domains with substantially duplicate content.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: SEO Consultant joel</title>
		<link>http://www.metah.ch/blog/2008/04/holy-grail-seo-model-for-flash-and-flex-content/comment-page-1/#comment-11701</link>
		<dc:creator>SEO Consultant joel</dc:creator>
		<pubDate>Wed, 15 Oct 2008 22:49:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.metah.ch/blog/2008/04/02/holy-grail-seo-model-for-flash-and-flex-content/#comment-11701</guid>
		<description>Interesting post, plus you got a pretty popular post from Matt.  Keep on delivering fresh content for us, thanks!</description>
		<content:encoded><![CDATA[<p>Interesting post, plus you got a pretty popular post from Matt.  Keep on delivering fresh content for us, thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ahmet</title>
		<link>http://www.metah.ch/blog/2008/04/holy-grail-seo-model-for-flash-and-flex-content/comment-page-1/#comment-11361</link>
		<dc:creator>Ahmet</dc:creator>
		<pubDate>Tue, 24 Jun 2008 19:02:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.metah.ch/blog/2008/04/02/holy-grail-seo-model-for-flash-and-flex-content/#comment-11361</guid>
		<description>Hi Richard, 

I would be very interested to see the sites using XSL (and not indexed). We need to understand that in the case of flexdirectory.com the good ranking come from the popularity of Ted Patrick&#039;s blog.
Being well indexed and being well ranked is another story :) 

By the way, schematic.com doesn&#039;t use the XSL... 

About the pudding it is in the fact that you can have the same information layer with two formating (users vs search engine) :D </description>
		<content:encoded><![CDATA[<p>Hi Richard, </p>
<p>I would be very interested to see the sites using XSL (and not indexed). We need to understand that in the case of flexdirectory.com the good ranking come from the popularity of Ted Patrick&#8217;s blog.<br />
Being well indexed and being well ranked is another story :) </p>
<p>By the way, schematic.com doesn&#8217;t use the XSL&#8230; </p>
<p>About the pudding it is in the fact that you can have the same information layer with two formating (users vs search engine) :D</p>
]]></content:encoded>
	</item>
</channel>
</rss>

