Free AMP Validator: Test Your AMP Pages
Validate up to 5 AMP pages with the official AMP validator. See every error and warning, a required-markup checklist and whether your AMP and canonical pages are linked correctly.
- ✓ Free
- ✓ No sign-up
- ✓ Official AMP validator
- ✓ 5 URLs per check
- ✓ Paste HTML
- ✓ CSV report
By Sheikh Shadi Shuvo, Founder of Backlink Express · Updated
AMP in one sentence
AMP is an open-source HTML framework for fast-loading pages. Google still indexes AMP pages, but since July 2026 it treats them like any other page and no longer serves them from its AMP Cache.
How to validate an AMP page
- Enter up to 5 URLs. They can be AMP pages, or normal pages that link to an AMP version.
- Or paste HTML to test an AMP page before it's published.
- Click "Validate AMP". You'll see PASS or FAIL, a markup checklist, and every error and warning with its line number.
- Fix errors first, then download the report for your developer.
What this AMP validator checks
- Full AMP validation with the official validator: every tag, attribute, script and CSS rule.
- A required-markup checklist of the 8 things every AMP page needs (below).
- AMP discovery: if you enter a normal page, we follow its rel="amphtml" link to the AMP version.
- The link pair: whether the AMP page's canonical points back to the original page.
Required markup for a valid AMP page
According to the AMP documentation, every AMP HTML page must have:
| # | Requirement |
|---|---|
| 1 | Start with <!doctype html> |
| 2 | A top-level <html ⚡> or <html amp> tag |
| 3 | <head> and <body> tags |
| 4 | <link rel="canonical" href="…"> in the head |
| 5 | <meta charset="utf-8"> as the first child of the head |
| 6 | <meta name="viewport" content="width=device-width"> in the head |
| 7 | <script async src="https://cdn.ampproject.org/v0.js"></script> in the head |
| 8 | The AMP boilerplate CSS in the head |
Source: amp.dev, 'Create your AMP HTML page: required markup' (checked October 2026).
AMP errors vs warnings
- Errors make the page invalid AMP. AMP-specific features and platforms that rely on valid AMP won't treat it as AMP.
- Warnings flag things that should be fixed (often deprecated usage) but don't make the page invalid.
Google's AMP documentation still asks that AMP pages be valid so they work as expected for users.
Common AMP errors and how to fix them
| Error (paraphrased) | Fix |
|---|---|
| The tag 'img' may only appear as a descendant of tag 'noscript' | Replace <img> with <amp-img> and give it width, height and layout |
| The mandatory attribute 'height' is missing in tag 'amp-img' | Add width and height (or a layout that doesn't need them) |
| Custom JavaScript is not allowed | Remove your own <script> tags; use AMP components or amp-script |
| The attribute 'style' may not appear in tag … | Move inline styles into <style amp-custom> |
| Author stylesheet too large | Shrink the CSS in <style amp-custom> to fit AMP's limit |
| Missing required extension script | Add the <script custom-element=…> for each AMP component you use |
| Disallowed tag (iframe, form, video…) | Use the AMP version: amp-iframe, amp-form, amp-video |
| Missing AMP boilerplate | Copy the exact boilerplate CSS from the AMP documentation |
Linking AMP and canonical pages
Search engines find AMP versions through a pair of links:
- On the normal page:
<link rel="amphtml" href="https://example.com/post/amp/"> - On the AMP page:
<link rel="canonical" href="https://example.com/post/"> - Standalone AMP pages (no separate normal version) still need a canonical, pointing to themselves.
Enter the normal page's URL in the tool and it checks both directions for you.
Does Google still use AMP in 2026?
Yes, but it no longer gets special treatment. Here's how it changed:
| When | Change |
|---|---|
| 2021 | AMP no longer required for Top Stories; the AMP badge was removed from results |
| 1 July 2026 | Google Search sends users directly to the publisher's AMP pages instead of the Google AMP Cache; signed exchanges and AMP Cache updates no longer needed for Google Search |
| Today | Google indexes AMP pages like other pages and says AMP content ranks just like any other web page |
Sources: Google Search Central AMP documentation and 'Latest updates' log (checked October 2026); Search Engine Land and Search Engine Journal coverage of the 2021 changes.
What this means: keep AMP valid if you use it (for Google, Web Stories or other platforms), but don't expect a ranking boost. If you're starting fresh, a fast regular page meets the same bar. Check your page's other basics with our Schema Checker and Google Index Checker.
Should you keep or remove AMP?
| Your situation | Suggested approach |
|---|---|
| AMP pages are valid and your regular pages are slow on mobile | Keep AMP for now; fix the regular pages' speed first |
| Regular pages already pass Core Web Vitals | AMP adds upkeep without a ranking benefit; removing it is reasonable |
| AMP pages have many validation errors | Either fix them or remove AMP; broken AMP helps no one |
| You use Web Stories or AMP-only features | Keep AMP and keep it valid |
| AMP versions are missing content, ads or tracking | Users get a worse page; fix parity or remove AMP |
Our guidance, based on Google's AMP documentation and the July 2026 AMP change.
How to remove AMP safely
- List your AMP URLs (for example with our Sitemap URL Extractor or your AMP plugin settings).
- Remove the rel="amphtml" link from your regular pages so search engines stop discovering AMP versions.
- 301-redirect each AMP URL to its regular (canonical) page, so visitors and links aren't lost. Google's documentation recommends redirecting AMP URLs when you remove AMP.
- Deactivate the AMP plugin (on WordPress) only after the redirects work.
- Watch Search Console: the AMP report will empty over time, and the regular pages should be indexed in their place.
Always back up the site before you change redirects or remove a plugin.
Other ways to validate AMP
- Browser console: add
#development=1to an AMP URL and open developer tools. - Command line: install the validator with
npm install -g amphtml-validatorand run it on a file or URL. - Search Console: the AMP report shows issues across your whole site; Google recommends URL Inspection to confirm indexing.
- AMP's web validator and browser extension give the same results as this tool.
About this tool
- Engine: the official amphtml-validator package (the AMP Project's WebAssembly validator).
- Formats: AMP web pages (AMP for Email and AMP for Ads use different rules).
- Limits: up to 5 URLs per check, or pasted HTML up to 1 MB. Private and local addresses are blocked.
- Privacy: pages and pasted code aren't stored.
Frequently asked questions
What is an AMP validator?
A tool that checks an AMP page's HTML against the official AMP rules and lists every error and warning. Invalid AMP pages can't use AMP's special features.
Is this AMP validator free?
Yes. Check up to 5 URLs per run, or paste HTML, with no sign-up. You can download the errors as a CSV.
Is this the official AMP validator?
It runs the official amphtml-validator package published by the AMP Project. The AMP docs say all official validation methods produce the exact same result.
Can I check a normal page?
Yes. If the page links to an AMP version with rel="amphtml", we find it, validate it and check that its canonical tag points back to your page.
What's the difference between an AMP error and a warning?
Errors make the page invalid AMP. Warnings point out things that should be fixed but don't make the page invalid.
Does Google still use AMP?
Google still indexes AMP pages like any other page. Since July 2026, Google Search sends users straight to the publisher's AMP pages instead of serving them from the Google AMP Cache, and Google says AMP content ranks just like any other page.
Is AMP a ranking factor?
No. Google applies the same standards to all pages regardless of the technology, and AMP hasn't been required for Top Stories since 2021.
Is AMP dead?
Not officially. Google hasn't deprecated AMP and still supports it, but the benefits that made it popular (the lightning-bolt badge, the Top Stories requirement and Google's AMP Cache) are gone. Many sites now focus on fast regular pages instead.
Do I need signed exchanges or to update the AMP Cache?
Not for Google Search. Google's July 2026 update says publishers no longer need to update the AMP cache or configure signed exchanges.
How do I validate AMP in my browser?
Open the AMP page, add #development=1 to the end of the URL, and open the browser's developer console. Validation errors are listed there.
How do I link an AMP page to the normal page?
On the normal page, add <link rel="amphtml" href="AMP URL">. On the AMP page, add <link rel="canonical" href="normal page URL">. A standalone AMP page should point its canonical to itself.
Should I remove AMP from my site?
If your normal pages are already fast and you don't need AMP for another platform, removing it simplifies maintenance. Redirect AMP URLs to their canonical pages and remove the rel=amphtml links. Google has a guide on removing AMP content.
Can I validate more than 5 URLs?
Run another check. For a whole site, Search Console's AMP report shows issues across all your AMP pages.
More free SEO tools
DR Checker
Check the Ahrefs Domain Rating of up to 5 websites at once.
Spam Score Checker
See the spam score of up to 5 domains, with the signals behind it.
Google Index Checker
Check if up to 5 URLs are in Google, and why a page might not be.
Schema Checker
Find and validate the structured data on any page against Google's rules.
Need links from sites with real authority and real traffic?
Browse manually vetted publishers and order guest posts from one dashboard.
See the marketplaceUses the official amphtml-validator package from the AMP Project. Backlink Express is not affiliated with Google or the AMP Project.