Valid HTML!
< Upgrade frequency - a no-win situation? | Blog | New Roadmap forum, plus news on Injader 2.0.2 >
Valid code has always been a big priority for Injader. Back in the days when Injader was called Majestic, this priority took a hit when the WYSIWYG posting editor was first introduced. It was very, very difficult to provide a custom editor that generated valid HTML. Slowly, I let the standards slip.
But now that TinyMCE is used in Injader, valid code is a very important part of Injader once again. Posts created with the old editor are not automatically cleaned up when you upgrade to the latest version, but some code is tidied up when you edit the post with TinyMCE.
As the rest of Injader contains valid HTML it's very good to have an editor that does the same.
Why should you care?
Through making some mistakes on one of my own sites, I found that if you have invalid code in your header, your site can actually be excluded from search engines altogether. It's not so much that you get blacklisted, more that your site cannot be indexed. When I corrected the code my site reappeared on the major search engines within a week or two.
Using valid code should make your site's appearance more consistent across different web browsers and on mobile devices. However, there are still quirks and bugs with web browsers (especially older versions). Even valid code is not always enough to make your site display the same in all browsers.
Valid code also makes it easier to find errors on your site. Most websites have hundreds if not thousands of HTML errors, and the response is usually "well it looks OK, so what's the problem?" The problem is that with so many existing errors, new and much more serious errors can creep in unnoticed. If you can get the elusive "this page is valid HTML" message on your site, it makes it a lot easier to fix errors that might occur in future.
Try validating your site today: The W3C Markup Validation Service
Speaking of which, it looks like I've got an error on Injader.com... I'd better fix that!
No related content found.