Bulk AMP Validator
Check a batch of live URLs against the AMP HTML requirements that most commonly break a page — the doctype/⚡ marker, required head tags, the boilerplate CSS, disallowed <img>/inline styles/custom scripts, and the 75 KB custom-CSS cap — with a pass/fail count across the whole batch.
Input
Up to 20 URLs, one per line. Duplicates are ignored.
Output
| URL | Status | Errors | Warnings |
|---|---|---|---|
| No data yet | |||
| URL | Severity | Issue |
|---|---|---|
| No data yet | ||
Guides
What the Bulk AMP Validator does
Paste a list of live URLs and this tool fetches each one server-side and checks it against the AMP HTML requirements that most commonly break a page: the required doctype and ⚡/amp marker, the boilerplate <head> (charset, viewport, canonical link, the AMP runtime script, the boilerplate CSS), the elements AMP disallows outright (raw <img>, inline style="", arbitrary <script> tags, unapproved stylesheets), and the 75 KB custom-CSS cap.
How to use it
- Paste up to 20 URLs, one per line.
- Click Validate AMP pages. Every URL is fetched in parallel server-side (cross-origin HTML can't be read in the browser).
- Check the Summary for a pass/fail count across the whole batch, the Per-page results table for a quick status per URL, and All issues for the exact problem on each page.
What gets flagged
- Errors — things that make the page invalid AMP: a missing/non-standard doctype, a missing
amp/⚡marker, missing charset/viewport/canonical/runtime script, a missing boilerplate stylesheet, raw<img>tags, disallowed<script>tags, an unapproved external stylesheet, or custom CSS over 75 KB. - Warnings — things that work but aren't compliant: a missing
<noscript>boilerplate fallback, inlinestyle=""attributes, or!importantin custom CSS (AMP strips it).
Scope
This checks the requirements that account for most real-world AMP validation failures — it isn't a byte-for-byte port of Google's full AMP HTML specification (that engine is a multi-megabyte Closure-compiled validator, too heavy to run per-request). Treat a clean result as "no obvious AMP violations found," and use it as a fast first pass across a batch of pages before running the official AMP Test on any page it flags.
Why validate in bulk?
A single template bug — a missing extension script, an inline style that crept in — usually breaks every page built from that template at once. Checking one URL at a time hides how systemic the problem is; running the whole batch surfaces it immediately.
Privacy
URLs are fetched by our server only to read their markup and aren't stored. Requests to private or local network addresses are blocked.
Use it from code
From 3 credits per callREST API
curl -X POST https://api.iotools.cloud/v1/tool/bulk-amp-validator \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"urls": "https://amp.dev/documentation/examples/introduct…"
}'Swap in your own key from your account. The tool's fields are the body — no wrapper.
Ask an AI agent
Use the IOTools `bulk-amp-validator` tool (Bulk AMP Validator) on this input:
YOUR_INPUT_HEREPaste this at any agent connected to the IOTools MCP server, then add your input.