AMP redirect error on GSC

  • Resolved mf01

    (@mf01)


    2 years, 10 months ago

    Hi,

    I was using your AMP plug-in as “transitional” mode. Then I changed it to “standard” mode, but then I started having many Google Search Console (GSC) issues, so I disabled it (it’s been deleted from my website for about 2.5 month) and installed AMP for WP. I think it was a bad decision as the situation got worse. I ended up disabling AMP for WP also it after several weeks. Currently my website does not use AMP, but I am still having some lingering issues, and the most perplexing one is redirect error.

    It seems that all the posts I published after I switched to “standard” mode using your plug-in are having redirect errors on GSC. The most difficult part is that when I “test live” those pages, they have no problems, so I cannot figure out what to fix. (If it’s not clear enough, I didn’t change their URLs nor tried to redirect them to somewhere else.) I can actually search those pages on Google, so I think this is the GCS issue.

    I wonder if some of the strings or codes from your plugin are still remaining on my website somewhere and causing redirection confusion. I am not savvy enough so I am really hoping you could help me. Where should I look at in order to find the possibilities that your plugin, even after I deleted them, can be telling my website to do some redirections? I really want to fix this. Thanks!

    The page I need help with: [log in to see the link]

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Support Milind More

    (@milindmore22)

    Hello @mf01

    I can not comment on behalf of AMP for WP plugin, so you will have to connect with them to know if they kept anything on your site.

    The official AMP plugin does not leave any data or files if uninstalled.

    The GSC cache (stores) your AMP pages in its (AMP Cache) Storage, which will be used to serve pages when someone requests them from search results.

    The AMP cache will get updated when google bots re-index your pages, sometime it may take days or months to update those, something we can’t control from the AMP plugin.

    The redirection error is probably showing because you had AMP pages previously but GSC can’t find them so it’s redirecting to non-AMP version of the Page.

    I will recommend contacting GSC support to learn about how you can resolve this issue

    Hope this helps!

    Thread Starter mf01

    (@mf01)

    Thanks for your reply. I am not asking about AMP for WP. It’s strictly about your plug-in. I wanted to ask you because I’ve read topics created by people who started having some errors when they switched from transitional mode to standard using your plugin. And the timing when I started having redirect errors seem to coincide with the timing I switched to from transitional to standard. Any thoughts on this?

    >The redirection error is probably showing because you had AMP pages previously but GSC can’t find them so it’s redirecting to non-AMP version of the Page.

    I figured I would have redirect errors for the pages with /amp that no longer exist. Plus, I’ve already added scripts on my website so that access to /amp pages will be directed to non-AMP pages.

    But instead I am having errors on non-AMP pages. Does it make sense to you?

    Of course I have contacted GSC, but you cannot really know if someone will respond…

    Thanks for your help.

    Plugin Support Milind More

    (@milindmore22)

    But instead I am having errors on non-AMP pages. Does it make sense to you?

    So you are getting AMP errors on non-AMP pages? that’s strange!

    I will recommend checking out this article on how you try and remove AMP pages using GSC Removal tool to remove AMP pages (please enter /amp/ URL or it will also remove non-AMP pages)

    Hope this helps!

    As we didn’t receive a response I’ll mark this as resolved. Feel free to open a new support topic if you require any further assistance.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘AMP redirect error on GSC’ is closed to new replies.