No matter what site you build it will never be able to make money unless it gets traffic. You ask anyone online who is either new or intermediate what their biggest challenge is. The majority would say that getting traffic to their site is their number one priority.

So when building a site you will naturally want to build it in a way that will help this to happen. In order to do this you need to research extensively what way you will be able to get in front of people searching for products or information relative to your sites theme. You will need to research markets somewhat relative to your interests. For example you may be interested in travel.

Some guru's say you should not necessarily build a site around something you are interested in - instead you should build a site around a subject that will make you money. While this is understandable many people would be challenged to keep up the motivation doing something they do not like when they are starting out - because at this point there will be very little if any money coming in.

What you can do is pick a subject of general interest and then find niches within that which are profitable. This way you have the best of both worlds helping you to stay motivated and make money at the same time.

So your primary goal is to build a site that can compete with others and make you money. Develop the site in a way that the search engines will be able to understand and your visitors will enjoy. This way you will build relationships and as a result make money. To learn more on how to put all this together select any of the following links.

I've done quite a bit of research into web analytics lately, and I have found a couple of things. Google analytics Is a great tool, but it cannot be the only tool an organization relies on. Because it is a purely JavaScript based, it is unable to catch browsers that do not have JavaScript enabled, this includes the search engine robots, some hand held devices, as well as a percent of users that manually turn this off. That being said we need a tool to parse the log files from the server and to give us information about these users, as well as providing us with "on demand" stats where as Google's stats are next day. The server logs also contain a wealth of other information that we are collecting automatically, so we might as well take advantage of it.

I have come to the conclusion that we need to use Google Analytics but we also need a tool that reads the server logs. There are quite a variety of tools that would fill this need. Google recently purchased Urchin who's web analysis product runs Google analytics, costs about $3k and will work with the Google Mini, Urchin also gives the ability to read logs from server software other than IIS (like apache, the software used for open source applications) .

Urchin will be releasing another version shortly, and this will be the first release since the Google buyout. Another option is WebTrends Analytics it costs about $4k. It Like Urchin will read both IIS and Apache logs, and has a web interface for users. The last product is NetTracker, it runs about $4k for the software, and another grand for support. it was recently bought out by Unica. The administration of netTracker is not the smoothest, and the support seems to have declined on quality since the buy out.

Just what is a 301 Redirect?

There seems to be a lot of confusion as to what to do when you move, delete, or want to redirect incoming web traffic from an 'old' web page to a 'new' web page. A 301 redirect is the most efficient method for web page redirection from an old web page to a new web page location. There is also some confusion as to how to handle the complete move or redirection from one web domain to another web domain. According to Google, "If you need to change the URL of a page as it is shown in search engine results, we recommended that you use a server-side 301 redirect instead."

How to Set Up a 301 Redirect

Depending on your web environment, there are several methods to set up a 301 redirect. A 301 redirect is not that hard to implement and it should preserve your search engine rankings for that particular page or web domain.

.htaccess 301 Redirection

The .htaccess file needs to be placed in the root directory of your old website. In this example, we are redirecting incoming web traffic from an old domain to a new domain.

Options +FollowSymLinks

RewriteEngine on

RewriteRule (.*) http://www.newdomain.com/$1 [R=301,L]

The .htaccess file is the most common method used for 301 web site redirection.

PHP 301 Redirection

You would place this code in a file at the old location.

Header( "HTTP/1.1 301 Moved Permanently" );

Header( "Location: http://www.new_location.com" );?>

IIS 301 Redirection

• In Internet Services Manager, you need to right click on the file or folder you wish to redirect
• Select the radio button titled "a redirection to a URL".
• Enter the redirection web page
• Check "The exact URL entered above" and the "A permanent redirection for this resource"
• Click on 'Apply'

That is all there is to it.

There are other methods in addition to set up a 301 redirection which include coding for ASP, ASP.NET, Java, CGI, Cold Fusion and Ruby on Rails. The above are the most common that I've encountered. When set up correctly, a 301 redirect will preserve your search engine rankings when it is necessary to move files around or switch, or consolidate, domain names.