Let's now fix the "Soft 404" error.
Once more, pick the URLs with the "Soft 404 error".
Seems the loading of the first page on the list is very okay.
Let's use the "Fetch as Google" button once more and see if the page can be accessed okay by Googlebot.
The next step is choose the "Fetch and render" button. This is what refers Googlebot to the page. It also renders the page to make you see it the way Google sees it.
Now, Google found this page again for indexing.
Also see how the page is rendered by Google.
Below are some resources shown by Google. They are resources that Google cannot see completely, but only users can see.
Now click on Fetching to view the active HTTP status code.
What does the 200 status mean? It simply means that the page was found by Googlebot and is available for indexing.
And any time Googlebot is dropping by, it should index the page.
Join the Discussion
Write something…
Makinitwork
Premium
Hi Israel, I have 708 URL errors left from a deleted online shop. Can I remove them via the Removal option on Google Search Console? Site support hasn't said they can't help as such but are sending me options that are not working or out of date. Can I do a redirect? Jen
terri2018
Premium
Hi Israel, This is very helpful, thank you!
I followed the steps in your training, but I'm not sure what I need to do with this part.
Googlebot couldn't get all resources for this page. Here's a list:
URL
https://syndication.twitter.com/settings
Type:
Resource
Reason:
Blocked
Do you think this has something to do with my Twitter icon?
Thanks again.
I followed the steps in your training, but I'm not sure what I need to do with this part.
Googlebot couldn't get all resources for this page. Here's a list:
URL
https://syndication.twitter.com/settings
Type:
Resource
Reason:
Blocked
Do you think this has something to do with my Twitter icon?
Thanks again.