| 2:18 pm on Jul 23, 2007 (gmt 0)|
That is perfectly acceptable. It is called SOFA (search optimized flash architecture)
| 2:52 pm on Jul 23, 2007 (gmt 0)|
thanks for your reply. So is there any guideline on Search Engines Terms and Conditions?
| 2:55 pm on Jul 23, 2007 (gmt 0)|
Macromedia actually have a tool that does this for you too...
|Swf2html extracts text and links from a Macromedia Flash .SWF file, and returns the data to stdout or as an HTML document. |
I would think the cloaked version is a bit more cleaner than the extracted Macromedia data.
There really is no need to cloak the HTML version. I'd be offering that to my visitors as an alternative to the Flash version. Block the Flash from getting indexed (Google can read Flash files) and let the HTML version do its thing.
| 3:08 pm on Jul 23, 2007 (gmt 0)|
thanks for your reply.
I'll try to find more information about that tool from macromedia, thanks.
The thing is that both versions are shown on the same page.
| 5:56 pm on Jul 23, 2007 (gmt 0)|
it is passed for the American Disability Act (ADA) with treaty with like 20 other world wide countries. So now we can create dynamic flash content that can be indexable (to an extent).
| 11:34 pm on Jul 23, 2007 (gmt 0)|
|I'll try to find more information about that tool from macromedia, thanks. |
Adobe - Player Licensing : Search Engine SDK FAQ
|Who should use the Macromedia Flash Search Engine SDK? |
The Macromedia Flash Search Engine SDK is designed for search engine application engineering teams. Users of the SDK can add Flash file decompression, parsing, and indexing features to their server-based search applications.
| 11:52 pm on Jul 23, 2007 (gmt 0)|
It's not cloaking.
We've been using similar techniques since the late 90's, and we've never had any trouble with SE.
Good thing more people are starting to take note of these solutions these days. Although it's kind of funny to see how things seem to be re-discovered in type ten-year intervals :)
| 12:24 am on Jul 24, 2007 (gmt 0)|
...also it should probably be mentioned: The Macromedia SE SDK is not being used by the pros.
Instead: Unobtrusive Flash Objects (UFO) or SWFObject in combination with SWFAddress is the way to go, or custom-build something similar.
| 12:41 am on Jul 24, 2007 (gmt 0)|
I would think these methods only apply if you have 100% Flash based content which is usually rare. In the case of 100% Flash, an HTML version is usually suggested. That takes care of any and all issues you may have with various UAs. ;)
Simple menus, splash pages, etc. can all be addressed using the attributes available for the elements you are using.
| 12:58 am on Jul 24, 2007 (gmt 0)|
Definitely with 100% Flash-sites, yes!
Rare?! I don't know about that. Depends where you look I guess :)
However, I see more and more hybrid-sites utilizing these same concepts (as the embedded applications gets more and more content-dependant). Maybe not so much on the Flash-scene as within the AJAX-community - where it has really become a major issue lately.
In response to Google being able to read SWF-files: There's much confusion going around out there on this topic. Here's the deal: Yes Google can index SWFs, but only the text that is embedded within the published SWF, not text that is dynamicly loaded on the client at runtime. As most flash-development today involves pulling data from a DB at runtime, Google will not be able to index/see that content. Going with a replacable DIV, or similar, is therefore a must if you want to have your content indexed.
| 8:49 am on Jul 24, 2007 (gmt 0)|
It would be a bit foolish if search engines would not allow serving accessible alternatives for Flash content. Here is the relevant W3C guideline:
|Guideline 11. Use W3C technologies and guidelines. |
Checkpoint 11.4 If, after best efforts, you cannot create an accessible page, provide a link to an alternative page that uses W3C technologies, is accessible, has equivalent information (or functionality), and is updated as often as the inaccessible (original) page. [Priority 1]
| 7:34 am on Jul 25, 2007 (gmt 0)|
I've been having very good success with swfobject for several years now. Plus, it allows you to build and bill for two sites (one flash, one html), instead of just one. Naturally, it works with any portion of the page you like.
| 1:17 pm on Jul 25, 2007 (gmt 0)|
I have been working with Macromedia Flash Search Engine SDK and it seems to work very well.
I have been trying to work with a php based page where it uses user agent detection with a php if else statement.
userAgent.ToLower.IndexOf("msnbot") > 1 ¦¦
userAgent.ToLower.IndexOf("slurp") > 1 ¦¦
userAgent.ToLower.IndexOf("ask jeeves/teoma") > 1)
// Insert code for Html layer here.
// Insert current code for flash layer here.
If the page is detected by a SE then the text variation displays. If not then the flash content is displayed.
I am still trying to figure out if the SE's will look at it as spamming or cloaking. If anyones has any experience with this please let me know!
| 2:55 pm on Jul 25, 2007 (gmt 0)|
I think that SEO has a LOT to do with common sense.
If the content you show inside the flash (let's say SE's can't index it) is exactly the same that the one you show in the html, I would say it should be fine and not be considered cloaking. The SE's mission is to show relevant content to people that is looking for something related to it. So doing this should be a fine way to make it happen.
But always showing exactly the same content in both versions. That's where common sense HAS to appear.
| 3:16 pm on Jul 25, 2007 (gmt 0)|
|If the content you show inside the flash (let's say SE's can't index it) |
But, the SEs can index it. And, they get better at it as time goes by. So, it is up to the developer to make sure that the Flash version is blocked from getting indexed while the HTML version does its thing.
Or, you can get high tech with the process and start doing IP based content delivery. It works like a charm if you do it correctly. I don't want the bots inside my Flash content "guessing" at what is there. They still aren't smart enough to do that so "I" have to provide them with the path of least resistance, my HTML version whether it be public or bot only.
In the ultimate scenario, the Flash developer would have taken this all into consideration and is detecting for the Flash Player. If not installed and/or not supported, the HTML version is served. It's that simple.
| 5:56 am on Jul 26, 2007 (gmt 0)|
I agree with pageonresults, the flash web page should be blocked from indexing by robots.txt. Its a best way as google guidelines also suggest the same.
|You may want to consider creating HTML copies of these Flash pages for our crawler. If you create HTML copies, please be sure to include a robots.txt file that disallows the Flash pages in order to ensure that our crawler doesn't recognize these pages as duplicate content. |
Along with it I also add a small text link in bottom for flash version. This is for the user who land up from Google SERPs. Or else someone suggest to check whether the user could read flash or not, depending upon it will redirect to flash or html version. I have never tried this as i am a non technical person for it.
| 8:06 am on Jul 26, 2007 (gmt 0)|