• Resolved euklidis

    (@euklidis)


    Hello,

    it seems google can crawl my articles from 2025, but the sitemap for articles from2024 is not opening or 2024 post types. This is so strange and i really cannot find the root of it.

    The page I need help with: [log in to see the link]

Viewing 11 replies - 1 through 11 (of 11 total)
  • Hi, it may be caused by a server memory issue. Go to Settings > XML Sitemap > Post types (tab) and try two things:

    1. disable as many “expensive” options as you can, start with “Disable automatic priority calculation” and “Update the Last Modified date on each new comment.”
    2. if that does not help, try setting “Split by” to “Month”.

    Alternatively, you could look into increasing your host/server allowed PHP memory. It depends on your hosting provider.

    Thread Starter euklidis

    (@euklidis)

    i don’t think this is the issue. We are taking about a dedicated high performance server. This is not logical. php memory limits are at 2GB

    That does indeed not seem logical in that case. But have you tried option 2? It might turn out that after switching to “Month” that only one monthly sitemap fails, which that might help figure out where it goes wrong…

    Or are you seeing any related errors in the server error log?

    Thread Starter euklidis

    (@euklidis)

    I am afraid that if i do that google will have to recrawl everything again and we are talking about 55.000 articles…

    The data (URLs, lastmod dates etc.) inside the sitemaps will remain the same so even if Google might take a while reading all sitemaps, it will not affect your site indexation.

    But I understand your hesitation 🙂

    How many posts in 2024? Are there many more than other years?

    Thread Starter euklidis

    (@euklidis)

    About 1.000 maybe a bit more

    Okay so much less than other years… Then it seems PHP memory would not be the cause. Do you have access to server error logs?

    Thread Starter euklidis

    (@euklidis)

    Nothing on error logs

    I notice sitemap-posttype-page.xml is showing the same error. Have you tried disabling the options Automatic priority calculation and Update lastmod on comments temporarily to see if that fixes the error?

    To get error messages in a log file, you can activate WordPress debug mode. Set the WP_DEBUG, WP_DEBUG_LOG to true and WP_DEBUG_DISPLAY to false as discussed there. Then visit a failing sitemap to trigger the error. Then find the debug.log file that should appear in your /wp-content/ folder via FTP or your hosting provider file browser.

    Copy and send any fatal errors to me via https://status301.net/contact/

    Thread Starter euklidis

    (@euklidis)

    Strangely there is no error appearing in DEBUG. Just checked the articles, is is about 5.000 -6.000 per year

    • This reply was modified 1 year, 2 months ago by euklidis.

    That is strange… Have you tried disabling (even temporarily) the options Automatic priority calculation and Update last mod date on comments?

    I also noticed that when following greek URLs (the long ones) in older year 2012 to 2017, I get a 403 Forbidden response from the server.

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

The topic ‘Sitemap fails in past years’ is closed to new replies.