All posts tagged seb development

Flash Indexed in Searches?

March 17th, 2009 by Glenn Gabe

When it comes to SEO, Flash can be a polarizing topic. Whenever I’m speaking with clients about their SEO initiatives (along with their creative and technical staff), it only takes one mention of flash to suddenly get a mixture of angry, excited, and confused looks.

When you break it down, some brand managers love how engaging flash can be, designers love the boundless creativity it offers, IA directors can do without it, SEO’s cringe at the thought of it, and C-level marketers don’t know who to listen to! But one thing is clear. Flash isn’t going anywhere…as you can see by the massive number of websites that employ flash content.

index-flash-logo

I bring a somewhat unique perspective. I started developing with Flash in 1997, and yes, I once developed highly interactive and engaging flash movies that would make most SEO’s go for my jugular. My roots are in interactive development, and flash was a key tool in my arsenal.

Today, I still understand the power of flash when used properly, but I also know the incredible power of SEO. I’m not against the use of flash, but you better believe I want it optimized if it’s going to be used by my clients. I like to think I’ve come a long way. :)

Since I have a broad background in flash development and have developed hundreds of flash movies and applications over the past 12 years, it’s been interesting to delve deeply into flash SEO to see how it has evolved. Although I’ve written previously about using SWFObject to provide crawlable alternative content for flash (along with flash video content), I’ve also been heavily testing and analyzing how the engines index flash (SWF files).

Personally, I’m tired of showing clients the big blank cache of their flash sites in Google! It’s a great visual and is usually a jaw-dropping experience for them, but that simply can’t remain the standard. That’s why I was excited last June when Adobe, Google, and Yahoo announced their partnership.

Improved Flash Indexing, June 2008

In June of 2008, Adobe announced that it was working with Google and Yahoo on improving flash indexing. As you canindex-flash-partnership imagine, I was chomping at the bit to test and analyze how the engines were indexing flash, based on this announcement.

Just to clarify, Google was indexing SWF files prior to the partnership, but they weren’t working with Adobe on streamlining and improving the process. I can remember one of my clients a few years ago sending me a link to one of their SWF files in the SERPs, along with one line of text, “What the heck is this?” :) What was presented in the SERPs wasn’t exactly pretty, but it was a start.

My goal since the announcement has been to make some sense out of how the engines index flash, what are some best practices you should follow when publishing flash content, and what are some things to watch out for as you develop more flash content.

After yet another round of testing over the past few weeks, I decided to write this post so I can help lead you down the right path. Unfortunately, it’s not as easy as that last sentence sounds since this is a highly dynamic area of SEO… It has even changed since July and I fully expect it to keep evolving. That said, I’ll provide some findings and guidance below.

First, since I’ve heard every flash pun in the world over the past year, let me get something out of the way:

This post will not be over in a flash, nor will it be a flash in the pan, hopefully your seo life won’t flash by before your eyes, and Flash the superhero won’t be helping you with your projects… OK, enough with the flash puns! :) Let’s jump in.

GOOGLE IS CRAWLING FLASH, FORGET ABOUT SEO, LET’S DEVELOP EVERYTHING IN FLASH, WOOHOO! But wait…

I remember a flash designer commenting on one of my blog posts about flash seo saying, “Your post is now irrelevant! Google is indexing Flash! Let’s all binge on flash.” Not in those exact words of course. I think my first reaction was “hold on a second buddy…” Nothing has been perfected yet, and actually, this was just announced! By the way, I was right. It wasn’t perfected yet. It was a step in the right direction, but there were other factors that impacted how your flash files were being crawled, namely how you publish your flash content.

In addition, all flash content was obviously not being indexed so it would be premature to think you could disregard providing the engines with alternative html content (which has been a standard practice from an SEO standpoint). It would be crazy to think that Google and Yahoo would instantaneously index all flash content on the web, right?

Great News, But There Were Some Problems

At that time (July 08), Google was in fact indexing SWF files, but there were some limitations. For example, Google was not indexing SWF files published using some of the popular JavaScript-based publishing methods. I could clearly see that using standard object and embed tags and SWFObject 2.x using static publishing yielded strong results, but using earlier versions of SWFObject to write out your flash movies (that relied on JavaScript) wasn’t yielding positive results.

And by the way, many developers were using those JavaScript-based methods in order to get around the “Click to Activate” issue from a few years ago (or what flash developers liked to call the “Grey Box of Death”.) So at that time, if you were a flash designer or developer using JavaScript to publish your flash movies, your SWF files were NOT being indexed. Again, this was a work in progress.

More Concerns About Flash Indexing

But, my concerns didn’t stop with JavaScript publishing methods. I started to wonder what type of content within SWF files was being indexed? Was it just static text in flash, imported xml, dynamically loaded SWF files, flv files, text files, ActionScript code, etc? Was Google finding and following links in SWF files? Did SWF files build PageRank? Did links in flash pass PageRank? What about nofollow? Was my code being indexed? What about text that’s broken down into artwork in flash? So on and so forth.

Flash is not a simple application…it’s definitely multifaceted (think code, static text, dynamic text, object oriented code, vectors, photos, video, etc.) Needless to say, I had a lot of questions (like many in the industry).

Let’s Not Take A Step Back As Flash Developers…

There was one part of the announcement that really concerned me. Specifically, that dynamically loaded content would not be associated with the parent flash movie (like txt, xml, etc.) I was concerned because that’s a common way for experienced flash developers to scale their content. In addition, dynamically loaded SWF’s would not be associated with the parent movie.

Excuse me, but I have been using that technique since I started developing with flash! Most flash developers and designers understand that breaking up your flash movies into manageable pieces is critical to keeping file-size down and scannability up.

So based on what I explained above, how would the announcement about indexing flash content impact best practices in flash development? Would developers start loading content into one SWF versus logically breaking their content apart? Would they stop using xml data and flood their parent SWF with text? What about spammers? Could they take advantage of how flash was being indexed? And of course, the goal for SEO is ranking, so what would rank? Would the SWF file rank, the parent webpage, or both? MORE >>

10 Harsh Truths About Corporate Websites

By Paul Boag

We all make mistakes running our websites. However, the nature of those mistakes varies depending on the size of your company. As your organization grows, the mistakes change. This post addresses common mistakes among large organizations.

Most of the clients I work with are large organizations: universities, large charities, public sector institutions and large companies. Over the last 7 years, I have noticed certain recurring misconceptions among these organizations. This post aims to dispel these illusions and encourage people to face the harsh reality.

The problem is that if you are reading this post, you are probably already aware of these things. But hopefully this article will be helpful to you as you convince others within your organization. In any case, here are our 10 harsh truths about websites of large organizations.

1. You Need A Separate Web Division

In many organizations, the website is managed by either the marketing or IT department. However, this inevitably leads to a turf war, with the website becoming the victim of internal politics.

In reality, pursuing a Web strategy is not particularly suited to either group. IT may be excellent at rolling out complex systems, but it is not suited to developing a friendly user experience or establishing an online brand.

Screenshot of Zeldman's website
Zeldman urges organisations to create a separate web division.

Marketing, on the other hand, is little better. As Jeffrey Zeldman puts it in his article Let there be Web divisions:

The Web is a conversation. Marketing, by contrast, is a monologue… And then there’s all that messy business with semantic markup, CSS, unobtrusive scripting, card-sorting exercises, HTML run-throughs, involving users in accessibility, and the rest of the skills and experience that don’t fall under Marketing’s purview.

Instead, the website should be managed by a single unified team. Again, Zeldman sums it up when he writes:

Put them in a division that recognizes that your website is not a bastard of your brochures, nor a natural outgrowth of your group calendar. Let there be Web divisions.

2. Managing Your Website Is A Full-Time Job

Not only is the website often split between marketing and IT, it is also usually under-resourced. Instead of there being a dedicated Web team, those responsible for the website are often expected to run it alongside their “day job.” When a Web team is in place, it is often over-stretched. The vast majority of its time is spent on day-to-day maintenance rather than longer-term strategic thinking.

This situation is further aggravated by the fact that the people hired to “maintain” the website are junior members of the staff. They do not have the experience or authority to push the website forward. It is time for organizations to seriously invest in their websites by hiring full-time senior Web managers to move their Web strategies forward.

3. Periodic Redesign Is Not Enough

Because corporate websites are under-resourced, they are often neglected for long periods of time. They slowly become out of date with their content, design and technology.

Eventually, the website becomes such an embarrassment that management steps in and demands that it be sorted. This inevitably leads to a complete redesign at considerable expense. As I point out in the Website Owners Manual, this a flawed approach. It is a waste of money because when the old website is replaced, the investment put into it is lost, too. It is also tough on finances, with a large expenditure having to be made every few years.

Screenshot of Cameron Molls Article
Cameron Moll encourages web designers to realign their website rather than redesign.

A better way is continual investment in your website, allowing it to evolve over time. Not only is this less wasteful, it is also better for users, as pointed out by Cameron Moll in his post Good Designers Redesign, Great Designers Realign.

4. Your Website Cannot Appeal To Everyone

One of the first questions I ask a client is, “Who is your target audience?” I am regularly shocked at the length of the reply. Too often, it includes a long and detailed list of diverse people. Inevitably, my next question is, “Which of those many demographic groups are most important?” Depressingly, the answer is usually that they are all equally important.

The harsh truth is that if you build a website for everyone, it will appeal to no one. It is important to be extremely focused about your audience and cater your design and content to it. Does this mean you should ignore your other users? Not at all. Your website should be accessible by all and not offend or exclude anybody. However, the website does need to be primarily aimed at a clearly defined audience.

5. You Are Wasting Money On Social Networking

I find it encouraging that website managers increasingly recognize that a Web strategy is more than running a website. They are beginning to use tools such as Twitter, Facebook and YouTube to increase their reach and engage with new audiences. However, although they are using these tools, too often they do so ineffectively. Tweeting on a corporate account or posting sales demonstrations on YouTube misses the essence of social networking.

Screenshot of Microsoft's Channel 9 website
Microsoft dramatically improved its image amoung the development community by allowing Microsoft staff to speak out via the Channel 9 website.

Social networking is about people engaging with people. Individuals do not want to build relationships with brands and corporations. They want to talk to other people. Too many organizations throw millions into Facebook apps and viral videos when they could spend that money on engaging with people in a transparent and open away.

Instead of creating a corporate Twitter account or indeed even a corporate blog, encourage your employees to start Tweeting and blogging themselves. Provide guidelines on acceptable behavior and what tools they need to start engaging directly with the community connected to your products and services. This demonstrates not only your commitment to the community but also the human side of your business.

6. Your Website Is Not All About You

Where some website managers want their website to appeal to everybody, others want it to appeal to themselves and their colleagues. A surprising number of organizations ignore their users entirely and base their websites entirely on an organizational perspective. This typically manifests itself in inappropriate design that caters to the managing director’s personal preferences and contains content full of jargon.

A website should not pander to the preferences of staff but should rather meet the needs of its users. Too many designs are rejected because the boss “doesn’t like green.” Likewise, too much website copy contains acronyms and terms used only within the organization.

7. You’re Not Getting Value From Your Web Team

Whether they have an in-house Web team or use an external agency, many organizations fail to get the most from their Web designers. Web designers are much more than pixel pushers. They have a wealth of knowledge about the Web and how users interact with it. They also understand design techniques, including grid systems, white space, color theory and much more.

Post from Twitter complaining about being a pixel pusher
Treating designers as pixel pushers wastes their design experience: post from Twitter complaining about being a pixel pusher

It is therefore wasteful to micro-manage by asking them to “make the logo bigger” or to “move that 3 pixels to the left.” By doing so, you are reducing their role to that of a software operator and wasting the wealth of experience they bring.

If you want to get the maximum return on your Web team, present it with problems, not solutions. For example, if you’re targeting your website at teenage girls, and the designer goes for corporate blue, suggest that your audience might not respond well to that color. Do not tell him or her to change it to pink. This way, the designer has the freedom to find a solution that may even be better than your choice. You allow your designer to solve the problem you have presented.

8. Design By Committee Brings Death

The ultimate symbol of a large organization’s approach to website management is the committee. A committee is often formed to tackle the website because internal politics demand that everybody has a say and all considerations be taken into account. To say that all committees are a bad idea is naive, and to suggest that a large corporate website could be developed without consultation is fanciful. However, when it comes to design, committees are often the kiss of death.

Illustration showing why design by committee fails
Design by committee leads to design on the fly.

Design is subjective. The way we respond to a design can be influenced by culture, gender, age, childhood experience and even physical conditions (such as color blindness). What one person considers great design could be hated by another. This is why it is so important that design decisions be informed by user testing rather than personal experience. Unfortunately, this approach is rarely taken when a committee is involved in design decisions.

Instead, designing by committee becomes about compromise. Because committee members have different opinions about the design, they look for ways to find common ground. One person hates the blue color scheme, while another loves it. This leads to designing on the fly, with the committee instructing the designer to “try a different blue” in the hopes of finding middle ground. Unfortunately, this leads only to bland design that neither appeals to nor excites anyone.

9. A CMS Is Not A Silver Bullet

Many of the clients I work with have amazingly unrealistic expectations of CMS (content management systems). Those without one think it will solve all of their content woes, while those who have one moan about it because it hasn’t!

It is certainly true that a CMS can bring a lot of benefits. These include:

  • reducing the technical barriers of adding content,
  • allowing more people to add and edit content,
  • facilitating faster updates,
  • and allowing greater control.

However, many CMS are less flexible than their owners would like. They fail to meet the changing demands of the websites they manage. Website managers also complain that their CMS is hard to use. However, in many cases, this is because those using it have not been adequately trained or are not using it regularly enough.

Finally, a CMS may allow content to be easily updated, but it does not ensure that content will be updated or even that the quality of content will be acceptable. Many CMS-based websites still have out-of-date content or poorly written copy. This is because internal processes have not been put in place to support the content contributors.

If you look to a CMS to solve your website maintenance issues, you will be disappointed.

10. You Have Too Much Content

Part of the problem with content maintenance on large corporate websites is that there is too much content in the first place. Most of these websites have “evolved” over years, with more and more content having been added. At no stage has anybody reviewed the content and asked what could be taken away.

Many website managers fill their website with copy that nobody will read. This happens because of:

  • A fear of missing something: by putting everything online, they believe users will be able to find whatever they want. Unfortunately, with so much information available, it is hard to find anything.
  • A fear users will not understand: whether from a lack of confidence in their website or in their audience, they feel the need to provide endless instruction to users. Unfortunately, users never read this copy.
  • A desperate desire to convince: they are desperate to sell their product or communicate their message, and so they bloat the text with sales copy that actually conveys little valuable information.

Steve Krug, in his book Don’t Make Me Think, encourages website managers to “Get rid of half the words on each page, then get rid of half of what’s left.” This will reduce the noise level on each page and make the useful content more prominent.

Conclusions

Large organizations do a lot right in running their websites. However, they also face some unique challenges that can lead to painful mistakes. Resolving these problems means accepting that mistakes have been made, overcoming internal politics and changing the way you control your brand. Doing so will give you a significant competitive advantage and allow your Web strategy to become more effective over the long term.

About the author

Paul Boag is the founder of UK Web design agency Headscape, author of the Website Owners Manual and host of award-winning Web design podcast Boagworld.com.