If you have recently got a lot of AMP Errors on Google Search Console for your WordPress site, you are not alone.
Google has been focussing on the mobile-friendly experience for users of various websites. For the webmasters who are looking to implement error-free, fast mobile pages, Google has recently added a new feature to its Google Search Console. The newly added feature is designed to help the webmasters to achieve and monitor the Accelerated Mobile Pages or AMP implementation. What is this new feature and how will you resolve the errors reported by AMP errors? Let us take a look at the AMP errors and their resolution.
What are AMP Errors on Google Search Console?
Many of the sites are implementing AMP or Accelerated Mobile Pages for their content. If you are someone who publishes AMP enabled content on your website, Google Search Console has an AMP Error report page for reporting the issues related to AMP implementation. It should be a valuable addition given the fact that many webmasters have been opting for a proper AMP implementation.
The AMP Error reporting essentially lets you check an overview of the status of your site with regards to the AMP implementation of your site. It will guide you to the errors and help you further drill down and analyze the specific errors and then address them. This can be helpful in understanding the requirements that your site needs for a successful implementation of AMP.
If you have decided to opt for AMP error reporting, implementing it on your site may not be a tough task. It must be as easy as installing a plugin. The error reporting feature has not yet been fully implemented. It should soon be available through your CMS and plugin developers.
How to Resolve Google Search Console AMP Errors
Well, like we said, taking care of AMP implementation should be as easy as installing a plugin in WordPress. The plugin will take care of the AMP implementation and handle it on its own. Well, ideally. But, even after that – if you still see a lot of AMP errors, here are a few troubleshooting options you can opt for.
Here are a few fixes you can implement –
- Give priority to the errors reported on the AMP report. You should ideally find a combination of errors and warnings. Pay attention to the issues first.
- The errors may be sorted in the order of severity, date of occurrence, number of pages that have been affected and other aspects. Resolving them in the order of preference available in the default order should be the best option.
- You may find a few errors that may affect a lot of pages. Your first step should be addressing those errors that are causing the issue in multiple pages. They are generally referred to as Common Cause Errors.
- Once you have fixed these standard errors, you can move to the errors that are unique to each page.
You might find a considerable error count, but remember that a single error may cause it, but affect multiple areas of your website.
- Check for the exact nature of an error. If it is a syntax issue, you can check the documentation for the correct syntax.
- Run the validation of each of your affected page. You would need to click on the Inspect icon to address this issue. This will populate all the errors, including the current error. Most of the times, it so happens that you may have fixed the error already, but it may not have been validated because the page has not been re-crawled after the error has been fixed.
- Fix the errors one by one and test each of them one by one. This will ensure that all the fixes will go live instantly.
- Once you are sure that you have fixed all the issues, go for Validate and Update to commence validation of your page. Please note that validation may take a while to complete.
Continue fixing each of the errors one by one. Once you corrected all the errors and validated them, opt for warnings, the warnings can essentially be about missing files and structures.
The Validation Process
Once you have fixed the reported issues and submitted a validation request, it will begin checking your site. If all the reported instances are gone, Google marks the problems as being fixed and pushes the entry to the bottom in the status table.
The validation is done for the issue both at the instance level and the whole site. You need to fix all the instances of the problem for the error report to be shown as being ‘fixed.’
The Concluding Thoughts
The AMP implementation is being observed in many sites. Webmasters of news sites are typically seen to be implementing the Accelerated Mobile Pages implementation. Please note that the issue of AMP is quite massive in its own right. It would not be possible to understand the concept and its execution in a concise article of this nature. However, we would assume that the efforts that we made in that direction would have been of help for your requirements.
AMP issues as notified in the Google Search Console may be of different nature – the major ones being Errors and Warnings. You should invariably attempt fixing the errors and validate them. Unless you implement the AMP correctly, you may end up finding your site not being available in the search results. The tips we have provided on addressing the AMP implementation and sorting out the errors as notified in the Google Search Console can be of utmost importance. While, concerning the warnings, you may get listed in the search results – but still may face issues regarding other essential features.
If you are an expert in the arena of AMP implementation and are aware of any other tips that would be helpful in the proper application of AMP, do share them with us. Since AMP and the error reporting feature on Google Search Console are entirely new, it may be quite helpful for our readers and webmasters alike to implement the tips for a sufficient resolution of the AMP errors.