SEU, Search Engine Useless

Lately I have been asked again and again, “What can I do to improve my rankings in Google?”. This is a bit of a loaded question, but one I always attempt to answer when I am dealing with anything search related.

I usually begin with a quick glance at the website using the 30 second test, a skim of the source code to view the semantics of the HTML and then check out the basic structure of the document and a few other technical bits here and there.

In most instances this process is just a formality as the real answer is usually quite obvious, Search Engine Useless content, or SEUs. Content that is invisible to the search engines that you are just throwing away, usually without being aware of the real consequences.

This content may be semantic and validate by W3C standards, it could even be fully accessible in some instances, but to search engines it means nothing. Search Engine Useless (SEU) content is something that plagues our industry and drives people to inquire, “Why isn’t my website getting exposure?”

Listed below are some of the most common offenders.

Iframes

Usually used on a website where you need to quickly pull in a 3rd parties content without the bother of dealing with server-side implementations. Stemming from quick deals established by sales departments that have little or no communication with developers or just the job that had to get out the door with no fuss.

The interesting thing is most of this content I encounter is very useful and engaging to the users, which would bring in relevant referral traffic if you could only expose the content.

Flash

Flash can be fully accessible when developed correctly with the new tools available over the last couple of years. It can even aid in screenreader detection in some instances, improving accessibility for websites.

Yet this accessibility, which would usually aid search engine optimisation efforts, will do nothing to help search engine spiders crawl Flash content.

The <embed> or <object> elements are the SEU offenders in this instance. Hiding good content in a plug-in that cannot be crawled by search engines. Alternate content can be offered, using great standards compliant techniques, but is rarely executed in a truly efficient or consistent manner.

AJAX

Often developed with improved interfaces for content delivery to users, but AJAX and JavaScript still tend to be used as blankets to cover content from search engines.

HIJAX has been coined as an accessible and searchable way of exposing content to the users (and search engines) but most current Web 2.0 implementations tend to ignore this idealistic technique of development.

Video and Audio

Engaging and a great way to present content but you won’t see it turn up in the search engine result pages unless you are going through Google Video. Transcripting is a great alternative but I have yet to see a corporation excited about this solution.

Lack of Content

If you don’t actually produce original content and lots of it… that could be strategy to think about. This is a problem I deal with regularly. No, FAQs and Terms & Conditions don’t count.

Why Can’t We Fix This?

It’s the bottom line that pushes these blind spots in content out to the users. It’s sales, advertising and marketing having to make targets each month without having a well thought out process to be able to implement things efficiently and being able to slow down and provide minimum standards for development on large, public websites.

It’s about SEO being the buzzword for quick results, until someone suggests long term solutions to make a real difference and solve the real problem and suddenly you don’t hear the topic brought up at meetings so much anymore.

We know the technical solutions, so why aren’t they being implemented? Well, it’s just easier to implement this way. No fuss, no problems with technical implementation or developers adding further bottlenecks to a deal that had to be out yesterday.

The Solutions Right Now

Education is always a big factor in reducing SEUs littering our industry. Slowly suggesting how to rebuild these SEU elements next time they redesign, rework or just have time to factor some of these elements that are hurting chances at returning great search results.

Having these methods and techniques as a slow mantra to be repeated at every opportune moment. This can slowly find it’s way into future builds and into future project plans without people even realising it.

One last solution is the optimisation of the actual page the SEU is embedded on. Optimising the usual page titles, meta-data and semantic headers that surround these elements. Also thinking about adding items such as introduction paragraphs, tags for users to contribute descriptive data and captions, summaries and anything else that may be relevant to the user.

It’s just small steps, but these can help to slowly eliminate one SEU at a time.

Comments

Max Design - standards based web design, development and training » Some links for light reading (23/10/07) says: October 24, 2007 @ 12:42 am

[...] SEU, Search Engine Useless [...]

Richard Morton says: October 24, 2007 @ 1:24 am

SEU - Good term, I like it.

You mention that Flash content can be fully accessible, but don’t say whether this means it is likely to be search engine friendly, does it help or not? Do you know any examples of good accessible flash content and or search engine friendly flash content.

ambrose says: October 24, 2007 @ 10:18 am

Your link to “30 second test” in the second par is wrong.

Standardzilla says: October 24, 2007 @ 10:25 am

@ambrose - thanks for that, corrected now.

@Richard - reading that back I totally missed the point of that Flash blurb I wrote, I meant to say that Flash can be fully accessible, yet still is not indexed by search engines.

Search spiders cannot access the embedded flash movie. One rare occurrence where being accessible does not aid SEO efforts.

Samatva says: October 25, 2007 @ 12:45 pm

Search engine robots have serious “disabilities” - they are basically blind and deaf. If you make your site accessible to poeple with disabilities, you will also make it accessible to bots. Neat, huh?

See WebAim for all you need to know…
http://webaim.org/

Standardzilla says: October 25, 2007 @ 12:50 pm

@samatva - to an extent that is true, but thinking that if you simply have an accessible website that you are also perfectly optimised for search engines, then you are incorrect.

Accessibility does not aid exposing Flash content (as in accessible Flash publishing, rather than alternative content), avoiding duplicate content filtering and other SEO specific issues that are not covered by simple WCAG checkpoints.

Both accessibility and SEO can be fine tuned once you cover these basic concepts. Advanced SEO principles do not often cross-over with many advanced accessibility issues (eg. captioning does nothing for SEO, yet transcripting aids both sides)

Arquero says: January 16, 2008 @ 8:30 pm

I have a site that uses iframes for dynamic content (so only information needed is loaded). To get search engines to actually index the iframe content, a link is displayed within the iframe object:

Ex: Page description

This way browsers with iframes disabled would see the links. Search Engines can see the content.

Pros: Search Engines can see iframe content, since they do index links within iframe tags.

Cons: Google’s ‘Page Rank’ will now rank ’somepage.php’ rather than the parent page. Also google will index somepage.php rather than the parent page, so when you click on it from a search you will now have the contents of the iframe without the parent page. This may look ugly as it was in my case. To compensate the iframe has a javascript redirect to the parent page with information about that iframe so things like scroll-bar placement can be achieved. Of course Search Engines ignore this javascript and then proceed to index the content.

This workaround is not a perfect solution, but since the iframe content can contain very relavent information, this is better than nothing. The other option would be to detect from the server end that the user requesting a page is really a crawl-bot and spit out all information, bypassing the iframes to get things like page rank to work correctly, but for times when you don’t have control over an iframes content, the previous solution works well.

Arquero says: January 16, 2008 @ 8:33 pm

The link ‘Page Description’ isn’t supposed to be a link, I didn’t know HTML wasn’t disabled for posts…

Here is the correct example:
<iframe src=”somepage.php”><a href=”somepage.php”>Short Description</a></iframe>

Posizionamento sui motori di ricerca: qualche consiglio - TomStardust.com says: December 10, 2008 @ 12:17 am

[...] descritte benissimo nel post SEU, Search Engine Useless su Standardzilla, che riassumo in [...]

Leave a Comment