lancecarr

One or the other, not both and AMP for WP is fine to create the correct Instant Articles feed.

If you don’t want an amp page indexed then don’t create the amp version in the first place.

In cases like this, this is what you do.
Immediately copy the amp URL that supposedly has the problem and enter it into the AMP Project Validator here:
https://validator.ampproject.org/

If it receives a pass, get on with your life because there was no problem in the first place.

In your case there is no problem. Generally these errors get reported because while Google was crawling the page or your site or while analyzing the code THEY had a problem leading to a false error being generated.

Next time Googlebot swings by they will re-analyse the page and it will return to the index provided the page is of sufficient quality according to Google’s rules.

The key to understanding these messages from Google is that AMP is an evolving standard.

Nothing is set in stone yet so things keep changing especially when it comes to what is and is not allowed in the code being used.

If Google reports to you that something about your page is an error but NOT CRITICAL you can safely ignore it.

The important part is that “It MAY become and error in the FUTURE” but at the moment it is NOT an error.

• This reply was modified 7 years, 6 months ago by lancecarr.

Go to the bottom of this page, all previous versions can be selected.

https://www.ads-software.com/plugins/accelerated-mobile-pages/advanced/

The latest update removed the need to have the separate AMP plugin by Automattic installed as well.

Latest update fixed this problem.

@frenchomatic
The “posts” page is set to nothing and yes, there really is a category called blog.
As I mentioned in the op yes, archive pages support is on.
The site was working perfectly until the AMP by Automattic and subsequent WQP AMP updates recently.
Since then I followed the exact instructions given by the WP AMP guys for removing the old AMP plugin completely, then updating the WP AMP plugin and finally re-adding the updated AMP plugin.
So here we are!

Just adding here for completeness I have the same problem but do not use the category base remover add-on.

URL: https://singleserve.net.au/category/single-sweet/amp/

No I don’t use that add-on.

@pierreto

The reports of errors are coming from the AMP plugin by Automattic page as well.

People who are not using the WP AMP plugin are also reporting the errors so this is an AMP by Automattic problem.

You have no errors on that page.

If you enter the amp url into the AMP validator here:
https://validator.ampproject.org/
you will see you get a Pass with no issues reported.

As a general rule, if you see errors in the Webmaster Tools console go to the AMP Validator and make sure they are real.

Sometimes the Google Bot crawling your site may encounter problems and this results in errors being reported that are not real.

If this is the case just ignore time and the next time your site gets crawled the page will update.

Try going to Settings/Permalinks and saving.

What you might want to do is remove all the changes made by the Auto-optimize plugin, set the title and description correctly in Yoast and test to see if you can get it showing correctly.

THEN re-apply the Auto-optimze settings again. Could be a cache problem.

Twitter fully supports the AMP project so let’s get that out of the way first!
Because of that if there is a “normal” URL posted on Twitter then Twitter will attempt to detect whether or not there is an AMP version of that URL.
If there is and the user is also detected to be on a mobile device then Twitter will direct the user to the AMP version.
This is the whole point of AMP pages.
The only way to stop that behavior from your end is to remove the AMP versions of the pages you don’t want Twitter or even Google to serve up to users.