If I can't get from the search engine to the source page, that's a degraded experience. If I can't copy-paste the url but there's some ridiculous browser-defined JS method for inserting whatever the site host says the link is into my clipboard, that's a degraded experience. And we'll see further degraded experiences as Google turns "We screwed up web linking!" from a despised practice into a first-class, browser-supported practice.
The Google AMP viewer/cache is how AMP works in reality. Google has indicated that they are not willing to turn the cache off so it's fair to evaluate AMP in that context.
I don't see anything in AMP syntax to turn off the cache or choose which one is used. For links coming from Google search, Google's AMP cache will be used.
It's the same way you get any page into Google's search results. You can either wait for it to be indexed, or submit it manually. As long as you're supporting the protocol, there shouldn't be a problem. AMP pages have a custom attribute in the <html> tag that lets Google distinguish them.
You can also link your pages explicitly, as described here.
My understanding is that this markup will trigger Google to add the page to their own cache and present a link to the page in their cache in the search results. (The search result pointing to "google.com/amp/...", the page showing the infamous header, etc.)
I don't see how you can use that to get other caches (or even just the original AMP page) into Google's search results.
(Sorry if I'm mistaken though)
> The cache acts as a CDN to improve page speeds, but isn't a requirement for indexing.
How, as a site author, would you control that?
Is there a way to use AMP but explicitly opt-out of caches? I'm not aware of one. (Short of deliberately violating the AMP spec, but then you can't really say you're using AMP anymore)
By having the "desktop" version of the site (which has a high PageRank) point at the AMP version of its pages using rel="canonical", perhaps? (And then the AMP version could redirect desktop viewers back to the desktop site.)
