<?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: Update on SWF Indexing Issues</title>
	<atom:link href="http://www.peterelst.com/blog/2008/07/06/update-on-swf-indexing-issues/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.peterelst.com/blog/2008/07/06/update-on-swf-indexing-issues/</link>
	<description>Flash Platform Consultant</description>
	<pubDate>Thu, 04 Dec 2008 22:32:28 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.5</generator>
		<item>
		<title>By: Like A Fish Needs A Bicycle: RIA and SEO &#124; Iona.LABS</title>
		<link>http://www.peterelst.com/blog/2008/07/06/update-on-swf-indexing-issues/#comment-19090</link>
		<dc:creator>Like A Fish Needs A Bicycle: RIA and SEO &#124; Iona.LABS</dc:creator>
		<pubDate>Mon, 18 Aug 2008 03:07:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.peterelst.com/blog/?p=621#comment-19090</guid>
		<description>[...] and searchable. Much written, with no real concrete answers. Lots of tests (A very good one done by Peter Elst), a contest held by Ryan Stewart (Flexmagically Searchable, FTW!), and some well formed opinions [...]</description>
		<content:encoded><![CDATA[<p>[...] and searchable. Much written, with no real concrete answers. Lots of tests (A very good one done by Peter Elst), a contest held by Ryan Stewart (Flexmagically Searchable, FTW!), and some well formed opinions [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Like A Fish Needs A Bicycle: RIA and SEO &#124; Visualrinse &#124; Design and Development by Chad Udell</title>
		<link>http://www.peterelst.com/blog/2008/07/06/update-on-swf-indexing-issues/#comment-19042</link>
		<dc:creator>Like A Fish Needs A Bicycle: RIA and SEO &#124; Visualrinse &#124; Design and Development by Chad Udell</dc:creator>
		<pubDate>Mon, 04 Aug 2008 03:50:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.peterelst.com/blog/?p=621#comment-19042</guid>
		<description>[...] and searchable. Much written, with no real concrete answers. Lots of tests (A very good one done by Peter Elst), a contest held by Ryan Stewart (Flexmagically Searchable, FTW!), and some well formed opinions [...]</description>
		<content:encoded><![CDATA[<p>[...] and searchable. Much written, with no real concrete answers. Lots of tests (A very good one done by Peter Elst), a contest held by Ryan Stewart (Flexmagically Searchable, FTW!), and some well formed opinions [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mitchell Thomas</title>
		<link>http://www.peterelst.com/blog/2008/07/06/update-on-swf-indexing-issues/#comment-18924</link>
		<dc:creator>Mitchell Thomas</dc:creator>
		<pubDate>Thu, 17 Jul 2008 23:23:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.peterelst.com/blog/?p=621#comment-18924</guid>
		<description>Nice article Peter. I wonder what is the use of indexing a swf file that is dependent upon the data (i.e. flashvars) that get passed to it? I'm specifically talking about flash video players and widgets here - but even a flash website that is programmed to respond to deep linking, could potentially have the same problem. It seems that there are a lot of swf files out there that are not very useful outside of the context of the HTML page they are embedded in. And even if the swf can stand by itself one of the reasons we embed them in HTML pages is so the swf can be viewed at the size it was designed to be viewed at. I realize you can set the scaleMode to noScale in actionscript - but what if your application requires scaling?

As for your tests - have you tried filling in the title/description in the Document properties so see how that affects indexing? The title and description are part of the compiled swf, so they should be readable by the Googlebot.</description>
		<content:encoded><![CDATA[<p>Nice article Peter. I wonder what is the use of indexing a swf file that is dependent upon the data (i.e. flashvars) that get passed to it? I&#8217;m specifically talking about flash video players and widgets here - but even a flash website that is programmed to respond to deep linking, could potentially have the same problem. It seems that there are a lot of swf files out there that are not very useful outside of the context of the HTML page they are embedded in. And even if the swf can stand by itself one of the reasons we embed them in HTML pages is so the swf can be viewed at the size it was designed to be viewed at. I realize you can set the scaleMode to noScale in actionscript - but what if your application requires scaling?</p>
<p>As for your tests - have you tried filling in the title/description in the Document properties so see how that affects indexing? The title and description are part of the compiled swf, so they should be readable by the Googlebot.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Google Indexes SWFs and external content &#124; Fleximagically Searchable &#124; Ryan Stewart's Flex SEO Contest &#124; Circle Cube Studio</title>
		<link>http://www.peterelst.com/blog/2008/07/06/update-on-swf-indexing-issues/#comment-18916</link>
		<dc:creator>Google Indexes SWFs and external content &#124; Fleximagically Searchable &#124; Ryan Stewart's Flex SEO Contest &#124; Circle Cube Studio</dc:creator>
		<pubDate>Tue, 15 Jul 2008 23:55:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.peterelst.com/blog/?p=621#comment-18916</guid>
		<description>[...] information: I&#8217;ve found that&#8217;s helpful at Peter Elst&#8217;s post. And Ryan explains Google and Flash&#8217;s relatoinship development here. Here and here is what [...]</description>
		<content:encoded><![CDATA[<p>[...] information: I&#8217;ve found that&#8217;s helpful at Peter Elst&#8217;s post. And Ryan explains Google and Flash&#8217;s relatoinship development here. Here and here is what [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Flex SEO Contest - my two first entries &#124; Cyril Hanquez</title>
		<link>http://www.peterelst.com/blog/2008/07/06/update-on-swf-indexing-issues/#comment-18907</link>
		<dc:creator>Flex SEO Contest - my two first entries &#124; Cyril Hanquez</dc:creator>
		<pubDate>Mon, 14 Jul 2008 13:05:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.peterelst.com/blog/?p=621#comment-18907</guid>
		<description>[...] the comments and concerns regarding SEOing Flash and Flex files, Ryan Stewart decided to launch a contest to [...]</description>
		<content:encoded><![CDATA[<p>[...] the comments and concerns regarding SEOing Flash and Flex files, Ryan Stewart decided to launch a contest to [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Hans Van de Velde</title>
		<link>http://www.peterelst.com/blog/2008/07/06/update-on-swf-indexing-issues/#comment-18897</link>
		<dc:creator>Hans Van de Velde</dc:creator>
		<pubDate>Sat, 12 Jul 2008 20:56:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.peterelst.com/blog/?p=621#comment-18897</guid>
		<description>When you say that Google will start indexing XML files, I wonder about how Google will be able to interpret the text. For example, what I experienced is that a title-tag or h1,h2,h3,... tags have more weight when your content gets indexed and ul/ol-tags are simply lists of thing.s But when you don't use HTML, there is no more standard meaning in your content (!)

To prove my point, I also have a funny (quite nicely working) example/experiment I'd like to share here. For one particular website, I used XHTML pages to put my content in (and no XML files as usual). Surprisingly, parsing the XHTML was easier that I thought.
Result: the whole site is fully indexed by Google (yippie !).
You can check this example by typing “site:www.alternativ.be” in Google (even all the images have been indexed too).

When structuring dynamic content it’s important to have tags that are semantically correct. For example, a title in your Flash site should be treated differently than body-text and so on, and so on...

Side note: the Alternativ website itself was built in ActionScript 2 and the content management system with Flex 2 with ActionScript 3 and I must say that with E4X, extracting content from any XHTML page is a breeze.</description>
		<content:encoded><![CDATA[<p>When you say that Google will start indexing XML files, I wonder about how Google will be able to interpret the text. For example, what I experienced is that a title-tag or h1,h2,h3,&#8230; tags have more weight when your content gets indexed and ul/ol-tags are simply lists of thing.s But when you don&#8217;t use HTML, there is no more standard meaning in your content (!)</p>
<p>To prove my point, I also have a funny (quite nicely working) example/experiment I&#8217;d like to share here. For one particular website, I used XHTML pages to put my content in (and no XML files as usual). Surprisingly, parsing the XHTML was easier that I thought.<br />
Result: the whole site is fully indexed by Google (yippie !).<br />
You can check this example by typing “site:www.alternativ.be” in Google (even all the images have been indexed too).</p>
<p>When structuring dynamic content it’s important to have tags that are semantically correct. For example, a title in your Flash site should be treated differently than body-text and so on, and so on&#8230;</p>
<p>Side note: the Alternativ website itself was built in ActionScript 2 and the content management system with Flex 2 with ActionScript 3 and I must say that with E4X, extracting content from any XHTML page is a breeze.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: More on the Flex SEO contest &#124; switch for SWFObject to Object/Embed tags &#124; zedia flash blog</title>
		<link>http://www.peterelst.com/blog/2008/07/06/update-on-swf-indexing-issues/#comment-18886</link>
		<dc:creator>More on the Flex SEO contest &#124; switch for SWFObject to Object/Embed tags &#124; zedia flash blog</dc:creator>
		<pubDate>Sat, 12 Jul 2008 01:40:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.peterelst.com/blog/?p=621#comment-18886</guid>
		<description>[...] around the fact the Google would not reference website that use javascript to embed the flash file. Peter Elst seems to think the contrary but I think it is worth a try. I was previously using SWFObject to [...]</description>
		<content:encoded><![CDATA[<p>[...] around the fact the Google would not reference website that use javascript to embed the flash file. Peter Elst seems to think the contrary but I think it is worth a try. I was previously using SWFObject to [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: savvas.malamas &#187; Blog Archive &#187; Saving {my} twitter..</title>
		<link>http://www.peterelst.com/blog/2008/07/06/update-on-swf-indexing-issues/#comment-18884</link>
		<dc:creator>savvas.malamas &#187; Blog Archive &#187; Saving {my} twitter..</dc:creator>
		<pubDate>Fri, 11 Jul 2008 19:35:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.peterelst.com/blog/?p=621#comment-18884</guid>
		<description>[...] Just because I use it everyday it is obvious that sometimes I tweet things that I might don&#8217;t want to be available to the public timeline (Flex doesn&#8217;t have a timeline) and especially to search engines (Google please leave my twitter account and try to use Adobe&#8217;s help for swf indexing). [...]</description>
		<content:encoded><![CDATA[<p>[...] Just because I use it everyday it is obvious that sometimes I tweet things that I might don&#8217;t want to be available to the public timeline (Flex doesn&#8217;t have a timeline) and especially to search engines (Google please leave my twitter account and try to use Adobe&#8217;s help for swf indexing). [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: A Thought About Flash Indexing &#171; Dead Ink Vinyl</title>
		<link>http://www.peterelst.com/blog/2008/07/06/update-on-swf-indexing-issues/#comment-18824</link>
		<dc:creator>A Thought About Flash Indexing &#171; Dead Ink Vinyl</dc:creator>
		<pubDate>Tue, 08 Jul 2008 17:15:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.peterelst.com/blog/?p=621#comment-18824</guid>
		<description>[...] has announced the Flex SEO Contest to encourage the community to establish best practices for Flash/Flex indexing. The rules are straightforward and the top prize is CS4 Master Collection. I like the challenge and [...]</description>
		<content:encoded><![CDATA[<p>[...] has announced the Flex SEO Contest to encourage the community to establish best practices for Flash/Flex indexing. The rules are straightforward and the top prize is CS4 Master Collection. I like the challenge and [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gerd Kamp</title>
		<link>http://www.peterelst.com/blog/2008/07/06/update-on-swf-indexing-issues/#comment-18822</link>
		<dc:creator>Gerd Kamp</dc:creator>
		<pubDate>Tue, 08 Jul 2008 05:52:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.peterelst.com/blog/?p=621#comment-18822</guid>
		<description>We are also in urgent need of some place to put  robots info / crawling restrictions.

At work  we make use of remote calls to xml files e.g. for our live event tickers . In addition to our reporting we also include near-time stats and position data. This data is licensed to us under the condition that it is not (easily) publicly available. 

The application and the data is then pushed to our customers sites (e.g. around 100 newspapers, publishers and portals for EURO2008).   Since these sites are not ours we do not have access to the robots.txt files.  Using  META tags is also not an option since we are using XML files.

Switching over to serving the data files only from servers that are under our control is (currently) not an option.

So where do we put the robots infos? Google/Adobe? I guess there are more having the exact same problems. Some clarification would definitely help

All this would not be an issue if instead of indexing the xml file etc. separately. Google would use the information in order to link back to the originating swf file.</description>
		<content:encoded><![CDATA[<p>We are also in urgent need of some place to put  robots info / crawling restrictions.</p>
<p>At work  we make use of remote calls to xml files e.g. for our live event tickers . In addition to our reporting we also include near-time stats and position data. This data is licensed to us under the condition that it is not (easily) publicly available. </p>
<p>The application and the data is then pushed to our customers sites (e.g. around 100 newspapers, publishers and portals for EURO2008).   Since these sites are not ours we do not have access to the robots.txt files.  Using  META tags is also not an option since we are using XML files.</p>
<p>Switching over to serving the data files only from servers that are under our control is (currently) not an option.</p>
<p>So where do we put the robots infos? Google/Adobe? I guess there are more having the exact same problems. Some clarification would definitely help</p>
<p>All this would not be an issue if instead of indexing the xml file etc. separately. Google would use the information in order to link back to the originating swf file.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
