Title: Issues with AMP plugin
Last modified: August 31, 2016

---

# Issues with AMP plugin

 *  Resolved [CoolDavidoff](https://wordpress.org/support/users/cooldavidoff/)
 * (@cooldavidoff)
 * [10 years, 4 months ago](https://wordpress.org/support/topic/issues-with-amp-plugin/)
 * Hello, I’d like to provide feedback first, bevor reviewing it (can’t delete a
   review later).
 * I downloaded your wonderful plugin today when webmastertools told me “there is
   no AMP version of your site”.
 * Installed it, activated it, but google still say the same. a) Any idea how long
   it takes google to notice that we now have (had) your wonderful plugin to create
   AMP compliant pages?
 * Well, pages too, or only posts, like the plugin from automatic?
 * Anyway, the above isn’t even my key worry, it doesn’t matter how long google 
   takes to notice your plugin’s magic.
 * BUT: HUGE ISSUE with your plugin is, it does not respect a site’s menu! So for
   example, take any site, it will have certain pages/posts accessable from the 
   menu, for good reason. And others not, again for good reason.
 * Yet your plugin doesn’t care. Like a bad bot really (another plugin I just looked
   at), your plugin “misbehaves” and shows ALL pages/posts it could find, in a blue
   box at the top, for the visitor to happily click and access pages he isn’t meant
   to access that way! Pages that can’t be locked either, in case you wanted to 
   start arguing that way.
 * To make it short, I would LOVE your plugin and support it, but had to deactivate
   it immediately for the above reason.
 * Would you like to consider my improvement suggestion before I rate it?
    Again,
   thank you so much for what otherwise looks like the most wonderful plugin!
 * [https://wordpress.org/plugins/accelerated-mobile-pages/](https://wordpress.org/plugins/accelerated-mobile-pages/)

Viewing 10 replies - 1 through 10 (of 10 total)

 *  Plugin Author [Ahmed Kaludi](https://wordpress.org/support/users/ahmedkaludi/)
 * (@ahmedkaludi)
 * [10 years, 4 months ago](https://wordpress.org/support/topic/issues-with-amp-plugin/#post-7060668)
 * Let me discuss this with my co-developer and get back to you 😉
 *  Plugin Author [Mohammed Kaludi](https://wordpress.org/support/users/mohammed_kaludi/)
 * (@mohammed_kaludi)
 * [10 years, 4 months ago](https://wordpress.org/support/topic/issues-with-amp-plugin/#post-7060682)
 * Hi CoolDavidoff,
 * Thank you very much for your feedback, I really appreciate that you took out 
   sometime and given us some valuable feedback to improve this plugin. Here are
   the answers to your queries one by one.
 * Q. Installed it, activated it, but google still say the same. a) Any idea how
   long it takes google to notice that we now have (had) your wonderful plugin to
   create AMP compliant pages?
    A. While developing the plugin this was the first
   thing in mind, when Google crawls the website it will directly knows that the
   site has AMP version, because in the source code it will detect the AMP tag rel
   =”amphtml”like this [http://take.ms/PSVsu](http://take.ms/PSVsu)
 * Q. Well, pages too, or only posts, like the plugin from automatic?
    A. This plugin
   will work for both Posts and Pages.
 * Q. BUT: HUGE ISSUE with your plugin is, it does not respect a site’s menu! So
   for example, take any site, it will have certain pages/posts accessable from 
   the menu, for good reason. And others not, again for good reason.
    A. For that
   we have created a custom mobile menu for the AMP Plugin, when you activate the
   plugin a New Menu slot will be enabled for the users to add a custom menu for
   the AMP version of the site. Like this [http://take.ms/OMcOh](http://take.ms/OMcOh).
 * We have created the custom menu feature after your feedback to improve the plugin.
   I have pushed this feature in Version 0.4 update, please install the latest version
   of the plugin and do let me know your feedback.
 * I thank you once again for your feedback, so that we can together make this plugin
   better and useful for other people.
 * Mohammed Kaludi
 *  Thread Starter [CoolDavidoff](https://wordpress.org/support/users/cooldavidoff/)
 * (@cooldavidoff)
 * [10 years, 4 months ago](https://wordpress.org/support/topic/issues-with-amp-plugin/#post-7060711)
 * Hey Mohammed, thank you so much for your quick reply.
    I just tested your new
   v0.4, and you asked for my feedback, so here it is:
 * Before (ie in v0.3) you didn’t show ALL pages (I guess because in this case here
   it would be too many, hehe) BUT you showed pages in the AMP menu that were nowhere
   in the site menu (for good reason), and so that was not usable from a client 
   perspective. Any client, because every bigger site has many pages they don’t 
   want to be accessible from any menu, AMP or otherwise.
 * Now (ie in v0.4) we can choose the wp menu to display (thank you, VERY good solution!)
   BUT you nonetheless only show the TOP entries in the AMP menu. And even when 
   the (mobile) visitor clicks a link to drill down, on the next page you still 
   show the same TOP entries only. Thus the mobile menu is still not usable (other
   than to reach a top level page).
 * Therefore my question: Isn’t it technically possible to have your AMP plugin 
   merely “copy” the entire wp menu structure defined by the customer/webmaster?
 * Thus top level and child levels, the whole wp menu that’s active/activated. Yet
   ONLY what’s defined in the wp menu (not reverting back to 0.3…).
 * In my (non-expert) view this should be easy: You already make use of the top 
   level entries, I am sure the child levels are accessable the same way, no?
 * (PS: I know, your v0.4 now allows to create an extra AMP menu, and again that’s
   VERY good (you are brillant), nonetheless I am not sure you intended as default
   to only show the TOP level pages?)
 *  Thread Starter [CoolDavidoff](https://wordpress.org/support/users/cooldavidoff/)
 * (@cooldavidoff)
 * [10 years, 4 months ago](https://wordpress.org/support/topic/issues-with-amp-plugin/#post-7060712)
 * Oh and by the way, this was not an answer 😉
 * Any idea how long it takes google to notice that we now have (had) your wonderful
   plugin to create AMP compliant pages?
    A. While developing the plugin this was
   the first thing in mind, when Google crawls the website it will directly knows
   that the site has AMP version, because in the source code it will detect the 
   AMP tag rel=”amphtml”like this [http://take.ms/PSVsu](http://take.ms/PSVsu)
 * How long, any idea?
 *  Thread Starter [CoolDavidoff](https://wordpress.org/support/users/cooldavidoff/)
 * (@cooldavidoff)
 * [10 years, 3 months ago](https://wordpress.org/support/topic/issues-with-amp-plugin/#post-7060818)
 * Mohammed?
    I sent the feedback you requested, but you don’t reply?
 *  Plugin Author [Mohammed Kaludi](https://wordpress.org/support/users/mohammed_kaludi/)
 * (@mohammed_kaludi)
 * [10 years, 3 months ago](https://wordpress.org/support/topic/issues-with-amp-plugin/#post-7060820)
 * Hi CoolDavidoff,
 * I apologize for not getting back to you on time, was super busy with other things.
 * Can you please elaborate this part, I’m not able to understand.
 * Therefore my question: Isn’t it technically possible to have your AMP plugin 
   merely “copy” the entire wp menu structure defined by the customer/webmaster?
 * And for how long it should take google to notice do we have AMP installed on 
   the site or not?
    It really depends on multiple factors like how often google
   bots crawl your site and how long does it take to process and update it in search
   results, but my guess is it should take few days ( like 8-10 days ) before showing
   it in the results, or may be less for some sites depending on the factors I mentioned
   above.
 * Thanks
 *  Thread Starter [CoolDavidoff](https://wordpress.org/support/users/cooldavidoff/)
 * (@cooldavidoff)
 * [10 years, 3 months ago](https://wordpress.org/support/topic/issues-with-amp-plugin/#post-7060821)
 * Now (ie in v0.4) we can choose the wp menu to display (thank you, VERY good solution!)
   BUT you nonetheless only show the TOP entries in the AMP menu.
    And even when
   the (mobile) visitor clicks a link to drill down, on the next page you still 
   show the same TOP entries only. Thus the mobile menu is still not usable (other
   than to reach a top level page).
 * So:
    In v0.3 you showed even links that are NOT in the custom menu: BAD. In v0.4
   you show ONLY THE TOP LEVEL menu entries: Less BAD.
 * Question: Why don’t you simply show ALL custom menu entries?
    Only custom menu
   entries, but all of them, not just the top level ones.
 * Sorry but I don’t know what else to write, I find it very clear. And if you have
   used your own software you know very well what it showed in v0.3 and what it 
   now shows in v0.4.
 * Is my suggestion now clear enough?
 *  Thread Starter [CoolDavidoff](https://wordpress.org/support/users/cooldavidoff/)
 * (@cooldavidoff)
 * [10 years, 3 months ago](https://wordpress.org/support/topic/issues-with-amp-plugin/#post-7060842)
 * Mohammed, why do you ask people to provide feedback/suggestions, and then don’t
   bother to reply? Don’t waste our time, it will only waste yours too.
    So now 
   you’ve turned me from “great plugin” to “disappointed”, foolish.
 * Nonetheless a tip: I see you got meanwhile many complaints about plugin functionality,
   or rather not. I would strongly suggest you respond to both complaints in reviews(
   1 star certainly) and in support. Just comment, would give you a much better 
   standing. 😉
 * Other than that: Given how many problems the plugin creates, and you seem to 
   address/answer none, I’d pull the plug, retire it, revise it, then revive it.
   Just what I would do. Better would have been to fully test it first.
 *  [stefiemeekers](https://wordpress.org/support/users/stefiemeekers/)
 * (@stefiemeekers)
 * [10 years, 3 months ago](https://wordpress.org/support/topic/issues-with-amp-plugin/#post-7060845)
 * Hi,
 * I installed your plug-in on my site a few weeks ago.
    Google webmaster tools 
   is saying that I have 0 indexed AMP pages and 19 AMP pages with errors. The errors
   listed are the following:
 * Error Pages with errors
    Incorrectly nested tag 19 Invalid attribute value 19
   Prohibited attribute 17 Unknown syntax error 16 Error in schema.org NewsArticle
   14 Missing supported structured data element 1 Prohibited tag 1
 * I also received a mail from google saying that the AMP pages do not meet their
   guide lines and will not show in google search.
 * Any tips on how to fix the problems?
 * When I remove your app I am left with a copy of each page with /?noamp
    Is this
   going to harm my site having identical pages? Can I remove all these extra pages
   if I decide not to use the app?
 * Thanks and Kind regards
    Stefie [http://www.maltabudget.com](http://www.maltabudget.com)
 *  Plugin Author [Ahmed Kaludi](https://wordpress.org/support/users/ahmedkaludi/)
 * (@ahmedkaludi)
 * [9 years, 11 months ago](https://wordpress.org/support/topic/issues-with-amp-plugin/#post-7060874)
 * Hey Stefie,
 * We have just released an update of this plugin. Please try it and it should fix
   webmaster tools errors.
 * Regards,
    Ahmed

Viewing 10 replies - 1 through 10 (of 10 total)

The topic ‘Issues with AMP plugin’ is closed to new replies.

 * ![](https://ps.w.org/accelerated-mobile-pages/assets/icon-256x256.png?rev=1693616)
 * [AMP for WP - Accelerated Mobile Pages](https://wordpress.org/plugins/accelerated-mobile-pages/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/accelerated-mobile-pages/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/accelerated-mobile-pages/)
 * [Active Topics](https://wordpress.org/support/plugin/accelerated-mobile-pages/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/accelerated-mobile-pages/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/accelerated-mobile-pages/reviews/)

 * 10 replies
 * 4 participants
 * Last reply from: [Ahmed Kaludi](https://wordpress.org/support/users/ahmedkaludi/)
 * Last activity: [9 years, 11 months ago](https://wordpress.org/support/topic/issues-with-amp-plugin/#post-7060874)
 * Status: resolved