sbbn

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.

Hi, just wanted to say I also removed two FooGallery widgets and switched briefly over to a different theme and still had the same problem. Any thoughts?

Hello! I made the changes in style.css but it didn’t change anything, unfortunately.

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.

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.

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.

Again, sorry for the delay.

I finally used Health Check and unfortunately even with all plugins deactivated, I still can’t export.

Hello! Thanks for the suggestion, and sorry for the delay — I waited until I updated to 4.9.2 before digging around.

That file is indeed there, I checked it out on CPanel.

Then I disabled these plug-ins one at a time to see if it would help: Updraft, WP-Spamshield, Wordfence, and StopBadBots. I just tried those thinking maybe the problem was a security program accidentally blocking access. Disabling them didn’t solve the problem.

Pretty baffled here. Could there be some kind of conflict with our custom layout?

Okay, I’ve added it and will see what happens. Thanks!

Hmm. I just started using Wordfence too and seeing tons of bots hit that login page when I look at the live traffic. I must have the settings wrong — thanks for mentioning it, it gives me somewhere to start.

The same bots accessing the CSS were trying to access wp-login.php and other similar sites. It seemed sketchy.

That’s the one, thank you! I tried .tagline and several other options but none worked. Much appreciated!

Thank you, that was exactly what I needed! The only thing I had to do was redefine a menu, but otherwise it was pretty much just plug-and-play.

Hi Ben — I’m planning on trying it again when I open my new website in a month or so.

However, on my current main website, any time I update to the new Yoast, my hits and Google rankings drop by about 40% to 50%. (I last tried in mid October so it’s a recent problem.) Since that’s a website I probably won’t have much longer, I think I’ll pass on upgrading Yoast there. I would assume that, once upgrading to the new Yoast, the SEO would improve after a few weeks, or maybe after I review each post to fix the settings to work with the new version, but I don’t really have time for that.

Thanks for your reply. I’ll keep this review in mind and update/change after using it on the new website, but it’ll be a few months before I know how it works.

Thanks apessoa, I’ll check that out.

Thanks to you as well, frizzel, and I’ll check Data Transporter out when I get around to finding a new SEO. I saw your comments to the developer on the other thread this morning — good luck!

Final note: I did just realize after checking my webpage hits that for the days I had the new Yoast SEO, Google wasn’t indexing my website. I was getting 50% of the usual number of hits. My Alexa rank plummeted, too, but no idea if Yoast had anything to do with it.