> peter hall (the owner of the project) was told this by google in person 5 > months ago.
I would assume that the indexing method follows patterns that are similiar to domains that abuse SEO, and so, like a virus scanner would, the domain is flagged the same as an abusing domain is flagged. I think this distinction is important, as to not assume that google is exclusively targeting the project, or flash content. The Ripple toolkit is written to redirect the google agent; this is probably a common SEO abuse technique. > Just checking... you're aware that Google already reads text inside a > SWF, right? (Try a search term like "contrary evidence filetype:swf" to > confirm.) Hi John, I'm aware, but I don't expect that our clients would like their sites searchabe only by appending filetype:swf with every search. Another problem is that the only way to get the page to initialize correctly is to detect the agent that's accessing the swf file. This is necessary to properly redirect it to the page it's embedded in, otherwise the link would launch the swf file without the markup page it was designed to be launched in. Passing an initialization query string to the swf when it's launched from the proper markup page would do the trick too; where all other agents that access the swf directly would be redirected, but, again, you get the google smack down if you redirect the agent. It's unfortunate that it doesn't suffice to satisfy our clients. I think the bottom line is that either Adobe, Google, or both need to do something about this situation; it's a big pain in the ass. H _______________________________________________ Flashcoders mailing list [email protected] http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
