Toolsky

Free Online Tools & Utilities for Every Task.

AMP Validator

Validate your Accelerated Mobile Pages (AMP) for errors.

Why use AMP?

Speed

Instant Loading: AMP pages are optimized for speed and pre-cached by Google.

Visibility

Mobile SEO: Google prioritizes valid AMP pages in the mobile search results carousel.

Experience

UX: Provides a smooth, distraction-free reading experience for mobile users.

Compliance

Strict Standards: Even a single missing mandatory tag can invalidate the entire AMP status.

An AMP page can look perfect in a browser and still not be AMP at all. Accelerated Mobile Pages follow a strict rulebook — restricted HTML tags, required boilerplate, sized images, no author-written JavaScript — and a single violation silently disqualifies the page. This AMP validator checks your page against those rules and reports the specific errors standing between your markup and a valid AMP document.

What AMP Validation Really Checks

AMP is a web component framework built for fast-loading mobile pages. In exchange for speed, it imposes strict constraints: a specific document structure starting with a required boilerplate, AMP-specific components such as amp-img instead of the regular image tag, inline CSS under a size limit, and a ban on most custom JavaScript. A page is either valid AMP or it is an ordinary web page wearing AMP's clothes — there is no partial credit, because platforms that serve AMP content only trust pages that pass validation completely.

The validator parses your page the way the AMP runtime would. It flags mandatory-markup errors, disallowed tags and attributes, missing required elements, and layout problems, typically with references to the line or component responsible. Think of it as a compiler for your page: the errors it lists are the exact items to fix, and a clean result means the document satisfies the AMP specification. The rules themselves are published in the official documentation at amp.dev, which is the reference worth consulting when an error message needs context.

What This Validator Does for You

  • Error-by-error reporting: instead of a bare pass/fail, you get the individual problems to fix, which turns debugging from guesswork into a checklist.
  • Checks real pages: validate the page you actually publish, catching issues introduced by templates, plugins or ad code rather than only hand-written test files.
  • Catches silent failures: invalid AMP rarely shows a visual symptom — the page looks fine while quietly losing its AMP status. Validation is the only way to know.
  • Fast re-checking: fix an error, validate again in seconds, and repeat until the document is clean — the loop professional publishers build into their workflow.
  • Free and immediate: no installation or project setup stands between you and a first result.

How to Validate an AMP Page

  1. Open the page you want to check and copy its URL (or have the page's HTML ready, depending on the state of your project).
  2. Enter the URL into the validator.
  3. Run the validation and wait for the report.
  4. Read the errors from the top: fix mandatory-structure problems first, since one broken requirement can make later messages misleading.
  5. For each flagged component, replace disallowed markup with its AMP equivalent — for example, standard image tags become amp-img with explicit width and height.
  6. After making changes, validate the page again and repeat until no errors remain.
  7. Once clean, run a broader health check on the page with the SEO analyzer to confirm the non-AMP side of the page is in equally good shape.

Typical Situations Where Validation Saves You

The most common story is the theme update. A publisher's AMP templates work for months, then a theme or plugin update injects a standard script tag or an unsized image into the layout, and every article silently drops out of AMP eligibility. Nothing looks broken. Traffic from AMP surfaces fades, and only a validation run reveals that a single disallowed element appeared in the shared template — one fix restores the whole site.

Other regular cases: a marketing team adds a third-party widget or form that uses forbidden JavaScript; a developer hand-writes an AMP landing page and forgets the boilerplate or the canonical link; an ad integration exceeds the CSS limit. In each case the workflow is identical — validate, fix the listed components, re-validate. Teams that also care about how their pages are built more broadly often pair this check with the website technologies check to see what a page is actually loading, or tidy hand-written markup with the HTML formatter before validating.

Limitations and Things Validation Cannot Tell You

A valid AMP page is not automatically a good page. Validation certifies rule compliance; it says nothing about whether the content is useful, the layout is readable or the page converts. Conversely, some real-world problems — a slow origin server, oversized images that follow the rules, a consent banner that harms user experience — sit outside the validator's scope entirely.

It is also worth being clear-eyed about AMP's current role. Google once required AMP for certain news placements, but since 2021 page experience signals apply to all pages and AMP is no longer a prerequisite for Top Stories eligibility. Many publishers still benefit from AMP's enforced discipline and speed, especially on ad-heavy or emerging-market mobile traffic — but the decision to use AMP is now a performance and maintenance choice, not a search requirement. Validate rigorously if you run AMP; just make the decision to run it with current facts.

Frequently Asked Questions About AMP Validation

What does "invalid AMP" actually mean?

It means your document breaks at least one rule of the AMP specification — a missing boilerplate, a banned tag, custom JavaScript, an image without dimensions. Platforms that distribute AMP content will not treat the page as AMP until every error is fixed.

Why does my page look fine but fail validation?

Browsers are forgiving and render almost anything. The AMP runtime is not. A page can display perfectly while violating rules that are invisible on screen, which is exactly why a validator exists.

What are the most common AMP errors?

Missing or altered boilerplate, regular img tags instead of amp-img, images and videos without width and height attributes, disallowed HTML tags, author-written JavaScript, and inline CSS exceeding the size limit.

Do I still need AMP for Google search?

AMP is no longer required for Top Stories or for good rankings generally; fast, well-built regular pages qualify on their own merits. AMP remains an optional framework some publishers keep for its enforced performance discipline.

Can one error invalidate the whole page?

Yes. AMP validity is all-or-nothing: a single disallowed element in a template can disqualify every page using that template, which is why template-level fixes are so powerful.

How often should I validate?

After every template change, theme or plugin update, and new third-party integration — the moments when silent breakage happens. High-volume publishers validate as part of their deployment checks.

What is the difference between errors and warnings?

Errors break validity and must be fixed. Warnings and deprecations highlight things that still pass today — such as components being phased out — but deserve attention during your next maintenance pass.

Trust, but Validate

AMP's bargain has always been strict rules in exchange for guaranteed behaviour. The validator is how you hold up your side of that bargain: run it after every change that touches your templates, fix exactly what it lists, and your pages keep the status you built them for.