A question I often ask my target market is, "what's your biggest challenge with building your business online?" And one answer I get frequently is this:

How do I make my website earn money?

If you've got a business online, then it's likely you have some sort of web presence. Perhaps it's a one-page 'sign up for my list' kind of site, or a full-blown brochure site with a menu of choices, or maybe your site is in the form of a blog. Regardless of what kind of site (or sites) you have, if they're not doing what you want them to - and since we're in business, ultimately that means making some sort of a profit - then it's time to make some changes.

But how do you REALLY know whether your site is working or not? Here are four strategies to test and track your pages to know what needs fixing:

1. Let the numbers speak

I'm sure if the sky was the limit, you'd hire the most expensive web designer with the fanciest tools to create the most spectacular site imaginable for your business - and someday you just may do that.

For now, though, even an ugly site can make money. I can think of at least two sites right now that I personally think are not that pleasing to the eye, yet I know they are raking in the bucks each and every month, year after year.

So don't get caught up in having the most polished and professionally looking site. Focus more on having the pieces in place that will bring you the cash, too.

2. Give your site only one job

Think of each page of your website as a separate entity with one main purpose. It may be to sell something, or to sign up for your list, or to get people to call you for an appointment. Whatever it is, make it clear that that one thing is the action your visitor should take from being on that page.

3. Track your numbers

Most web hosts offer statistics that you can use to watch your numbers, or there are other web stat programs that you could use as well (such as Google Analytics). However you are keeping an eye on your numbers, you should be looking for two things: how many people visit your site and how many people take the action you want them to take.

From those two numbers, you can figure out your conversion rate, which tells you how many of those visitors took the action you wanted them to - like sign up for your list. If you make small changes to your page AND watch these numbers at the same time, you'll be able to tweak things to increase your conversion rate.

4. Make one change at a time

This is a very effective way to increase the conversion rates on sales pages and sign-up pages. Change just one thing - for example, the headline - and watch your numbers. Compare those statistics to your previous ones and decide whether or not to keep the change. (You can also do this via a split-test in your shopping cart, where the software does the number crunching for you.)

I see so many sites that try to be all things to all people by offering everything under the sun in too small a space - a website - and all that does is confuse people and encourage them to click away. Remember, 'a confused mind always says no', so always go back to the main questions when considering making changes to your website: What's the purpose of this page? What is the one thing I want my visitor to do here? And then design your copy around the answer. Keep it simple and you'll get better results every time.

Don't be fooled by seeming simplicity. A lot of developers get comfortable with a certain way of designing a database for their web applications that they miss out on techniques they should rather employ to make things run faster and more efficiently. A lot of developers don't bear in mnd that the small site they are creating now might grow into something incredibly large and complex, and the database they designed has become bloated and doesn't scale well to meet the demands of the increased traffic.

This article hopes to provide web developers with a few techniques to help make their database and queries faster and more efficient.

1. Avoid Character Types

When you are designing a database, it is so easy to set all data types to the VARCHAR type as it can then contain any data you want; numbers or text. But character data is amongst the most inefficient data type you can get. If a field is only going to contain numbers, then make it one of the appropriate types (INT, DOUBLE, etc).

Also, wherever possible in your web development code, try to use numeric data types as opposed to characters. One of the most common things a script has to store are flags like whether someone answered yes or no to a question, etc. You could of course store it as 'Y' or 'N' but why not store it as 0 and 1?

The reason this makes a difference is when you have a database, for example, with over 500 000 entries, and are running a SELECT on that field, comparisons are processed a lot faster for numeric data types than character types. Also, if you need to return data to the calling script, numeric data is less memory intensive than character data. In addition, your web development language (PHP, ASP, etc) would also be able to process and perform functions on numeric data better than character data.

I am not trying to convince you never to use character data types. Sometimes it is a necessity, but if you can find ways to reduce the amount of character data processed by your SQL database, the better your server will cope.

2. Normalization

Normalizing a database is really quite a complex process. It is a process that describes a way to design a database structure to avoid repetition of data in your database and can lead to significant performance benefits if employed correctly. However, the entire process of normalisation is a bit beyond the scope of this article as it can fill books on its own, but any developer designing a database should seriously consider becoming knowledgable about normalisation and employing it in their own designs.

For a good tutorial on this process: http://www.keithjbrown.co.uk/vworks/mysql/mysql_p7.php

3. DateTime vs Timestamp fields

This actually relates to 1. a bit. The big difference to bear in mind here is that a field of type DATETIME is actually stored as a series of characters. A field of type TIMESTAMP is actually stored as an integer. So therefore, a more efficient way of storing dates is using the timestamp method. The timestamp has its drawbacks however. For one, you cannot store a date early than 1 January, 1970. Also, timestamps in your script will need recalculating to get to the character format. Because of this recalculation, it may not be better to store as timestamp. It really is a case of testing which format works better for your needs.

4. Use LIMIT where possible

In your queries, if you are doing a SELECT to a database and you only expect a certain number of results, using the LIMIT statement can speed your query up incredibly.

For example, if you have a table of users and you need to run a query to search for one users record, you can use a query like:

SELECT user_name FROM users WHERE user_id = 453;

This query is perfectly valid and will return the right result. But you also know there will only be ONE result. The query above will search the database, find what you want, but then still continue searching after that. It would run a lot faster if you could tell the query that once it has found what you are looking for to stop searching. LIMIT can do this, as this query shows:

SELECT user_name FROM users WHERE user_id = 453 LIMIT 1;

Imagine this scenario. You have a table called logins, that records every login from a user. It currently contains over 2 000 000 records, and you want to find the first time a user logged in. Now bear in mind that because this table inserts data over time, it is already sorted for by date. You could do the following query:

SELECT MIN(login_date) FROM logins WHERE user_id = 4876;

This will return the record you want, but SQL will now have to get all dates for that user, sort them and then return the lowest value to you. Our table is already date sorted simply because of the way it records data for us. So using LIMIT can be more effective:

SELECT login_date FROM logins WHERE user_id = 4876 LIMIT 1;

Because it is sorted, the first one will always be a users first login.

5. Avoid using LIKE

If you have tried to employ 1. above, then hopefully you will be in a scenario where you do not need to use LIKE all that much. LIKE is one of the most inefficient ways of searching a table. LIKE performs a text comparison search in a field and with no wildcards is as efficient as a direct comparison; i.e. WHERE name = 'Jane' is equivalent to WHERE name LIKE 'Jane'. It is when you start introducing the wildcard characters like '%' that things get really hairy.

If you do have to use LIKE, then at least try and make efficient use of the wildcards. These are '_' (underscore) and '%'. Let me explain all this with a real world example.

In a project I was involved in, we had a SQL database storing logs generated automatically from a mail server. Unfortunately, the mail server pretty much just dumped a very long string of text data into a field that contained the data we wanted. A script had to be written to find all logs that referred to a login by a user into the POP server. The only way we could do this was to search every record for a string in the msg field that had the text "User logged in" in it. The first query developed was something like this:

SELECT msg FROM logs WHERE msg LIKE '%User logged in%';

This query took on average of about 35 minutes to process. Obviously not an ideal situation. The way the LIKE worked here was that it had to parse through every single portion of each and every record in the msg field looking for text that matched "User logged in" anywhere in the text. We were able to determine eventually that the text "User logged in" occured at the end of that text in the msg field and so we altered the query:

SELECT msg FROM logs WHERE msg LIKE '%User logged in';

The '%' at the end was removed as we do not want to worry about text after because there is none. The query now only compares text to our string in the msg field at the end of the field and no longer parses through the entire piece of text stored in msg. The query now ran in under 2 minutes. (This was actually still too long, but how we optimised from there is a little beyond the scope of this article.)

Hopefully with all these elements put into practice on your next web development project, you can have a database that runs quickly, efficiently, uses as little resources as possible and wont grind to a halt when the load suddenly increases.

One should agree that content is the main thing that keeps visitors coming back for more to your website. Without content, your website is a dead duck in the water. Here are 5 smart ways you can create content for your website without breaking an arm and a leg:

1. Outsource Your Content

You can hire a professional freelancer to create content for you. This is an easy way to get your content created hands free. But the only problem is cost. If you have tons of extra cash lying around, then this is a viable option.

2. Use RSS Feeds

By installing RSS feeds on your site, you can have fresh new content generated practically on the fly. RSS Feeds can typically grab content from new blog posts around the web, news sites and other websites. You can also promote your content via RSS feeds using FeedBurner.

3. Use Blogs

Create a blog and allow people to comment on your posts. The comments are also a way of creating content for your site, only you are not writing the content, your readers are.

4. Create A Forum

A forum is one of the best ways to have tons of content created for you by others. If you have a popular forum, you'll have loads of fresh new information posted by the forum members.

5. Leverage Articles

Take reprint rights articles from article directories and publish them on your own website. There's a whole world of articles out there on article directories that you can use as long as you include the resource box with them.