Forum Moderators: Robert Charlton & goodroi
Appreciate your reply on this
The SWFobject approach turns 'normal' thinking upside down -- it presents the html content as the default version,and then tests the user agent for Flash support. If it's there, then the script serves the swf file. The Flash-enabled end user sees no difference compared to the more ordinary approach, but the code is much more transparent to a spider. For example, it doesn't require a noscript element, and it does a great job testing the Flash support for version, suggesting version upgrades when necessary, and so on.
Just a word of caution: whenever your are serving a second version of any content via any techology, there may be a temptation to 'enhance' the version that the spider will see by default (to use deceptive cloaking, in other words.) It's much better to have identical content in both versions -- you do risk frying your rankings with any form of deception.
1).The content between the sources are EXACTLY the same.
2).The purpose behind this is to enable browsers with limitations to utilize the content you are providing. Section 508 accessibility is extremely important, not only to Google but people with disabilities.
I personally have friendships with younger people with visual impairments and I would greatly appreciate the cooperation of webmasters in this arena.
Please help our fellow disabled Internet users. Amber and family you know who I am talking about.
If that's not cloaking, then what on earth would be? And that's all a white-hat needs to know.
A black-hat would wonder what kinds of cloaking Google can automatically detect. And what HE needs to know is, Google is always getting better at automatic detection. If Google isn't parsing SWF files yet today, they may be by next Thursday.
In those penalized cases, I feel the practice was reported to Google by an unhappy SERPs competitor, then detected and penalized by hand.