The Code looks Good, but is it Search Engine Friendly too?

June 4, 2008 – 6:00 am

No matter how good a developer is, each one makes few mistake while writing HTML code. And I am talking precisely about mistakes which the Search Engines don’t like - some small ones and some fatal search engine disasters. These mistakes happen not because we don’t know how to write an HTML code but because after we are done writing the code, we say to our selves, it’s done and it’s looking fine; why bother change it now for Search Engines. Not every developer is a Search Engine guru and very few know (or bother to know) that couple of such coding mistakes here and there might cause the site to choke to death. But don’t panic yet, it’s easy to avoid these mistakes - just consider the following while you code a website next time:

• Make it a thumb rule to avoid repeating yourself. If it’s a commonly used object property, place it in CSS. If it’s a repeated Javascript, store it in an external file and call where ever required.

• Don’t mess up the code with unused or unclosed DIV’s. If a DIV opens, it should close as well and if it doesn’t, it shouldn’t open. It’s as simple as that.

• The most common web developer mistake - every page has it’s own unique title and description, please do not put the title and description tag in the include files.

• Please make all links and references to images, CSS and JavaScript root relative by starting them with a slash, “/”. Dreamweaver users, please set the “Links relative” option to “Site root” in the Site Definition wizard. This is handy because root relative links don’t break when files are moved from one directory to another.

• Don’t put too many files in a single directory. Keep the heirachy going and manage the files in different directories.

• Use Validator to keep the code and CSS clean. Clean code is easier to manage then something that’s messed up.

• Don’t use <br> for <p> tag as it’s unprofessional and results in inconsistent layout in different browsers.

• Avoid spacer graphics and nested tables. Use heading tags, unordered lists and numbered lists to organize content instead.

• Make it a habit to put a forward back slash ‘/’ at the end of every URL.

Image credit:Flickr