Support » Plugin: Facebook Instant Articles & Google AMP Pages by PageFrog » /amp disappearing off the URL and not displaying the AMP post

  • Resolved kimstuart

    (@kimstuart)


    My AMP plugin works fine, this is the second site I’ve installed it on and used it successfully.

    I love the idea of your addition, but I can’t seem to get it to work.

    When I activate your plugin, the /amp at the end of the post is redirected to the original post and no AMP content is displayed.

    Does this need to be enabled on EVERY post in order for it to work properly? The AMP plugin enables all posts immediately, so does this negate that functionality?

    https://wordpress.org/plugins/pagefrog/

Viewing 15 replies - 16 through 30 (of 33 total)
  • the only frustration is that the Google crawl is slow so when you’ve made your fixes, it can be 3-4 days before it’s acknowledged by Big G.

    I keep hoping that they do a Fixed box for AMP errors like they do on Link & 404 errors in GWT. That would make things even more efficient.

    Thread Starter kimstuart

    (@kimstuart)

    Totally agree, but I know how many SEO folks haven’t done their AMP yet and that means none of the regular people have either, so it’s still free traffic right now 😉

    Plugin Author pagefrog

    (@pagefrog)

    Hi all,

    Thanks for all the feedback, it really makes it a lot easier for us to squish bugs when we’ve got helpful people onboard!

    c, would you mind sharing your site URL (preferably both the working one and the non-working one)?

    gooma2, could you also share an example of one of your pages that is working and one that’s not?

    Would anyone experiencing an issue be able to print and share their rewrite rules? Here’s some info on how to do that: https://wordpress.org/support/topic/how-to-print-rewrite-rules?replies=7

    We are changing some of the code that manipulates URLs inside PageFrog now, so hopefully this will be fixed in version 1.0.7.2.

    well we deactivated your plugin so I’m unable to share a non-working link as they are all working with the PageFrog plugin turned off.

    Our website is: https://movietvtechgeeks.com/

    Yesterday is when we noticed that after installing this plugin (which I really do like) three days ago, our Indexed AMP pages suddenly began dropped (from 4K and as of yesterday down to 449).

    We tested deactivating the plugins dealing with AMP and the only one that caused the weird issue with newer articles redirecting fine while older articles would just stay on the old address rather than the AMP redirect was this one.

    We turned this plugin in off yesterday morning and this morning our Indexed AMP Pages suddenly jumped back up again. Our developer is still trying to figure out how this could be causing the issues as we would love to be able to use this one. You all did a wonderful job with what it can do.

    I was hoping that it wasn’t just us so when others mentioned having the same issue, it gave us hope that we’ll be able to use this plugin again.

    Glad this might be fixed, I love this plugin personally, it’s a huge help as it means I don’t have to figure this stuff out myself, although I probably will do in the future for educational purposes.

    Is it a possibility that this could be an issue with the server itself? IE could this be done to strange redirect rules conflicting with NGINX or APACHE, we personally run NGINX.

    I also just updated to 1.0.7.2 and tried out the new “Force AMP Compliance”, which is a great feature, however, it doesn’t seem to have fixed the redirect issue, also it would be better if you could individually select plugins, as we use a plugin to load images from AWS, which obviously doesn’t work with this feature enabled.

    In terms of rewrite rules, we got the following response from a “/amp/” page:

    array (
      '(.?.+?)(?:/([0-9]+))?/?$' => 'index.php?pagename=$matches[1]&page=$matches[2]',
      '(.+?)/([0-9]+)/([^/]+)/amp(/(.*))?/?$' => 'index.php?category_name=$matches[1]&p=$matches[2]&name=$matches[3]&amp=$matches[5]',
      '.+?/[0-9]+/[^/]+/([^/]+)/?$' => 'index.php?attachment=$matches[1]',
      '(.+?)/amp(/(.*))?/?$' => 'index.php?category_name=$matches[1]&amp=$matches[3]',
      '(.+?)/?$' => 'index.php?category_name=$matches[1]',
    )

    I don’t know if that is any help.

    I can give you an example of a newer article that directs to AMP and one that doesn’t:

    https://movietvtechgeeks.com/7-drills-to-add-to-nfl-combine/amp/

    This one below always goes back to the original link.

    https://movietvtechgeeks.com/shes-got-game-109-recap/amp/

    I hit the button that ‘Enforces AMP compliance,’ but that then takes out our “Related Articles” that work fine in all other instances. You see them at the bottom of the first link article I put above.

    Update: I took my site down for a bit to check out differences in permalinks, I changed my permalink to post date and then tried AMP with both Pagefrog and the Automatic AMP plugin, that still resulted in a redirect to the original page.

    However, after disabling Pagefrog I was able to access Automatic’s AMP page, so it seems the problem, at least for me is a mix of permalinks and something to do with Pagefrog.

    Our current Permalink structure is:

    /%category%/%post_id%/%postname%/

    I have also left this on the automatic plugin support page, see if they can fix permalinks.

    our permalinks are Post Name since we’re a news site.

    I was hoping the update would fix this, but even after disabling the other AMP plugins (Yoast Glue) the issue remained until I deactivated this one.

    I’m just wondering is this plugin is also forcing an AMP redirect that the other ones are doing which is causing the issue.

    With the AMP plugin, Yoast Glue and this one, it’s 3 plugins being used for one specific format thing.

    Thread Starter kimstuart

    (@kimstuart)

    While it is 3 plugins for seemingly one thing, really it’s three plugins for three different things – and I’m optimistic that each of them does nothing more than the purpose, and does it with the least amount of code possible.
    I’d be fine with three lightweight plugins that work properly than one big bloated one that isn’t so great. It doesn’t appear that Glue is causing any issues with anything else, turning it off or on did not affect the situation we had.

    I’m out of town until the end of the week, but am hopeful that the PF plugin will be working properly by then!

    I’ve got our developer going through all of our error codes and trying to look into the PageFrog one to see what might be causing this weird issue. The others work together really well thankfully.

    Now to just get this one going. If people have a plugin that created intext links (like the Related Posts plugin does) they may get a lot of errors from ‘rel=’. AMP doesn’t like that.

    Plugin Author pagefrog

    (@pagefrog)

    Hello everyone,

    Breaking news!! We’ve identified and resolved all the issues mentioned here regarding permalinks. There was an issue where the “amphtml” tag was not pointing towards the right AMP url, which caused a lot of issues.

    The new 1.0.9 update includes a fix for this so that the “amphtml” tag will always point towards the right AMP url. Most of the issues mentioned here should be resolved.

    Please try it!

    Nicholas Griffin

    (@thetechnuttyuk)

    I just tried it and I’m still getting the same redirect for “/amp”, “/?amp” continues to work fine however.

    Personally I think this is something to do with the wp-amp plugin, I have wrote on their WordPress support page and their Github page, but have yet to get a response.

    For me at least, I think the plugin will only respond to the date permalink format, we use a “/%category%/%post_id%/%postname%/” format, and when I tested it with just the wp-amp plugin and the date format last week the “/amp” URL would work, but it will not work with our current permalink setup.

    I did however, have some luck with another plugin that has been forked on Github (I was told about it on my Github issue: https://github.com/Automattic/amp-wp/issues/314?_pjax=%23js-repo-pjax-container), I don’t know how this guy fixed it, but for me, this plugin works great:

    https://github.com/gabrielperezs/amp-wp

    The only problem is that it likes to think it’s Automatic’s version, but for now it works great.

    Nicholas Griffin

    (@thetechnuttyuk)

    Coach-Guitar

    (@coach-guitar)

    This is not a problem of amp, i had the same problem on my site , if you have Yoast SEO, you have to disable ‘redirect ugly urls’ in the permalinks section (sorry mine is in french, i’m not sure about the translation). Because Yoast thinks it’s a mistake in the URL, it redirects to the article.

    gooma2

    (@gooma2)

    even with the Yoast Redirect Ugly Urls, older articles/posts still redirect back to the original article.

    Sadly, this is happening to us and many others after two weeks so we’re having to let go of the hope that the PageFrog plugin will work.

    Apple News has already updated their News Format with a great plugin that’s working fine (that was the other reason I was rooting for PageFrog). We’ve not had a single error since deactivating this plugin.

Viewing 15 replies - 16 through 30 (of 33 total)
  • The topic ‘/amp disappearing off the URL and not displaying the AMP post’ is closed to new replies.