‘?amp’ querystring vs /amp/ in path
-
The WP AMP Plugin’s AMP HTML syntax is valid, but the url generation seems to cause issues.
https://amp.dev/documentation/guides-and-tutorials/learn/amp-caches-and-cors/amp-cache-debugging?format=websites recommends the tool https://ampbench.appspot.com/ which says the AMP URL does not pass the test. https://ampbench.appspot.com/validate?url=https%3A%2F%2Fwww.history101.com%2Fvikingfacts%2F%3Famp
AMPbench seems to fail on the querystring ‘?amp’ as far as I can tell. There isn’t much in terms of documentation on the expected URL structure but using ‘?amp’ causes issues with purging caches.
The first issue I ran into was when I attempted to purge the amp cache. I had to use the work around listed in:
https://github.com/ampproject/amphtml/issues/10883Which worked fine for Google’s amp cache but not cloudflare or bing.
If you look at any mainstream site that has amp implemented, they us either a subdomain, directory in the path, or some combination of the two. Your implementation is the first i’ve seen that uses a query string.
Due to lack of documentation or official specification in regards to the AMP URL structure, I can see how this issue occurred. One can argue that the issue is with the AMP Cache code, but why go against the examples in their docs?
My concern here is that other tools/services related to AMP may fail here.
The page I need help with: [log in to see the link]
-
I think the issue is that the “AMP URL” label is misleading. This is not validating the format of the URL, but actually checks whether that page is valid AMP.
The “FAIL” comes from the AMP validation output that you can see when scrolling down on https://ampbench.appspot.com/validate?url=https%3A%2F%2Fwww.history101.com%2Fvikingfacts%2F%3Famp:
tl;dr your site is not valid AMP at the moment.
The topic ‘‘?amp’ querystring vs /amp/ in path’ is closed to new replies.
