Support » Plugin: SEOPress, on-site SEO » Sitemap ignoring noindex

  • Resolved QROkes

    (@qrokes)


    Category pages that have been manually set to “noindex” in SEOpress are still included in sitemap. This is causing Google Search Console to send a lot of errors because we are sending URLs (in sitemap) with “noindex” metatag.

    Please, fix this as soon as possible to stop Google from sending emails reporting these errors.

Viewing 7 replies - 1 through 7 (of 7 total)
  • Yes. I am also facing the same issues with categories. I came to know this today morning, when Search console thrown errors. After diagnosing, it seems that either permalinks are not being flushed, or sitemap generator is somehow broken.πŸ™

    Also, XML Image Sitemaps option does not seem to be working. I am not seeing any image sitemap in the source code of my sitemap.

    Plugin Author Benjamin Denis

    (@rainbowgeek)

    Hi,

    @qrokes go to SEO, XML sitemaps, Taxonomies tab to globally include or exclude post categories.

    By default, we exclude any content (post, page, post type, term) set as noindex “individually” (not globally).

    @abhidesh128 to see your Image sitemaps you have to open one of your sitemap (eg: post sitemap) and look at its source code to see the image tags πŸ™‚

    Thread Starter QROkes

    (@qrokes)

    @rainbowgeek Please, check this issue, categories that “individually” have been set as “noindex” are included in the sitemap. This is causing a lot of errors in Google. This bug was recently introduced. This is a critical issue!

    And please, don’t mark as resolved an issue when it’s not really resolved.

    Plugin Author Benjamin Denis

    (@rainbowgeek)

    @qrokes we double check this and we saw the issue.
    It happens for term taxonomies only.
    Quick fix: edit wp-seopress/inc/functions/sitemap/template-xml-sitemaps-single-term.php and relace line 123 with this line:

    if ( ! get_term_meta($term->term_id, '_seopress_robots_index', true) && ! get_term_meta($term->term_id, '_seopress_robots_canonical', true)) {

    It will solve the issue.

    This patch will be added in our next update.

    ETA: January 2022

    Thread Starter QROkes

    (@qrokes)

    Thanks a lot!
    You should consider a quick release for this one.

    Regards.

    Thanks @rainbowgeek for your reply and resolving the issues.

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