to be back here since one of the forum users just pm me a question about this ... Peoples ... here are some things to be made clear . First of all cache control and no archive control over the sites . It's true for linkwells / splog's / and everything involved into '' link building process '' none care if the pages will be copied / duplicated and so on ....
On the google , when you are searching for any keyword you will see something similar with this picture
Code:
http://img142.imageshack.us/img142/8782/examplest.jpg
It's called '' cache '' by them just because the page it's '' saved '' on their servers in the process of indexing ( an actual copy of the page ) .
One more point , I don't know who told you guys a page after it's crawled it's means will be actually added to the index

THAT'S WRONG ! crawling and indexing process it's different ! Actually most of G' folks who speak and explain to large audience about their dirty business always trying to make the difference between their 3 step of the process
A => crawling / B => indexing / C => delivery request of the queries from their index !
It's not important about them and I think about anyone how this processes are going to go from technically point of view but you guys have to understand this processes since your main goal it's to manipulate the results of the queries

... from here will come your traffic so maybe the sales or clicks which you will dream about ....
Now ... the second thing ... The '' cache-control '' from the browsers :
Code:
<META HTTP-EQUIV="CACHE-CONTROL" CONTENT="NO-CACHE">
This piece of code from the files delivered by the server it's controlling how the date's will be used after the request . Here are some things which need to be said to understand how and why they are '' a must '' :
HTTP 1.1. Allowed values = PUBLIC | PRIVATE | NO-CACHE | NO-STORE.
Public - may be cached in public shared caches
Private - may only be cached in private cache
no-Cache - may not be cached
no-Store - may be cached but not archived
The directive CACHE-CONTROL:NO-CACHE indicates cached information should not be used and instead requests should be forwarded to the origin server. This directive has the same semantics as the PRAGMA:NO-CACHE.
Clients SHOULD include both PRAGMA:NO-CACHE and CACHE-CONTROL:NO-CACHE when a no-cache request is sent to a server not known to be HTTP/1.1 compliant.
It may be better to specify cache commands in http than in meta statements, where they can influence more than the browser, but proxies and other intermediaries that may cache information.
So via this specific requests served by the server spiders will consider to act in accordance with them , can be controlled how often the content delivered by the server it's '' set to expire '' / '' set to be cache '' and so on ... but this it's just about how the document's are delivered by the server and will be '' read '' by the agent who made the request ....
technically speaking such directives can be mixed and sometime it's a must to be mixed BUT , at the end of the day the hole process must be understand backwards just because you need the results

.... that's the point to understand the full process lol .
To answer to your question nobita , the truth it's you will never know actually with any command ( query on google / yahoo or msn ) how much links was already '' seen '' and '' counted '' for your main site , you know why ? well because first of all the '' index '' it's permanently updated , second because even if the page it's crawled it's not means will be actually included into the index , and 3'th even after including one page into the index it's not means will be here forever
