Analysis of AMP pages, handling of the most common problems and solutions.

Accelerate Mobile Pages

AMP stands for Accelerated Mobile Pages and corresponds to a technology (Web Component Framework) born from the collaboration between Google and Twitter to enable faster loading of web pages on mobile devices. This project, along with the “Mobile First Indexing” orientation, shows how much the Search Engine is targeting the “Mobile” market.

AMP allows you to dramatically reduce loading times compared to traditional pages for a completely revolutionized user experience that can translate into reduced page abandonment, more conversions, leads etc. as well as improving performance, which is one of the most significant ranking signals.

At present AMP includes mainly news sites but it is believed that the application pool over time may increase.

AMP pages are alternatives to traditional pages but follow specific syntactic and markup rules that differentiate them from canonical pages.

Matching link tags between the canonical page and the AMP version are used to notify the Search Engine of the existence of these AMP pages:

In this way when Google scans the canonical page (in the example: it also discovers the AMP verisone ( and, if it considers it valid, includes it in its CDN.

Very important to remember that the simplified version does not negatively impact the Crawling Budget of the website since Google dedicates one for AMP.

The AMP Tab includes all “Accelerated Mobile Pages (AMP)” discovered during the crawl. These are identified through the HTML AMP tag and rel=”amphtml” inlinks.

AMP: filters

To populate this tab you must enable both the “Store” and “Crawl” AMP options (“Config > Spider”).

  • Address: identifies the scanned URL.
  • Occurrences: the number of canonical link tags discovered (either via the link element or HTTP).
  • Indexability: identifies whether the URL is indexable or non-indexable.
  • Indexability Status: identifies why a URL cannot be indexed.
  • Title 1: corresponds to the first title heading on the page.
  • Title 1 Length: displays the length of the title based on the number of characters.
  • Title 1 Pixel Width: displays the width of the page title measured in pixels.
  • h1 – 1: corresponds to the first H1 heading on the page.
  • h1 – Len: displays the number of characters of heading H1.
  • Size: defines the size in bytes of the AMP page.
  • Word Count: determines the total number of words within the body tag excluding HTML markup.
  • Text Ratio: corresponds to the ratio of the number of text characters (“non-HTML”) found in the HTML body tag of a page to the total number of characters the HTML page consists of by displaying the figure as a percentage.
  • Crawl Depth: identifies the distance of the AMP page from the initial crawl page based on the number of clicks. In Seo Spider, redirects are counted as an additional layer.
  • Response Time: displays the time it takes to download the Url. The unit of measurement is the second.
  • The AMP Tab includes two types of filters: the first type related to purely Seo controls, the second type for specifications peculiar to AMP pages.
  • Non-200 Response: identifies which URLs in AMP version do not respond with a 200 “OK” status code. Potential causes could be: blocked by robots.txt, no response, redirects, client and server errors.
  • Missing Non-AMP Return Link: identifies URLs that have an AMP version but do not provide the tag link rel=”amphtml” back to the AMP URL.
  • Missing Canonical to Non-AMP: displays AMP URLs that are missing the Tag Link to canonical URLs or have a Tag Link to another AMP resource.
  • Non-Indexable Canonical: AMP URLs that have non-indexable URLs as canonical are shown. Normally canonical links should be indexable.
  • Not Indexable: identifies “AMP Urls” that are not indexable because they are correctly canonicalized to the desktop version (canonical).
  • Indexable: displays “AMP URLs” that are indexable. AMP URLs that have a desktop equivalent should always be unindexable because they are canonicalized to the desktop equivalent. Only AMP URLs that do not have a desktop equivalent version should be indexable.

AMP: example

  • Missing HTML AMP Tag: AMP HTML pages must contain a top-level HTML or HTML AMP tag.
  • Missing Head Tag: AMP HTML pages must contain the head tag, which is instead considered optional in HTML.
  • Missing Tag Body: AMP HTML documents must contain the <body tag>. This filter displays pages where the tag is missing.
  • Missing Canonical: AMP URLs must contain a canonical tag within the Head that points to the regular (non-AMP) HTML version of the AMP HTML document, or to itself if no such HTML version exists.
  • Missing/Invalid Meta Charset Tag: AMP HTML pages must contain a meta charset=”utf-8″ tag immediately after the <head tag> which is used to encode the page.
  • Missing/Invalid Meta Viewport Tag: AMP HTML pages must contain the meta name=”viewport” content=”width=device-width,minimum-scale=1″ tag within their head tag. It is also recommended to include initial-scale=1 to achieve a responsive viewport.
  • Missing/Invalid AMP Script: the Seo Spider checks that AMP HTML pages contain an async script tag src=”” within their head tag.
  • Missing/Invalid AMP Boilerplate: identifies AMP HTML pages that either do not contain AMP boilerplate code in their head tag or the same is invalid. The AMP-boilerplate code <style amp-boilerplate>…</style> hides the page content by setting the opacity of the body section to 0. After loading the AMP, the system calculates the layout of the page, and the AMP system sets the opacity of the body section to 1 allowing the content to be seen.
  • Contains Disallowed HTML: identifies any AMP URL with HTML that is not allowed for AMP.
Seo Spider Tab