Errors after update

The AMP validation tool (not Google) gives that page a Pass with no errors reported.

Often the Googlebot encounters glitches when it is crawling AMP pages and then reports errors.

Of course at that time you go running around trying to fix errors that actually don’t exist!

So, when you see an error reported in Webmaster Tools, take that URL and enter it into the actual AMP Project validator here: https://validator.ampproject.org/

If it fail there you have a problem, if it passes then ignore the error and pretty soon Google will re-crawl and remove the errors.

Hi – thank you for the response! I show it as failed? It initially shows as “pass” but wait a second or two and it shows failed. Here are the test results:

https://validator.ampproject.org/#url=http%3A%2F%2Fmylennarhome.dev.onpressidium.com%2Fbad-air-conditioner-and-ventilation-causing-mold-issues%2Famp

Also, if you look at the same URL in development (with updated plugin) vs. production, the CSS for defined fonts (Roboto) does not seem to be working either.

Development: https://mylennarhome.dev.onpressidium.com/bad-air-conditioner-and-ventilation-causing-mold-issues/amp

Production: https://mylennarhome.com/bad-air-conditioner-and-ventilation-causing-mold-issues/amp

@krisfannin

We have already created a ticket on this, I will make sure that this gets fixed immediately.

Here’s the ticket reference: https://github.com/ahmedkaludi/accelerated-mobile-pages/issues/1616

I apologize for the inconvenience.

Much appreciated!