After the v2.1 update, the plugin now activates both /amp/ and ?amp

  • Resolved sarangsss29

    (@sarangsss29)


    3 years, 6 months ago

    Hi,
    So after the AMP v2.1 update, the plugin now activates both /amp/ and ?amp no matter which option you select.
    The only difference is
    When this option is selected,
    Path suffix: /amp/
    The is ?amp does not redirect to /amp/
    Both URLS are accessible.

    Choosing this option:
    Legacy transitional: ?amp
    /amp/ is also accessible, but it is not in AMP format. It is just the regular non-amp post accessible also with /amp/ at the end.
    This is a serious issue for duplication!

    Legacy reader: /amp/ & ?amp`
    As the name suggests, both are available.

    Note: I tested it using Transitional and Reader mode (2021 theme).

    Is there a way if I select Path suffix: /amp/ option, the ?amp won’t be available and redirect to /amp/

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author Weston Ruter

    (@westonruter)

    I don’t think this is a problem for duplication because both /amp/ and ?amp will have the same link[rel=canonical]. Also, the canonical page will only be linking to one of the two versions in link[rel=amphtml].

    I think I have the same problem

    With the previous version, the /amp/ and /amp urls were automatically redirected to /?amp

    with this version the url /amp/ remains /amp/ and /amp is redirected to /amp/ which is not an amp page but simply the standard url with the addition of /amp/.

    example

    mysite.org/test/amp/ is the same non-amp page as mysite.org/test/

    mysite.org/test/?amp/ is the actual amp page instead.

    basically every non-amp page now has two identical urls

    mysite.org/test/
    mysite.org/test/amp/

    This is not ideal from a seo perspective.

    The question is: why is there no longer the following redirection?

    mysite.org/test/amp/

    redirected to

    mysite.org/test/?amp/

    Thanks

    Plugin Author Weston Ruter

    (@westonruter)

    Again, duplication is only a problem when there are duplicate pages with the different rel=canonical links, right? In this case the AMP pages have the same canonical URL.

    Nevertheless, I think the reason why no redirection is happening is that your permalinks still have the amp rewrite endpoint cached. Try going to your Permalinks admin page and re-save. That may cause your desired redirection to occur.

    Plugin Author Weston Ruter

    (@westonruter)

    Flushing permalinks does indeed resolve this issue, per the other support topic.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘After the v2.1 update, the plugin now activates both /amp/ and ?amp’ is closed to new replies.