Google Indexing Issue When Using Jetpack

Thanks for the report. I’m not quite sure what could be causing this yet.

When using Jetpack, were you using some features that may have had an impact on indexing, like the Sitemap feature?

If you activate Jetpack again today, do you experience similar issues?

found Jetpack was causing this 403 error when Google hit https://shebloggedbynight.com.

Were you seeing this 403 error on the site, or in your Google webmaster console?

Looking at your existing sitemap, I see you’ve switched to using the non-www version of your domain, so that’s the only version of your URLs you should see in your Google webmaster console. Jetpack shouldn’t get in the way of that.

Let us know what happens if you try to activate Jetpack again!

I activated Jetpack a few minutes ago and ran a check through Google Webmaster Tools again, and the 403 error came back. I deactivated and ran the URL Inspection again, and it showed the URL was fine.

When I went to [ redundant link removed ] when I had Jetpack on, it loaded just fine. The problem seemed to be with Google being unable to access the page with its mobile webcrawler. From my end, everything looked fine until I went into my Google Webmaster Console and saw 1 page with an error, and discovered what was going on.

This apparently started back in August, and I have no idea what could have happened in August that started this.

I don’t know enough about sitemaps to really understand them, but I’m pretty sure I used Yoast to generate a sitemap. It’s been a long time but I don’t think I used Jetpack for that.

I don’t know enough about sitemaps to really understand them, but I’m pretty sure I used Yoast to generate a sitemap.

You do indeed appear to be using Yoast, and when you turn Jetpack on, it should respect that and let Yoast continue to deliver its sitemap.

Could you try to activate Jetpack again, and then visit this page and see if there are any differences when Jetpack is activated?
https://shebloggedbynight.com/robots.txt

I cannot think of anything else where Google would be blocked.

Okay, I am officially baffled.

This morning I reactivated Jetpack to test out your suggestion, and robots.txt didn’t change.

But I also tried URL Inspection again out on Google Webmaster Tools and NOW [ redundant link removed ] is available, even with Jetpack activated.

The only change I’ve made since I last posted was I updated a plugin called Redirection, which manages 301 directs and 404s.

I’ll keep Jetpack activated and test with the URL Inspection tool a few more times to see if it sticks.

That’s odd indeed! Let us know if the problem comes up again!

Unfortunately the fix was short lived.

I updated Jetpack to 9.6.1 this morning and started getting “URL is not available to Google” errors again when running URL Inspection on https://shebloggedbynight.com

When I deactivated Jetpack the URL was fine again.

Unfortunately I don’t know what version of Jetpack I was using when this all started, I think 9.6.0 but I can’t be sure.

started getting “URL is not available to Google” errors again when running URL Inspection on https://shebloggedbynight.com

How did the robots.txt file I mentioned earlier looked like when Jetpack is active? Was there anything different there that would be blocking search engines?

I apologize for not getting back to this sooner.

The robots.txt file doesn’t change whether Jetpack is active or not. It’s always this:

User-agent: *
Disallow: /wp-admin/
Allow: /wp-admin/admin-ajax.php

I kept Jetpack off for a few months and enabled it on July 9th and it was fine, until July 17th when I started getting the error on Google Webmaster Tools again. I disabled Jetpack to check tonight and while it was disabled, Google was able to crawl https://shebloggedbynight.com, but turning Jetpack back on made Google unable to crawl or index that top page.

I didn’t do any updates or anything to the website on July 17th so I don’t know what changed. It worked fine for 8 days and then went back to not working again.