I recently came across a piece of code on a web site I was checking out in preparation for my SEO seminar.
Programmers used green comment text as a way to distinguish notes to the programmer or reminders, from code that makes the site work. These notes do not show up as content in the graphic interface of the web site. If you want to see what sort of “conversations” and notes programmers leave behind when building a site, simply look at the source code and scroll for the green bits.
Now, imagine a company in a highly competitive field having this sort of programmer’s annotation about a future product in the code. This could well be a major issue if a competitor receives advance notice of future actions, just because a programmer wanted to identify a placeholder for a future product on the web page.
While I find this interesting from a competitive intelligence perspective, it raises another question: when you approve your web site, do you ever actually look at the code? Have you considered the liabilities that inadvertent disclosure can bring to your company? Do you have any sort of quality assurance and brand protection process in place re: coding? And, in earlier posts I talked about the importance of meta tags and title tags – so: what is your quality assurance process to make sure these search engine optimization aids are in place and make sense from a brand and messaging architecture point of view?