Not every site needs a site map, they can certainly be a good idea. Site maps provide a dual purpose: They provide search engine spiders easy access to all of your site pages and they provide site visitors easy access to all of your site pages. The difference is that search engines and visitors access your site map differently and therefore there are different methods that need to be applied to creating site map(s) that are friendly for both engines and search spiders.

Small sites typically don't need a site map so long as all pages are linked in the main navigation. Once you get into main and sub-navigation menu's then site maps are helpful in allowing search engines and visitors to quickly find anything they are looking for within just a couple of clicks. A single site map can be used for both purposes or multiple site maps can be created. Here we'll address creating site maps for spiders and humans separately.

Site Map For Spiders

.xml file

An .xml document should be added to your site's root directory containing links to all site pages. This .xml file should then be referenced should be compiled and placed into a proper .xml document which should be uploaded into the root directory.

Robots.txt file

With your .xml site map file in place you must then make it accessible to search spiders. Reference the site map in your robots.txt file by adding a line for sitemap: URL (example: sitemap: http://www.polepositionmarketing.com/sitemap.xml)

Keep current

Be sure that your .xml file is updated and uploaded frequently, or at least as often as pages are added or removed from your site. Large sites should implement an automated site map update monthly or even weekly or daily.

Site Map For Visitors

Navigation links

A site map designed for human visitors is just like any other website page. Link to the site map page should be included in the primary navigation or the site's global footer. Visitors should be able to find this link without too much searching.

Additional page links

Site map should also be linked from various pages within the site such as Help pages and your custom 404-redirect page. This helps point visitors to the site map as a quick and easy means to find what they need.

Overview

It's helpful to provide a short overview paragraph at the top of your site map page. This can be a nice introduction should someone land on this page directly from a search engine or elsewhere.

Heading and layout

The layout of the site map should present a clear visual hierarchal structure or your website. Both headings and sub-headings should be used above properly grouped links.

Text links & descriptions

Site map should primarily use textual links and page should not be cluttered with images or other distractions. It is also a good idea to provide an additional short description (provided there is room) for each link that allows the visitor to better understand where each link will take them.

Keep current

Be sure that your site map is updated and uploaded frequently, or at least as often as pages are added or removed from your site.

As I said above, not every site needs a site map. But those that do should be sure that the site map(s) they create are actually benefiting them. And the best way to do that is to make sure your site maps provide maximum usability for visitors and search engine spiders.

'Fully integrated' is a term used to describes websites that are progressive enough to include virtually every form of online media in their web presence.

If you look at sites like Yahoo, Forbes and virtually any of the major television network sites you can gain some idea of what I am taking about.

These sites contain either news of blog information. They also contain original video streaming sources and audio streams including podcasts. These sites tend to subscribe to the idea that the web user wants it all and should be able to find it all when they visit the business site.

A fully integrated site will often use flash or other animated or moving text. The interesting dynamic is that the best of these sites understand navigation and ease of use remains a critical concern for guests.

Forbes, for example is highly adept at slideshow type presentations on a multitude of topics. It could be top selling cars, entertainers, vacation hot spots, etc. These slideshows are optimized for search engines and are easy to breeze through.

It seems as if a site like this has the potential to garner some of the same consumers of media that have been courted mostly by network television or traditional newsprint.

Most fully integrated sites did not start off that way. In most cases they worked through issues they could easily address and then added features as their knowledge and confidence grew in relation to the their site development skills.

That's something I have always suggested. Do the best you can at developing a site with the most comprehensive development techniques at your disposal. That doesn't mean you have to have a fully integrated site in order to conduct business, but it does mean that you do not simply wipe your brow, release a sigh and suggest to yourself that your work is finished.

The truth is there are more skills in online web development that are being released than ever before. More programs are working with each other allowing a new robust platform for online use. The role of online web development is an ever changing - ever growing function in relation to how you manage your site and in the use of the most effective marketing tools available.

Many sites will develop an internal compass that provides the date they want to upgrade the website to include new functions. In essence they treat their website like software developers treat upgrades. Some will even go so far as to indicate their website has gone from version 1.0 to version 1.1 or 1.5. The idea is to challenge their own thinking in relation to developing a website even after the website has been launched.

This has the potential of keeping visitors interested in finding out what improvements you will come up with next.

Perhaps the greatest development rule of thumb is that you should always strive to be more integrated by attempting to meet the real and perceived expectations of your site visitors. This mentality will always give you a new goal line in your race for the perfect business.

Things which exist on one's personal computer are referred to as "client side", and on the web host as "server side". The average internet user might have first heard "client" in the context of applications installed on the personal computer, such as "email client". Those mail systems which can be used from anywhere are "web mail", and exist on the server side.

In practical terms, all your office suite programs, media players, programs to edit images, most games, and so forth, are probably client side, although "utility" type functions are evolving on the server side. For example, users can now share data on server side spreadsheets and word processors.

Most browser function is defined on the client side, perhaps with some JavaScript add-ons for interaction, calendars, multi-level menus, animated graphics, et cetera.

Business enterprise level content management, databases, store systems, and much more are on the server side. Server side programming can range from simple CGI scripts ("Common Gateway Interface") written in a variety of languages, such as Perl. Large databases can be built in the popular open-source MySQL, and accessed through interfaces programmed in PHP.

First embodiments of such CGI functions started a new copy of the executing module for each command request. To avoid server shutdown from excessive workload, host programmers have evolved better ways, but these need not concern us ordinary mortals.

Fortunately for this author, a web site builder does not need to be an expert in all those server side tools in order to use them. Most hosting companies now offer access to pre-installed modules. Persons wanting better features can purchase modules from third parties to upload and install, such as shopping carts, which are backed by support staff, user, or similar.

If the site builder lacks a very fast connection to the server, s/he can install client side copies of operating systems for SQL, PHP, other... to emulate behavior on the host. Sometimes the emulation is less than perfect, such as with different release generations, so adjustments may be needed after upload.

Why would anyone bother to do this? One reason is that PHP can take over parts of HTML coding, such as with "include files" which represent often used sections of header, footer, body, or serve more robustly than JavaScript for interactivity and utility functions.

If the connection is fast, however, present day "shared hosting" and "virtual private/dedicated servers" make it very difficult for one domain owner to break the system for other users. And only privileged employees have access to the power switch. VPS allows power users to get more behind the scenes than can the SH customer.

Caveat: Whether your HTML writing is done directly on host account or on personal computer for upload, keep an off-site copy against the day your hosting company drops or back levels your content. It will happen.

What ever the approach a person uses for working on the internet, all these elements are examples of "distributed processing", a concept which some large mainframe computer manufacturers had hoped would never be realized. Now that the small guys and gals have forced the issue, by using ever more powerful personal computers in place of dumb terminals, the big dogs have learned to love and profit from it.