tedster - 3:33 am on Jan 6, 2007 (gmt 0)

Yes, Google does call them "pages" - but what they store in the cache is the content of the html document found at a specific url at a specific time, right?

The W3C has long wrestled with a technical definition for "page" - especially as the future of html is clearly device independent. In 2005 they did use a tentative definition for "web page" in a working draft. That's as close as they have come to a definition, to my knowledge.

Web Page A collection of information, consisting of one or more resources, intended to be rendered simultaneously, and identified by a single Uniform Resource Identifier. More specifically, a web page consists of a resource with zero, one, or more embedded resources intended to be rendered as a single unit, and referred to by the URI of the one resource which is not embedded. This term was developed from the definition of web page in Web Characterization Terminology & Definitions Sheet. Glossary of Terms for Device Independence [w3.org] W3C Working Draft 18 January 2005

My point is that to understand Google's indexing process, it can be critical not to have a naive understanding of what a "page" is, no matter how casually you, or Google, or anyone else may use the word in some situations.