An SEO professional was having trouble with their pages not being indexed due to their AMP page implementation.
Their developer explained that some pages were not being indexed because of the unsupported HTML tag attributes. However, the page is only on their blog and their normal site is not affected by this issue. Their blog is in AMP.
However, some of the things on the page not being indexable include menu bars, header, footer, etc. which are all non-AMP compatible. Or, they use code that isn’t supported by the normal AMP indexing process that Google uses.
They were wondering if they need to create two versions of the page so there is some sort of backup, and if this process is something they need to do for AMP.
John answered that there is more than one issue at play. He joked that he would like to say “it depends” on this one. Anyway, he said that if it’s not a valid AMP page, they are unable to process it with the AMP-based cache.
This means that if you have two versions of a page – say it’s in AMP as well as traditional HTML – then they would just use the traditional HTML version of the page when indexing it. From an indexing perspective, this is just fine.
If you have a pure AMP site, where you have a setup that is just the AMP version, then they would still index the AMP page as an HTML page, even if it’s invalid. They just would not be able to process the page with the AMP cache because of the error in the AMP page.
Thus, they would not be able to give you the advantage of an AMP cache boost as a result.
This happens at approximately the 5:38 mark in the video.