Bulk AMP Validator
Validate up to 100 AMP pages with the official AMP validator, and check that canonical and AMP pages point at each other. AMP is optional for Google today. How it Works
Validation
The official AMP validator's errors and warnings, with links to the spec.
Discovery
Regular pages are followed to the AMP version they link to.
Pairing
Canonical and AMP pages point at each other, after redirects and trailing slashes.
A Real Example
Checked 17 November 2026https://amp.dev/
- What the tool found
- Valid AMP, with 0 errors and 0 warnings. Canonical ↔ AMP shows standalone, but not because the page names itself: its rel="canonical" points to https://amp.dev/index-2021/, which is itself an AMP page.
- What to do
- Standalone AMP is allowed, but a homepage should name its own URL as canonical. Pointing it at https://amp.dev/ keeps Google from choosing the older address as the one to index.
Reading the Result
Valid
The official AMP validator passed the page; warnings don't change that. Google can serve a valid, paired page from the AMP Cache, though AMP has been optional for Top Stories since 2021.
Invalid
At least one validator error, each with its line and a link to the spec. An invalid page isn't eligible for AMP features in Google Search: fix the errors or drop AMP.
Not AMP
The URL isn't AMP and has no rel="amphtml", or the AMP URL it links to doesn't serve AMP. For an old AMP URL that now redirects to its canonical page, that is the expected result after removing AMP.
Broken Pairing
The AMP page has no rel="canonical", or its canonical page fails or doesn't link back with rel="amphtml". Google connects the two only when they point at each other.
What it Can't Tell You
- Pages are fetched as HTML without running JavaScript: it validates the markup, not how the AMP runtime renders it or whether Google has the page in its AMP Cache.
- It checks the URLs you give it, not the site. AMP links left in navigation, sitemaps or other pages after removing AMP aren't found.