• Hello,

    I added my sitemap to Google search console, but I got a message “couldn’t fetch”

    I also precise that my website has a lot of posts (+50,000) and your plugin doesn’t seem to split the sitemaps. It’s one big page.
    Thanks.

Viewing 11 replies - 1 through 11 (of 11 total)
  • Plugin Author xmlsitemapgenerator

    (@xmlsitemapgenerator)

    Hello.

    Did it give any more specific reason?
    Are you able to navigate to the sitemap in your browser and see it?

    A common issue is permalink settings:
    https://blog.xmlsitemapgenerator.org/2016/06/troubleshooting-your-wordpress-sitemap.html

    This is correct. We do not split the sitemap, it is generated dynamically on request as one big file.

    Thread Starter vmackey1

    (@vmackey1)

    Thanks for your reply.
    The permalink settings isn’t set to plain. And yes I can see the sitemap by browsing it.

    The only precision the google console is giving me is:

    “General HTTP error
    We encountered an error while trying to access your Sitemap. Please ensure your Sitemap follows our guidelines and can be accessed at the location you provided and then resubmit.”

    Any idea?

    Plugin Author xmlsitemapgenerator

    (@xmlsitemapgenerator)

    Are you able to share your sitemap address so I can take a look?
    If you don’t want to share it here you can send it via our support page :
    https://xmlsitemapgenerator.org/contact.aspx

    Thread Starter vmackey1

    (@vmackey1)

    Thank you. I have sent you a message through your support system with the sitemap address.

    Plugin Author xmlsitemapgenerator

    (@xmlsitemapgenerator)

    Thanks. I just tried it and it does work. It may have timed out for google as it did take a while. It could be a combination of the server and size of the site when trying to produce the sitemap. How many pages are there in your site?

    Thread Starter vmackey1

    (@vmackey1)

    I see. The server is quit big. And there is 30000 posts. And a lot of categories (I think approx 20000).

    Plugin Author xmlsitemapgenerator

    (@xmlsitemapgenerator)

    I’d have thought that should be okay then. But like i said it was a bit slow to come back with the results.

    We don’t support scheduled production of sitemaps to caching, although it is something we are looking at. If you have a caching plugin this might help with the issue.

    Unfortunately I’m not sure there is much more I can suggest right now. One thing I will do is look at if there are any performance improvements we can make to the current code, but that will take a while.

    sorry I cant be of more help.

    Thread Starter vmackey1

    (@vmackey1)

    I have indeed a caching solution installed. But I’m not sure it’s taking the sitemap in consideration. I’ll have to see.

    Yes, I think an option to split the sitemap would be necessary for big sites like mine. They say that the best solution is to set 1000 posts per sitemap.

    I hope you can add this functionality.

    Regards,

    I’ve been following this post, and I just read something that might interest you both.

    Apparently, WP 5.5, due out the 11th of this month, is going to feature sitemaps in core.

    According to that article, “Each sitemap file contains a maximum of 2,000 URLs per sitemap, when that threshold is reached a new sitemap file is added.”

    Thread Starter vmackey1

    (@vmackey1)

    Thanks for the tips @linux4me2

    Plugin Author xmlsitemapgenerator

    (@xmlsitemapgenerator)

    The main difference with our sitemap generator is the ability to configure defaults per category / tag and to be able to edit at a page level.

    Most users probably don’t want this level of control and so there are other simpler plugins etc. The same is true of the new wordpress feature:

    “Are there any UI controls to exclude posts or pages from sitemaps?
    No. User-facing changes were declared a non-goal when the project was initially proposed,”

    So you only really need to use our plugin if you want proper control / flexibility with your sitemap.

    We will look at index feature, it might be something easy to implement. we might be able to implement some basic caching too, to aid performance.

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

The topic ‘Google Search Console – Couldn’t Fetch’ is closed to new replies.