Accelerated-mobile-pages: AMP Plugin "AMPhtml" link conflict possibly leading to Google discovery issue.

[kIwOk168]

Greetings Ahmed and Mohammed,

Please bear with me as I'll try to be as specific as possible with the issue I encountered.

I've decided to install your Accelerated-Mobile-Pages Wordpress plugin to amp-enable my site. I chose your plugin because it supports "pages" and my website is created mostly on pages, not posts.

When I activated the plugin, I got a "This theme requires the following plugin: AMP. Begin installing plugin" notification. You can see it from the image below:

I've tried and your plugin really doesn't work in my setup if the AMP plugin (by Automattic) isn't installed. Once installed, my pages do work by appending /?amp in the url. You can see an example below:

However, I looked at the value on the non-amp page and it's pointing to the /amp/ URL append (probably because this is the URL append of the AMP plugin) instead of your plugin's /?amp URL append. You can see this highlighted in the image below:

I've tested and the /amp/ versions don't exist (because the AMP plugin doesn't support pages yet), only the /?amp versions do.

Now I'm foreseeing a problem that Google will have an issue with discovery since the value is pointing to non-existent pages (/amp/ versions).

I would love to hear your thoughts.

In any case, maybe a quick solution would be to allow customization of the amp append. Like add a setting wherein we can change the amp append from the default /?amp into something else.

Thank you very much.

[nicholasgriffintn]

Yeah the plugin requires AMP, it was part of a new release because the AMP plugin has already solved many of the validation issues to do with AMP, and fixed a lot of hard to fix problems to do with iframes, galleries, etc, so it made sense for the developer to switch to that.

As for the page AMPhtml links, that's a good shout. It does seem to be the case that pages have the "/amp/" tag for AMPhtml, although they only work with the "/?amp" URL.

I'm going to look into it for my own site, see why that is.

@ahmedkaludi

[nicholasgriffintn]

I think that my latest pull request might fix this issue, you can find it here: #94

[kIwOk168]

Oh, so that AMP+Accelerated Mobile Pages combo was intentional, I thought it was just a theme issue. Thanks for clarifying this, Nicholas.

I do hope that @ahmedkaludi and @MohammedKaludi can resolve this AMPhtml conflict in the next release. It seems like Google is not detecting the amp-enabled pages generated by the Accelerated Mobile Pages plugin. It's only been a day so I'll wait a few more days to see if Google discovered the amp-enabled pages.

[nicholasgriffintn]

@kIwOk168 It does take a while for Google to notice your AMP pages, personally it took them about a week to detect all of ours.

[kIwOk168]

So just to update, Google was able to discover the AMP pages but has a lot of errors, probably because it's reading the /amp/ pages and not the /?amp versions.

These are all the errors being shown:

While these are the "pages" that Google is detecting, notice that they all have the /amp/ extension instead of the /?amp extensions:

[nicholasgriffintn]

Hey,

What your issue seems to be is that "/amp/" is redirecting to the base URL, instead of loading the amp page. The link should load with "/amp/", however, your site is redirecting that for some reason.

[ahmedkaludi]

Yes @nicholasgriffintn Nicholas is right! @kIwOk168 Can flush the rewrite rules?

[kIwOk168]

Hmmm... I don't really know what's doing the redirect. The AMP versions work with /?amp though like https://www.relationshipspotlight.com/unlock-her-legs-review/?amp

I really feel that it's because "AMPhtml" is pointing at "https://www.relationshipspotlight.com/unlock-her-legs-review/amp/" which is non-existent; only the /?amp version is existent.

Sorry @ahmedkaludi , I don't know how to flush rewrite rules... I'm not a programmer, I'm just a guy who loves and wants to make your plugin work. How do I exactly do that? Thanks.

[nicholasgriffintn]

It's real simple @kIwOk168, just follow these instructions:

Step 1: In the main menu find "Settings > Permalinks".
Step 2: Scroll down if needed and click "Save Changes".
Step 3: Rewrite rules and permalinks are flushed.

No programming needed :).

[kIwOk168]

ooohh, so that's what it's called.

And wow, it worked :) /amp/ versions are working now... I hope Google now gets to see these pages correctly... Thanks @nicholasgriffintn and @ahmedkaludi ... great plugin!

[ahmedkaludi]

Thanks @kIwOk168 Please share your review on the plugin page, https://wordpress.org/support/plugin/accelerated-mobile-pages/reviews/

We will appreciate it.