This report helps you fix errors that prevent your AMP pages from appearing in Google Search results with AMP-specific features.
The top level view shows critical issues affecting AMP pages on your your site. Click a specific issue to see pages affected by this issue and issue details.
AMP status report in Search Console - Google Search Console Training
What's in the report
Critical issues: Pages affected by critical AMP issues can't be displayed on Google. A list of critical issues found on your site is shown directly beneath the chart on the top-level page of the AMP report, with the title Why AMP pages are invalid. Click an issue in the list to see pages with the selected issue.
Non-critical issues (warnings): AMP pages with non-critical issues can still be shown on Google if they don't have any critical issues as well. A list of non-critical issues found on your site is shown below the critical issues list on the top-level page of the AMP report, with the title Non-critical issues. Click an issue in the list to see pages with the selected issue. AMP pages with warnings might not be shown with all possible AMP features (such as being shown in a Top Stories carousel). In other words, these pages might only be shown as plain blue link search results.
Page status (valid and invalid pages): AMP pages are either valid or invalid. Valid AMP pages can be shown on Google; invalid AMP pages can't be shown on Google. If a page has any critical issues, it is considered invalid; if it has only warnings, or no issues at all, it is considered valid. You can see a list of valid AMP pages by clicking View data about valid AMP pages below the chart on the top-level page of the AMP report.
What to look for
You should aim for the following numbers in your report:
- Zero critical issues on your site. See recommendations for fixing errors in Prioritize and fix issues.
- The total count of AMP pages on the report (valid + invalid pages) should be close to the number of AMP pages on your site. If not, see Troubleshooting missing AMP pages.
This report isn't a comprehensive list of every AMP page on your site. It displays a sample of your AMP pages to help you understand their overall status and any issues affecting them.The report is limited to 1,000 URLs per issue. It's possible that there are additional pages that we didn't detect or count for some reason.
The report can show only 200 critical + non-critical issues total. If your site has a very long list of issues (whether or not there are active instances), only the top 200 issues, ranked by importance, will be shown.
AMP issues
In addition to standard AMP-specific errors, the report can expose the following additional issues (errors and warnings).
| Issue | Description |
|---|---|
| Content mismatch: Missing embedded video | The canonical web page has an embedded video that is missing in the AMP version. It is usually best to include all the same important content resources in your AMP version as in the canonical web page. Note that the video is detected by URL; if you have two different URLs pointing to the same video, you will see this warning. |
| Image size smaller than recommended size | The structured data in the AMP refers to an image that is smaller than our recommended size. This may prevent the page from appearing with all AMP-related features on Google Search, and may also prevent your Discover cards from appearing with large images (leading to decreased website traffic and user engagement). To fix, use a larger image according to our guidelines. |
| AMP page domain mismatch | The AMP page is hosted on a different domain than its canonical version. This can be confusing to mobile searchers who see one URL domain in search results and a different one when they open the page in the AMP reader. (Does not affect page indexing or ranking.) |
| URL not found (404) | The AMP URL requested could not be found. Learn about fixing 404 pages. |
| Server error (5XX) | Unspecified 5XX server error when requesting the AMP page. Learn more about server errors. |
| Blocked by robots.txt | The requested AMP URL was blocked by a robots.txt rule. If this is not what you want, test your robots.txt file for the blocking rule, and then modify or remove the rule (or ask your web developer to do it for you). |
| Crawl issue | Unspecified crawling error for the AMP page. Use the URL Inspection tool on your AMP URL to troubleshoot the problem. |
| Referenced AMP URL is not an AMP | A canonical page references an AMP that is not, in fact, an AMP page. Learn how a non-AMP page should reference an AMP page. |
| Referenced AMP URL is self-canonical AMP | The canonical page points to a stand-alone AMP. You cannot reference a stand-alone AMP as the AMP version of a page. Learn how to reference an AMP from a non-AMP page. |
| URL marked 'noindex' | AMP is blocked by a 'noindex' directive. Google cannot index a page that is blocked by noindex; either remove the noindex directive, or remove the reference to the blocked page. |
| 'unavailable_after' date for this page has expired | AMP page has an "unavailable_after" meta tag or directive that has already passed, indicating that it should no longer be served. You should either update the tag to a future date, or remove the tag. |
| Canonical points to invalid URL | A canonical page references an AMP version using an invalidly formatted URL. Learn how to properly reference an AMP version. |
| amp-story canonical error |
A page incorrectly references an amp-story page as its AMP version. This is not allowed because an amp-story page is, by definition, self-canonical: it must point to itself with a |
| Module script declared without nomodule alternative (or the reverse) | You are using either a  New to Search Console? Never used Search Console before? Start here, whether you're a complete beginner, an SEO expert, or a website developer. Search Clear search Close search Google apps Main menu |