PenciDesign Supporter replied
Hi,
Please check your AMP page again. I've checked on http://validator.ampproject.org and have not found any errors/warnings.
Regards,
PenciDesign.
Hi,
All warnings are back for all other pages. The last one I reported wasn't solved even after I deleted wp-qads. Please undo everything. I don't need one signal for amp. It's been too much. My search impressions dropped drastically.
Hi,
The situation improved but was not solved. Can you please look into it?
Okay. Please let me know once you are done :)
Hi, after you have connected Onesignal for AMP, I have got a message from Google search Console.
Search Console has identified that your site is affected by 3 AMP issues:
Top Errors
Errors can prevent your page or feature from appearing in Search results. The following errors were found on your site:
Usage of the !important CSS qualifier is not allowed.
The tag 'style amp-custom' appears more than once in the document.
Top Warnings
Warnings are suggestions for improvement. Some warnings can affect your appearance on Search; some might be reclassified as errors in the future. The following warnings were found on your site:
An AMP component 'script' tag is present more than once in the document.
We recommend that you fix these issues when possible to enable the best experience and coverage in Google Search.
If this is happening because of the changes you made to enable OneSignal, please undo it. I would like to have a clean image on search console rather than having Onesignal for AMP
Thanks
Hello, this documentation doesn’t work for your theme's amp plugin. This one is for "AMP for WP" plugin.
Hi, thanks. But my onesignal push notifications aren't working on the amp pages
Hi, can you please help me enabling AMP?
Want to join this conversation or access attachments? Sign in first.
Open your ticket archive, review validated licenses, and continue product support conversations from one customer portal.