<?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: Flash can now be indexed by search engines and other code</title>
	<atom:link href="http://scriptingenabled.org/2008/07/flash-and-search-engine/feed/" rel="self" type="application/rss+xml" />
	<link>http://scriptingenabled.org/2008/07/flash-and-search-engine/</link>
	<description>Hacking the web to be more accessible</description>
	<pubDate>Tue, 06 Jan 2009 11:15:10 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Nicolas GALLET</title>
		<link>http://scriptingenabled.org/2008/07/flash-and-search-engine/#comment-27</link>
		<dc:creator>Nicolas GALLET</dc:creator>
		<pubDate>Wed, 09 Jul 2008 08:20:02 +0000</pubDate>
		<guid isPermaLink="false">http://scriptingenabled.org/?p=9#comment-27</guid>
		<description>@Al : they get nothing if you give nothing.
Flash is optional. Different user experiences should be deployed to serve all users: those who can see Flash and those who don't (example : rolex.com or nurun.com). In that case, we cannot consider text rendering as an alternative. It is rather the opposite: Flash is an alternative to text.

I'm an SEO, and really think that this "new" implementation is a bad thing: Flash contents aren't structured as well as in HTML. Because it seems to be full text analysis, how can Flash contents be correctly interpreted/ranked by search engines ?</description>
		<content:encoded><![CDATA[<p>@Al : they get nothing if you give nothing.<br />
Flash is optional. Different user experiences should be deployed to serve all users: those who can see Flash and those who don&#8217;t (example : rolex.com or nurun.com). In that case, we cannot consider text rendering as an alternative. It is rather the opposite: Flash is an alternative to text.</p>
<p>I&#8217;m an <span class="caps">SEO, </span>and really think that this &#8220;new&#8221; implementation is a bad thing: Flash contents aren&#8217;t structured as well as in <span class="caps">HTML.</span> Because it seems to be full text analysis, how can Flash contents be correctly interpreted/ranked by search engines ?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Al</title>
		<link>http://scriptingenabled.org/2008/07/flash-and-search-engine/#comment-22</link>
		<dc:creator>Al</dc:creator>
		<pubDate>Fri, 04 Jul 2008 12:53:52 +0000</pubDate>
		<guid isPermaLink="false">http://scriptingenabled.org/?p=9#comment-22</guid>
		<description>Forgot to say that the only (possibly major for this site!) problem with my method is that non-JS and non-Flash people get nothing. That's why replacing the doc.write with real alternative text would be a good idea, but as I said google would then index both it and the flash.</description>
		<content:encoded><![CDATA[<p>Forgot to say that the only (possibly major for this site!) problem with my method is that non-JS and non-Flash people get nothing. That&#8217;s why replacing the doc.write with real alternative text would be a good idea, but as I said google would then index both it and the flash.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Al</title>
		<link>http://scriptingenabled.org/2008/07/flash-and-search-engine/#comment-21</link>
		<dc:creator>Al</dc:creator>
		<pubDate>Fri, 04 Jul 2008 12:51:53 +0000</pubDate>
		<guid isPermaLink="false">http://scriptingenabled.org/?p=9#comment-21</guid>
		<description>Nope, it didn't - I'll replace angles by squares. Here's the code:

[div id="flashElement"]
  [script type="text/javascript"]
    document.write("This is our 'you need a better version of flash' spiel");
  [/script]
  [noscript]
    [object]
      [param...]
      [embed src="flash.swf" /]
    [/object]
  [/noscript]
[/div]
[script type="text/javascript"]
  swfobject("flash.swf", "flashElement");
[&#60;/script]</description>
		<content:encoded><![CDATA[<p>Nope, it didn&#8217;t - I&#8217;ll replace angles by squares. Here&#8217;s the code:</p>
<p>[div id="flashElement"]<br />
  [script type="text/javascript"]<br />
    document.write(&#8221;This is our &#8216;you need a better version of flash&#8217; spiel&#8221;);<br />
  [/script]<br />
  [noscript]<br />
    [object]<br />
      [param...]<br />
      [embed src="flash.swf" /]<br />
    [/object]<br />
  [/noscript]<br />
[/div]<br />
[script type="text/javascript"]<br />
  swfobject(&#8221;flash.swf&#8221;, &#8220;flashElement&#8221;);<br />
[&lt;/script]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Al</title>
		<link>http://scriptingenabled.org/2008/07/flash-and-search-engine/#comment-20</link>
		<dc:creator>Al</dc:creator>
		<pubDate>Fri, 04 Jul 2008 12:50:44 +0000</pubDate>
		<guid isPermaLink="false">http://scriptingenabled.org/?p=9#comment-20</guid>
		<description>It may still be possible to have google index the flash and use swfobject. Consider the following code:


  
    document.write("This is our 'you need a better version of flash' spiel");
  
  
    
      
      
    
  


swfobject("flash.swf", "flashElement");


Obviously that is grossly simplified, and the JS for "get better flash" is a bit lame. You could simply write it in the div as you may currently do, but then google will get the warning AND the flash. Everyone else will just get the warning OR the swfobject-supplied flash. Putting it in a js document.write() means that google gets its  business from , non-js people get the same, and js people get either a warning about flash being old or the flash provided by swfobject.

No idea if that would work, but maybe worth a try?


(Hope my html gets entity-ised properly!)</description>
		<content:encoded><![CDATA[<p>It may still be possible to have google index the flash and use swfobject. Consider the following code:</p>
<p>
    document.write(&#8221;This is our &#8216;you need a better version of flash&#8217; spiel&#8221;);</p>
<p>
  </p>
<p>swfobject(&#8221;flash.swf&#8221;, &#8220;flashElement&#8221;);</p>
<p>Obviously that is grossly simplified, and the JS for &#8220;get better flash&#8221; is a bit lame. You could simply write it in the div as you may currently do, but then google will get the warning <span class="caps">AND </span>the flash. Everyone else will just get the warning OR the swfobject-supplied flash. Putting it in a js document.write() means that google gets its  business from , non-js people get the same, and js people get either a warning about flash being old or the flash provided by swfobject.</p>
<p>No idea if that would work, but maybe worth a try?</p>
<p>(Hope my html gets entity-ised properly!)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stéphane Deschamps</title>
		<link>http://scriptingenabled.org/2008/07/flash-and-search-engine/#comment-17</link>
		<dc:creator>Stéphane Deschamps</dc:creator>
		<pubDate>Thu, 03 Jul 2008 12:11:21 +0000</pubDate>
		<guid isPermaLink="false">http://scriptingenabled.org/?p=9#comment-17</guid>
		<description>@Mathieu: haha, it's just not *so* real-life, the idea that people do things the right way... :)

@Chris:

&lt;blockquote&gt;

Just making it indexable by search engines should not stop people from assuming users have the right flash version.

&lt;/blockquote&gt;

Yeah, but consider that Flash plugins have now been able for a while to detect they're not up-to-date and ask you if they can update on-the-fly.

The only good reason for SWFobject was that it gave the user a choice -- again, if people did it right.</description>
		<content:encoded><![CDATA[<p>@Mathieu: haha, it&#8217;s just not <strong>so</strong> real-life, the idea that people do things the right way&#8230; <img src='http://scriptingenabled.org/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>@Chris:</p>
<blockquote>
<p>Just making it indexable by search engines should not stop people from assuming users have the right flash version.</p>
</blockquote>
<p>Yeah, but consider that Flash plugins have now been able for a while to detect they&#8217;re not up-to-date and ask you if they can update on-the-fly.</p>
<p>The only good reason for <span class="caps">SWF</span>object was that it gave the user a choice &#8212; again, if people did it right.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mahtieu 'p01' Henri</title>
		<link>http://scriptingenabled.org/2008/07/flash-and-search-engine/#comment-16</link>
		<dc:creator>Mahtieu 'p01' Henri</dc:creator>
		<pubDate>Thu, 03 Jul 2008 08:21:33 +0000</pubDate>
		<guid isPermaLink="false">http://scriptingenabled.org/?p=9#comment-16</guid>
		<description>I also have mixed feelings about this.

Regarding your note on SWFObject et al. it shouldn't be so much of a problem if search engines do not index the .SWF file since it is supposed to be an enhancement to an accessible, and indexable, page. That is of course assuming that people do things the right way.</description>
		<content:encoded><![CDATA[<p>I also have mixed feelings about this.</p>
<p>Regarding your note on <span class="caps">SWFO</span>bject et al. it shouldn&#8217;t be so much of a problem if search engines do not index the .SWF file since it is supposed to be an enhancement to an accessible, and indexable, page. That is of course assuming that people do things the right way.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
