Top quality web design, professional SEO internet Marketing optimization, content management, links campaigns, expecialized E-Marketing, PPC Pay Per Click campaigns, WebPro developments

Friday, April 21, 2006

Top Ten Mistakes in Web Design

1. Bad Search

Overly literal search engines reduce usability in that they're unable to handle typos, plurals, hyphens, and other variants of the query terms. Such search engines are particularly difficult for elderly usersbut they hurt everybody.
A related problem is when search engines prioritize results purely on the basis of how many query terms they contain, rather than on each document's importance. Much better if your search engine calls out "best bets" at the top of the list -- especially for important queries, such as the names of your products.
Search is the user's lifeline when navigation fails. Even though advanced search can sometimes help, simple search usually works best, and search should be presented as a simple box, since that's what users are looking for.


2. PDF Files for Online Reading

Users hate coming across a PDF file while browsing, because it breaks their flow. Even simple things like printing or saving documents are difficult because standard browser commands don't work. Layouts are often optimized for a sheet of paper, which rarely matches the size of the user's browser window. Bye-bye smooth scrolling. Hello tiny fonts.
Worst of all, PDF is an undifferentiated blob of content that's hard to navigate.
PDF is great for printing and for distributing manuals and other big documents that need to be printed. Reserve it for this purpose and convert any information that needs to be browsed or read on the screen into real web pages.


3. Not Changing the Color of Visited Links

A good grasp of past navigation helps you understand your current location, since it's the culmination of your journey. Knowing your past and present locations in turn makes it easier to decide where to go next. Links are a key factor in this navigation process. Users can exclude links that proved fruitless in their earlier visits. Conversely, they might revisit links they found helpful in the past.
Most important, knowing which pages they've already visited frees users from unintentionally revisiting the same pages over and over again.
These benefits only accrue under one important assumption: that users can tell the difference between visited and unvisited links because the site shows them in different colors. When visited links don't change color, users exhibit more navigational disorientation in usability testing and unintentionally revisit the same pages repeatedly.


4. Non-Scannable Text

A wall of text is deadly for an interactive experience. Intimidating. Boring. Painful to read.
Write for online, not print. To draw users into the text and support scannability, use well-documented tricks:
subheads
bulleted lists
highlighted keywords
short paragraphs
the inverted pyramid
a simple writing style, and
de-fluffed language devoid of marketese.


5. Fixed Font Size

CSS style sheets unfortunately give websites the power to disable a Web browser's "change font size" button and specify a fixed font size. About 95% of the time, this fixed size is tiny, reducing readability significantly for most people over the age of 40.
Respect the user's preferences and let them resize text as needed. Also, specify font sizes in relative terms -- not as an absolute number of pixels.


6. Page Titles With Low Search Engine Visibility

Search is the most important way users discover websites. Search is also one of the most important ways users find their way around individual websites. The humble page title is your main tool to attract new visitors from search listings and to help your existing users to locate the specific pages that they need.
The page title is contained within the HTML "tittle" tag and is almost always used as the clickable headline for listings on search engine result pages (SERP). Search engines typically show the first 66 characters or so of the title, so it's truly Page titles are also used as the default entry in the Favorites when users bookmark a site. For your homepage, begin the with the company name, followed by a brief description of the site. Don't start with words like "The" or "Welcome to" unless you want to be alphabetized under "T" or "W."
For other pages than the homepage, start the title with a few of the most salient information-carrying words that describe the specifics of what users will find on that page. Since the page title is used as the window title in the browser, it's also used as the label for that window in the taskbar under Windows, meaning that advanced users will move between multiple windows under the guidance of the first one or two words of each page title. If all your page titles start with the same words, you have severely reduced usability for your multi-windowing users.
Taglines on homepages are a related subject: they also need to be short and quickly communicate the purpose of the site.


7. Anything That Looks Like an Advertisement

Selective attention is very powerful, and Web users have learned to stop paying attention to any ads that get in the way of their goal-driven navigation. (The main exception being text-only search-engine ads.)
Unfortunately, users also ignore legitimate design elements that look like prevalent forms of advertising. After all, when you ignore something, you don't study it in detail to find out what it is.
Therefore, it is best to avoid any designs that look like advertisements. The exact implications of this guideline will vary with new forms of ads; currently follow these rules:
banner blindness means that users never fixate their eyes on anything that looks like a banner ad due to shape or position on the page
animation avoidance makes users ignore areas with blinking or flashing text or other aggressive animations
pop-up purges mean that users close pop-up windoids before they have even fully rendered; sometimes with great viciousness (a sort of getting-back-at-GeoCities triumph).


8. Violating Design Conventions

Consistency is one of the most powerful usability principles: when things always behave the same, users don't have to worry about what will happen. Instead, they know what will happen based on earlier experience. Every time you release an apple over Sir Isaac Newton, it will drop on his head. That's good.
The more users' expectations prove right, the more they will feel in control of the system and the more they will like it. And the more the system breaks users' expectations, the more they will feel insecure. Oops, maybe if I let go of this apple, it will turn into a tomato and jump a mile into the sky.
The Web User Experience states that "users spend most of their time on other websites."
This means that they form their expectations for your site based on what's commonly done on most other site. If you deviate, your site will be harder to use and users will leave.


9. Opening New Browser Windows

Opening up new browser windows is like a vacuum cleaner sales person who starts a visit by emptying an ash tray on the customer's carpet. Don't pollute my screen with any more windows, thanks (particularly since current operating systems have miserable window management).
Designers open new browser windows on the theory that it keeps users on their site. But even disregarding the user-hostile message implied in taking over the user's machine, the strategy is self-defeating since it disables the Back button which is the normal way users return to previous sites. Users often don't notice that a new window has opened, especially if they are using a small monitor where the windows are maximized to fill up the screen. So a user who tries to return to the origin will be confused by a grayed out Back button.
Links that don't behave as expected undermine users' understanding of their own system. A link should be a simple hypertext reference that replaces the current page with new content. Users hate unwarranted pop-up windows. When they want the destination to appear in a new page, they can use their browser's "open in new window" command -- assuming, of course, that the link is not a piece of code that interferes with the browser’s standard behavior.


10. Not Answering Users' Questions

Users are highly goal-driven on the Web. They visit sites because there's something they want to accomplish -- maybe even buy your product. The ultimate failure of a website is to fail to provide the information users are looking for.
Sometimes the answer is simply not there and you lose the sale because users have to assume that your product or service doesn't meet their needs if you don't tell them the specifics. Other times the specifics are buried under a thick layer of marketese and bland slogans. Since users don't have time to read everything, such hidden info might almost as well not be there.
The worst example of not answering users' questions is to avoid listing the price of products and services. No B2C ecommerce site would make this mistake, but it's rife in B2B, where most "enterprise solutions" are presented so that you can't tell whether they are suited for 100 people or 100,000 people. Price is the most specific piece of info customers use to understand the nature of an offering, and not providing it makes people feel lost and reduces their understanding of a product line. We have miles of videotape of users asking "Where's the price?" while tearing their hair out.
Even B2C sites often make the associated mistake of forgetting prices in product lists, such as category pages or search results. Knowing the price is key in both situations; it lets users differentiate among products and click through to the most relevant ones.

Thursday, February 23, 2006

Database of Web Robots


Database of Web Robots, Overview




  1. ABCdatos BotLink
  2. Acme.Spider
  3. Ahoy! The Homepage Finder
  4. Alkaline
  5. Anthill
  6. Walhello appie
  7. Arachnophilia
  8. Arale
  9. Araneo
  10. AraybOt
  11. ArchitextSpider
  12. Aretha
  13. ARIADNE
  14. Arks
  15. ASpider (Associative Spider)
  16. ATN Worldwide
  17. Atomz.com Search Robot
  18. AURESYS
  19. BackRub
  20. Unnamed
  21. BBot
  22. Big Brother
  23. Bjaaland
  24. BlackWidow
  25. Die Blinde Kuh
  26. Bloodhound
  27. Borg-Bot
  28. BoxSeaBot
  29. bright.net caching robot
  30. BSpider
  31. CACTVS Chemistry Spider
  32. Calif
  33. Cassandra
  34. Digimarc Marcspider/CGI
  35. Checkbot
  36. ChristCrawler.com
  37. churl
  38. cIeNcIaFiCcIoN.nEt
  39. CMC/0.01
  40. Collective
  41. Combine System
  42. ConfuzzledBot
  43. CoolBot
  44. Web Core / Roots
  45. XYLEME Robot
  46. Internet Cruiser Robot
  47. Cusco
  48. CyberSpyder Link Test
  49. CydralSpider
  50. Desert Realm Spider
  51. DeWeb(c) Katalog/Index
  52. DienstSpider
  53. Digger
  54. Digital Integrity Robot
  55. Direct Hit Grabber
  56. DNAbot
  57. DownLoad Express
  58. DragonBot
  59. DWCP (Dridus' Web Cataloging Project)
  60. e-collector
  61. EbiNess
  62. EIT Link Verifier Robot
  63. ELFINBOT
  64. Emacs-w3 Search Engine
  65. ananzi
  66. esculapio
  67. Esther
  68. Evliya Celebi
  69. nzexplorer
  70. FastCrawler
  71. Fluid Dynamics Search Engine robot
  72. Felix IDE
  73. Wild Ferret Web Hopper #1, #2, #3
  74. FetchRover
  75. fido
  76. Hämähäkki
  77. KIT-Fireball
  78. Fish search
  79. Fouineur
  80. Robot Francoroute
  81. Freecrawl
  82. FunnelWeb
  83. gammaSpider, FocusedCrawler
  84. gazz
  85. GCreep
  86. GetBot
  87. GetURL
  88. Golem
  89. Googlebot
  90. Grapnel/0.01 Experiment
  91. Griffon
  92. Gromit
  93. Northern Light Gulliver
  94. Gulper Bot
  95. HamBot
  96. Harvest
  97. havIndex
  98. HI (HTML Index) Search
  99. Hometown Spider Pro
  100. Wired Digital
  101. ht://Dig
  102. HTMLgobble
  103. Hyper-Decontextualizer
  104. iajaBot
  105. IBM_Planetwide
  106. Popular Iconoclast
  107. Ingrid
  108. Imagelock
  109. IncyWincy
  110. Informant
  111. InfoSeek Robot 1.0
  112. Infoseek Sidewinder
  113. InfoSpiders
  114. Inspector Web
  115. IntelliAgent
  116. I, Robot
  117. Iron33
  118. Israeli-search
  119. JavaBee
  120. JBot Java Web Robot
  121. JCrawler
  122. AskJeeves
  123. JoBo Java Web Robot
  124. Jobot
  125. JoeBot
  126. The Jubii Indexing Robot
  127. JumpStation
  128. image.kapsi.net
  129. Katipo
  130. KDD-Explorer
  131. Kilroy
  132. KO_Yappo_Robot
  133. LabelGrabber
  134. larbin
  135. legs
  136. Link Validator
  137. LinkScan
  138. LinkWalker
  139. Lockon
  140. logo.gif Crawler
  141. Lycos
  142. Mac WWWWorm
  143. Magpie
  144. marvin/infoseek
  145. Mattie
  146. MediaFox
  147. MerzScope
  148. NEC-MeshExplorer
  149. MindCrawler
  150. mnoGoSearch search engine software
  151. moget
  152. MOMspider
  153. Monster
  154. Motor
  155. MSNBot
  156. Muncher
  157. Muninn
  158. Muscat Ferret
  159. Mwd.Search
  160. Internet Shinchakubin
  161. NDSpider
  162. NetCarta WebMap Engine
  163. NetMechanic
  164. NetScoop
  165. newscan-online
  166. NHSE Web Forager
  167. Nomad
  168. The NorthStar Robot
  169. ObjectsSearch
  170. Occam
  171. HKU WWW Octopus
  172. OntoSpider
  173. Openfind data gatherer
  174. Orb Search
  175. Pack Rat
  176. PageBoy
  177. ParaSite
  178. Patric
  179. pegasus
  180. The Peregrinator
  181. PerlCrawler 1.0
  182. Phantom
  183. PhpDig
  184. PiltdownMan
  185. Pimptrain.com's robot
  186. Pioneer
  187. html_analyzer
  188. Portal Juice Spider
  189. PGP Key Agent
  190. PlumtreeWebAccessor
  191. Poppi
  192. PortalB Spider
  193. psbot
  194. GetterroboPlus Puu
  195. The Python Robot
  196. Raven Search
  197. RBSE Spider
  198. Resume Robot
  199. RoadHouse Crawling System
  200. RixBot
  201. Road Runner: The ImageScape Robot
  202. Robbie the Robot
  203. ComputingSite Robi/1.0
  204. RoboCrawl Spider
  205. RoboFox
  206. Robozilla
  207. Roverbot
  208. RuLeS
  209. SafetyNet Robot
  210. Scooter
  211. Search.Aus-AU.COM
  212. Sleek
  213. SearchProcess
  214. Senrigan
  215. SG-Scout
  216. ShagSeeker
  217. Shai'Hulud
  218. Sift
  219. Simmany Robot Ver1.0
  220. Site Valet
  221. SiteTech-Rover
  222. Skymob.com
  223. SLCrawler
  224. Inktomi Slurp
  225. Smart Spider
  226. Snooper
  227. Solbot
  228. Speedy Spider
  229. spider_monkey
  230. SpiderBot
  231. Spiderline Crawler
  232. SpiderMan
  233. SpiderView(tm)
  234. Spry Wizard Robot
  235. Site Searcher
  236. Suke
  237. suntek search engine
  238. Sven
  239. Sygol
  240. TACH Black Widow
  241. Tarantula
  242. tarspider
  243. Tcl W3 Robot
  244. TechBOT
  245. Templeton
  246. TitIn
  247. TITAN
  248. The TkWWW Robot
  249. TLSpider
  250. UCSD Crawl
  251. UdmSearch
  252. UptimeBot
  253. URL Check
  254. URL Spider Pro
  255. Valkyrie
  256. Verticrawl
  257. Victoria
  258. vision-search
  259. void-bot
  260. Voyager
  261. VWbot
  262. The NWI Robot
  263. W3M2
  264. WallPaper (alias crawlpaper)
  265. the World Wide Web Wanderer
  266. w@pSpider by wap4.com
  267. WebBandit Web Spider
  268. WebCatcher
  269. WebCopy
  270. webfetcher
  271. The Webfoot Robot
  272. Webinator
  273. weblayers
  274. WebLinker
  275. WebMirror
  276. The Web Moose
  277. WebQuest
  278. Digimarc MarcSpider
  279. WebReaper
  280. webs
  281. Websnarf
  282. WebSpider
  283. WebVac
  284. webwalk
  285. WebWalker
  286. WebWatch
  287. Wget
  288. whatUseek Winona
  289. WhoWhere Robot
  290. Weblog Monitor
  291. w3mir
  292. WebStolperer
  293. The Web Wombat
  294. The World Wide Web Worm
  295. WWWC Ver 0.2.5
  296. WebZinger
  297. XGET
  298. Nederland.zoek

    Nine things you can do to make your web site better

    1 Conceive, design and organize your site to be exactly what it is: a web site. -
    The Web is not print. While this may seem like an overtly obvious statement, designers, programmers and users trip up on this very issue every day. It's a common misconception, which branches off to notions like "a site author can control how a site looks to the pixel" and "a well-written web page will look exactly the same on all browsers." Let go of these ideas from the very start. Accessing a web site is a client-server interaction which varies in ways dependent upon several variables, not the least of which include connection speeds and client hardware, software and configuration.

    So, as you make decisions about your site, carefully consider and exploit the medium. Make no assumptions about the user, because a dizzying array of configurable clients can access your site. Not everyone has Javascript and cookies enabled, or is sitting in front of that great 22-inch monitor that you are, or is using IE on Windows. Accept that your "pages" will not look exactly the same to everyone. Remember that search engines will run indexing software on your site and this software only understands text (for now). Don't focus on visual design, concentrate on making your site as usable as possible. Users should be able access your site quickly and intuitively and even bookmark (a misnomer that points back to the Web=print misconception) specific documents on it; so go nuts and facilitate this.

    The rest of these recommendations aim to help achieve this end.

    2 - Validate your markup.
    There are rules which specify how to create documents renderable by web clients. Follow them. Markup is either correctly written or it's not. If you're using pure CSS and XHTML or just plain ol' HTML, make sure your markup is correctly written by using a validator: software which checks markup for mistakes. This one and this one work just fine. If your markup is valid it has the best chance of rendering on the widest array of clients. If you have invalid markup, don't assume that just because your browser is forgiving that everyone else's is.

    3 - Avoid frames and splash pages.
    Frames on a web site are not ideal for lots of reasons. Frames prevent the user from being able to bookmark individual documents on a site. They present related information in separate documents, which keeps search engines from associating related information. They require that a browser make more than one document request per document, which increases client-server connections and eats server CPU cycles, network bandwidth and users' time. Frames are also, coincidentally, being deprecated.

    When I say "splash page", I am referring to a welcome page with one link on it to "enter" the site. Splash pages are unnecessary and meaningless. The first time a user goes to your site, it might seem like a nice effect. But every time after that, a splash page just gets in the way. For a search engine it makes the bulk of your site another needless step into the hierarchy. Don't make users, robots and your server work harder than necessary to deliver the content on your site.

    4 - Optimize your site to be as small a download as possible.
    Making a user wait for your site to download is the best way to get him or her to go elsewhere. While creating your site, remember that more than half the web surfers in the US in February of 2003 used a 56k or less dial-up connection. Entire books and web sites are dedicated to the subject of how to optimize a site, so I won't even attempt to cover the subject here.

    5 - Make your site URLs as short, descriptive, static, technology-inspecific and permanent as possible.
    Remember that your site's navigation URLs can be totally independent of the physical file system on your server. What I mean is, if you have a

    /about_this_site/index.htmlfile on your server, the URL to the about section does not have to be (and should not be)
    /about_this_site/index.htmlDecide on your site URL structure before you begin creating the documents which will present the information. Make them as short and descriptive of the content as possible, and avoid any indicators of the technology behind them. Avoid file extensions (like .php, .htm, .html, .asp) and don't expose query string parameters. Google specifically recommends using "static" (querystring-less) links to every document on your site. For example, if you have a section which describes the staff of a company, don't use
    /staff.htmlto point to the staff page. Use
    /staff/instead. Then use
    /staff/joesmith/for Joe Smith's page, instead of
    /staff.asp?firstname=joe&lastname=smithOnce you've determined the URLs for your site, use server-side technology to make them work.

    Finally, once you create a URL which points to a section on your site, stick to it. If you follow these suggestions from the start and then re-organize your site, your URLs don't have to change. However, if you absolutely must change a URL, make sure the original URL redirects or points to the new section, so that cached search engine referrals and bookmarks still work.

    6 - Make the information on your site textual, and offer non-Javascript-dependent navigation.
    Images on a web document, while meaningful to human eyes, are actually just a collection of 1's and 0's to search engine indexing software and non-graphical browsers. Make sure all of the information on your site exists in a text format. For example, if your site has a masthead which is an image that contains the title of your site in it, make sure you set the alt attribute to describe the content of the image. You should even ensure that the most relevant information on a page appears first in your markup, and make other elements (navigation, etc) follow.

    Short of installing a text browser like Lynx, a good test to see what your site looks like to an indexing robot or a non-graphical browser is to turn off images in your browser. If you're using Internet Explorer, to do this, in the Tools menu choose Options, and on the Advanced tab go to Multimedia, and uncheck "Show pictures." In Mozilla, go to Tools, Image Manager, and choose "Block Images from this Site." Then view your site, and make sure that without images, all information is adequately represented. This same concept applies to all objects (like Flash movies and Java applets.)

    Additionally, remember that search engine robots do not execute Javascript. If any navigation elements on your site use Javascript, set the onclick attribute of the a element to the Javascript call, and the href attribute to the destination of the link. This way Javascript-enabled browsers will execute the script, and the link will still be usable to non-Javascript-enabled clients.

    7 - Actively direct search engine indexing robots.
    Search engine robots want instructions on how to correctly index your site, so give 'em to 'em. Read up on search engine guidelines and features (like caching site text and image search). Determine how and what areas of your site should be indexed. The use of meta tags and the robots.txt file are the most common methods of directing robots to your content. Use this robots.txt validator to ensure your robots.txt file is correct.

    For example, Google has been Scribbling.net's biggest referrer since day one, but I noticed that often users from Google would land on pages that weren't the most relevant to their search terms. So I checked out how the Googlebot indexes sites. I wanted robots to index only the permanent locations of posts, but not the front page (as it constantly changes to show the latest post). I don't want any of the images or text cached and presented out of context. I also have a page or two that I don't want anyone to find via a search at all. So here's my robots.txt file which lays out some of these instructions. Additionally, the robots meta tags on my front page say "noindex,follow,noarchive", which effectively tells robots to follow links but not to index or archive the front page. The same tag on any post page says "index,follow,noarchive" which tells robots to index the content on that page but not to archive it.

    This way, if the day the Googlebot indexes my site is the day I have a post on the front page about a dog, with a link to the dog post's permanent URL, the Googlebot will index only the permanent location of the dog post. Four days later, when my front page has a post on it about a cat, and someone searches for site:scribbling.net dog, the only pages returned should be the dog post (and any associated documents) and not the front page.

    8 - Serve "friendly" error messages.
    The most unhelpful, dead-end message you can get from a web server is:

    404 Not Found The web server cannot find the file or script you asked for. Please check the URL to ensure that the path is correct. Please contact the server's administrator if this problem persists. A usable web site does a lot better than that. Hook up friendly error messages which include navigation to documents that do exist or don't throw an error, a search box and/or a contact email address. Get creative.

    9 - Don't "click here."
    I think I've already said enough about this.

    Happy Blogging

    Meta Tags Keywords in Diferent Languages

    A common use for META is to specify keywords that a search engine may use to improve the quality of search results. When several META elements provide language-dependent information about a document, search engines may filter on the lang attribute to display search results using the language preferences of the user. For example:

    <-- For speakers of US English -->
    "<"meta lang="" name="keywords">en-us" content="vacation, Greece, sunshine">

    <-- For speakers of British English -->
    "<"meta lang="" name="keywords">en" content="holiday, Greece, sunshine">

    <-- For speakers of French -->
    "<"meta lang="" name="keywords">fr" content="vacances, Greece, soleil">

    <-- For speakers of Portuguese -->
    "<"meta lang="pt" " content="ferias, Grecia, sol" name="keywords">

    Happy Blogging

    Wednesday, February 22, 2006

    Blogging

    A blog is a personal journal that is kept on a website for everyone to read. Traditionally a blog contains personal writings and links to other websites or blogs. I am no expert on blogs, but I am interested in them.
    Blogging is what you do to create a blog. Blogger is what you are when you have a blog. The term blog comes from “web log”.