Support » Plugin: Yoast SEO » Sitemap index can be read, but has errors

Viewing 3 replies - 1 through 3 (of 3 total)
  • I have the same problem, is there anyone can help.
    My website has sitemap has been indexed for more than 4 years, but suddenly this error shows up in my search console and guess what, a lot of my valid pages are disappeared in google.
    my website addresss is:
    http://arangweb.ir/
    and the sitemap link: http://arangweb.ir/sitemap_index.xml

    Same thing, it has broken something big time on Nginx. I have thousand of errors and they all started when 5.2.2 came out but nothing changed in WordPress Core so I guess Yoast has a big bug.

    Been running all my WordPress on Nginx for 2+ years nothing has changed but now something catastrophic has been broken.

    The problem …. if you inspect your Nginx error logs is that despite you using permalinks … when the sitemap is crawled /index.php is being added onto the end of every permalink resulting in Yoast telling GoogleBot ALL your pages are 404.

    But if you look at the sitemap itself … it does not have /index.php on the end of the urls. Something internally is causing this.

    • This reply was modified 3 weeks, 4 days ago by  .
    Plugin Support MariusG

    (@marius_codeinwp)

    Hi @anuragbardia1396,

    We’ve inspected your XML Sitemap, everything seems to be working correctly. However, there is one sitemap which does not have the “Last Modified” date, the portfolio-item sitemap. It seems your website has a custom post type portfolio-item which is not meant to be public.

    Please go to SEO → Search Appearance → Post Types → portfolio-item and select No when asked if you want to show them in the search results. Does this fix your error?

    If not, please send us a full-page screenshot from Google Search Console where it shows this error message.

    We are looking forward to your reply.

    @fekrazadeh and @mitchellk, please create separate threads and make sure to include screenshots from Google Search Console too. The error message is pretty generic, it’s possible that these are totally different issues.

Viewing 3 replies - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.