AMP with structured data, AMP Warnings, AMP Errors & How to Fix AMP Errors
Established AMP websites with AMP errors can cause serious drops in website traffic if left unchecked, Mainly due to Google treating AMP errors like a 404 page not found or server errors, So when the website had AMP pages ranking keywords on page 1 last week and when those AMP pages contain AMP errors, The keywords that the website was ranking for mobile will drop.
AMP with structured data
AMP can be a stand-alone canonical that serves all traffic, so, there’s no need to have a separate desktop or mobile sites, You have to add structured data to your content that may make your page eligible to appear in carousels and rich results, However, being eligible for a certain Search feature doesn’t guarantee display of that feature.
AMP is not a ranking signal, Google Search is using mobile speed as a ranking factor, but sites can be fast by using a variety of techniques, including AMP, Google Search discovers the AMP pages by using sitemaps to notify Google of new and updated pages.
Your page isn’t surfacing in the top stories carousel because the page hasn’t been indexed, the page didn’t make it to the carousel, Googlebot has to crawl all the documents, including AMP, within the server’s crawl budget to avoid causing issues on your site.
The AMP report and the Index Coverage report are different, This is because they have different purposes that Index Coverage report provides an overview of indexed documents from the host and other reports are more about identifying issues on the host.
How to Fix Common AMP Errors
Categorized webmasters and SEO professionals had issues with figuring out AMP errors & AMP warnings, all resulting in stress about AMP valid pages being indexed. AMP pages that prevent Googlebot from crawling are considered an AMP error, AMP warnings in Google search console will not prevent AMP pages from showing up in SERPs (Search engine results pages), but if left untreated the issue could result in Googlebot not crawling the AMP page.
AMP pages are valid but with warnings and errors
AMP warnings will keep you occupied long enough as it is, So if other website indexing issues need to be fixed or keyword ranking problems are present, handling them 1st is more important, You should address AMP warnings, As many are not easy or clear to fix. Google’s documentation on AMP errors and warnings tend to stop with just errors, Since AMP is a Google project and Google has a lot of projects, the information isn’t as readily available as desired.
The error in “the required structured data element” is one of the most common AMP warnings, anything wrong with the schema will trigger this AMP warning, You can use the structured data testing tool to figure out errors in the schema. “The value for the headline field is missing”, Exactly what it says, test the URL and find the headline that is missing and add one. “The featured images aren’t 1200px wide at least”, All featured images for blogs need to be at least 1200 pixels wide.
The problem of “Logo images that aren’t 60px high by 600px wide”, All logo images used in the menu section or header needs to fit inside a 60 pixel high by 600 pixels wide box. “Favicon image isn’t 60px by 60px”, The favicon image needs to be 60 pixels by 60 pixels. “The value for image field is missing”, All of these fields need to be populated with value regardless of being used or not.
URL is On Google but has issues
When you are facing the issue (URL is On Google but has issues), You should fix the above warning in the Google Webmaster Console, You can recrawl the URL from the Google Webmaster Console, You can re-submit the URL and press the request again URL and see if the error is resolved on the fresh crawl, Google has a cached copy of your URL and may have found some issues in the past but it may have got resolved.
You should check the AMP version of the page, Sometimes the Google Webmaster Console can show that the AMP version of the page has issues “(Linked AMP version is valid with warnings)”, AMP-specific features in Google Search results is valid but is not fully compliant with AMP best practices, You should go to the AMP validation website to see if your page has any errors.
You have to add your link/amp/ to the AMP Validation Website, If there are any AMP related issues you should solve them and at times the AMP validation will show that the page has no problems, When your AMP page is valid and Google Webmaster Console is showing a warning, you can ignore it as it again a false positive.
When your page has reported content or manual Google penalty in the Google Webmaster Console, you can click on the link to check if your page or website has any security or manual action warning from Google, you don’t have to worry much about this as they get resolved automatically when Google re-crawl your website, the changes to your AMP pages can take about a week to be updated in the Search Console.
Although this isn’t all of the issues that can happen related to the AMP warning for errors in structured data elements, it’s the most popular. Crawling & indexing an AMP page is the same as crawling and indexing a regular web page. However, if you have AMP errors, especially around the required markup, it will affect the success of your AMP pages being crawled.
AMP is good – but only on mobile!
Some people don’t like the very limited AMP format at all, Amp comes with a simple display on mobile phones and it offers the instant load, But try loading an AMP page on a large screen desktop computer, it was never meant to be displayed on a large display – only on mobile phones. we have to use a simple hand-shaking standard to secure that Google only links to the AMP version of a page with the original page linking to the AMP page and the AMP page linking back with a CANONICAL tag to the original page.
The problem of the Google linking to AMP-pages in search results for desktop users was with a site where the original pages by mistake had been set to NOINDEX with the META-robots tag, It is a mistake by the webmaster, Both the AMP and original version of your pages should be allowed for both crawling & indexing.
Google must fix this problem, The links to AMP pages should never be presented to desktop users. But until Google do this, you can only do one of three things: Live with the risk- until Google fixes this, that some desktop users will get a really shitty experience when Google sends them to the AMP version of your pages – and accept the poor user engagement and conversions, you will probably get out of that, You can implement a server-side solution that checks if an AMP page is requested from a desktop user and 301 redirect them to the original version.
AMP pages – CANONICAL tag not working
The problem of “AMP pages (CANONICAL tag not working)”, when you look at the source of the AMP page, you will see that it has a valid CANONICAL tag back to the original page, when we test the AMP page – in several tools, it is 100% valid. so, No errors.
Valid AMP Pages can fail in Google, “CANONICAL Tag is not (always) working”: Anyone that has been trying to implement AMP on a website knows what a nightmare it can be to get everything right, Google can change the standards without any warnings or proper backward compatibility, the official tools for testing is inconsistent, Google Search Console report AMP Titles as a duplicate problem.
Taking the website traffic for mobile with it, the competitors are trying to improve their search visibility as well, So when one website loses keyword ranking, another website gains keyword ranking, So you should make sure Google product management is part of your SEO services, Google Search Console Issues are always maintained, So if AMP is used, AMP error fixes are part of mobile optimization.