Quote:
Originally Posted by wige
This is not bad from an SEO standpoint. This is bad from EVERY standpoint. How do you feel when your are browsing from site to site and all of a sudden a window pops up, disables the normal browser functions and starts playing music? You close it, you leave, you never come back...
...And what if the user has a slow connection or an older computer? Either they are forced to a page where they have to wait forever for the flash to load (ie, they leave and never come back) or they don't have flash and are forced to a page with no content and now no back button (in otherwords, they leave and never come back)...
...So this is bad for your users, bad for the search engines, but I guess at least your client's site looks cool... |
I totally agree with you and I tried to explain it a zillion times to our clients... but they still want the full flash site with all the bells and whistles.
I have created the html version of this site under a different domain name with flash header and flash left navigation but with full html content and text links in the footer. It is a pixel-perfect copy of the full flash site with all the same behaviours except background music (the music would start again and again by opening the html pages and it is even more boring than the continuous music on the flash site) and it is displayed in a normal browser window, not a maximized one. The client was complaining about it, he wants maximized window and bg music...
This site generated another problem. The full flash site has a main navigation and a subnavigation on the bottom of each "page" like 3/1, 3/2, 3/3 displaying partial text contents to prevent scrolling. "Of course" the client wanted the html site to act the same way... So I "sliced" the content of each html page, placing them into individual divs and displaying only one div at a time to simulate the paging system of the flash site. The result is a html page with one visible div and a lot (there are 103 on one page!) of hidden divs (display:none). Showing/hiding divs is done by javascript of course.
Another big no-no by the google guidelines... it looks like 98% of the text on the page were hidden text...
But again, I couldn't find a better solution to solve the client's needs - anybody have better ideas?