How to use the search console to improve AMP implementation?

Team TypeStack
Team TypeStack ...
Dec 05, 2022  . 5 min read
shareshareshare
share

In this blog, we’ll talk about how to use Search Console to improve your AMP implementation. After finishing reading it, you should be able to understand AMP reports in GSC and find AMP issues Google discovered on your website, fix them, and ask Google to validate your fixes. Before we discuss the Search Console reports, let’s do a quick introduction to AMP.

AMP, or Accelerated Mobile Pages, is an open-source HTML framework that provides a straightforward way to create web pages that are fast, smooth-loading, and prioritize the user experience. It can be used to easily create websites, stories, ads, and more. There are several reasons to use the AMP framework. Web page speed improves the user experience and core business metrics, building AMP pages is simple and reduces developer overhead, AMP has lots of components that can be used as website building blocks and they are already optimized for best performance.

Besides the general benefits of the AMP framework, there are additional benefits for AMP on Google Search, such as serving from the Google cache, and more opportunities to appear in AMP-related experiences.

When Google detects AMP on your website, you'll see a report in Search Console detailing any AMP issues that Google found on your pages. That can be really handy when reviewing your AMP implementation. It will help you focus your efforts on the most important tasks. The top-level view depicts crawled AMP pages with issues found by Google. The default chart shows the trends for AMP errors, but you can click Valid with warnings and Valid to see their trends too. In addition, you will see a checkbox to add the number of impressions your AMP pages got on Search. This can be very helpful to understand how issues affect your results.

Below the chart, you'll find a table with issues grouped by type. AMP pages with an error cannot be shown in search results. For example, your AMP page is blocked by robots.txt, custom JavaScript is not allowed, or the HTML tag has an invalid layout specified by its attributes. Indexed AMP pages with warnings can be shown in Google Search results. But they might not be shown in AMP rich results or the top stories carousel.

Warnings include non-optimal pages or the use of deprecated features that may become errors in the future. Valid AMP pages work as expected for users and can be included in AMP-related features. So, if everything is green, it means you're doing a great job. Issues are sorted by a combination of severity, validation state, and the number of pages affected by default. If you see an error that seems like a result of a bad template, fix it first. Then continue with fixing other unique issues on each page.

Click a specific issue to see more details, with a link to learn more about how to fix it and the process to notify Google about your fixes. You'll also find the list of example URLs affected by this issue. Moreover, to find the exact location of the offending code, you can click a specific URL to find the HTML. If you want to see a full list of errors for a specific URL that is shown in the report, click the Inspect icon next to the URL. This will open the URL Inspection, already discussed in this video series. This test pinpoints all errors, not just the current issue, and provides a code explorer highlighting the errors and providing more information.

It is possible that an error has been fixed on the live page but is still listed as an error because it has not been re-crawled. You can check that by testing the live version of your page in the URL Inspection results. If that's the case, request validation through the AMP issue page. After knowing what is required to be fixed, you have two options: you make the required code changes or share the details with a developer that can execute code changes to your website. You can do that by grabbing a link using the Share button from any issue page.

Note that the sharing link gives access to the current page only, and any validation history pages for this issue. The other pages don’t get access to your resource or enable the shared user to execute any kind of action on your account or property. By disabling sharing for this page, you can revoke the link at any time. Also, it might be a better idea to use the AMP test tool, where you can upload a piece of code to check for issues in addition to testing a specific page. It can be helpful to debug issues for new pages. But note that the tool will check your general AMP implementation without specific information about Google indexing.

After you or your developer fix the error, confirm the fix by inspecting the live version of the page. Then, click Validate Fix from the AMP issue page and Google will validate your changes. The validation process can take several days and you will receive progress notifications by email. If the current instance exists in a sample of pages, validation ends, and the validation state remains unchanged. If the sample pages don’t have any current error, validation will continue with the state Started.

When all error or warning URLs have been checked and the issue count is zero, the issue state changes to Passed. By clicking the validation details link on the issue details page, you can see the progress of a validation request. Hope this blog has helped you understand how to optimize your website by improving AMP warnings and errors. Your users will thank you for that.

success