Page design and Google cache

Divs, templates and javascript

[stever]

The Google cache, by inserting its own HTML, disrupts absolutely positioned divs on the page.

I am using templates for a site which has a fair number of content rich pages.

My alternatives?
Leave as is and let the cache look a mess.
Change divs into tables.
Insert javascript to snap layers to an image. Would mean leaving template system as each page would need to be editable on body tag.
No-cache tag (with all the possible implications)

Any suggestions or ideas? I did find a year old thread about using a javascript redirect, but the proponents of that idea now seem to be using no-cache. And how will this work with CSS-P in the future?

[tedster]

I use a lot of absolute positioning, and I let Google sort it out as best they can. Some pages I no-cache, but not all by any means.

Bottom line for me is that I will NOT consider the Google cache to be yet another browser that I must write compatible code for.

[joshie76]

Actually, I'm yet to find someone who isn't a web designer (of some sort) that knows the Google cache even exists...

[tedster]

That's what I always thought, too, Josh. Until the Director at my biggest contract called me.

Actually he thought that it was his site - he ALWAYS clicks on the Google cache link...because he wants the site in his cache!!??! So he was upset at the way some of his pages were displaying.

[papabaer]

You might try assigning a z-index value to the layers at the top of your pages. Even layers that are set using position:absolute. I've done this in the past and was able to ensure my page layers display ON-TOP of the Google/Cache Box instead of the other way around.

In any case, I don't sweat it... it IS only a cached page after all. I imagine before long Google will adapt their code to accomodate CSS-P.

[stever]

Thanks for the replies.

I've actually got divs sitting on top of a tabled-out template, but a thought (a la papabaer) occurred later on that wrapping everything in the template in a div might solve the problem (until I can get around to making the template non-table).

As far as not bothering about the cache goes, I was struck by Brett's comment a year ago about how many people might just hit the back button when they see a broken layout.

[sun818]

<META NAME="GOOGLEBOT" CONTENT="NOARCHIVE"> ?