41 views 0 comments

Google Search Console Update: Critical & Non-Critical AMP Errors by @MattGSouthern

by on December 22, 2016
 

‘);
$(‘#sponsored-category-header .sponsored-category-logo’).append(‘ ‘);
$(‘#sponsored-category-header’).append(”);
$(‘#sponsored-category-header .sponsored-category-details’).append(‘

‘);
$(‘#sponsored-category-header .sponsored-category-details’).append(cat_head_params.sponsor_text);

}

});

Google Search Console’s Accelerated Mobile Pages (AMP) report will now differentiate between critical and non-critical errors. Previously, the report would only list all AMP errors with no indication of how serious one error was over the other.

That was not an ideal solution for site owners, because it made it difficult to prioritize which AMP errors to tackle first. A “non-critical” error is a small issue that would be good to fix, while a “critical” error is one that would prevent an AMP from being served in search results at all.



style="display:inline-block;width:336px;height:280px"
data-ad-client="ca-pub-6195106720243437"
data-ad-slot="9231209008">

Here’s an example of how it looks:

Screen Shot 2016-12-21 at 7.15.13 PM

Ideally, AMPs should be error-free, so it’s recommended that both critical and non-critical issues are addressed. Though if time is limited, the new addition to the AMP error report provides a good starting point.

Earlier this week, it was spotted in Google’s data anomalies page that an update was made to Google’s Accelerated Mobile Pages report. Could this be the update Google was referring to?

Read Full Article

Article source: http://tracking.feedpress.it/link/13962/5013323

Be the first to comment!
 
Leave a reply »

 

Leave a Response