Bulk AMP Validator

What the AMP validator checks

AMP pages must follow a restricted form of HTML: a required set of tags in the head, the AMP runtime script, AMP components in place of some standard elements, inline CSS within a size limit, and no author JavaScript outside sanctioned components. An invalid AMP page is treated as an ordinary page, so the AMP features you built it for do not apply.

This tool uses the official validator published by the AMP project, the same engine behind the AMP browser extension and the command-line validator. It runs in your browser after the page HTML is fetched by our server.

Validating many pages at once

Paste up to 50 URLs. Three are processed at a time, failed fetches are retried once, and the progress bar counts real completed pages. You can stop at any time and keep the results gathered so far. If you paste the URL of a normal page that links to an AMP version with rel="amphtml", the tool follows that link and validates the AMP version instead.

Pairing AMP and canonical pages

When an AMP page is an alternative version of a normal page, the two must point to each other:

<!-- on the canonical page -->
<link rel="amphtml" href="https://example.com/article/amp/">

<!-- on the AMP page -->
<link rel="canonical" href="https://example.com/article/">

A standalone AMP page, with no separate normal version, uses its own URL as the canonical. The tool fetches the canonical page and confirms that it links back to the exact AMP URL, reporting a missing link, a link to a different AMP URL, or an unreachable canonical page.

Fixing common errors

• Mandatory tag missing. Usually the AMP runtime script, the amp-boilerplate style, the viewport tag or the canonical link. Copy them from the AMP boilerplate in the documentation.
• Disallowed tag or attribute. Replace img with amp-img where required, remove custom scripts, and move event handlers into AMP actions.
• Missing component script. Each AMP component such as amp-carousel needs its own script tag in the head.
• Stylesheet too long. Inline CSS is limited, so remove unused rules.

Is AMP still worth it?

Google removed AMP as a requirement for Top Stories when page experience became a ranking signal, and it ranks AMP pages like any other page. Many sites have retired AMP in favour of fast standard pages. If you are keeping AMP, keep it valid: an invalid AMP page delivers none of its benefits. If you are removing it, redirect the AMP URLs to their canonical pages and remove the rel="amphtml" links.

Pasting HTML

For a template that is not yet public, switch to pasted HTML. Nothing is sent to our server in this mode: the validator runs entirely in your browser on the text you paste. Line numbers in the results refer to the pasted text.