Skip to main content

Crawl Issue (Google Search Console – AMP)

Google Search Console continuously monitor your website’s compatibility with AMP (Accelerated Mobile Pages) recommendations. It sends you email notifications when there is an issue. One of these issues is the “Crawl Issue” which basically means that Google is not able to access to a page in your website.

Crawling means a visit or a series of visits from Google to your website for tracking purposes. Google does this for indexing your website which means potentially showing your website in the search results.

A notification email for the “Crawl Issue” looks like this:

Email notification for Crawl Issue

New issue detected on

Search Console has identified that your site is affected by 1 new issue of type AMP. Errors can prevent your page or feature from appearing in Search results. The following errors were found on your site:

Crawl issue

When you click the link, it takes you to Search Console dashboard which shows the issues and warnings for your website:

Crawl Issue in Search Console

In the dashboard, you may see Disallowed tag present or Error in required structured data element errors as well.

Here is what Google says about this issue.

How to fix the Crawl Issue in Search Console

Follow the 3 steps below to solve this issue:

  1. In the Search Console dashboard, find the URL that is responsible for the Crawl Issue
  2. Enter the URL in the search field at the top of the page and click the Search icon
  3. Click “Request Indexing“. After the indexing is completed, go back to the Search Console and click “Validate Fix
Fix Crawl Issue

URL is not on Google

This page is not in the index, but not because of an error. See the details below to learn why it wasn’t indexed. Learn more

URL might be known from other sources that are currently not reported

Note: It may take a few days from Google to validate the fix. You will receive an email about the result.

Are you seeing “Custom JavaScript is not allowed” error in the Search Console? Check this post out.

Content mismatch: Missing embedded video (Solved)

Google Search Console monitors your website periodically and send you notifications when there is a design or coding issue that may affect your search rank. “Content mismatch: Missing embedded video” is one of these issues that you should pay attention to.

When you login to your Google Search Console dashboard, this is how it looks like:

Content mismatch: Missing embedded video solve
Google Search Console with “Content mismatch: Missing embedded video” warning

Accelerated Mobile Pages (AMP) Project is an initiative to motivate and help developers to build more responsive and fast websites. Google supports this initiatives and encourage people to follow AMP principles for a better web.

Are you seeing “Disallowed tag present” error in Google Search Console? Check this post out.

How to fix “Content mismatch: Missing embedded video” warning

Here is Google’s explanation for this warning:

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.

Source: Google-specific AMP errors

The quickest fix is that having the same content for your web page’s desktop and mobile versions. What-if you don’t explicitly create mobile versions of your pages? (WordPress and many other content management systems do it for you).

In this case, the issue might be a false-positive which means it is not an actual problem but an inaccurate analysis. I had this warning for my blog’s homepage because there is a video in one of my posts. This post shows up in the homepage. However, AMP version of the homepage doesn’t show this video:

AMP site and Missing embedded video warning
AMP version is like how it is supposed to be

This warning went away after I clicked “Validate Fix” in the Google Search Console (I clicked it once the video post went into the second page).