Dear,
Firstly thanks for your awesome work.
I use newspaper theme v8.8 with tagdiv amp plugin v1.2.
At least I have 2 problems:
-
Generated amp page own internal links to cross-reference my article and they do not use the attribute rel=”amphtml” which is recommended.
Google Search console message: Invalid URL for HTML attribute “href” in tag “a”
See more: https://www.ampproject.org/docs/fundamentals/spec#links
Page example: https://www.beart.fr/art-culinaire/recettes-bien-etre/wraps-maison/amp/ -
Goggle search console message: The “img” tag can only appear as a descendant of the “noscript” tag. Did you want to use “amp-img”
See more: https://www.ampproject.org/docs/reference/components/amp-img
Page example: https://www.beart.fr/voyages/puy-en-velay/amp/
How can I fix these amp error ?
Bonus questions:
How to change url scheme for amp page ?
- Currently it is domain_name/category/article_name/amp
- I would like: domain_name/amp/category/article_name
Is it a better practice to end url by /amp ?
Thanks for your help
Best regards
-
This topic was modified 8 years by
lucie_barragan.
-
This topic was modified 8 years by
lucie_barragan.
-
This topic was modified 8 years by
lucie_barragan.
-
This topic was modified 8 years by
lucie_barragan.
Currently it is domain_name/category/article_name/amp
I would like: domain_name/amp/category/article_name
not really the correct methodology there, as the canonical name is the ‘real’ content location; while the /amp/ endpoint is simply an additional location for the still rare amp-connections via compatible devices and which points back at the original canonical location; meaning the /amp/ endpoint is not a real URL, but a redirect, just like a print-friendly page. You can’t have two URLs SERPS for the same page, so the “real” location is the desktop location for “most” people, and the /amp/ endpoint is secondary location for the small audience seeing/getting /amp/ content — it’s not the canonical link in SERPS.
Hope that made some kind of sense.
(I don’t work here.)
Hi,
The first problem in that example seems to be with this link in the post content
– https://www.screencast.com/t/P1UcH0t5TiYc
That link does not work in AMP or the default post, please check and fix it, or remove it.
That other error would appear on all your MAP post pages however. Images in the sub-footer will cause it. I believe this is added on our to-do list and we will try to convert the image tags manually entered in the sub-footer to proper AMP image tags, automatically. Or provide some kind of solution.
Thanks