Hello,
Thank you for contacting the support and sorry for any inconvenience that might have been caused due to that.
That means the website page has been discovered by Google and indexed. However, upon inspecting your website URL in the SERPs, I haven’t found most of the links. If you have recently submitted your sitemap, then wait for few days, and your URLs will show in SERPs.
You can also try to resubmit your sitemap if above fails:
Delete your sitemap in GSC. It will not hurt your SEO in any way.
Learn more about this here: https://support.google.com/webmasters/answer/183669?hl=en
Submit the sitemap again. Make sure to submit only sitemap_index.xml and nothing else.
Okay, I will try to wait for a few more days. If the situation is still the same on Sunday, I will ask for your help again. Thank you for your help.
Hello,
Sure, please do let us know how this goes and we will provide further guidance.
Meanwhile, if you have any other questions do feel free to raise them.
Thank you.
Hello, I checked and chose to check the URL today, and the following information appeared:
No: “noindex” was detected in the “X-Robots-Tag” HTTP header
But I did not select NOINDEX in RANKMATH. Could you please help me to confirm what happened?
Hello,
Thank you for your reply.
That error should not come, as I have manually reviewed all the links inside your sitemap, and they seem to be indexable. That must be an old error. I have even checked the HTTP headers, and I didn’t see any parameter related to X-Robots-Tag.
Could you please share that particular URL in which you are getting this error?
looking forward to helping you.
Hello,
Just wanted to add that on checking your site I did not see any noindex tag within the pages. If it is a No Index error on the sitemaps, then there is nothing to be worried about.
Usually, the noindex detected in the x-robots tag’ is not a problem for the sitemap file itself. It is normal practice to assign the noindex to the sitemap file since you do not want to show the sitemap file itself in the Google Search results.
We recommend waiting for a while to see if the status changes. In many cases, it updates itself to “Success” after a while.
Alternatively, can check if you have another sitemap on your root folder and delete that. Then you can also delete the sitemap in GSC and try to submit it again to Google Search Console.
We hope this clarifies your point. If you have any other questions for us please do not hesitate to raise them.
Yes, I am on my https://www.aaforfun.cf/sitemap_index.xml
See the nodeinx mark, so this does not affect the operation of the sitemap, right?
In addition, the sitemap that I resubmitted is clicked and displayed:
Unable to read Sitemap
Hello,
Thank you for the follow-up, and apologies for the delay.
Yes, the noindex detected in the x-robots tag will not affect your website, nor the operation of your sitemaps.
As my colleague mentioned above, it is normal practice to assign the noindex to the sitemap file since you do not want to show the sitemap file itself in the Google Search results.
If you are still getting the error upon resubmitting your sitemap, please check this link for troubleshooting steps:
https://rankmath.com/kb/couldnt-fetch-error-google-search-console/
I hope that helps.
Thank you, and please don’t hesitate to contact us anytime if you need further assistance with anything else.
I see the example of the first item in the solution, his xml is valid, as shown in the picture below
But when I check my own sitemap, it shows the following situation:
Hello,
Thank you for your reply.
You don’t have www inside your URL, and your domain is redirecting from non-www to www. that is why it’s giving a “text/html” error. Please kindly re-run the with the www prefix.
Looking forward to helping you.
I added www and it still cannot be read normally. A friend told me that noindex is in the header after testing, but the header part is not rewritten in my wp. How can I solve it?
Hello,
The error comes from the non-www prefix URL because your website is redirecting to www. If you visit the URL with the www prefix, you will not get the error. It’s a very common behavior. There is nothing to worry about. Please see the screenshot I have shared below.
Screenshot:
https://ibb.co/cbvv0zT
Looking forward to helping you.
Hello,
Since we did not hear back from you for 15 days, we are assuming that you found the solution. We are closing this support ticket.
If you still need assistance or any other help, please feel free to open a new support ticket, and we will be more than happy to assist.
Thank you.
