Hi there, Prabhat.
Yes, I followed in the screencast here: https://i.rankmath.com/pipRDp
However, I could not follow the second step regarding the caching plugin as it appears they don’t have one installed.
Is there another step I should take before giving you guys access? See the image below.
https://drive.google.com/file/d/1xBYvYqx6ugP-Xk7cmLTKVeTDozXiFfNc/view?usp=sharing
Hello,
Thanks for your reply.
You can give us the access and we would further investigate the issue.
Looking forward to helping you.
Thanks.
Hello,
I have updated the sensitive data as requested. Can you please check further?
Thank you.
Hello,
Thank you for the update, and sorry for the delay.
I’ve tried checking your post-sitemap, and it seems that it is already showing the correct number of your published posts (19).
If it’s still not showing on your end, please clear your browser’s cache or try using a different browser.
Let us know if the issue still persists or you still need assistance with this issue.
Thank you, and looking forward to your update.
Hey there. Thanks.
Why are we still seeing the same sitemap error in GSC?
(See the previous screenshot)
Hello,
It seems that the last read date was not yet updated. In this case, please remove all the sitemaps submitted in your GSC, then resubmit your main sitemap only https://healthexpertsalliance.com/sitemap_index.xml
And give Google some time to recrawl your website. Google will also use this to crawl the other sitemaps.
I hope that helps. Thank you, and please don’t hesitate to contact us anytime if you need further assistance with anything else.
Okay, I did that and it’s still showing errors for now, just FYI. I’ll give Google time as you suggested. Though why do you think the post sitemap is still producing errors?
https://drive.google.com/file/d/1kmzgq1Mn-jddu04IAYOiDW968ck0gpSh/view?usp=sharing
Hello,
Thank you for the follow-up, and sorry for the delay.
The last crawl/read date showing is still April 15th, and the URL count is only showing 6 instead of 19. The errors seem to be pointing to some indexed URLs that are not included in your sitemap, but you can also check those upon clicking your post-sitemap.xml to be sure.
In this case, you may need to give it some time for Google to recrawl your post-sitemap and see if there are still any errors reported to investigate further.
Let us know if the issue still persists after the next crawl date.
Thank you.
Hi guys,
The sitemap was read today and it’s still got the same errors…
Hello,
Thank you for the update, and sorry for the delay.
I’ve further checked your sitemap, and it seems that you haven’t verified the www (or non-www) and HTTP (or HTTP) version of your website.
Please ensure that only 1 version of the sitemap is working (200 Ok status), and the rest are redirecting to it. You can also use this tool to check. Please follow the steps in this link:
https://rankmath.com/kb/couldnt-fetch-error-google-search-console/#5-check-for-the-correct-version-of-the-sitemap
Once done, resubmit your main sitemap /sitemap_index.xml and give some time for Google to recrawl your site.
I hope that helps. Thank you, and looking forward to your update.
Hey Reinelle,
I’m just getting round to this now. I understand the overview of the problem. We need to redirect 3/4 of those sitemap index URLs to just one, which is chosen to be our preferred sitemap. Some questions I have.
1. The two methods you list say how to redirect non-www to www URLs and vice-verser. However, they don’t say how to redirect non-www URLs to non-www URLs. In the case of redirecting our http sitemap to our https sitemap, what method do we need to apply there? Neither seems applicable.
2. The Nginx method you link to from your KB article says that the server (in this case, our client’s server) requires that the server is running Nginx and, if not, links to a guide on setting that up for CentOS 7. Before I go asking for unprecedented access to our client’s servers, is there a way we can be sure that this guide is even applicable to their server setup? I’m kind of out of my wheelhouse with this stuff. Speaking of which…
3. Is this all something for their webmaster or website developer to be doing? If so, I don’t want to send a client instructions on how to perform a redirect on a server system that they may not even be using.
Appreciate you guys.
Hello,
Thank you for the update, and apologies for the delay.
Since you’re using the Nginx server for your site, I would recommend getting in touch with your client’s web host as they are in a better place to help you redirect your website to the final version.
They should also have a redirect format in case the link in our knowledge base doesn’t have the exact configuration for www to non-www or vice versa, as well as the http to https.
I hope that helps. Thank you, and please don’t hesitate to contact us anytime if you need further assistance with anything else.
Thanks, Reinelle.
One last question is, do we need to redirect the website to the final version, or the sitemaps to the final version? I thought we were talking about the sitemaps.
Hello,
Thank you for the follow-up, and apologies for the delay.
You will need to redirect your whole website structure to its final version. In this way, there would be no confusion as well for Google to crawl the correct format of your site.
Upon redirecting your whole website, your sitemap will also be redirected to its final version.
I hope that helps.
Looking forward to helping you.
Thank you.
It looks like the website already is re-directed. Isn’t this how it’s supposed to be set up? The https://httpstatus.io/ screenshot you guys shared earlier was for the sitemap URLs, specifically. They’re all returning 200 codes, not the site URL. See below.
https://drive.google.com/file/d/1RFlu-zXgWBYLU-mhH6unAnNONxKZMKyS/view?usp=sharing
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.
