Flash.
For many years, SEO's have regarded Flash as the Megan Fox of the Internet, pretty to look at, but ultimately lacking in any real substance. The problem with Flash websites you see, was that search engine crawlers would struggle to read the content displayed on these sites, due to the structure of a traditional Flash file. In many instances, a Flash site, which on the face of it looked to have 30-40 pages, would actually only consist of one Flash file eg: mysite.swf. Because of this, Flash files would struggle to get indexed on search engines and if they did, it would just be the home page.
Thankfully for us, developments have now made things slightly easier when it comes to Flash optimisation. We now have what is called an "SWFObject" at our disposal - an open source javascript library (basically a collection of pre-written javascript controls) that you download and add to the head section of your Web page. This allows you to embed Flash content onto a page. In effect, this creates an alt tag for the flash content on your page – meaning that there is text to read even if the flash content does not display. Our friendly search engine spiders can thus crawl the site.
Using this file, you can also detect whether a user has a Flash plug-in enabled or not, and can then redirect them to another page or display alternative content if they don’t. The alternative content is obviously useful, in that it can be indexed and crawled by Search Engine bots.
So as an example, were I to have a Flash file praising the fact that I have the chiseled abs of a Roman God, I could embed html to sit in the SWFObject.
Using my amazing graphic skills, I was able to put together the following illustration:
Now, on the assumption that the image above is a Flash file (ie: shaun-flash.swf), we could optimise the Flash file by doing the following:
1) Firstly, in the <head> section, we would call up the SWFObject, as well as define a name value to the object id. So:
<script type="text/javascript" src="swfobject.js"></script>
<script type="text/javascript">swfobject.registerObject("FlashVideo", "9.0.0", false);</script>
2) Then, we embed the html code so that it sits behind the actual Flash file (shaun-flash.swf)
<div>
<object id="FlashVideo" classid="clsid:D27CDB6E-AE6D-11cf-96B8-444553540000" width="400" height="300">
<param name="movie" value="shaun-flash.swf" />
<object type="application/x-shockwave-flash" data="shaun-flash.swf" width="400" height="300">
<div>
<h1>Shaun is AWESOME<h1>
<p>And has the chiseled abs of a Roman God.</p>
<br /><br />
</div>
</object>
</object>
</div>
As the code shows, I am able to replicate the Flash content with applicable html, using header tags and other html attributes if necessary.
What is important though, is that each Flash page has its own url. If that is the case, than you can greatly optimise the site using the above.
If the site does not have unique urls, and everything is located in one .swf file, then the option of creating a static website to run alongside the Flash one is probably the best option.
Agree? Disagree? Let’s hear your thoughts.
Some other links of interest:






great post, we usually tend to recommend a complete redesign whenever a client arrives with a flash site, but i have also been reading about the options out there, and the swfobject seems like a viable one.
more of these types of articles please.
Posted by Griff on 2009/11/12