Welcome to WebmasterWorld Guest from 18.104.22.168
So I'd suggest looking in your server logs and seeing what http response googlebot has been getting - both for that date and others. Also check that the exact url Google has cached here and be sure that it actually resolves as-is.
Another comment - you say "Doesn't show any text." Are you speaking about the link in Google's header that says "Click here for the cached text only"?
Beyond that, this could very well be a Google problem, in which case patience is a virtue. If the url is still bringing in traffic at it's normal rate, then a Googlebug is what I'd assume.
Is it spiderable? or should i use .html at the end of the url.?
How can i optimize this dynamic site?
[edited by: tedster at 5:30 am (utc) on Nov. 27, 2007]
[edit reason] switch to example.com - it can never be owned [/edit]
Just one note - if this is a page and not a directory index, then it is better not to end with the final forward slash. Reserve that for cases where the url does point to a directory's index.
There's also a potential duplicate url issue. If /anytext and /anytext/ both resolve to the same content, you can have duplicate troubles eventually.
You can reduce these two concerns by 1) not ever using any relative links anywhere on the site and 2) making sure that your server uses a 301 redirect to add the trailing slash to any request that comes in without one.
There may be other potential problems as well. I prefer to stick with the simpler convention of "no trailing slash for a page" whenever I can.
Also, those urls may be OK, but they certainly do have a lot of apparent gibberish in them. I'd be concerned that it isn't all needed and that you can resolve some urls without all the "directories" in them, or by changing a "directory" nam to something else. Definitely give a "kick test" to those urls and make 100% sure that exactly and only one version resolves.
All of which is getting pretty far afield from your original issue about no "cached text". Has that situation changed yet?