DCrx you are correct. To address this issue there are new trends in SWFObject / SWFAddress where "duplicate" pages are made each correlating to content seen by the user via #anchor. This technique confuses engines, allocates PageRank as well as keyword relevancy to the wrong URL because Google ignores #anchors.
- users with flash see:http://www.asual.com...e...e&year=2001
- Googlebot sees:http://188.8.131.52...:...=en&strip=1
When I pointed this issue out to the creator of the technique his reply was:
"The case is valid. Deep links with anchors published on other sites
will tell Google to index the start page.
If you want people to link to the site properly you should offer them
other mechanisms to do so ("Link to this page" button, Permalink, RSS,
A bit ironic that their own "SEO" example proves the technique is invalid and that they make no mention of this issue to their own users! Why would I want to offer a method to help users link to the site "properly" other than the address in the address bar? Obviously these folks don't get it!
Bottom line, there is still no method to optimize Flash to compete with HTML. There is no way that I know of to retrofit SWFObject with sIFR. Therefore the best loki can hope for is to help Flash content be indexed using SWFObject. At the same time engines index some content in Flash and the content in loki's clients site may in fact already be indexed. Indexed and ranking are two different issues SWFObject may allow for an increase in indexed content but at the same time it quashes the ability to rank for valuable keyword terms.
The only other thing you can do to help, is to implement Adobe Flash SDK which is designed for site search but used by Google. This is not a fix by any means but Google's Matt Cutts recently verified that Google is using the SDK.