Jetpack Blocked Resources Google webmaster (search console)

Other Screenshots “https://prntscr.com/7xxcgm”

These errors appear because you use the Stats module on your site.

You can rest assured, though: such errors will have no negative side-effects, and won’t impact your site or its ranking.

Google’s Blocked Resources Report allows you to spot pages on your site that cannot be indexed by Google. It’s a good way for site owners to make sure there are no pages that Google can’t crawl because of an error, or an unintentional blog.

In this particular case, the resource mentioned in the report is not a page of your site: it’s the tracking code used by Jetpack to record visits on your site.

We’ve recently added a robots.txt file to the domain hosting the tracking code, to ask all bots to not index anything on stats.wp.com. We do so to prevent well-behaving bots and search engines from ever hitting the stats pixel and thus triggering a view in your stats.
Until recently, we maintained a list of these bots and search engines crawlers, and excluded them from the stats, but by adding the robots.txt file it allows us to be more precise, and to improve the accuracy of your stats.

To conclude, you can continue to use Jetpack Stats safely, and ignore these errors. As they’re not related to pages hosted on your site, it won’t have an effect on your site’s ranking in Google and other search engines.

The only effect it will have is a positive one: from now on, Jetpack Stats will block more bots, and consequently give you more accurate stats by excluding more false visitors from your daily views.

In the future, these errors will eventually disappear as we’ve made further adjustments a few days after our initial set of changes. Our new measures remain in place, but we’ve added an extra rule to make no errors get displayed in Google Search Console.

I had also got the same problem,

2014 Nove, moving from wp.com to self hosted, I keep on using jetpack on my selfhosted.

2015 Nove, migration to other hosting company, I keep on using jetpack, and I realized there are some error a week ago, Well actually i dont see any decrease in indexed / search page but i just think if there any way to reset this error… so it is clean on my google analytic dashboard.

Thanks in advance

if there any way to reset this error… so it is clean on my google analytic dashboard.

Google doesn’t seem to offer a way to reset or remove these notices from your Webmaster console. However, we’ve made some more adjustments to Jetpack’s Stats module to allow GoogleBot to access the files:
https://stats.wp.com/robots.txt

We then block the bot from triggering a visit in your stats later, so that doesn’t affect your stats and Google Webmaster Console’s shouldn’t complain about these URLs anymore. If you run a recent version of the Jetpack plugin, no new errors should appear!

Same issues with the latest Jetpack, twentysixteen theme, Jan 2016. Several blocked resources with impact listed by Google as Low (~10) to Medium severity (2), for example /wp-content/plugins/jetpack/modules/photon/photon.js?ver=20130122.

Google is also flagging ‘Crawl-delay: 1’ as an issue in the robots.txt file:
User-agent: *
Crawl-delay: 1
Disallow: /wp-content/plugins/
Disallow: /wp-admin/

Jetpack is great for security and stats, we’d love to keep using it if someone knows how to work around or remove these SEO penalties.

It is also flagging /wp-content/plugins/jetpack/modules/related-posts/related-posts.js?ver=20150408 as a blocked script with ‘Disallow: /wp-content/plugins/’ red flagged in robots.txt:

User-agent: *
Crawl-delay: 1
Disallow: /wp-content/plugins/
Disallow: /wp-admin/

Thanks!

@pro99 These warnings appear because you’ve blocked access to your /wp-content/plugins/ directory in your site’s robots.txt. To get rid of the warning, you’ll need to update your site’s robots.txt file.

You could ignore the warning, since Google doesn’t need to be indexing Javascript files on your site.

Google is also flagging ‘Crawl-delay: 1’ as an issue in the robots.txt file:
Crawl-delay: 1

You can also edit your site’s robots.txt to get rid of that warning. Before you do so, I’d recommend checking why you added this line in the first place. If this was added by a plugin, you can contact the plugin author to find out more.