AMP analysis

Analysis of the AMP version of a website and management of critical issues.

AMP scan

Screaming Frog allows you to analyze Accelerated Mobile Pages (AMP) quickly and efficiently using the official AMP validator to enable bulk validation of URLs.

The analysis highlights common Seo problems and validates them by checking required HTML mark-up, prohibited HTML elements according to the specification, and more.

There are currently three options for analyzing and validating AMP:

  1. Scan a site to check AMP and see the data in the AMP tab.
  2. Upload and check AMP URLs separately.
  1. Scan a Site for an Audit Seo AMP Elements

The first thing to do is to enable the AMP (Crawl + Store) option from the configuration menu and start crawling the website.

Refer to AMP version data

When the crawling process is complete, simply click on the AMP tab, where all discovered AMP URLs are shown and choose from the 17 filters available to identify common SEO or validation issues.

Fifteen of the 17 proposed filters are immediately available to you, while “non-200 Response” and “Missing <html amp> Tag” you can populate by starting the configurable “Crawl Analysis” via “Crawl Analysis > AMP.”

AMP board filters

Below are all of Screaming Frog’s opportunities for granular analysis of the AMP version dinun website.

  • Non-200 Response.
  • Missing Non-AMP Return Link.
  • Missing Canonical to Non-AMP.
  • Non-Indexable Canonical.
  • Indexable.
  • Non-Indexable.
  • Missing HTML AMP Tag.
  • Missing/Invalid Doctype HTML Tag.
  • Missing Head Tag.
  • Missing Body Tag.
  • Missing Canonical.
  • Missing/Invalid Meta Charset Tag.
  • Missing/Invalid Meta Viewport Tag.
  • Missing/Invalid AMP Script.
  • Missing/Invalid AMP Boilerplate.
  • Contains Disallowed HTML.
  • Other Validation Errors.

To learn more about the features of each filter, I invite you to consult the section on the AMP Tab.

Through Crawl Analysis you can easily and intuitively discover all AMP URLs that are not responding with status code 2xx and need to be optimized.

To find out the source of AMP URL errors you simply click on a URL in the top panel of the window and then on the ‘Inlinks’ tab at the bottom.

Remember that ‘amphtml’, are references to a URL through a rel=”amphtml” link found within the header in HTML.

Below is a close-up view of the ‘Inlinks’ tab.

In this example you can see how The html url (https://www.telegraph.co.uk/business/essential-insights/cyber-resilience/) has a rel=”amphtml” link tag to its AMP version (https://www.telegraph.co.uk/business/essential-insights/cyber-resilience/amp/), which, however, has a 404 status code.

At this point, having discovered all the errors between the Html and Html AMP versions, you can export the data using “Bulk Export > AMP” choosing on which focus to begin optimization.

Upload and check AMP URLs separately.

Alternatively, AMP URLs can be checked separately using list mode by uploading a list from file or manually and crawling them.

The most recommended solution is to verify both desktop and AMP equivalent URLs together; this process is possible by loading the desktop versions and changing the Seo Spider configuration according to the following process:

First you need to change the scan to “List” mode.

By default of Screaming Frog the Crawl Depth is set to ‘0’ in list mode, so only uploaded URLs are scanned.

For our purpose this setting will have to be removed, since AMP versions (at scan depth ‘1’) must also be scanned.

Having inhibited a limit to “Crawl Depth” the Spider will analyze all loaded URLs and found links as if it were in the “Spider” crawl mode.

At this point in order to scan only AMP equivalents and not other internal links (otherwise we would have repeated the first option of scanning the entire site described above), all resource and page links must be disabled apart from AMP links.

With this configuration step completed you are able to add the URLs to be crawled and follow the process outlined above.

AMP Tutorial Analysis

Seo Spider Tab