so we launched our site at the beginning of the week and Tuesday I started to notice bits and pieces of some of the required placeholders were making it into the google results for the page description on some of the keywords.
Some Site - Our awesome tagline here .. no seriously A Link on the page with a keyword. [/orc/#*$!#*$!x/cccccccc/#*$!x/#*$!x/#*$!x/gleft/#*$!xx_#*$!#*$!x_fffffff_content_spots:ContentSpot1]. 20 6 0 More... More... image ... www.somedomain.com/ - Cached - Similar
If it's some kind of placeholder, then by the time your page is sent out, it presumably should have been replaced with some actual content, either by your web design program or by your server (depending on which is responsible for making the content replacment).
To put it another way, it looks like your page is being sent out with the placeholder in the HTML code, rather than the content that was supposed to replace the placeholder text.
One of your text lines references ContentSpot2, the other ContentSpot1. An inconsistency?
If it's some sort of an include, looks like the include file isn't being found.
If it's a CMS, looks like the code is either malformed and the CMS can't understand it, or maybe it can't find the replacement content.
If it's from your web design program, it's not putting the content at the location where it should be.
or perhaps google found, crawled and indexed one of your unprocessed source files. do the files containing these placeholders get requested directly and processed by the server or are they preprocessed and some other processed version of the file is supposed to be served.
this is the rendered HTML page. [/orc/#*$!#*$!x/cccccccc/#*$!x/#*$!x/#*$!x/gleft/#*$!xx_#*$!#*$!x_fffffff_content_spots:ContentSpot2]. I believe that this is not a true placeholder but is required to be present on the page for the dynamic spots to load correctly.
To me it looks like the spiders are ignoring the display:none that is needed with AJAX content.