4 ms·

>from a despised practice into a first-class, browser-supported practice Browsers already support WebComponents. This is just Javascript, there's nothing prop

>from a despised practice into a first-class, browser-supported practice Browsers already support WebComponents. This is just Javascript, there's nothing proprietary about it. It sounds like you're not even complaining about how AMP itself works, but the CDN/caching services such as Google AMP Cache. Regardless, none of this results in lock-in as your original comment claimed. And again, degradation is too subjective to compare directly.

wmf 10y ago
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.
- SquareWheel 10y ago
  >Google has indicated that they are not willing to turn the cache off Can you elaborate? Google's AMP Cache is an optional feature. Cloudflare also provides an AMP cache.
  - tyingq 10y ago
    Do cloudflare hosted AMP pages make their way into Google search results?
  - wmf 10y ago
    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.
xg15 10y ago
How would you get a cloudflare-served AMP link into (the first page of) Google's search results?
- derefr 10y ago
  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.)
  - SquareWheel 10y ago
    Very close. AMP pages use a rel="canonical" to point to the desktop site, and desktop pages use rel="amphtml" to point back. Using rel canonical on your main page could be very dangerous from an SEO perspective, as it gives complete authority to the other page.
- SquareWheel 10y ago
  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. https://www.ampproject.org/docs/guides/discovery https://www.ampproject.org/docs/guides/discovery The cache acts as a CDN to improve page speeds, but isn't a requirement for indexing. Sorry if I came off as crass in my previous reply, but the amount of misinformation around AMP is really astounding.
  - xg15 10y ago
    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)

wmf 10y ago

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.

SquareWheel 10y ago
>Google has indicated that they are not willing to turn the cache off Can you elaborate? Google's AMP Cache is an optional feature. Cloudflare also provides an AMP cache.
- tyingq 10y ago
  Do cloudflare hosted AMP pages make their way into Google search results?
- wmf 10y ago
  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.

xg15 10y ago

How would you get a cloudflare-served AMP link into (the first page of) Google's search results?

derefr 10y ago
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.)
- SquareWheel 10y ago
  Very close. AMP pages use a rel="canonical" to point to the desktop site, and desktop pages use rel="amphtml" to point back. Using rel canonical on your main page could be very dangerous from an SEO perspective, as it gives complete authority to the other page.
SquareWheel 10y ago
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. https://www.ampproject.org/docs/guides/discovery https://www.ampproject.org/docs/guides/discovery The cache acts as a CDN to improve page speeds, but isn't a requirement for indexing. Sorry if I came off as crass in my previous reply, but the amount of misinformation around AMP is really astounding.
- xg15 10y ago
  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)