Google problem - what's wrong with my site?

[boarderman23]

We recently changed a site (coinflippoker.com) over to CSS. Things just haven't seemed right since the switch and when you look at the "cached" version in Google, none of the search words are highlighted. Google also isn't indexing very many of the new pages and for the ones it does, it takes forever (use to do so in a few days or less).

If you look at a cached version of any page you will see that the search words aren't highlighted. Rankings have been down and it seems like Google is only giving rankings to certain pages that have quality inbound links and the ones without these links don't seem to rank like they should.

I would have to imagine that Google sees the text, but it just doesn't make sense to me why words aren't highlighted. Is Google just seeing my pages but no text and therefore not giving any pages a ranking without inbound links?

Any help would get GREATLY appreciated!

[Jay]

Interesting. I don't know that I'd worry about Google cache really though. How long ago was it that you made the switch to CSS?

[boarderman23]

Made the change in early February and have noticed this since. I just think the cached problem may have something to do with Google not indexing/seeing the content (just a guess though).

[J S]

the page extensions didn't change or anything did they?

[themike537]

Nope, all the pages stayed exactly the same, all we did was switch the template to the new one, and got rid of all the junk code like spans and stuff and updated it all to CSS.

[kaus]

I had the same thing happen to me in January. Except mine would also be completely blocked out. Its a CSS issue and this is what one of the google people told me...I still dont, not sure if this is the same thing with yours but it might help you

What you are seeing is your page being inserted into another page and the rendering errors resulting from that insertion.The rendering errors only occur when inserted into Google's cache page template.It would be good to have a page that works at least partially when viewed in Google's cache but a page being borked in Google's cache doesn't necessarily translate to being borked when Google actually crawls and processes the page.The more than likely culprit in this case is that Google inserts a given page into a div within its cache template with position:relative, which sets it as the reference point for your page. That normally works but if your page has any elements sensitive
to which parent it is relative to, problems can result.

[boarderman23]

Not exactly sure what that means..something about the way the CSS is set up?

Not sure if this has anything to do with it, but in my HTML tag at the very top it has a few links and code I have no clue about. When I look at other CSS sites it doesn't have any of that. It's the: xmlns=, xmlns:v=, xmlns: o = Should those be in there at the top?