Google bot gets an instant 301 from homepage - nothing is crawled:(

denis11154

Newbie
Joined
Dec 13, 2020
Messages
3
Reaction score
0
Hello!
Any clue on why it might happen?
The site appears on site: command.
We have recently moved to https: protocol with the help of "Very simple ssl" plugin. (Maybe its connected to the 301?)
The site is crawled just fine with Screaming frog and shows 200 on all pages ( even if crawled as googlebot user agent)
Nothing is blocked with robots.txt
Thanks for the help!

1625425037125.png
 
Have you added the https version of the website to the GSC? It now redirects to the https version, which is crawled and taken separately usually. Just add it as a new version, a new property, same domain just https
 
Have you added the https version of the website to the GSC? It now redirects to the https version, which is crawled and taken separately usually. Just add it as a new version, a new property, same domain just https
1625427252633.png

As you can see it is already on https, do you still think that re adding the property might do the trick?
Thanks for the answer btw.
 
Well that's the first thing I would do. Then I would check out both the .htaccess and robots.txt files to see if the crawler is being redirected from there. But if this all started exactly when you implemented the SSL, then the only issue should be the redirection it caused. And if redirection checkers like https://www.redirect-checker.org/ show a 200 code, then it could be the fact that you have to add the https version of the website in GSC to see the crawler's action.
 
The redirect checker shows 200.
The things is that even on the coverage report u can only see 1 redirected page which is the homepage...
I hope re adding the property will do the job.
Thank you for your time!
1625428726732.png

Well that's the first thing I would do. Then I would check out both the .htaccess and robots.txt files to see if the crawler is being redirected from there. But if this all started exactly when you implemented the SSL, then the only issue should be the redirection it caused. And if redirection checkers like https://www.redirect-checker.org/ show a 200 code, then it could be the fact that you have to add the https version of the website in GSC to see the crawler's action.
 

Attachments

  • 1625428625228.png
    1625428625228.png
    51 KB · Views: 9
Back
Top