AMP Checker: Check AMP Markers for Any URL

An AMP checker shows whether a web page carries AMP markers and whether it points to a separate AMP version. Enter a URL and this free tool reports if the page is marked as AMP, if an amphtml link exists, and any basic errors or warnings it finds. It is a quick inspection, not a full validation.

What Is an AMP Page and What Does an AMP Checker Look For?

An AMP page is a web page built with the AMP (Accelerated Mobile Pages) framework, which uses a restricted subset of HTML plus AMP components to keep mobile pages light. A page checker looks for the signals that identify and support that format.

AMP sites usually follow one of two setups:

• Paired pages: a regular canonical page links to a separate AMP version with a link tag whose rel value is amphtml. The AMP version then points back to the regular page as its canonical.
• Standalone AMP: the AMP page is the only version, so it is its own canonical.

This tool inspects the page you enter and reports four kinds of information:

• Whether the html element carries the amp attribute or the lightning bolt symbol, which marks a page as AMP.
• Whether the page contains an amphtml link, and the AMP URL that link reports.
• Errors for a missing AMP boilerplate style or a missing UTF-8 charset meta tag.
• Warnings for a missing viewport meta tag or for legacy elements such as frame, frameset, object, param, applet and embed, which may not be AMP-compatible.

How to Use the AMP Checker

You run the check by entering one URL and clicking one button. The result appears on the same page in a few seconds.

1. Type or paste the page address into the Website URL field. The placeholder shows the format: https://example.com.
2. Use the full path of the page you care about, such as an article or product page, not just the homepage. AMP is applied page by page.
3. Click Check AMP. The button changes to Checking... while the page is fetched.
4. Read AMP Marker Found (Yes or No) and AMP Link Found (Yes or No).
5. If an AMP URL is shown, copy it and run the checker again on that address to inspect the AMP version itself.
6. Review any items listed under AMP Errors and AMP Warnings, then fix them in your page template.

If you leave out http:// or https://, the tool adds https:// for you.

Worked Example: Checking a Paired AMP Setup

Say you publish a blog post at example.com/blog/trail-shoes and your platform also generates an AMP copy at example.com/amp/blog/trail-shoes. You want to confirm the two are connected.

First, enter the regular post URL. The tool returns AMP Marker Found: No and AMP Link Found: Yes, with the AMP URL listed as example.com/amp/blog/trail-shoes. That is correct: the regular page should not be marked as AMP, but it should advertise its AMP version.

Next, enter the AMP URL. Now you should see AMP Marker Found: Yes. Suppose the result also lists the error "Missing AMP boilerplate CSS" and the warning "Missing viewport meta tag". The AMP page is flagged as AMP, but its head section is incomplete. Add the required boilerplate style and a viewport tag such as width=device-width, then run the check again until the error list disappears.

How to Read and Act on the Results

Each result tells you something specific about one side of your AMP setup. The table below summarizes the common outcomes.

When the AMP link is missing

If you have an AMP version but AMP Link Found says No, search engines have no signal that the two pages belong together. Add a link tag with rel set to amphtml in the head of the regular page, with the AMP URL as its href.

When the AMP URL looks wrong

The AMP URL shown is exactly what the page reports. If it points to a staging domain, a redirect, or a page that returns an error, fix the link in your template. You can test that address with a bulk HTTP status checker to confirm it returns a 200 status.

When errors or warnings appear

Treat errors as fixes to make now. A missing charset tag or boilerplate style will stop a page from being valid AMP. Treat warnings as items to review: a legacy element like embed or object may be fine on a non-AMP page, but it does not belong on an AMP page, where media is normally added with AMP components.

Who Needs an AMP Page Checker?

Anyone responsible for a site that publishes or inherited AMP pages can use this check as a fast first pass.

• SEO specialists auditing a news or blog site can confirm that the paired pages are still linked after a theme or plugin change.
• Developers can verify that a new template outputs the amp attribute, charset and viewport tags before deeper testing.
• Site owners after a migration can find out whether old AMP markers are still being served, or whether AMP was switched off cleanly.
• Content teams can spot-check a handful of URLs without opening page source by hand.

Google no longer requires AMP for Top Stories, as stated in its Search Central documentation, so many sites have removed it. If you are deciding whether to keep AMP, run this check on a sample of URLs first to see where it is still active, then compare against your Core Web Vitals results.

Best Practices and Troubleshooting Tips

A few habits make the results far more reliable and save time when something looks off.

• Check both versions. Run the regular page and the AMP page separately. Each one answers a different question.
• Use the final live URL. Enter the exact address visitors see, including the right www or non-www host and https.
• Test a sample of templates. Check one article, one category page and one product page, because each may use a different template.
• Verify related basics. Use an HTTP header checker to confirm the status code and headers on the AMP URL.
• Do not forget images. AMP pages use amp-img elements, and missing alt text hurts accessibility. An image alt text checker can scan the page for gaps.
• Keep internal links clean. Navigation inside AMP pages should point to working URLs, which you can audit with an internal link checker.

If you see an error message instead of results

• Please enter a valid URL: remove spaces and check for typos in the domain.
• Not reachable as a public address: the page must be publicly accessible. Local, private or password-protected staging sites cannot be checked.
• Could not fetch the URL: the site may be down or may block automated requests. Try again later or check your firewall rules.
• The URL returned HTTP followed by a code: the page responded with an error status such as 404 or 500. Fix the page first, then re-run the check.

If the result surprises you

A page you expect to be AMP may show Marker No because the amp attribute is added by a script after load, or because the URL redirects to the regular page. Open the URL in a browser, view the page source, and confirm that the html tag really includes amp or the lightning bolt in the delivered markup.

What This AMP URL Checker Does Not Do

This tool inspects selected markers and requirements. It does not perform full AMP validation, so a page with no errors here can still fail the official AMP validator. Component rules, custom CSS size limits, script requirements and attribute checks are outside its scope.

It also reads the page's raw HTML source. Content that appears only after scripts run in a browser will not be seen. Finally, it shows the AMP URL the page reports, but it does not display the canonical link, so check that tag in the source of both pages yourself.

Note that the word amp has other meanings. This page is about Accelerated Mobile Pages on websites, not electrical amperage, batteries or multimeters.

Use the AMP checker above to confirm what a page signals today, fix the errors and warnings it lists, and then run a full validation before you rely on AMP. For more diagnostics, browse the website audit and performance tools.