AMP Validator
Check a public AMP page URL for common AMP setup requirements. The AMP Validator fetches the submitted page from the server, reviews the returned HTML for required AMP markers, runtime, boilerplate, canonical and viewport tags, and script restrictions, then reports an overall valid, warning, or invalid status.
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.
The AMP Validator gives site owners, developers, and SEO reviewers a quick server-side checklist for a public AMP page. Enter the full URL of the page you want to inspect, click Validate AMP, and the tool fetches the HTML, checks for common AMP requirements, and returns a status table for each check.
Use this as a fast first pass before a deeper AMP review. It is not the official AMP validator and it does not guarantee full AMP specification compliance, search ranking changes, Core Web Vitals results, or instant page loading. It is designed to catch missing setup pieces that are easy to overlook when publishing or auditing an AMP template.
How to use the AMP Validator
- Copy the complete public URL of the AMP page you want to check, including
https://orhttp://. - Paste it into the field labeled Enter AMP Page URL.
- Click Validate AMP.
- Wait while the tool fetches and audits the page. The button shows a loading state during the request.
- Review the overall status card for the tested host.
- Use the results table to see which checks passed, failed, or produced a warning.
The submitted URL must be reachable by Digital Domain Kit's server. Private dashboards, localhost URLs, staging pages blocked by login, firewall-protected URLs, and pages behind aggressive bot protection may fail even if they work in your own browser.
What this tool checks
The validator performs a server-side HTTP request with redirects allowed and a 15-second timeout. After the HTML is fetched successfully, it runs six checks against the returned source. These checks are intentionally narrow: they look for important AMP document signals, not every rule in the AMP specification.
| Validation check | What the tool looks for | Result behavior |
|---|---|---|
| AMP HTML Tag | An opening <html> tag with an amp attribute or lightning attribute. |
Fails if that AMP marker is not found in the HTML tag. |
| AMP JS Library | The AMP runtime URL https://cdn.ampproject.org/v0.js. |
Fails if the AMP runtime script URL is missing. |
| AMP Boilerplate | The text amp-boilerplate in the fetched HTML. |
Fails if the required boilerplate marker is missing. |
| Canonical Link | A <link> tag with rel="canonical". |
Fails if a canonical link tag is not detected. |
| Viewport Meta | A <meta> tag with name="viewport". |
Fails if the viewport meta tag is not detected. |
| Script Restrictions | Script tags that point to the AMP CDN rather than non-AMP scripts. | Shows a warning when a non-AMP script tag is found. This warning does not increase the failed-check count. |
How to read the status
The results table shows each validation check with a Pass, Fail, or Warning status. The overall card is based on the number of failed checks, while the script restriction warning is shown separately as a warning signal.
- Valid means none of the fail-counted checks failed. Review any warning rows before treating the page as production-ready.
- Warning means one or two fail-counted checks failed. The page has missing AMP setup items that should be reviewed.
- Invalid means three or more fail-counted checks failed. The submitted page is likely missing core AMP structure or may not be an AMP page.
A Valid result from this tool means the page passed this checklist, not that every AMP component rule, layout constraint, structured data guideline, or search requirement has been validated. For release-critical work, pair this result with the official AMP validator and browser testing.
Inputs, outputs, and limitations
The only input is a URL that passes standard URL validation. The tool waits briefly, then fetches the submitted URL from the server with redirects enabled. If the remote response is not successful, the page shows a message such as Failed to reach the website with the HTTP status. If the request errors or times out, it shows Could not analyze the website.
The output is a page-level AMP checklist for the fetched HTML. It does not crawl alternate AMP URLs, inspect every linked resource, execute JavaScript, run Lighthouse, measure performance, test Core Web Vitals, validate structured data, or simulate Google's indexing systems. It also does not confirm that your canonical and AMP versions point to each other correctly beyond detecting a canonical link tag in the submitted HTML.
Because the audit is pattern-based, unusual but valid markup may need a second review, and malformed markup can hide issues from a simple regular-expression check. Treat the table as a practical triage report: helpful for spotting common missing tags, but not a substitute for a complete AMP compliance workflow.
Server fetch and privacy notes
This tool is server-side. The URL you enter is sent to Digital Domain Kit so the application can request the page and analyze the returned HTML. Do not submit private admin pages, unpublished client URLs, secret preview links, signed URLs, or pages that your policies do not allow an external service to fetch.
The tool analyzes the fetched response for the visible report. It does not provide a file upload control and it does not ask for account credentials. The tested site may still receive a request from Digital Domain Kit's server, and normal web server, security, CDN, analytics, or bot-protection logs on the tested site may record that request.
Example review workflow
Suppose you publish an AMP article template and want a quick sanity check before handing it to a deeper QA process. Paste the AMP page URL into the validator and run the audit. If AMP HTML Tag, AMP JS Library, and AMP Boilerplate all fail, you may have tested the regular canonical article instead of the AMP version, or the AMP template may not be outputting the required AMP document structure.
If the page passes the AMP structure checks but shows a Script Restrictions warning, review the source for ordinary custom scripts. AMP documents have strict rules for JavaScript, and many non-AMP scripts need to be removed, replaced with AMP components, or moved to the canonical non-AMP page.
Troubleshooting
| Problem | Likely cause | What to try |
|---|---|---|
| The form says the URL is invalid. | The value does not pass URL validation. | Use a complete URL such as https://example.com/article/amp/, including the protocol. |
| The tool cannot reach the website. | The page returned an unsuccessful HTTP status, blocked the server request, redirected unexpectedly, or timed out. | Open the URL in a browser, confirm it is public, check redirects, and review firewall or bot-protection rules. |
| The result is invalid for a page that should be AMP. | The submitted URL may be the canonical page, or required AMP markup may be missing from the template. | Confirm the AMP URL pattern, view the page source, and check for the AMP HTML tag, runtime script, boilerplate, canonical link, and viewport tag. |
| The script check shows a warning. | The fetched HTML contains a script tag that is not served from the AMP CDN. | Review whether the script is allowed in AMP, replace it with an AMP component when possible, or remove it from the AMP template. |
| The tool passes but another AMP validator reports errors. | This tool checks a focused set of common markers and does not evaluate every AMP component or rule. | Use the official AMP validator for full specification errors, then use this page again for quick follow-up checks after template edits. |
Related tools
AMP validation is usually part of a broader markup and SEO review. These related Digital Domain Kit tools can help you inspect surrounding page details after the AMP checklist.
- HTML Formatter helps make copied page source easier to read while you inspect AMP tags and scripts.
- HTML Minifier can reduce HTML size after you have confirmed your markup is correct.
- HTTP Headers Parser helps review response headers for redirects, caching, content type, and server behavior.
- SEO Analyzer gives a broader page-level SEO check beyond AMP-specific markup.
- Schema Generator helps create structured data separately from AMP validation.
- Canonical Generator helps draft canonical tags before adding them to templates.
Technical references
- AMP HTML specification
- AMP documentation: validate AMP pages
- MDN: rel canonical
- MDN: viewport meta tag
Editorial information
Built and maintained by Digital Domain Kit. Editorial and technical behavior reviewed September 14, 2026. The current implementation is a Laravel Livewire tool that validates the submitted value as a URL, waits briefly, fetches the page server-side with redirects allowed and a 15-second timeout, then checks the returned HTML for AMP document markers, canonical and viewport tags, and non-AMP script tags. To report a problem with this tool or its documentation, use the contact page.