Google Search Console errors

Same… sort of.

getting errors on the AMP pages
Error Pages with errors
1 Prohibited attribute 2
2 Incorrectly nested tag 2
3 Invalid attribute value 2
4 Required attribute missing 2
5 Unknown syntax error 1

here is a new thread (in the AMP plugin forum) listing the actual errors: https://www.ads-software.com/support/topic/help-with-amp-vaidation-errors

But have no idea WHAT is causing these errors nor anyway to see / repair them

A little help please..

Same by me…

Fix errors on your AMP pages:

Incorrectly nested tag
Invalid attribute value
Required tag missing
Required attribute missing

Google Console reports “Error in schema.org NewsArticle”.

————-
Google systems have detected that some of your AMP pages do not meet our guidelines and will therefore not show in Google Search AMP-related features. The following report provides examples of pages with errors.

Fix the NewsArticle structured data element in your page. AMP pages with an invalid NewsArticle structured data element may appear in Google Search results without AMP-specific display features
————-

We wound up hiring a developer to deal with all the errors since they are cropping up on everyone.

It’s very frustrating with Google as they love to quietly demand we all adhere to their new systems without giving us much of a playbook.

What’s even more frustrating is that they wants sites to implement changes immediately but there seems to be a slowness on Google Webmaster Tools in knowing what errors there are and if the fixes have been recognized yet. We all know this update is going to be universal across all sites (not just news sites) and it would be nice to have them being a little more communicative in what they need.

I’m thankful there are plugins like this that are helping smaller sites who can’t afford a developer but even they have their limitations on keeping up with all the changes. And you can bet they’ll be plenty more coming up as Google adjusts things.

Hello c, PPNSteve, ConquerorTravel, TRDK29, and gooma2,

Mike here from PageFrog—happy to help! So sorry for the delayed response. I’ve been receiving hundreds (maybe thousands!) of emails since AMP launched last week.

I’ve found that many, many, many errors are caused by older plugins that violate AMP regulations in one form or another. Over time, hopefully developers of these plugins will release AMP compatible updates, but for the time being it’s causing a lot of trouble.

For example, various plugins can cut out the “https” portion which breaks AMP, plugins often inject javascript which breaks AMP, they could handle styling in a certain way which breaks AMP, etc.

In our latest update, we released a new feature called Force AMP Compliance which disables conflicting plugins for your AMP Pages. Head under Mobile Formats > Settings, then scroll down to AMP and check the box beside Force AMP Compliance.

Try that out and let me know if the errors go away!