3 Tips to Resolve AMP Errors

3 Tips to Resolve AMP Errors pixelwork

3 Tips to Resolve AMP Errors

Tips to Resolve AMP Errors

Tips to Resolve AMP Errors
If you've been seeing some AMP errors in some of your WordPress posts, courtesy of the popular WordPress plugin WordPress AMPTomo Taylor, the AMP Community Manager at Google has posted some tips for resolve AMP errors.

Resolve AMP Errors

This was in response to a publisher who was still seeing hundreds of AMP errors, even with the latest version of the plugin.

Select some items and run the page through the AMP HTML validator to preview and validate:

  1. Open your page in the browser.
  2. Add “#development=1” to the URL, for example, https://pagina.com/#development=1.
  3. Open the Chrome DevTools console, turning on mobile emulation mode, and check for validation errors.
  4. Fix them AMP validation errors.

Use the validator AMP with DevTools It's not something very well known, but it's nice to see them promoting it as a debugging tool for validation error problems.

Check the AMP schema markup properties in the structured data testing tool.

  1. Make sure the article, video or Rich snippet is present.
  2. There should be no 'AMP' error warnings.
  3. Is the logo within 600 × 60?
  4. Does the logo conform to the UI guidelines for carousel logos?

This is an area where many editors initially get tangled. If the site's logo does not meet the guidelines, each page will generate an error. It will need to be updated to fix it.

Check the AMP HTML page link

  1. Is there a rel=amphtml on the canonical page?
  2. Is there a rel=canonical in the AMP HTML page?
  3. Is there a rel=amphtml link on the mobile web page, does it apply?

I haven't seen any errors related to the plugin, but if you're implementing a custom or manual solution it's worth checking.

Check external resources

  1. URL of all embedded iframes, videos, custom fonts, pixels, analytics, ads, etc., and similar content that is processed via the HTTPS scheme.
  2. Do not use “relative URL protocols”, this could cause problems when the article is loaded through Google's AMP Cache. When a document is displayed from a cache elsewhere, such as cdn.ampproject.org, a relative URL no longer points to its intended canonical. Instead use an absolute URL.

In my experience, after the logo issue, the plugin should show errors more often related to embedded content, especially on sites that make extensive use of embeds.

Some sites also have problems with WordPress and AMP specific coding. But when you click on each AMP error in Google Search Console, it will show the problematic coding, although it is not very intuitive to do for those without experience with coding.

But it's great to see Taylor (and others) continue to help webmasters who are still having issues with AMP implementation.