<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<?xml-stylesheet href="http://www.blogger.com/styles/atom.css" type="text/css"?>

<feed xmlns="http://purl.org/atom/ns#" version="0.3" xml:lang="en-US">
<link href="https://www.blogger.com/atom/22858567" rel="service.post" title="WebPro Web Designs Solutions" type="application/atom+xml"/>
<link href="https://www.blogger.com/atom/22858567" rel="service.feed" title="WebPro Web Designs Solutions" type="application/atom+xml"/>
<title mode="escaped" type="text/html">WebPro Web Designs Solutions</title>
<tagline mode="escaped" type="text/html">Top quality web design, professional SEO internet Marketing optimization, content management, links campaigns, expecialized E-Marketing, PPC Pay Per Click campaigns, WebPro developments
<a href="http://www.webpro-designs.com">Webpro Solutions</a> 
</tagline>
<link href="http://www.webpro-designs.com/blogger/blogger.htm" rel="alternate" title="WebPro Web Designs Solutions" type="text/html"/>
<id>tag:blogger.com,1999:blog-22858567</id>
<modified>2006-04-21T16:43:10Z</modified>
<generator url="http://www.blogger.com/" version="6.72">Blogger</generator>
<info mode="xml" type="text/html">
<div xmlns="http://www.w3.org/1999/xhtml">This is an Atom formatted XML site feed. It is intended to be viewed in a Newsreader or syndicated to another site. Please visit the <a href="http://help.blogger.com/bin/answer.py?answer=697">Blogger Help</a> for more info.</div>
<div xmlns="http://www.w3.org/1999/xhtml">Powered by WebPro Solutions</div>
<div xmlns="http://www.w3.org/1999/xhtml"><a href="http://www.webpro-designs.com">WebPro Designs</a> and <a href="http://www.webpro-designgrafico.com">WebPro DesignGrafico</a>.</div>
</info>
<convertLineBreaks xmlns="http://www.blogger.com/atom/ns#">true</convertLineBreaks>
<entry xmlns="http://purl.org/atom/ns#">
<link href="https://www.blogger.com/atom/22858567/114563532541886579" rel="service.edit" title="Top Ten Mistakes in Web Design" type="application/atom+xml"/>
<link href="http://www.webpro-designs.com" rel="related" title="Top Ten Mistakes in Web Design" type="text/html"/>
<author>
<name>WebPro Designs</name>
</author>
<issued>2006-04-21T16:46:00+01:00</issued>
<modified>2006-04-21T16:09:05Z</modified>
<created>2006-04-21T16:02:05Z</created>
<link href="http://www.webpro-designs.com/blogger/2006/04/top-ten-mistakes-in-web-design.htm" rel="alternate" title="Top Ten Mistakes in Web Design" type="text/html"/>
<id>tag:blogger.com,1999:blog-22858567.post-114563532541886579</id>
<title mode="escaped" type="text/html">Top Ten Mistakes in Web Design</title>
<content mode="escaped" type="text/html" xml:base="http://www.webpro-designs.com/blogger/blogger.htm" xml:space="preserve">&lt;strong&gt;&lt;span style="font-size:130%;"&gt;1. Bad Search&lt;/span&gt;&lt;/strong&gt;&lt;br /&gt;&lt;br /&gt;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.&lt;br /&gt;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.&lt;br /&gt;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.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;strong&gt;&lt;span style="font-size:130%;"&gt;2. PDF Files for Online Reading&lt;/span&gt;&lt;/strong&gt;&lt;br /&gt;&lt;br /&gt;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.&lt;br /&gt;Worst of all, PDF is an undifferentiated blob of content that's hard to navigate.&lt;br /&gt;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.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;strong&gt;&lt;span style="font-size:130%;"&gt;3. Not Changing the Color of Visited Links&lt;/span&gt;&lt;/strong&gt;&lt;br /&gt;&lt;br /&gt;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.&lt;br /&gt;Most important, knowing which pages they've already visited frees users from unintentionally revisiting the same pages over and over again.&lt;br /&gt;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.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;strong&gt;&lt;span style="font-size:130%;"&gt;4. Non-Scannable Text&lt;/span&gt;&lt;/strong&gt;&lt;br /&gt;&lt;br /&gt;A wall of text is deadly for an interactive experience. Intimidating. Boring. Painful to read.&lt;br /&gt;Write for online, not print. To draw users into the text and support scannability, use well-documented tricks:&lt;br /&gt;subheads&lt;br /&gt;bulleted lists&lt;br /&gt;highlighted keywords&lt;br /&gt;short paragraphs&lt;br /&gt;the inverted pyramid&lt;br /&gt;a simple writing style, and&lt;br /&gt;de-fluffed language devoid of marketese.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;strong&gt;&lt;span style="font-size:130%;"&gt;5. Fixed Font Size&lt;/span&gt;&lt;/strong&gt;&lt;br /&gt;&lt;br /&gt;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.&lt;br /&gt;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.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;span style="font-size:130%;"&gt;&lt;strong&gt;6.&lt;/strong&gt;&lt;/span&gt; &lt;strong&gt;Page Titles With Low Search Engine Visibility&lt;/strong&gt;&lt;br /&gt;&lt;br /&gt;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.&lt;br /&gt;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 &lt;microcontent.&lt;br /&gt;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."&lt;br /&gt;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.&lt;br /&gt;Taglines on homepages are a related subject: they also need to be short and quickly communicate the purpose of the site.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;strong&gt;&lt;span style="font-size:130%;"&gt;7. Anything That Looks Like an Advertisement&lt;/span&gt;&lt;/strong&gt;&lt;br /&gt;&lt;br /&gt;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.)&lt;br /&gt;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.&lt;br /&gt;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:&lt;br /&gt;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&lt;br /&gt;animation avoidance makes users ignore areas with blinking or flashing text or other aggressive animations&lt;br /&gt;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).&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;strong&gt;&lt;span style="font-size:130%;"&gt;8. Violating Design Conventions&lt;/span&gt;&lt;/strong&gt;&lt;br /&gt;&lt;br /&gt;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.&lt;br /&gt;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.&lt;br /&gt;The Web User Experience states that "users spend most of their time on other websites."&lt;br /&gt;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.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;strong&gt;&lt;span style="font-size:130%;"&gt;9. Opening New Browser Windows&lt;/span&gt;&lt;/strong&gt;&lt;br /&gt;&lt;br /&gt;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).&lt;br /&gt;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.&lt;br /&gt;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.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;strong&gt;&lt;span style="font-size:130%;"&gt;10. Not Answering Users' Questions&lt;/span&gt;&lt;/strong&gt;&lt;br /&gt;&lt;br /&gt;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.&lt;br /&gt;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.&lt;br /&gt;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.&lt;br /&gt;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.</content>
<draft xmlns="http://purl.org/atom-blog/ns#">false</draft>
</entry>
<entry xmlns="http://purl.org/atom/ns#">
<link href="https://www.blogger.com/atom/22858567/114069552267983486" rel="service.edit" title="Database of Web Robots" type="application/atom+xml"/>
<author>
<name>WebPro Designs</name>
</author>
<issued>2006-02-23T11:49:00+00:00</issued>
<modified>2006-04-21T16:43:10Z</modified>
<created>2006-02-23T11:52:02Z</created>
<link href="http://www.webpro-designs.com/blogger/2006/02/database-of-web-robots.htm" rel="alternate" title="Database of Web Robots" type="text/html"/>
<id>tag:blogger.com,1999:blog-22858567.post-114069552267983486</id>
<title mode="escaped" type="text/html">Database of Web Robots</title>
<content mode="escaped" type="text/html" xml:base="http://www.webpro-designs.com/blogger/blogger.htm" xml:space="preserve">&lt;h1 align="center"&gt;&lt;br /&gt;Database of Web Robots, Overview&lt;br /&gt;&lt;/h1&gt;&lt;br /&gt;&lt;p&gt;&lt;br /&gt;&lt;ol&gt;&lt;br /&gt;&lt;li&gt;ABCdatos BotLink&lt;br /&gt;&lt;li&gt;Acme.Spider&lt;br /&gt;&lt;li&gt;Ahoy! The Homepage Finder&lt;br /&gt;&lt;li&gt;Alkaline&lt;br /&gt;&lt;li&gt;Anthill&lt;br /&gt;&lt;li&gt;Walhello appie&lt;br /&gt;&lt;li&gt;Arachnophilia&lt;br /&gt;&lt;li&gt;Arale&lt;br /&gt;&lt;li&gt;Araneo&lt;br /&gt;&lt;li&gt;AraybOt&lt;br /&gt;&lt;li&gt;ArchitextSpider&lt;br /&gt;&lt;li&gt;Aretha&lt;br /&gt;&lt;li&gt;ARIADNE&lt;br /&gt;&lt;li&gt;Arks&lt;br /&gt;&lt;li&gt;ASpider (Associative Spider)&lt;br /&gt;&lt;li&gt;ATN Worldwide&lt;br /&gt;&lt;li&gt;Atomz.com Search Robot&lt;br /&gt;&lt;li&gt;AURESYS&lt;br /&gt;&lt;li&gt;BackRub&lt;br /&gt;&lt;li&gt;Unnamed&lt;br /&gt;&lt;li&gt;BBot&lt;br /&gt;&lt;li&gt;Big Brother&lt;br /&gt;&lt;li&gt;Bjaaland&lt;br /&gt;&lt;li&gt;BlackWidow&lt;br /&gt;&lt;li&gt;Die Blinde Kuh&lt;br /&gt;&lt;li&gt;Bloodhound&lt;br /&gt;&lt;li&gt;Borg-Bot&lt;br /&gt;&lt;li&gt;BoxSeaBot&lt;br /&gt;&lt;li&gt;bright.net caching robot&lt;br /&gt;&lt;li&gt;BSpider&lt;br /&gt;&lt;li&gt;CACTVS Chemistry Spider&lt;br /&gt;&lt;li&gt;Calif&lt;br /&gt;&lt;li&gt;Cassandra&lt;br /&gt;&lt;li&gt;Digimarc Marcspider/CGI&lt;br /&gt;&lt;li&gt;Checkbot&lt;br /&gt;&lt;li&gt;ChristCrawler.com&lt;br /&gt;&lt;li&gt;churl&lt;br /&gt;&lt;li&gt;cIeNcIaFiCcIoN.nEt&lt;br /&gt;&lt;li&gt;CMC/0.01&lt;br /&gt;&lt;li&gt;Collective&lt;br /&gt;&lt;li&gt;Combine System&lt;br /&gt;&lt;li&gt;ConfuzzledBot&lt;br /&gt;&lt;li&gt;CoolBot&lt;br /&gt;&lt;li&gt;Web Core / Roots&lt;br /&gt;&lt;li&gt;XYLEME Robot&lt;br /&gt;&lt;li&gt;Internet Cruiser Robot&lt;br /&gt;&lt;li&gt;Cusco&lt;br /&gt;&lt;li&gt;CyberSpyder Link Test&lt;br /&gt;&lt;li&gt;CydralSpider&lt;br /&gt;&lt;li&gt;Desert Realm Spider&lt;br /&gt;&lt;li&gt;DeWeb(c) Katalog/Index&lt;br /&gt;&lt;li&gt;DienstSpider&lt;br /&gt;&lt;li&gt;Digger&lt;br /&gt;&lt;li&gt;Digital Integrity Robot&lt;br /&gt;&lt;li&gt;Direct Hit Grabber&lt;br /&gt;&lt;li&gt;DNAbot&lt;br /&gt;&lt;li&gt;DownLoad Express&lt;br /&gt;&lt;li&gt;DragonBot&lt;br /&gt;&lt;li&gt;DWCP (Dridus' Web Cataloging Project)&lt;br /&gt;&lt;li&gt;e-collector&lt;br /&gt;&lt;li&gt;EbiNess&lt;br /&gt;&lt;li&gt;EIT Link Verifier Robot&lt;br /&gt;&lt;li&gt;ELFINBOT&lt;br /&gt;&lt;li&gt;Emacs-w3 Search Engine&lt;br /&gt;&lt;li&gt;ananzi&lt;br /&gt;&lt;li&gt;esculapio&lt;br /&gt;&lt;li&gt;Esther&lt;br /&gt;&lt;li&gt;Evliya Celebi&lt;br /&gt;&lt;li&gt;nzexplorer&lt;br /&gt;&lt;li&gt;FastCrawler&lt;br /&gt;&lt;li&gt;Fluid Dynamics Search Engine robot&lt;br /&gt;&lt;li&gt;Felix IDE&lt;br /&gt;&lt;li&gt;Wild Ferret Web Hopper #1, #2, #3&lt;br /&gt;&lt;li&gt;FetchRover&lt;br /&gt;&lt;li&gt;fido&lt;br /&gt;&lt;li&gt;Hämähäkki&lt;br /&gt;&lt;li&gt;KIT-Fireball&lt;br /&gt;&lt;li&gt;Fish search&lt;br /&gt;&lt;li&gt;Fouineur&lt;br /&gt;&lt;li&gt;Robot Francoroute&lt;br /&gt;&lt;li&gt;Freecrawl&lt;br /&gt;&lt;li&gt;FunnelWeb&lt;br /&gt;&lt;li&gt;gammaSpider, FocusedCrawler&lt;br /&gt;&lt;li&gt;gazz&lt;br /&gt;&lt;li&gt;GCreep&lt;br /&gt;&lt;li&gt;GetBot&lt;br /&gt;&lt;li&gt;GetURL&lt;br /&gt;&lt;li&gt;Golem&lt;br /&gt;&lt;li&gt;Googlebot&lt;br /&gt;&lt;li&gt;Grapnel/0.01 Experiment&lt;br /&gt;&lt;li&gt;Griffon&lt;br /&gt;&lt;li&gt;Gromit&lt;br /&gt;&lt;li&gt;Northern Light Gulliver&lt;br /&gt;&lt;li&gt;Gulper Bot&lt;br /&gt;&lt;li&gt;HamBot&lt;br /&gt;&lt;li&gt;Harvest&lt;br /&gt;&lt;li&gt;havIndex&lt;br /&gt;&lt;li&gt;HI (HTML Index) Search&lt;br /&gt;&lt;li&gt;Hometown Spider Pro&lt;br /&gt;&lt;li&gt;Wired Digital&lt;br /&gt;&lt;li&gt;ht://Dig&lt;br /&gt;&lt;li&gt;HTMLgobble&lt;br /&gt;&lt;li&gt;Hyper-Decontextualizer&lt;br /&gt;&lt;li&gt;iajaBot&lt;br /&gt;&lt;li&gt;IBM_Planetwide&lt;br /&gt;&lt;li&gt;Popular Iconoclast&lt;br /&gt;&lt;li&gt;Ingrid&lt;br /&gt;&lt;li&gt;Imagelock&lt;br /&gt;&lt;li&gt;IncyWincy&lt;br /&gt;&lt;li&gt;Informant&lt;br /&gt;&lt;li&gt;InfoSeek Robot 1.0&lt;br /&gt;&lt;li&gt;Infoseek Sidewinder&lt;br /&gt;&lt;li&gt;InfoSpiders&lt;br /&gt;&lt;li&gt;Inspector Web&lt;br /&gt;&lt;li&gt;IntelliAgent&lt;br /&gt;&lt;li&gt;I, Robot&lt;br /&gt;&lt;li&gt;Iron33&lt;br /&gt;&lt;li&gt;Israeli-search&lt;br /&gt;&lt;li&gt;JavaBee&lt;br /&gt;&lt;li&gt;JBot Java Web Robot&lt;br /&gt;&lt;li&gt;JCrawler&lt;br /&gt;&lt;li&gt;AskJeeves&lt;br /&gt;&lt;li&gt;JoBo Java Web Robot&lt;br /&gt;&lt;li&gt;Jobot&lt;br /&gt;&lt;li&gt;JoeBot&lt;br /&gt;&lt;li&gt;The Jubii Indexing Robot&lt;br /&gt;&lt;li&gt;JumpStation&lt;br /&gt;&lt;li&gt;image.kapsi.net&lt;br /&gt;&lt;li&gt;Katipo&lt;br /&gt;&lt;li&gt;KDD-Explorer&lt;br /&gt;&lt;li&gt;Kilroy&lt;br /&gt;&lt;li&gt;KO_Yappo_Robot&lt;br /&gt;&lt;li&gt;LabelGrabber&lt;br /&gt;&lt;li&gt;larbin&lt;br /&gt;&lt;li&gt;legs&lt;br /&gt;&lt;li&gt;Link Validator&lt;br /&gt;&lt;li&gt;LinkScan&lt;br /&gt;&lt;li&gt;LinkWalker&lt;br /&gt;&lt;li&gt;Lockon&lt;br /&gt;&lt;li&gt;logo.gif Crawler&lt;br /&gt;&lt;li&gt;Lycos&lt;br /&gt;&lt;li&gt;Mac WWWWorm&lt;br /&gt;&lt;li&gt;Magpie&lt;br /&gt;&lt;li&gt;marvin/infoseek&lt;br /&gt;&lt;li&gt;Mattie&lt;br /&gt;&lt;li&gt;MediaFox&lt;br /&gt;&lt;li&gt;MerzScope&lt;br /&gt;&lt;li&gt;NEC-MeshExplorer&lt;br /&gt;&lt;li&gt;MindCrawler&lt;br /&gt;&lt;li&gt;mnoGoSearch search engine software&lt;br /&gt;&lt;li&gt;moget&lt;br /&gt;&lt;li&gt;MOMspider&lt;br /&gt;&lt;li&gt;Monster&lt;br /&gt;&lt;li&gt;Motor&lt;br /&gt;&lt;li&gt;MSNBot&lt;br /&gt;&lt;li&gt;Muncher&lt;br /&gt;&lt;li&gt;Muninn&lt;br /&gt;&lt;li&gt;Muscat Ferret&lt;br /&gt;&lt;li&gt;Mwd.Search&lt;br /&gt;&lt;li&gt;Internet Shinchakubin&lt;br /&gt;&lt;li&gt;NDSpider&lt;br /&gt;&lt;li&gt;NetCarta WebMap Engine&lt;br /&gt;&lt;li&gt;NetMechanic&lt;br /&gt;&lt;li&gt;NetScoop&lt;br /&gt;&lt;li&gt;newscan-online&lt;br /&gt;&lt;li&gt;NHSE Web Forager&lt;br /&gt;&lt;li&gt;Nomad&lt;br /&gt;&lt;li&gt;The NorthStar Robot&lt;br /&gt;&lt;li&gt;ObjectsSearch&lt;br /&gt;&lt;li&gt;Occam&lt;br /&gt;&lt;li&gt;HKU WWW Octopus&lt;br /&gt;&lt;li&gt;OntoSpider&lt;br /&gt;&lt;li&gt;Openfind data gatherer&lt;br /&gt;&lt;li&gt;Orb Search&lt;br /&gt;&lt;li&gt;Pack Rat&lt;br /&gt;&lt;li&gt;PageBoy&lt;br /&gt;&lt;li&gt;ParaSite&lt;br /&gt;&lt;li&gt;Patric&lt;br /&gt;&lt;li&gt;pegasus&lt;br /&gt;&lt;li&gt;The Peregrinator&lt;br /&gt;&lt;li&gt;PerlCrawler 1.0&lt;br /&gt;&lt;li&gt;Phantom&lt;br /&gt;&lt;li&gt;PhpDig&lt;br /&gt;&lt;li&gt;PiltdownMan&lt;br /&gt;&lt;li&gt;Pimptrain.com's robot&lt;br /&gt;&lt;li&gt;Pioneer&lt;br /&gt;&lt;li&gt;html_analyzer&lt;br /&gt;&lt;li&gt;Portal Juice Spider&lt;br /&gt;&lt;li&gt;PGP Key Agent&lt;br /&gt;&lt;li&gt;PlumtreeWebAccessor&lt;br /&gt;&lt;li&gt;Poppi&lt;br /&gt;&lt;li&gt;PortalB Spider&lt;br /&gt;&lt;li&gt;psbot&lt;br /&gt;&lt;li&gt;GetterroboPlus Puu&lt;br /&gt;&lt;li&gt;The Python Robot&lt;br /&gt;&lt;li&gt;Raven Search&lt;br /&gt;&lt;li&gt;RBSE Spider&lt;br /&gt;&lt;li&gt;Resume Robot&lt;br /&gt;&lt;li&gt;RoadHouse Crawling System&lt;br /&gt;&lt;li&gt;RixBot&lt;br /&gt;&lt;li&gt;Road Runner: The ImageScape Robot&lt;br /&gt;&lt;li&gt;Robbie the Robot&lt;br /&gt;&lt;li&gt;ComputingSite Robi/1.0&lt;br /&gt;&lt;li&gt;RoboCrawl Spider&lt;br /&gt;&lt;li&gt;RoboFox&lt;br /&gt;&lt;li&gt;Robozilla&lt;br /&gt;&lt;li&gt;Roverbot&lt;br /&gt;&lt;li&gt;RuLeS&lt;br /&gt;&lt;li&gt;SafetyNet Robot&lt;br /&gt;&lt;li&gt;Scooter&lt;br /&gt;&lt;li&gt;Search.Aus-AU.COM&lt;br /&gt;&lt;li&gt;Sleek&lt;br /&gt;&lt;li&gt;SearchProcess&lt;br /&gt;&lt;li&gt;Senrigan&lt;br /&gt;&lt;li&gt;SG-Scout&lt;br /&gt;&lt;li&gt;ShagSeeker&lt;br /&gt;&lt;li&gt;Shai'Hulud&lt;br /&gt;&lt;li&gt;Sift&lt;br /&gt;&lt;li&gt;Simmany Robot Ver1.0&lt;br /&gt;&lt;li&gt;Site Valet&lt;br /&gt;&lt;li&gt;SiteTech-Rover&lt;br /&gt;&lt;li&gt;Skymob.com&lt;br /&gt;&lt;li&gt;SLCrawler&lt;br /&gt;&lt;li&gt;Inktomi Slurp&lt;br /&gt;&lt;li&gt;Smart Spider&lt;br /&gt;&lt;li&gt;Snooper&lt;br /&gt;&lt;li&gt;Solbot&lt;br /&gt;&lt;li&gt;Speedy Spider&lt;br /&gt;&lt;li&gt;spider_monkey&lt;br /&gt;&lt;li&gt;SpiderBot&lt;br /&gt;&lt;li&gt;Spiderline Crawler&lt;br /&gt;&lt;li&gt;SpiderMan&lt;br /&gt;&lt;li&gt;SpiderView(tm)&lt;br /&gt;&lt;li&gt;Spry Wizard Robot&lt;br /&gt;&lt;li&gt;Site Searcher&lt;br /&gt;&lt;li&gt;Suke&lt;br /&gt;&lt;li&gt;suntek search engine&lt;br /&gt;&lt;li&gt;Sven&lt;br /&gt;&lt;li&gt;Sygol&lt;br /&gt;&lt;li&gt;TACH Black Widow&lt;br /&gt;&lt;li&gt;Tarantula&lt;br /&gt;&lt;li&gt;tarspider&lt;br /&gt;&lt;li&gt;Tcl W3 Robot&lt;br /&gt;&lt;li&gt;TechBOT&lt;br /&gt;&lt;li&gt;Templeton&lt;br /&gt;&lt;li&gt;TitIn&lt;br /&gt;&lt;li&gt;TITAN&lt;br /&gt;&lt;li&gt;The TkWWW Robot&lt;br /&gt;&lt;li&gt;TLSpider&lt;br /&gt;&lt;li&gt;UCSD Crawl&lt;br /&gt;&lt;li&gt;UdmSearch&lt;br /&gt;&lt;li&gt;UptimeBot&lt;br /&gt;&lt;li&gt;URL Check&lt;br /&gt;&lt;li&gt;URL Spider Pro&lt;br /&gt;&lt;li&gt;Valkyrie&lt;br /&gt;&lt;li&gt;Verticrawl&lt;br /&gt;&lt;li&gt;Victoria&lt;br /&gt;&lt;li&gt;vision-search&lt;br /&gt;&lt;li&gt;void-bot&lt;br /&gt;&lt;li&gt;Voyager&lt;br /&gt;&lt;li&gt;VWbot&lt;br /&gt;&lt;li&gt;The NWI Robot&lt;br /&gt;&lt;li&gt;W3M2&lt;br /&gt;&lt;li&gt;WallPaper (alias crawlpaper)&lt;br /&gt;&lt;li&gt;the World Wide Web Wanderer&lt;br /&gt;&lt;li&gt;w@pSpider by wap4.com&lt;br /&gt;&lt;li&gt;WebBandit Web Spider&lt;br /&gt;&lt;li&gt;WebCatcher&lt;br /&gt;&lt;li&gt;WebCopy&lt;br /&gt;&lt;li&gt;webfetcher&lt;br /&gt;&lt;li&gt;The Webfoot Robot&lt;br /&gt;&lt;li&gt;Webinator&lt;br /&gt;&lt;li&gt;weblayers&lt;br /&gt;&lt;li&gt;WebLinker&lt;br /&gt;&lt;li&gt;WebMirror&lt;br /&gt;&lt;li&gt;The Web Moose&lt;br /&gt;&lt;li&gt;WebQuest&lt;br /&gt;&lt;li&gt;Digimarc MarcSpider&lt;br /&gt;&lt;li&gt;WebReaper&lt;br /&gt;&lt;li&gt;webs&lt;br /&gt;&lt;li&gt;Websnarf&lt;br /&gt;&lt;li&gt;WebSpider&lt;br /&gt;&lt;li&gt;WebVac&lt;br /&gt;&lt;li&gt;webwalk&lt;br /&gt;&lt;li&gt;WebWalker&lt;br /&gt;&lt;li&gt;WebWatch&lt;br /&gt;&lt;li&gt;Wget&lt;br /&gt;&lt;li&gt;whatUseek Winona&lt;br /&gt;&lt;li&gt;WhoWhere Robot&lt;br /&gt;&lt;li&gt;Weblog Monitor&lt;br /&gt;&lt;li&gt;w3mir&lt;br /&gt;&lt;li&gt;WebStolperer&lt;br /&gt;&lt;li&gt;The Web Wombat&lt;br /&gt;&lt;li&gt;The World Wide Web Worm&lt;br /&gt;&lt;li&gt;WWWC Ver 0.2.5&lt;br /&gt;&lt;li&gt;WebZinger&lt;br /&gt;&lt;li&gt;XGET&lt;br /&gt;&lt;li&gt;Nederland.zoek&lt;br /&gt;&lt;ul&gt;&lt;/ul&gt;&lt;br /&gt;&lt;p&gt;&lt;/p&gt;&lt;/li&gt;&lt;/ol&gt;</content>
<draft xmlns="http://purl.org/atom-blog/ns#">false</draft>
</entry>
<entry xmlns="http://purl.org/atom/ns#">
<link href="https://www.blogger.com/atom/22858567/114068745152245136" rel="service.edit" title="Nine things you can do to make your web site better" type="application/atom+xml"/>
<author>
<name>WebPro Designs</name>
</author>
<issued>2006-02-23T09:33:00+00:00</issued>
<modified>2006-02-23T09:37:31Z</modified>
<created>2006-02-23T09:37:31Z</created>
<link href="http://www.webpro-designs.com/blogger/2006/02/nine-things-you-can-do-to-make-your.htm" rel="alternate" title="Nine things you can do to make your web site better" type="text/html"/>
<id>tag:blogger.com,1999:blog-22858567.post-114068745152245136</id>
<title mode="escaped" type="text/html">Nine things you can do to make your web site better</title>
<content mode="escaped" type="text/html" xml:base="http://www.webpro-designs.com/blogger/blogger.htm" xml:space="preserve">&lt;strong&gt;1  Conceive, design and organize your site to be exactly what it is: a web site. -&lt;/strong&gt;&lt;br /&gt;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. &lt;br /&gt;&lt;br /&gt;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. &lt;br /&gt;&lt;br /&gt;The rest of these recommendations aim to help achieve this end. &lt;br /&gt;&lt;br /&gt;&lt;strong&gt;2 - Validate your markup.&lt;/strong&gt; &lt;br /&gt;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. &lt;br /&gt;&lt;br /&gt;&lt;strong&gt;3 - Avoid frames and splash pages. &lt;/strong&gt;&lt;br /&gt;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. &lt;br /&gt;&lt;br /&gt;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. &lt;br /&gt;&lt;br /&gt;&lt;strong&gt;4 - Optimize your site to be as small a download as possible. &lt;/strong&gt;&lt;br /&gt;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. &lt;br /&gt;&lt;br /&gt;&lt;strong&gt;5 - Make your site URLs as short, descriptive, static, technology-inspecific and permanent as possible. &lt;/strong&gt;&lt;br /&gt;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 &lt;br /&gt;&lt;br /&gt;/about_this_site/index.htmlfile on your server, the URL to the about section does not have to be (and should not be) &lt;br /&gt;/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 &lt;br /&gt;/staff.htmlto point to the staff page. Use &lt;br /&gt;/staff/instead. Then use &lt;br /&gt;/staff/joesmith/for Joe Smith's page, instead of &lt;br /&gt;/staff.asp?firstname=joe&amp;lastname=smithOnce you've determined the URLs for your site, use server-side technology to make them work. &lt;br /&gt;&lt;br /&gt;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. &lt;br /&gt;&lt;br /&gt;&lt;strong&gt;6 - Make the information on your site textual, and offer non-Javascript-dependent navigation. &lt;/strong&gt;&lt;br /&gt;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. &lt;br /&gt;&lt;br /&gt;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.) &lt;br /&gt;&lt;br /&gt;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. &lt;br /&gt;&lt;br /&gt;&lt;strong&gt;7 - Actively direct search engine indexing robots. &lt;/strong&gt;&lt;br /&gt;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. &lt;br /&gt;&lt;br /&gt;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. &lt;br /&gt;&lt;br /&gt;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. &lt;br /&gt;&lt;br /&gt;&lt;strong&gt;8 - Serve "friendly" error messages. &lt;/strong&gt;&lt;br /&gt;The most unhelpful, dead-end message you can get from a web server is:&lt;br /&gt;&lt;br /&gt;  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. &lt;br /&gt;&lt;br /&gt;&lt;strong&gt;9 - Don't "click here."&lt;/strong&gt; &lt;br /&gt;I think I've already said enough about this.&lt;br /&gt;&lt;br /&gt;&lt;em&gt;Happy Blogging&lt;/em&gt;</content>
<draft xmlns="http://purl.org/atom-blog/ns#">false</draft>
</entry>
<entry xmlns="http://purl.org/atom/ns#">
<link href="https://www.blogger.com/atom/22858567/114065613078794199" rel="service.edit" title="Meta Tags Keywords in Diferent Languages" type="application/atom+xml"/>
<author>
<name>WebPro Designs</name>
</author>
<issued>2006-02-23T00:51:00+00:00</issued>
<modified>2006-02-23T00:57:54Z</modified>
<created>2006-02-23T00:55:30Z</created>
<link href="http://www.webpro-designs.com/blogger/2006/02/meta-tags-keywords-in-diferent.htm" rel="alternate" title="Meta Tags Keywords in Diferent Languages" type="text/html"/>
<id>tag:blogger.com,1999:blog-22858567.post-114065613078794199</id>
<title mode="escaped" type="text/html">Meta Tags Keywords in Diferent Languages</title>
<content mode="escaped" type="text/html" xml:base="http://www.webpro-designs.com/blogger/blogger.htm" xml:space="preserve">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:&lt;br /&gt;&lt;br /&gt;&lt;-- For speakers of &lt;strong&gt;US English&lt;/strong&gt; --&gt;&lt;br /&gt;"&lt;"meta lang=" name="keywords"&gt;&lt;strong&gt;en-us&lt;/strong&gt;" content="vacation, Greece, sunshine"&gt;&lt;br /&gt;&lt;br /&gt;&lt;-- For speakers of &lt;strong&gt;British English&lt;/strong&gt; --&gt;&lt;br /&gt;"&lt;"meta lang=" name="keywords"&gt;&lt;strong&gt;en&lt;/strong&gt;" content="holiday, Greece, sunshine"&gt;&lt;br /&gt;&lt;br /&gt;&lt;-- For speakers of &lt;strong&gt;French &lt;/strong&gt;--&gt;&lt;br /&gt;"&lt;"meta lang=" name="keywords"&gt;&lt;strong&gt;fr&lt;/strong&gt;" content="vacances, Greece, soleil"&gt;&lt;br /&gt;&lt;br /&gt;&lt;-- For speakers of Portuguese --&gt;&lt;br /&gt;"&lt;"meta lang="&lt;strong&gt;pt&lt;/strong&gt;" " content="ferias, Grecia, sol" name="keywords"&gt;&lt;br /&gt;&lt;br /&gt;&lt;em&gt;Happy Blogging&lt;/em&gt;</content>
<draft xmlns="http://purl.org/atom-blog/ns#">false</draft>
</entry>
<entry xmlns="http://purl.org/atom/ns#">
<link href="https://www.blogger.com/atom/22858567/114064609687877155" rel="service.edit" title="Blogging" type="application/atom+xml"/>
<author>
<name>WebPro Designs</name>
</author>
<issued>2006-02-22T22:06:00+00:00</issued>
<modified>2006-02-22T22:08:16Z</modified>
<created>2006-02-22T22:08:16Z</created>
<link href="http://www.webpro-designs.com/blogger/2006/02/blogging.htm" rel="alternate" title="Blogging" type="text/html"/>
<id>tag:blogger.com,1999:blog-22858567.post-114064609687877155</id>
<title mode="escaped" type="text/html">Blogging</title>
<content type="application/xhtml+xml" xml:base="http://www.webpro-designs.com/blogger/blogger.htm" xml:space="preserve">
<div xmlns="http://www.w3.org/1999/xhtml">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.<br/>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”.</div>
</content>
<draft xmlns="http://purl.org/atom-blog/ns#">false</draft>
</entry>
</feed>
