And the answer is…

Thank you to all who submitted your answers on my previous post Which One Would You Choose; where I asked visitors to select from a choice of four site snapshots, which site they would complete a ESTA form on.

The lines are now closed and the votes are in…  Let’s see how the people chose…

Results from questionaire

Most people chose A.

The official site to complete an ESTA on is D. If you completed a form on D it would of been free and would be guaranteed to be processed. If you completed a form on any of the other three you would of had to pay approximately £30 – £40. These 3 sites are typical of many that are charging people to complete ESTA forms.

 

Official Sites Versus Unofficial Sites

The results here reflect reports that more people are paying to complete ESTA forms from unofficial sites. It’s important to note that the people who complete the forms and end up paying for them are not stupid. They are victims of well worked campaigns combined with efficient design.  Here are some design related reasons I believe people are paying to complete forms on the unofficial sites rather than for free on the official site:

 

Colour Schemes/Look & Feel

A lot of the unofficial sites appear have utilised ‘American’ colour schemes (reds and blues), flags and American imagery:

esta-us

estauk.com

travel-authroziation.org

Whereas the official site is prodominently green which most would not immediately associate with America:

official

It’s possible that some people are electing to use the ‘unofficial’ sites as the appear to have more synergy with the USA, and therefore people think that they look more official.

 

Calls to Action & Usability
There are clear calls to action on the unofficial sites. Well placed and noticeable buttons labelled:  Click Here, Instant Download, ESTA Form or Continue, help make it easy for the site visitor to complete what they want to do, in this case fill out an ESTA form.

buttons-links

The buttons and links are placed in a combination of places some at the top of the web page, some at the bottom but they all have at least one call to action that appears on screen as soon as the page appears on screen.

However, the official site has no clear call to action; you have to work really hard to discover what you have to do next.  In fact (as illustrated below) you have to scroll about 1600 pixels down the page (i.e. well below the fold – if you consider that the average screen displays 1020 pixels) before you even see the apply button! Ordinarily we’d recommend that calls to action appear both above and below the fold.

 

embassy-call

It’s possible then that some come to the official site, but lose confidence as it’s not immediately apparent what they need to do.

 

Assurance and Confidence
Here, both the official and unofficial sites do pretty well. Most of the sites in this example use checklists or step by step examples . Each help to give an impression of transparency and encourage confidence in the site.

Example1:

travel-authroziation-org-confidence

Example 2:

esta-us-confidence

 

Conclusion

One of the most important things to learn from this example is the importance of call to action and usability. Although  27% chose the official site based on a snapshot. Had the test been based on visiting the sites it may have been even less, seeing as visitors have to scroll down nearly twice the length of the screen to even find the apply button.

Every site needs a call to action whether it is to fill out a form, generate a phone call or submit a vote. The clearer the call to action is, the better the site will convert.

Similarly, consideration needs to be given to site look and feel. Use of colour and imagery, and theming to meet visitor’s expectations of how a site should look are key.

 

Suggestions for the Official Site

If I was tasked with redesigning the form on the official site, I’d look specifically at the following areas:

  1. The essential difference between the official site and the others is that it is free to complete the ESTA form. Yet this is not mentioned on the the official site . The first thing I would do is alert the visitor that the form is free to complete on this site.
  2. I would also address the call to action. I would place an apply now button close to the top of the page with enough white space around it for it to stand out.
  3. I would also look to address the design / colour scheme in order to reflect an outsider’s perception of “America”

How to Set up 301 & 302 Redirects

Within this post I’ll be explaining what a redirect is, the difference between a 301 and a 302 redirect lumaxartand how to set up redirects yourself. Right, let’s go:

What is a redirect?

A redirect is a command which automatically sends visitors to an alternative web page rather than the one they typed into their browser.

Why do you need to use redirects?

From time to time you may need to either delete a page, or change it’s URL. If you just go ahead and do this without a redirect, any visitor to the page will get a 404 which can be bad for users and for SEO (see our really rather good guide to managing broken links and 404’s and  for more information).

Why are they important?

Redirects help users by automatically taking them to an alternative page, or indeed the same page if you’ve simply changed the URL. Likewise, redirect also tells search engines that the page has moved.

Plain English Definitions of those Pesky Numerical Wotsits

What’s the difference between a 301 and a 302? What’s a 404? How’s a 404 differ from a 500? Be confused no longer:

301 – Permanent Redirect: This tells the search engines that the page has moved permanently. Over time authority from the old page will pass to the new version.

302 – Temporary Redirect: This tells the search engine that the page has moved temporarily. As such no authority from the old page will pass to the new version.

404 - Error Page/File Not Found: This tells the search engine that the web page cannot be found

500 – Internal Server Error: This means there is a problem with the code which is affecting the server. This may have been caused by incorrect coding or command set up. 

 

To 301 or 302… Which Redirect Should I Use?

  1. 301 – A permanent redirect should be used if you’ve changed the URL permanently. For SEO purposes it rocks as it helps maintain your natural search listing and indexing by the search engines (NB you might see a drop in rankings initially, but they should recover).
  2. 302 – A temporary redirect should be used only in the event that it’s a temporarily URL change. For SEO purposes it sucks as it passes no authority – therefore you might find that your lose rankings.

 

How do you set up redirects?

1. Open Notepad to create a new document.

2. Insert one of the following commands into notepad with your website URL address.

Temporary redirect
redirect 302 /old-webpage.html http://www.website.co.uk/new-webpage.html

Permanent redirect
redirect 301 /old-webpage.html http://www.website.co.uk/new-webpage.html

slide2

 

3. Save the notepad file as an HTACCESS file. You can do this by saving the file with the name .htaccess.

slide31

 

 4. Make sure to select ‘All files’ in ‘Save as type’.

save-slide-2

 

5. Open your FTP for your website. (Note: You will need to open the file in SFTP to be able to upload your HTACCESS file. You may need to enter a password to be able to log into the server.)

6. Upload the HTACCESS file to the root of your server. This is usually in the www folder on the server.

7. Test the web page to see that it is redirecting. (If the web page redirects from the old address to the new address, then the redirect is working.)

 

Having problems?

I’m still seeing the same web page even though I have uploaded the htaccess file. Have I done something wrong?

The redirect to the web page is probably incorrect. Check that you have put in the correct web page address. Also check your slashes ‘/’ and the web page language extension – htm, html, php, asp, aspx etc.

I’m receiving a 500 internal server error. What did I do wrong?

There is probably incorrect formatting in the HTACCESS file. Check the file for spacing and typing errors.

 

Hopefully now you’re good to go, but of course if you do have any queries please let me know via the comments.

 

 

Image source: Lumaxart

Which One Would You Choose?

Scenario:

You need to complete an ESTA (Electronic System for Travel Authorisation) form in order to travel to the States. You don’t know the official site, so you type esta form into your favourite search engine. Below are four screen shots taken from the top sites that appeared on Google for esta form:

A)

A)

A

B)

B)

B

C)

C)

C

D)

embassy-easta1

D

Now without cheating (i.e. don’t go and find out which is the official site) please select the one you would choose to submit your ESTA:

 A) Besta ESTA  B) ESTA Rantzen C) ESTA Egg D) ESTA Suprise

I’ll publish the results of the survey, reveal which is the official site and examine why choosing the wrong one of these four could prove costly next week…

How To Manage Broken Links & 404 Error Pages

Within this post we’ll be looking at broken links and 404 error pages – what they are, how they impact users and SEO, how to find them and perhaps most importantly, some ideas on how you might go about dealing with them.

What are broken links & 404 error pages?404

Broken links occur when web pages are deleted or moved but the link to the old address still exists.  When a user clicks on the broken link, the page cannot be found, so a 404 error page is displayed.

What does a 404 error page do?

A 404 error page tells the search engines and your web server that a web page cannot be found, this might be because it no longer exists or the url has been changed.

What do 404 error pages mean for SEO?

A 404 page tells the search engine that the page no longer exists. If the page genuinely no longer exists, and you no longer wish to rank for the terms targeted on the page, then that’s fine – over time the search engines will remove the page from their indexes. However, if the page does still exist and you still wish to rank for the terms targeted then you have a problem.

In the event that the page does still exist, but you have moved it, (or changed the url), then in order to preserve your ranking, and avoid returning a 404 error page, you will need to redirect the old url to the new one. How? If the page is moving temporarily, you should use a 302 redirect. If the page is moving permanently you should use a 301 redirect.

What do 404 error pages mean for users?

404 error pages can annoy users and cause them to leave your site as they are unable to navigate to the page which they wish to view. Clearly for this reason alone it’s best to minimise the number of broken links on your site.

How to find broken links on you website:

So how do you know if you’ve got broken links? There are many broken link checkers out there, but I tend to use Google Web Master Tools. If you haven’t done so already, set up a Google Web Master Tools account , then submit your sitemap. Google will crawl and index your website, and if there are any broken links, Web Master Tools will show you which links are broken and returning a 404 web page error.

So now you know which pages are returning 404 errors, what next?

How should you deal with 404’s on your site?

From time to time, you will need to delete pages from your site. For example, if you are an ecommerce site, and you stop selling a particular product. In this instance, it is conceivable that a visitor may have bookmarked the page, in order to return later to purchase. However as you no longer sell that product, the page may no longer exist.

In this instance you have a couple of options:

1)  You might choose to 301 redirect an old product page to a similar product which you still stock; or a page which references the fact that you no longer sell the old product line, but this is the new product which will replace it.

2) Let the default 404 page be displayed.

3) Provide users with a custom 404 page, rather than the default one.  Custom 404 pages are a little more user friendly, and if you create a good one, hopefully you’ll keep the visitor on the site.

How to Create a Custom 404 error page
You can configure a custom 404 error page by inserting a default error page command in the HTACCESS file that is on your server. The HTACCESS file can normally be found in the root of the public html folder – an example is shown below:

files-list1

You will then need to configure your HTACCESS file to display your custom 404 error page as the default error page for your website. Below is the code command to put in the HTACCESS file.

error-code1

Once you have uploaded the custom 404 web page and configured the HTACCESS file, test it with URL address errors associated with your domain to see that it is functioning correctly.

For example; type www.(yourdomain).com/404test . Your customised 404 error page should display.

Custom 404 error page designs

When it comes to 404 pages, ultimately you can be as creative as you like. However, ideally the custom 404 should be in keeping with the design of the rest of your website and should aid your visitors in finding what they are looking for.

Examples:

1. Apology with a home page link
You can offer website users a brief apology and lead them back to the home page.

2. Apology with a drop down menu
We’re sorry, but the web page that you are looking for is no longer available. Please select a product from the following menu.

3. Apology with a link list option
We’re sorry, but the page you were looking for no longer exists. We recommend you try:

a) Option A
b) Option B
c) Option C

Below are a few examples of custom 404 error pages to get those creative juices flowing!

luminous-file-not-found2

Image source: Luminous

 

custom-404-mozilla

  Image source : Mozilla

 

Seen some great custom 404 error pages? Hit up the comments and share them. Likewise let us know if you’ve got any further questions, or tips you’d like to share.

 

404 image credit : cbede

Creating and Customising a Blog for your Site

Blog iconMany businesses recognise the potential value of corporate blogging both in terms of potential SEO benefits, and engaging with their customers. As such we’re finding ourselves installing blogs on a fairly regular basis.

Therefore we thought that it might be useful to create a ‘how to’ post to act as a guide for those installing and customising Wordpress.

We’d love to hear your thoughts on this post, and if you’ve any other hints and tips to share please let us know via the comments.

 

Installing Wordpress

There are two ways to install a WordPress blog:

The easiest way, (if  it allows you to) is to install the blog through the control panel for your site. In the control panel click on the fantastico deluxe button, then on the left hand navigation under the title blog, click on the WordPress link, now click the new installation link that will appear on the page and follow the instructions provided on screen.

If you don’t have a control panel that allows you to automatically install a WordPress blog, you can manually install the blog. Instructions for this can be found on http://codex.wordpress.org/Installing_WordPress

Click on Fantastico, then on WordPress

Click on Fantastico, then on WordPress

Once WordPress is installed it will appear in a folder on your remote server (where the site is hosted). Download this folder to your computer.

For ease of explanation I have created a rudimentary template which you can view on www.gravytrain.co.uk/blog-test/

Example

Example

Branding your Blog

You can then add your branding to the blog using the following URLs:

Logo:

http://www.gravytrain.co.uk/blog-test/wp-content/themes/default/images/logo.jpg

Banner:

http://www.gravytrain.co.uk/blog-test/wp-content/themes/default/images/banner-image.jpg

Customising a WordPress Blog

The folder containing the files you need to edit can be found using the following path from the blog folder: \your-blog-folder\wp-content\themes\default\

1. Open style.css in a text editor and replace everything on it with the code below.

/* Begin Typography & Colors */
body {
font-size: 62.5%; /* Resets 1em to 10px */
font-family: ‘Lucida Grande’, Verdana, Arial, Sans-Serif;

color: #333;
text-align: center;
}

#page {
background-color: white;
border: 1px solid #000000;
text-align: left;
}

#headerimg     {
margin: 7px 9px 0;
height: 90px;
width: 800px;
}

#content {
font-size: 1.2em
}

.widecolumn .entry p {
font-size: 1.05em;
}

.narrowcolumn .entry, .widecolumn .entry {
line-height: 1.4em;
}

.widecolumn {
line-height: 1.6em;
}

.narrowcolumn .postmetadata {
text-align: center;
}

.thread-alt {
background-color: #f8f8f8;
}
.thread-even {
background-color: white;
}
.depth-1 {
border: 1px solid #ddd;
}

.even, .alt {

border-left: 1px solid #ddd;
}

#footer {

border: none;
}

small {
font-family: Arial, Helvetica, Sans-Serif;
font-size: 0.9em;
line-height: 1.5em;
}

h1, h2, h3 {
font-family: ‘Trebuchet MS’, ‘Lucida Grande’, Verdana, Arial, Sans-Serif;
font-weight: bold;
}

h1 {
font-size: 4em;
text-align: center;
}

#headerimg .description {
font-size: 1.2em;
text-align: center;
}

h2 {
font-size: 1.6em;
}

h2.pagetitle {
font-size: 1.6em;
}

#sidebar h2 {
font-family: ‘Lucida Grande’, Verdana, Sans-Serif;
font-size: 1.2em;
}

h3 {
font-size: 1.3em;
}

h1, h1 a, h1 a:hover, h1 a:visited, #headerimg .description {
text-decoration: none;
color: white;
}

h2, h2 a, h2 a:visited, h3, h3 a, h3 a:visited {
color: #333;
}

h2, h2 a, h2 a:hover, h2 a:visited, h3, h3 a, h3 a:hover, h3 a:visited, #sidebar h2, #wp-calendar caption, cite {
text-decoration: none;
}

.entry p a:visited {
color: #b85b5a;
}

.commentlist li, #commentform input, #commentform textarea {
font: 0.9em ‘Lucida Grande’, Verdana, Arial, Sans-Serif;
}
.commentlist li ul li {
font-size: 1em;
}

.commentlist li {
font-weight: bold;
}

.commentlist li .avatar {
float: right;
border: 1px solid #eee;
padding: 2px;
background: #fff;
}

.commentlist cite, .commentlist cite a {
font-weight: bold;
font-style: normal;
font-size: 1.1em;
}

.commentlist p {
font-weight: normal;
line-height: 1.5em;
text-transform: none;
}

#commentform p {
font-family: ‘Lucida Grande’, Verdana, Arial, Sans-Serif;
}

.commentmetadata {
font-weight: normal;
}

#sidebar {
font: 1em ‘Lucida Grande’, Verdana, Arial, Sans-Serif;
}

small, #sidebar ul ul li, #sidebar ul ol li, .nocomments, .postmetadata, blockquote, strike {
color: #777;
}

code {
font: 1.1em ‘Courier New’, Courier, Fixed;
}

acronym, abbr, span.caps
{
font-size: 0.9em;
letter-spacing: .07em;
}

a, h2 a:hover, h3 a:hover {
color: #06c;
text-decoration: none;
}

a:hover {
color: #147;
text-decoration: underline;
}

#wp-calendar #prev a, #wp-calendar #next a {
font-size: 9pt;
}

#wp-calendar a {
text-decoration: none;
}

#wp-calendar caption {
font: bold 1.3em ‘Lucida Grande’, Verdana, Arial, Sans-Serif;
text-align: center;
}

#wp-calendar th {
font-style: normal;
text-transform: capitalize;
}
/* End Typography & Colors */

/* Begin Structure */
body {
margin: 0 0 20px 0;
padding: 0;
}

#page {
background-color: white;
margin: 20px auto;
padding: 0;
width: 800px;
border: 1px solid #000000;
}

#header {
background-color: #FFFFFF;
margin: 0 0 0 1px;
padding: 0;
height: 90px;
width: 800px;
}

#headerimg {
margin: 0;
height: 90px;
width: 100%; float:left;
}

.narrowcolumn {
float: left;
padding: 0 0 0px 0px;
margin: 0px 0 0 10px;
width: 500px;
}

.widecolumn {
padding: 0px 0 20px 0;
margin: 5px 0 0 10px; float:left;
width: 500px;
}

.post {
margin: 0 0 40px;
text-align: justify;
}

.post hr {
display: block;
}

.widecolumn .post {
margin: 0;
}

.narrowcolumn .postmetadata {
padding-top: 5px;
}

.widecolumn .postmetadata {
margin: 30px 0;
}

.widecolumn .smallattachment {
text-align: center;
float: left;
width: 128px;
margin: 5px 5px 5px 0px;
}

.widecolumn .attachment {
text-align: center;
margin: 5px 0px;
}

.postmetadata {
clear: both;
}

.clear {
clear: both;
}

#footer {
padding: 0;
margin: 0 auto;
width: 760px;
clear: both;
}

#footer p {
margin: 0;
padding: 20px 0;
text-align: center;
}
/* End Structure */

/*    Begin Headers */
h1 {
padding-top: 70px;
margin: 0;
}

h2 {
margin: 10px 0 0;
}

h2.pagetitle {
margin-top: 10px;
text-align: center;
}

#sidebar h2 {
margin: 5px 0 0;
padding: 0;
}

h3 {
padding: 0;
margin: 30px 0 0;
}

h3.comments {
padding: 0;
margin: 40px auto 20px ;
}
/* End Headers */

/* Begin Images */
p img {
padding: 0;
max-width: 100%;
}

/*    Using ‘class=”alignright”‘ on an image will (who would’ve
thought?!) align the image to the right. And using ‘class=”centered’,
will of course center the image. This is much better than using
align=”center”, being much more futureproof (and valid) */

img.centered {
display: block;
margin-left: auto;
margin-right: auto;
}

img.alignright {
padding: 4px;
margin: 0 0 2px 7px;
display: inline;
}

img.alignleft {
padding: 4px;
margin: 0 7px 2px 0;
display: inline;
}

.alignright {
float: right; width:50%; height:30px; text-align:right;
}

.alignleft {
float: left; width:50%; height:30px; text-align:left;
}
/* End Images */

/* Begin Lists

Special stylized non-IE bullets
Do not work in Internet Explorer, which merely default to normal bullets. */

html>body .entry ul {
margin-left: 0px;
padding: 0 0 0 30px;
list-style: none;
padding-left: 10px;
text-indent: -10px;
}

html>body .entry li {
margin: 7px 0 8px 10px;
}

.entry ul li:before, #sidebar ul ul li:before {
content: “0BB 020″;
}

.entry ol {
padding: 0 0 0 35px;
margin: 0;
}

.entry ol li {
margin: 0;
padding: 0;
}

.postmetadata ul, .postmetadata li {
display: inline;
list-style-type: none;
list-style-image: none;
}

#sidebar ul, #sidebar ul ol {
margin: 0;
padding: 0;
}

#sidebar ul li {
list-style-type: none;
list-style-image: none;
margin-bottom: 15px;
}

#sidebar ul p, #sidebar ul select {
margin: 5px 0 8px;
}

#sidebar ul ul, #sidebar ul ol {
margin: 5px 0 0 10px;
}

#sidebar ul ul ul, #sidebar ul ol {
margin: 0 0 0 10px;
}

ol li, #sidebar ul ol li {
list-style: decimal outside;
}

#sidebar ul ul li, #sidebar ul ol li {
margin: 3px 0 0;
padding: 0;
}
/* End Entry Lists */

/* Begin Form Elements */
#searchform {
margin: 10px auto;
padding: 5px 3px;
text-align: center;
}

#sidebar #searchform #s {
width: 108px;
padding: 2px;
}

#sidebar #searchsubmit {
padding: 1px;
}

.entry form { /* This is mainly for password protected posts, makes them look better. */
text-align:center;
}

select {
width: 130px;
}

#commentform input {
width: 170px;
padding: 2px;
margin: 5px 5px 1px 0;
}

#commentform {
margin: 5px 10px 0 0;
}
#commentform textarea {
width: 100%;
padding: 2px;
}
#respond:after {
content: “.”;
display: block;
height: 0;
clear: both;
visibility: hidden;
}
#commentform #submit {
margin: 0 0 5px auto;
float: right;
}
/* End Form Elements */

/* Begin Comments*/
.alt {
margin: 0;
padding: 10px;
}

.commentlist {
padding: 0;
text-align: justify;
}

.commentlist li {
margin: 15px 0 10px;
padding: 5px 5px 10px 10px;
list-style: none;

}
.commentlist li ul li {
margin-right: -5px;
margin-left: 10px;
}

.commentlist p {
margin: 10px 5px 10px 0;
}
.children { padding: 0; }

#commentform p {
margin: 5px 0;
}

.nocomments {
text-align: center;
margin: 0;
padding: 0;
}

.commentmetadata {
margin: 0;
display: block;
}
/* End Comments */

/* Begin Sidebar */
#sidebar
{
padding: 0px 0 10px 0;
margin-left: 0px; float:right;
width: 190px; margin-top:10px;
}

#sidebar form {
margin: 0;
}
/* End Sidebar */

/* Begin Calendar */
#wp-calendar {
empty-cells: show;
margin: 10px auto 0;
width: 155px;
}

#wp-calendar #next a {
padding-right: 10px;
text-align: right;
}

#wp-calendar #prev a {
padding-left: 10px;
text-align: left;
}

#wp-calendar a {
display: block;
}

#wp-calendar caption {
text-align: center;
width: 100%;
}

#wp-calendar td {
padding: 3px 0;
text-align: center;
}

#wp-calendar td.pad:hover { /* Doesn’t work in IE */
background-color: #fff; }
/* End Calendar */

/* Begin Various Tags & Classes */
acronym, abbr, span.caps {
cursor: help;
}

acronym, abbr {
border-bottom: 1px dashed #999;
}

blockquote {
margin: 15px 30px 0 10px;
padding-left: 20px;
border-left: 5px solid #ddd;
}

blockquote cite {
margin: 5px 0 0;
display: block;
}

.center {
text-align: center;
}

.hidden {
display: none;
}

hr {
display: none;
}

a img {
border: none;
}

.navigation {
display: block;
text-align: center;
margin-top: 10px;
margin-bottom: 0px;
}
/* End Various Tags & Classes*/

/* Captions */
.aligncenter,
div.aligncenter {
display: block;
margin-left: auto;
margin-right: auto;
}

.wp-caption {
border: 1px solid #ddd;
text-align: center;
background-color: #f3f3f3;
padding-top: 4px;
margin: 10px;
-moz-border-radius: 3px;
-khtml-border-radius: 3px;
-webkit-border-radius: 3px;
border-radius: 3px;
}

.wp-caption img {
margin: 0;
padding: 0;
border: 0 none;
}

.wp-caption p.wp-caption-text {
font-size: 11px;
line-height: 17px;
padding: 0 4px 5px;
margin: 0;
}
/* End captions */

2. Open header.php in a text editor. Below is the code that should replace the code between the <body> tags.

<div id=”page”>
<div id=”headerimg”>
<div id=”company-logo” style=”float:left; width:229px;”><img src=”/blog-test/wp-content/themes/default/images/logo.jpg” alt=”logo” width=”229″ height=”89″ /></div>

<div id=”company-contact” style=”float:right; width:500px; margin-right:5px;”><h1 style=”color:#000000; font-family:Arial, Helvetica, sans-serif; font-size:24px; margin-top:5px; text-align:right; padding:0px;”>Company details/ slogan/ contact details will be put into here!</h1></div>
</div>
<div id=”custom-menu” style=”width:100%; float:left; margin-top:1px;”>

<div id=”menu1″ style=”width:150px; float:left; margin-right:4px; background:#000000; padding:5px; text-align:center; height:20px”><span style=”margin:5px 0px 0px 0px; font-family:Arial, Helvetica, sans-serif; color:#FFFFFF; font-size:14px; text-align:center;”>Menu Item1</span></div>

<div id=”menu2″ style=”width:150px;; float:left; margin-right:4px; background:#000000; padding:5px; text-align:center; height:20px”><span style=”margin:5px 0px 0px 0px; font-family:Arial, Helvetica, sans-serif; color:#FFFFFF; font-size:14px; text-align:center;”>Menu Item2</span></div>

<div id=”menu3″ style=”width:150px;; float:left; margin-right:4px; background:#000000; padding:5px; text-align:center; height:20px”><span style=”margin:5px 0px 0px 0px; font-family:Arial, Helvetica, sans-serif; color:#FFFFFF; font-size:14px; text-align:center;”>Menu Item3</span></div>

<div id=”menu-end” style=”float:left; background-color:#000000; width:298px; height:20px; padding:5px;”></div>

</div>

<div id=”banner-image” style=”width:800px; float:left; margin-top:2px;”><img src=”/blog-test/wp-content/themes/default/images/banner-image.jpg” alt=”banner image” /></div>

3. Now in the <header> section delete any styles containing kubrick.jpg or similar eg: #page { background: url(“<?php bloginfo(’stylesheet_directory’); ?>/images/kubrickbgwide.jpg”) repeat-y top; border: none; }.  Take care not to delete anything that isn’t a style as it may break the blog.

4. At this point, if you wish, you can edit the images and styles to suit your site. You will notice that the styles have been written inline. This is for example purposes, so you can and should move inlinestyles to the style sheet when you are happy with the look of the header.

5.Open single.php and add <?php get_sidebar(); ?> above the line containing <?php get_footer(); ?> (this ensures that the side menu appears when viewing a single blog entry which it doesn’t by default.)

6. If you wish you can edit the side menu and footer. Open sidebar.php and footer.php and have a play around. It is advisable to make a back up copy of these files if you are going to experiment.

That’s the look sorted, but there are still some other areas that need to be looked at.

SEO Considerations

For starters when you write blog posts the default URL extensions are not search friendly e.g. /page=2.php

This is unfriendly because it doesn’t display any information relating to the post. Search friendly WordPress URL’s will insert the date as well as the post titles instead. Example: http://www.gravytrain.co.uk/blog/2009/04/09/where-art-meets-web-design/

To check this, open a browser and sign into your blog, click on settings, then on perma links and select the option that gives the following url example: http://www.yoursite.co.uk/blog-test/2009/04/sample-post/

Now the post you write will generate search engine friendly URL’s.

Unfortunately this fix has now created another problem. If you have any previous posts and try clicking on them, you will see that they appear as broken links.

Don’t panic, here’s the fix:

Open or create a .htaccess file and paste the following code, make sure you change the word ‘blog’ if you used a different title for the folder you installed it to.  Type the correct URL where ‘yoursite’ is written:

<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /blog/
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /blog/index.php [L]
</IfModule>
Options +FollowSymlinks
RewriteEngine on
rewritecond %{http_host} ^yoursite.co.uk [nc]
rewriterule ^(.*)$ http://www.yoursite.co.uk/$1 [r=301,nc]

The second part of the code (rewrite) isn’t strictly to do with the blog but it helps with the SEO of your site.

Save and upload the .htaccess file to the root folder.

OK, just one more consideration and we’re there. This consideration is also SEO related. Depending on the installation of  the blog, it will sit on either a http://site.com/blog address or a http://www.site.com/blog address.

Ideally you want the blog to sit on http://www. with rest of the site.  This can be checked by looking at the address bar of  your blog and seeing if there is a ‘www.’ infront of the domain.

This is called canonicalisation – you can read more about the effects of this has here .

To move the blog to a http://www. location you have to open functions.php and paste the following code just after <?php at the top of the page. Again replace ‘yoursite’ with your own domain.

update_option(‘siteurl’,’http://www.yoursite.com/blog/’);
update_option(‘home’,’http://www.yoursite.com/blog/’);

Now upload it. Once you have checked it works delete the lines you just added, save and upload again. I know it sounds a little strange but it is important and the redirect will continue work.

Now you have finished and you can go sup your pint in the pub while basking in the glory of creating a customised blog!