Sitemap could not be read

#687089
Viewing 5 replies - 1 through 5 (of 5 total)
  • Hello,

    We apologize for the inconvenience you’re experiencing with submitting your sitemap to the Google Search Console. The “Couldn’t fetch” error can be caused by various issues, including sitemap configuration errors or accessibility problems.

    To address this issue, we recommend following these steps:

    1. Rename the Sitemap File: According to John Mueller, changing the name of the sitemap file can resolve this issue. You can do this by heading over to Indexing → Sitemaps in the Google Search Console and adding a new sitemap with the URL `https://rankmath.com/wp-content/uploads/2023/04/An-example-of-a-properly-configured-sitemap-2.png

    Rename the sitemap file

    1. Add the Correct Site URL to Google Search Console: Ensure that you have added the correct site URL to Google Search Console and verified it. You can refer to this knowledgebase article on adding a URL property to the Search Console.

    2. Add the Sitemap to Google Search Console: After adding the correct site URL, navigate to Indexing → Sitemaps in the Search Console and paste the correct sitemap URL in the Add a new sitemap field.

    Add the sitemap to Google Search Console

    If you’ve followed these steps and are still encountering the error, please let us know, and we’ll be happy to assist you further.

    We hope this helps resolve the issue. If you have any other questions or need further assistance, please feel free to reach out to us.

    Sources:
    Troubleshooting the “Couldn’t Fetch” Error in Google Search Console » Rank Math
    Indexed, Not Submitted in Sitemap – Google Search Console » Rank Math

    Hello,

    Apologies for the inconvenience.

    For initial troubleshooting, please follow the steps to flush the sitemap cache:

    1. Flush the Sitemap cache by following this video screencast:
    https://i.rankmath.com/pipRDp

    2. Exclude the Sitemap files of the Rank Math plugin in your caching plugin. The cache could be via a plugin or from the server. For plugins or Cloudflare, please follow this article:
    https://rankmath.com/kb/exclude-sitemaps-from-caching/

    3. Disable the transient cache for the sitemap by applying this filter. This will make sure that your XML sitemap always reflects the latest changes on your site:

    /** 
     * Filter if XML sitemap transient cache is enabled.
     *
     * @param boolean $unsigned Enable cache or not, defaults to true
     */
    add_filter( 'rank_math/sitemap/enable_caching', '__return_false');

    If you’re not sure how to add this code, you can follow this guide:
    https://rankmath.com/kb/wordpress-hooks-actions-filters/

    Once done, remove all your submitted sitemaps and resubmit your main sitemap only and give Google some time to recrawl your site:
    https://rankmath.com/kb/submit-sitemap-to-google/

    Hope that helps.

    Anonymous
    Rank Math free

    Hello Team,

    We have tried everything but it is stimm same.

    What else we can do?

    Regards

    Anonymous
    Rank Math free

    Hello Team,

    Kindly advise how can we fic this issue.

    Regards

    Hello,

    Checking our sitemap it seems to be loading fine as you can see from the screenshots below:

    Rank Math support

    Rank Math support

    Please try following this step from this guide and see if that will help: https://rankmath.com/kb/couldnt-fetch-error-google-search-console/#rename-the-sitemap

    If the issue persists, please share a new screen of the sitemap report after you submitted your sitemap there again.

    Let us know how that goes. 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.

Viewing 5 replies - 1 through 5 (of 5 total)

The ticket ‘Sitemap could not be read’ is closed to new replies.