What you’ll need
Public URLs or pasted AMP HTML.
Validate AMP markup with the official AMP Project validator.
Free to use · No saved inputsPublic URLs or pasted AMP HTML. New here? Start with “Try an example”.
The supplied AMP markup is validated by this app’s server using the packaged official validator. It is not sent to a third-party validation API.
Public URLs or pasted AMP HTML.
Run the packaged official validator, report line/column errors and check linked AMP/canonical relationships.
Validator version is reported. Valid markup does not guarantee search appearance or indexing.
An AMP page that looks fine can still contain a disallowed attribute, missing component script or invalid structure. This bulk AMP validator gives you specific validation findings rather than asking you to compare markup line by line. Use it when an AMP template changes or a publisher needs to check a set of pages before releasing an update.
Paste AMP HTML or enter the public AMP URLs you want to validate. Keep the non-AMP counterpart available when checking page relationships.
Run validation and inspect each error’s message and line or column where provided. Note the reported validator version with your test evidence.
Fix the relevant template or markup, validate again and review the AMP/canonical relationship before publishing.
Valid means the markup passed the packaged validator used for this run. It does not guarantee indexing, ranking or a special search appearance. A canonical relationship warning is a separate issue from syntax validity, and an unreachable page cannot be treated as validated content.
Use Fetch & Render to inspect the ordinary page version and SEO Before & After Checker when an AMP template release also changes other page signals.
Validator version is reported. Valid markup does not guarantee search appearance or indexing.
Yes. Saved AMP HTML is sent to this app’s server for validation with the packaged AMP validator. It is not forwarded to an external validation API or stored as an input log.
No. It identifies problems. Update the source template or markup and rerun the validator to check that the reported errors have actually been resolved.