Support » Plugin: AMP for WP - Accelerated Mobile Pages » Error after upgrade to version 0.9.97.47

  • After upgrading to version 0.9.97.47, while checking the AMP page, error: The page does not meet the AMP criteria. Problems with the code: The tag “link rel = canonical” is specified in the document several times. Installed Rank Math SEO.

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Author Ahmed Kaludi

    (@ahmedkaludi)

    Can you revert to the older version and confirm if the issue fixes? So we will be sure of that.

    Also, can you share the steps on how we can recreate the issue?

    I immediately returned to version 0.9.97.45. There are no errors on this version. How do you recreate the problem I do not know. But on version 0.9.97.47 there are really two “link rel = canonical” in the code. I do not understand much, but I remember that one was at the very top, and that one was a little lower.

    Plugin Author Ahmed Kaludi

    (@ahmedkaludi)

    I did tested this on my localhost and seems to be working perfectly but since the bug is there on your end, we need to go to the root cause of this. Can you please create a bug report on https://github.com/ahmedkaludi/accelerated-mobile-pages/issues/new

    Our developer team works on the bug report and they find out the solutions to it.

    As I see it, the problem is not only with me. I also wanted to add that when checking structured data, some are duplicated, for example: BreadcrumbList, BlogPosting. And in the HTML code of the page, in its upper part, two almost or identical codes are displayed. They are displayed in the latest version and the older version, but in the older version, “link rel = canonical” is not added to one of the codes. I use Rank Math SEO and I think the problem is with it. On another site I use Yoast SEO and there are no such problems on the latest version. Hope this helps.

    Plugin Author Ahmed Kaludi

    (@ahmedkaludi)

    I would still recommend you to create a bug report on the link I shared in the last reply. So our dev team will work on that bug.

Viewing 5 replies - 1 through 5 (of 5 total)
  • You must be logged in to reply to this topic.