Google Now Indexing Flash Content

Erik Olson, ON THE TOPIC OF General

Jul02 5

I found it hard to contain my joy when Google announced on its Official Blog that it is now able to index Flash content. Hooray!

According to Google, they have perfected an algorithm, "that explores Flash files in the same way that a person would, by clicking buttons, entering input, and so on. Our algorithm remembers all of the text that it encounters along the way, and that content is then available to be indexed."

This is not in the future; Google is indexing Flash sites right now.

While this is a huge step in the direction of having Flash files as crawlable as HTML files, some major hurdles still need to be overcome. Currently, the only content being indexed is embedded directly in the swf. "This includes Flash ‘gadgets’ such as buttons or menus, self-contained Flash websites, and everything in between," as well as URLs. It doesn’t, however, index content loaded externally from HTML, XML, or other swfs. Those files will be indexed as a separate resource and not associated with the parent Flash file.

Another major limitation is the inability to see Flash files loaded using Javascript. This is unfortunate since a large number of Flash files are embedded using swfObject. Also, they do not index non-textual content like images or FLV files; essentially, Google’s only indexing text.

As a Flash developer and designer, I’ve learned that the greatest limitation to Flash is its separation from other elements on the page. With getting information in and out of Flash using External Interface in Actionsript—and now that Flash content is now beginning to be indexed—the tide is turning for Flash accessibility.

Read more about the SEO-related benefits of this new announcement from our very own faux-hawked Josh Chambers. (And yes, Josh, a post on how to design SEO-friendly Flash is forthcoming. And no, you still can’t sit at the designers’ lunch table).

Doug Avery said on 07/02 at 11:11 AM

I was all happy about this until I heard about the JS issue. That’s a huge problem, and while I understand that Google’s not prepared to rifle through all our JS files, they need to work on making an exception for swfObject.

Josh Chambers said on 07/02 at 11:28 AM

Your lunch table is stupid anyway...its never wiped off and stuff…

brad said on 07/02 at 06:19 PM

NOTICE this is off topic.

It looks like a print stylesheet has not been set up? Is there a specific reason for this?

Doug Avery said on 07/02 at 06:55 PM

@brad that’s a good question. Looks like it’s being linked to in the header, but the link is dead...I think it might not have transferred over from the test server. Thanks for spotting this!

frank said on 07/06 at 08:22 AM

Even though there may be some JS issues, it is still a huge step in a great direction for actionscript designers. It is a drawback to designing in flash and I am thrilled to see Google at least taking a stab at fixing it.

Great post!