Loading...
Loading...
Ready
Enter a domain on the left and run the test. Results stream in here.
Paste any URL. We fetch the live HTML to inspect the document for AMP signals.
We check the html element for the amp attribute and look for a rel=amphtml link to classify the page as AMP, AMP-paired, or non-AMP.
For AMP pages we verify the runtime script, boilerplate, charset, viewport, and canonical, reporting any missing required pieces.
AMP (Accelerated Mobile Pages) is an open framework for building ultra-fast, stripped-down mobile pages. Since 2021 Google no longer requires AMP for the Top Stories carousel or gives it a ranking boost, so its strategic importance has declined. However, many publishers still maintain AMP pages, and they must remain valid to avoid serving broken or non-cacheable content.
An AMP page is identified two ways: the <html> element carries an amp or ⚡ attribute (e.g. <html amp> or <html ⚡>), making it the canonical AMP document; or a non-AMP page links to its AMP version with <link rel="amphtml" href="...">. This tool detects both signals and tells you whether the URL is an AMP page, has an AMP version, or neither.
A valid AMP page must: declare <html amp>, include <meta charset="utf-8"> as the first meta, have a viewport meta with width=device-width, load the AMP runtime via <script async src="https://cdn.ampproject.org/v0.js">, include the AMP boilerplate style, and provide a <link rel="canonical"> pointing to the regular HTML version (or to itself if it's standalone). This tool checks for these markers.
If you have paired pages (a regular HTML page plus an AMP version), the AMP page's canonical should point to the regular HTML URL, and the HTML page should link to the AMP page with rel=amphtml. If the AMP page is standalone (no separate HTML version), its canonical should point to itself. A missing or wrong canonical is one of the most common AMP errors.
No. This is a fast structural check for the key AMP signals — the amp attribute, the amphtml link, the AMP runtime script, the boilerplate, charset, viewport, and canonical. Full AMP validation requires checking every disallowed tag and CSS rule against the AMP spec. For a definitive pass, run Google's official AMP validator after fixing the structural issues this tool surfaces.
Only if the linking is wrong. Done correctly, the rel=amphtml and rel=canonical pairing tells Google the two URLs are the same content, and Google indexes the canonical (HTML) version. Problems arise when the AMP page lacks a canonical, points its canonical to itself while a separate HTML version exists, or the HTML page forgets the amphtml link.
It depends. If AMP already drives meaningful traffic and you can keep it valid, there's no urgency to remove it. For new projects, modern responsive pages with strong Core Web Vitals usually deliver AMP-level speed without AMP's constraints. If you do remove AMP, redirect AMP URLs to their canonical HTML versions to preserve any equity.