Amp errors in Google Search Console & How to fix Google amp crawl issues
The AMP format is suitable for all types of static web content such as news, recipes, movie listings, product pages, reviews, videos, blogs & more. AMP users like content that loads fast & without fuss, using AMP makes it more compelling for people to consume & engage with your content on mobile devices, 40% of users abandon the site that takes more than three seconds to load.
Google Accelerated Mobile Pages
Accelerated Mobile Pages (AMP) is a type of HTML optimized for mobile, It enables pages to load extremely fast on a mobile device. with the use of AMP markup, The site can present a separate version of a page optimized for fast delivery on mobile, AMP pages are a one-size-fits-all solution you should use across your entire site, you should click on each AMP error in Google Search Console, and it will show the problematic coding, although it isn’t very intuitive for those inexperienced with coding to figure some of them out.
Mobile is the future of the search, Over 53% of all searches online happen on mobile, Google search algorithm will embrace a full mobile-first index, which means it will separate & prioritize the mobile experience over desktop, Speed & responsiveness are crucial to SEO across all devices, but especially on mobile, mobile devices will be accessing the internet via cellular networks on data plans that may or may not have monthly data caps on them.
How Google AMP works
Certain AMP pages may show up in a special content carousel at the top of the SERPs (search engine results pages) for certain keywords. On putting restrictions on what kinds of HTML tags, CSS, and JS can be used on an AMP page, the number of visuals & other complex elements that can be present is highly limited, Readability of text is the main emphasis of AMP pages, It tends to work best for short-form text-centric content like news & blogs.
Some kinds of AMP pages will not work well such as complex conversion pages, Interactive Tools, and video-heavy pages. When conversions on your site are driven by monetization flows or other middleware-driven forms, those pages may not render within AMP’s restrictions on complex JS, Strict rules on file sizes & JS make it difficult to run large videos or the interactive tools on AMP pages.
Not all mobile search queries generate an AMP carousel, Creating an AMP-enabled version of a page won’t eliminate the fully-featured version, The mobile visitor who lands on your AMP page will navigate back to the original version, brands should optimize for mobiles – such as responsive design, image & video file size minimization, and fast loading – on your standard pages, your site must be HTTPS for your AMP pages to show up.
Is AMP suitable for your site?
AMP-enabled pages outperform non-AMP pages even when the search results are not showing AMP results, This is due to the improvements in the speed of sites that are AMP-enabling achieve. When you’re in the process of optimizing for mobile, your priority should be compressing images, minifying CSS and JS, removing extraneous code, and doing anything else to improve your overall site speed.
So, You should determine which site sections receive the most mobile organic traffic, you should evaluate whether the content on those pages would still benefit users within AMP’s more limited environment, You can conduct keyword research to see whether those pages’ target keywords are AMP preferred. You should implement AMP pages only if you’re confident they will enhance the experience for the visitors engaging with your content, not as an attempt to “beat the algorithm” or find a shortcut to the top of the SERPs (Search engine results pages).
How to Fix Common AMP Errors
The best Plugin is AMP for WP-Accelerated Mobile Pages, where you can add the logo, while on adding the AMP plugin, it offers an error in the webmaster because it does not add the logo, and you can check the site in Google structured data testing tool, Although you can install the AMP for WP-Accelerated Mobile Pages, it doesn’t work smoothly (at least, if you use conflicting plugins like Yoast or Monarch), You have a single option: you should place all the necessary tags and code manually which takes time or you can add Glue for Yoast SEO & AMP.
To detect AMP errors, you should select some articles, add amp/ to the link and run the page through the AMP HTML validator to preview & validate, You can open your page in your browser, You can add “#development=1” to the URL, for example, https://example.com/#development=1, You can open the Chrome DevTools console, with mobile device mode emulation enabled, and check for validation errors & make the appropriate fixes.
You can check AMP schema.org Article markup properties in the Structured Data Testing Tool, you can ensure that the NewsArticle, Article, or VideoObject Rich Snippet is present. The changes to your AMP pages take about a week to be updated in Search Console, Only valid AMP pages will show on Google Search. You should view an error report which can be found by clicking ‘Accelerated Mobile Pages’ under ‘Search Appearance’, This gives an overview of your site before narrowing onto any specific errors, you can fix them which only requires a few tweaks to templates or any other plugins used.
You should check the Structured Data Testing Tool, When you have a logo which doesn’t meet the AMP criteria, Every page will show an error message, It’s a stumbling block that impacts many users when starting out, You may have seen the error “A value for the logo field is required”, So, the logo should be updated & resized, You have to make sure that your logo ‘image’ attribute is within 600 x 60, This should fit in the UI guidelines for logos in the carousel.
You should check AMP HTML page linking, You have to check the external resources, the errors are caused by embedded content which can be frustrating for those sites which include a lot of links to external resources, so, you should fetch any URLs of all embedded iframes, videos, custom fonts, pixels, analytics, ads, etc, and similar content the HTTPS scheme.
You should not use “protocol relative URLs”, this might cause problems when the article is loaded via the Google AMP Cache. you should use an absolute URL as the relative URL won’t point to the desired canonical. The protocol-relative URL (PRURL) is the method for linking to the website that offers both HTTP & HTTPS, Although HTTPS links should be used for HTTPS-only websites and HTTP links should be used for sites that don’t support HTTPS at all, the Internet Archive supports both protocols and the PRURL could be used when linking to the site.
Although it’s not common, there can be instances where a plugin error is caused by HTML page linking, For those that have a customized AMP solution, it could be worth checking through links, you should ensure that there is a rel-amphtml link showing on the canonical page along with a rel=canonical on the amp htmp page, in cases where it is applicable. And all featured images for blogs need to be at least 1200 pixels wide.
AMP logo guidelines
Logos for all AMP pages, including AMP stories should be a raster file, such as .jpg, .png, or .gif, You should not use vector files, such as .svg or .eps. You should not use animation, the graphic part of the logo should be legible on the background color.
For logos used for general AMP pages, not AMP stories, there are different logo requirements for AMP stories, The logo should be a rectangle, not a square, The logo should be in a 60x600px rectangle, 60px high & 600px wide, The publishers should use only one logo per brand that is consistent across general AMP pages, You should use full wordmark or full logo; not an icon.