Home Web Design

Web Design
Get IT Out Of The SEO Business--Link to a Good Article PDF Print E-mail
Friday, 21 May 2010 19:40

It needed to be said...

IT departments do a great job with the things they do, but they can't do it all. Nor should they be asked to. It's enough enough these days dealing with security and keeping everything running smoothly. IT has highly trained people, but they are not web designers and they are most certainly not schooled in SEO (search engine optimization).

That said, here's the article.

How to Check What's Using Port 80 or 443 PDF Print E-mail
Friday, 16 April 2010 01:52

Technical warning: this may make your eyes glaze over unless you're a techie type. :-)

Every once in a while I have to learn something I didn't expect to learn, but which, upon its accomplishment, makes me feel very pleased that I was able to find out about something so useful and share it with others who might be having the same problem.

I was installing WAMP today, which basically turns my computer into a server that is then able to process websites under development. This gives me the ability to try out coding on a test server without disturbing a live site. This is something I've been wanting to do for a while, and now with all new sites being created in Content Management Systems it's become pretty much a necessity. Plus, I want to be able to write some code for various reasons and this way I can test it without having to be online. Much more convenient.

Despite following all instructions I  found, I could not get WAMP to work for me. I went to the forums and looked for solutions, finding a list of things to check. I went through that list and amde sure I did everything suggested, but was still not having any luck. The key to Wamp's functioning correctly had to be use of port 80, it was the only thing left. I needed to use port 80 for WAMP, and something had to be blocking it. I had closed down all the programs I had running that it was suggested I close down, but the problem was still the same. I needed a way to find out what was running on port 80.

My research on the web paid off, and I finally discovered how to find out what's using what port on my computer. It involved a Windows utility named "netstat".

More Fun with htaccess PDF Print E-mail
Tuesday, 13 April 2010 18:43

More and more I have had to be delving into the powerful tool of htaccess. When dealing with a large, dynamic site, sometimes it can take a good bit of research to put together the right code to get things to work, and with Search Engine Optimization (SEO) figuring out how to write redirects for dynamic pages can take quite a while. Code for simple page redirects looks much like this:

RewriteEngine On
Options +FollowSymlinks
Redirect Permanent /pagename.html http://www.domainname.com/newpagename.html

The first two lines must be in place in the htaccess file, once only, for redirects to work. The 3rd and last line is the actual redirect code.This produces a 301 redirect, necessary for search engine optimization purposes to retain the page rank of the original page.

One could also write:

RewriteEngine On
Options +FollowSymlinks
Redirect 301 /pagename.html http://www.domainname.com/newpagename.html

The only difference is in typing out "permanent" vs. "301".

In this case though, the page I wanted to redirect looked like this


The normal simpler method of redirection doesn't work because of that question mark and id at the end. The working code I finally came up with looked like this:

RewriteEngine On
Options +FollowSymlinks

RewriteCond %{QUERY_STRING} id=2
RewriteRule dynamicpage.php http://www.domainname.com/newpagename.php? [R=301,L]

Note that the RewriteCond line show the id=2. This was done because there was a particular page I wanted to have redirected to a new static page. It would need to be done differently if I was doing a general rewrite of all the dynamic pages served from the same dynamicpage.php.

In the second line, note the question mark at the end of the new URL. That ? removed the dynamic part of the url, " ?id=2", which otherwise shows up on the rewritten url when the page is redirected. And of course we add the R=301 to make sure it's a permanent redirect (without the =301 the server would automatically make it a temporary redirect) and the "L" says it's the last rule.

This solved the problem, and it tests as search engine friendly.

Broken Websites - What You as the Website Owner Should Know PDF Print E-mail
Saturday, 13 March 2010 11:15

One of the things I happen across frequently is a broken website. There are different degrees of "broken", ranging from a form that doesn't work properly or links that send one to the wrong page, to more technical issues that affect the workings of a website and not only discourage users but cause search engine problems as well. These things do happen, sometimes caused by changes one doesn't always know about at the host server, or perhaps changes in search engines and other things beyond one's control. They've happened to me, but the key is to fix them as soon as you know about them.

How do you find out if your site is broken?

Ideally, you should keep an eye on your website and spend some time looking through it once a week. That's not always possible if your business is busy, but it is important to spend some time on your site once in a while and make sure that things are working whenever you can. This also helps you to see things that your users see, and sometimes shows up problems you didn't know you had.  Send yourself a test email through any forms on your site. Run a link validation utility. Look at your site statistics to see if there are any 404 errors (these are "Page Not Found" errors). These are basics, and the website owner should be looking for problem areas like this that will send users scurrying off to other websites, taking their business with them. No matter how good a web designer might be, problems do occur from time to time and it is up to the website owner to find these, particularly if their business depends on their website, but even if the website is just additional advertising for them. No designer, no matter how good, has the time to keep up with every website they have ever designed or maintained and make sure it's working, nor should they be expected to do so. It's your website, it's up to you to track what's happening with it. Following are some items you should consider.

CSS and Internet Explorer (IE) PDF Print E-mail
Tuesday, 23 February 2010 19:06

Plenty has been written about CSS hacks for IE, most commonly about the problems with earlier versions of IE (versions 7 and earlier) not being standards compliant--so far off that a lot of work had to be done in code in order to make a page work properly with CSS in those browsers.

Recently I had a different sort of problem with a legacy shopping cart and the pages that run it when viewed with IE8. The pages were updated to a new design, but in the process the menu bar graphic appeared twice (one directly under the other) and although the menu items were listed within the second bar, on the blank bar above the same links also worked even though the menu items were not listed there. This only happened with IE 8. Not Opera, not FireFox, Not Chrome, not IE7... only IE8.

At the time I was snowed under with deadlines and could not spend a lot of time fiddling with it to get it right. I needed a quick fix, but looking through various sites brought up nothing particularly helpful. Tracking down issues like this can sometimes take a long time, and I did not have time to spend. But I did come across something extremely useful for a quick fix that ameliorated the situation and satisfied the customer until I had time to dig further into the problem.

IE8 apparently has a feature under its tools menu called "Compatibility View." This only works when IE8 senses a compatibility problem (which right away convinces me that the developers of the browser knew it would have issues... it's about time Microsoft came up with a browser that actually meets web design standards).

If you click on it, you can add the site in question to a list of sites with  "compatibility issues" so that every time you browse that site with IE8, you'll see that site as it looks in IE7. This was exactly the problem with the site I was working on, and I found that it fixed the problem. However, that's not going to help with all users, it only helped on one computer. I mention it here because while it's not a perfect emulation of the site viewed through IE7, it may help viewing older legacy sites.

What I finally found was another item that did the trick... until I can fix it properly. This came down to using a specialized meta tag, which emulates the page in IE7.

The page looks fine for now, and will be okay long enough for me to figure out the problem and get it fixed.


« StartPrev12NextEnd »

Page 1 of 2
TonerDesign.biz, Joomla templates by SG web hosting