4 ms·
Why would you generate both? At what endpoints would you serve which? Which would you serve as the canonical version, and how would people reach the alternative
by lucideer 10y ago
Why would you generate both? At what endpoints would you serve which? Which would you serve as the canonical version, and how would people reach the alternative?
If you're intending to content-negotiate for Googlebot I suspect you'll run into trouble.
- detaro 10y agoAMP is designed to be served at alternative endpoints. The canonical HTML version gets a rel=amphtml header and the AMP page a rel=canonical. https://www.ampproject.org/docs/get_started/create/prepare_for_discovery https://www.ampproject.org/docs/get_started/create/prepare_f...
- lucideer 10y agoThis I was completely unaware of. I'd read the majority of the docs, so this isn't really emphasised. Tbh, if this had been front-and-centre when I started implementing AMP, I might have actually finished the job without balking at the hard Google dependency and abandoning the effort. I'm still wary of it given the Google-hosting of AMPed pages accessed via SERPs, but this does make it slightly less awful I guess.