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.

Sites that require users to log in to access certain information and/or purchase products add an additional layer of potential complication to the usability process. To avoid potential visitor confusion and the possibility for errors, it is important that any login process requires little or no thought on the part of the site visitor.

Once logged in, you must be sure that visitors are able to find the information they want and expect to find. My Account pages need to provide visitors with access and ability to view and change personal information, as necessary.

Login Access

Access to any login page (or the login form itself) should be available consistently across all pages of the site. Be sure the form or link is obvious and easily differentiated from other areas of the web page.

Security

If the information behind your login contains sensitive data, you need to use the appropriate security protocols, assuring visitors that that you take their information's security seriously.

Registration

If visitors are not already registered a link to a new user registration form should be present. It's also smart to have a global link to "register" for any new visitors to the site.

Account benefits

Non registered visitors should be treated to benefits of account registration. This information should be located on the same page as the new user registration form.

Lost password

All login forms should contain an option to reclaim passwords and/or username should they have been forgotten. This information must also be passed securely.

Remember me

You can provide additional convenience (though less security) by giving visitors the option of checking a "remember me" box which will allow them to stay logged in indefinitely.

Privacy

Provide a link to your sites privacy information/policy near the login form submit button or email field. This gives your visitors confidence that you will treat their information with respect.

Status

The visitor's "logged in" status should be displayed at all times with a ready access to logout at their convenience. When additional security is necessary it's a good idea to automatically log them out after a set period of inactivity.

Change info

Once logged in, visitors should have access to change their user information, including usernames, passwords, contact info, payment details, etc.

Change confirmation

Once the visitor has submitted their information to be changed, provide a confirmation screen that shows the old and new info. This prevents errors and helps insure information remains accurate.

Financial details

Provide links to relevant financial information such as transaction history, invoices, balances, payment methods, etc. Provide printable version of this information.

Up-sell opportunities

Visitors that are logged in provide you an interested, captive audience. Consider discreetly utilizing up-sell opportunities - without being overbearing.

Subscribed services

Provide visitors access to the information/services to which they are subscribed. Also provide additional subscription options, if applicable.

Information management

Allow users to change the way they receive information, providing alternate methods such as snail mail, HTML or text based emails or to turning off communication entirely.

When visitors create an account with you they are making a commitment to you to enjoy the services or information that you provide. It's important not to let the usability process break down after visitors are committed. In fact, it's even more important to treat registered visitors respectfully and appropriately, ensuring they have access to the information they need. This develops long-term relationships and keeps them coming back.

Functions are used to perform a well defined task that is normally repeated at various places within a web site, web application, or other software application. The function sometimes needs certain information before performing its task, and sometimes returns a value to the calling page or program.

An example of how to use a simple function in PHP:

 function showMessage() {
echo "{$_SESSION["message"]}"; }

The above example shows a very simple function that displays the contents of a session variable called 'message'. The idea being that while a user is using a web site, etc, various messages are generated and stored in the 'message' session variable. Whenever the showMessage function is called, the contents of the session variable are displayed. So, for example, when the user logs on, you could display a message saying that they have done so. Likewise, when they log off, a different message could be displayed.

Calling a function

To call the showMessage function, you would just need to include the line:

showMessage()

in the web page (wrapped in php tags to distinguish it from normall HTML).

Passing values to a function

Often, a function requires one or more input values in order to perform its task. For example, take the following example that takes two numbers as input, and adds them together. The result is then returned to the calling web page or program.

function addNumbers($number1,$number2) {
$answer = $number1 + $number2;
return $answer; }

In the calling program we would have something similar to the following:

$number1 = "5";
$number2 = "6";
$sumOfNumbers = addNumbers($number1,$number2);
echo "$sumOfNumbers";

Obviously, in a real program you would not have the numbers hardcoded like this, but they would be obtained from user input or by some other means. Notice also that although the name of the returned variable is $answer, the calling program makes no reference to that. We could, if we wanted to, change the calling program to:

$answer = addNumbers($number1,$number2);
echo "$answer";

which might make things slightly easier to understand.