One of the best way to bring traffic to your ecommerce website is to adding your website to the shopping comparison engines (CSE). CSEs index your product data, and present them to the Internet shoppers for price comparison. Online users browsing CSEs are generally in the market to purchase a merchandise, traffic brought to you by CSEs are targeted traffic you may convert to "real" customers. There are more than a dozen CSEs, some FREE and most PAID engines, will help you increase your sales volume.

Setting up an ecommerce website is a little more involved than setting up a personal homepage. The basic domain and web hosting setup are identical, but ecommerce website requires a few additional components in order to offer credit card processing and secure checkout process. You may also use 3rd-party hosted ecommerce application, but this article discusses the procedure for creating a standalone website built from a shopping cart application.

1. Register a domain name.

Every once in a while customers complaints that they are seeing "unauthorized" credit card charge(s) on their bank account. Customers attempted to place an order online, and the credit card declines for some reason but the bank account of a buyer shows that the charge went through. We (merchant) look up our payment gateway and see multiple "declined" transactions. Customers ask us to remove the charge(s) for those transactions that were never approved in the first place. So, what is going on here? Let's start out with customer's question and merchant's response.

As described on URL Canonicalization article we published in March, having a unique URL ("canonicalization") for each webpage is important in improving your "Pagerank". Canonicalization is accomplished by redirecting non-standard webpages to a preferred ("standard") webpage.

One of the first things discussed when beginning SEO project is the URL canonicalization. You may argue that the impact on having multiple URLs resolving to a same page may not have huge effect on SEO (if you use it consistently internally), but it certainly doesn't hurt to normalize the URL so that only one Url serves a single webpage. Implementation is not too difficult for most webmasters, and there is an evidence that URL canonicalization will have a positive effect on your SEO effort.

On a production server, you will definitely want to turn off errors from displaying on the screen due to security and usability reasons but what do you do when you're on a development machine trying to debug a malfunctioning PHP script? PHP gives a programmer an ability to control logging of errors, and the types of errors to be displayed. You may enable PHP error display in one of two ways.

1. You may turn on error display at the script level when a server level error display is turned off.

I have been using CentOS 5.x for several years now, but PHP is still at 5.1.6 on the latest CentOS 5.7. More and more applications are now require higher versions of the PHP including Drupal 7 and Wordpress 3.2. I have upgraded a number of my servers to PHP 5.3.x over the course of last couple of years, and demand is higher each year. I have been using several custom repositories to upgrade the PHP to 5.3.x in the past, but using php53 packages makes it easier than ever to upgrade php to 5.3.x.