Hello @jokes213,
Thanks for reaching out and you need not give up on your site. You mentioned that Google Search Console reported that your URL is not on Google. Usually, Google Search Console will give a reason which will be a pointer. Can you share a screenshot of that notification you got? You can use any image-sharing service like https://pasteboard.co/, https://snag.gy/, https://imgur.com/, https://snipboard.io/, or even upload the screenshot to your own website. Once you upload it to an image sharing service, please share the link to the image here.
We look forward to hearing from you.
Thanks for sharing!
From the screenshot, though the notification says the URL is not on Google, it also mentions it is not due to any errors. For instance, we could not find noindex tags on that page that could prevent indexing. The URL is also in your post sitemap.
Furthermore, it happens that the URL might be known from other sources that are currently not reported. Since Google was able to find the URL but has decided not to index it, we recommend you check out this article for more information as to what other possible steps you can take — https://support.google.com/webmasters/answer/9012289?hl=en
What I think might also be the problem is my website robots.txt. Can you check my website robots.txt and see if it’s set up correctly? @maybellyne
pengreview.com/robots.txt
@jokes213 Thanks for your reply.
We reviewed your robots.txt file and do see that you have two sitemap directives contained within it:
Sitemap: https://pengreview.com/sitemap_index.xml
Sitemap: http://www.pengreview.com/sitemap.xml
If you have already submitted your sitemap to Google Search Console, it’s not necessary to also include the sitemap directive in the robots.txt file as well. Furthermore, we would not recommend having two different sitemaps specified.
You should only be submitting the sitemap_index.xml URL in Google Search Console, and if you are going to include a sitemap directive within the robots.txt file, it should only be the following:
Sitemap: https://pengreview.com/sitemap_index.xml
Thank you, I have updated the robots.txt file.
When I updated my sitemap on the search console the DISCOVERED URLS is 0. Can you help me find out what I am still missing here @devnihil @maybellyne https://pasteboard.co/DiWIp4EBVc67.jpg
Hi @jokes213
Upon checking your sitemap (https://pengreview.com/sitemap_index.xml), it all seems to load the sub-sitemaps as expected. Upon checking your robots.txt file (https://pengreview.com/robots.txt), it also has the default directives, so we wouldn’t suspect that there would be an issue here.
You might have to wait for Google Search Console to update the ‘discovered URLs’ count as the last read date is September 16, 2021. It might take some time for it to scan the URLs listed in the sitemap again.
With that being said, we did a site: search of your website here, and while it is listing valid URLs in the search results, if you try and scan it, it looks like there are also some invalid URLs that have Japanese characters. You might want to take a look at this and see if your website hasn’t been hacked previously. Please note that this isn’t being caused by the Yoast SEO plugin. You may want to read this article to learn more – https://developers.google.com/web/fundamentals/security/hacked/fixing_the_japanese_keyword_hack
Hello,
This thread has been marked as resolved due to a lack of activity.
You’re always welcome to re-open this topic. Please read this post before opening a new request.
Thanks for understanding!
After almost a month the discovered url is still 0. What is going on?
https://pasteboard.co/DXZrh46J7YSW.png
@mikes41720 @devnihil @maybellyne
@jokes213 Thanks for your reply.
The message of ‘Total Discovered URLs 0’ that you see in Google Search Console just means that the URLs contained in the sitemap were already found by Googlebot by other means, instead of via the sitemap. For example, Googlebot may have found the URLs from internal links or possibly from links on another site.
We are going ahead and marking this issue as resolved due to inactivity. If you require any further assistance please create a new issue.
