Skip to main content

Tag: Google AMP issue

Content mismatch: Missing embedded video (Solved)

Ned Leave a comment

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).

Disallowed tag present (Google AMP issue)

Ned 3 Comments

Google AMP (Accelerated Mobile Pages) helps you to make your website faster and more compatible across different browsers and devices. Most of the time it works silently, however, it may need your interruption for certain issues. “Disallowed tag present” is one of those issues.

Once the Google Search Console detects this issue, you will receive the email below. Click “Fix AMP issues” button to go to your dashboard and view error details.

New AMP issue detected for site
Search Console has identified that your site is affected by 1 new AMP related issue. This means that AMP may be negatively affected in Google Search results. We encourage you to fix this issue.
New issue found: Disallowed tag present.

Disallowed tag present email

In your Search Console dashboard, the issue looks like the screenshot below. Click the page name to see which tag caused this issue.

Disallowed tag present error in Search Console

Getting “Custom JavaScript is not allowed” error? Check this post out.

Fix “Disallowed tag present” issue

As the error message states, this issues occurs when there is an unsupported tag in your page. Therefore, the obvious fix is that removing this tag. For more information about this error message, check the AMP Project’s website.

In my case, the tag caused this error was approute. I placed this tag into my page as a code example. However, the text block got broken so the browser tried to render this code. Once I fixed the block, the issue disappeared.

Disallowed tag present code block
The invalid text block that caused “Disallowed tag present” error

Note: You should click “Validate Fix” button in the Search Console once you fix the issue. So that Search Console can recheck the page and mark it as AMP compatible. Validation may take hours or days. Make sure to check Search Console later if it is taking a long time.

Seeing “Error in required structured data element” issue? Check this post out.