Support » Plugin: All in One SEO » WordPress 5.5. Sitemap – Need to disable?

  • Resolved omris83

    (@omris83)


    If using AIO SEO, and the fact the new version of WP comes with a sitemap, do we need to do anything to make sure we only have the AIO Sitemap and not two?

Viewing 15 replies - 1 through 15 (of 17 total)
  • reaxl

    (@tolemak)

    Does anyone know if the AIOS Sitemap is better than the new WP 5.5 sitemap? Which one is more advanced?

    Thank you!

    Thread Starter omris83

    (@omris83)

    Def stick with AIO! Its much better.

    Anyway, I found the filter to remove the standard one.

    add_filter( ‘wp_sitemaps_enabled’, ‘__return_false’ );

    Luke Cavanagh

    (@lukefiretoss)

    The sitemaps XML feature in WordPress 5.5 core is pretty basic at the moment.

    New XML Sitemaps Functionality in WordPress 5.5

    add_filter( 'wp_sitemaps_enabled', '__return_false' );

    Plugin Support arnaudbroes

    (@arnaudbroes)

    Hey @tolemak,

    We have written a detailed article here on why we think our sitemap is still better than the new built-in one – https://semperplugins.com/wordpress-xml-sitemaps-vs-all-in-one-seo-sitemaps/

    @omris83 that’s correct, but you don’t need to add this filter yourself since AIOSEO will automatically disable the new built-in sitemap if our XML Sitemap module is active.

    – Arnaud

    Thread Starter omris83

    (@omris83)

    Weird as I still have that page /wp-sitemap.xml

    So I updated to WP 5.5

    And I can still navigate to mydomain.com/wp-sitemap.xml

    What makes it worse is it throws out a load of code which looks like wpbakery before its formatted. NOt sure who the issue lies with here. The theme (They’ve updated and are well known…) WPBakery (Also well known) or AIO SEO (Also well known!)

    Very confused.

    • This reply was modified 8 months ago by omris83.
    vshukla

    (@vshukla)

    I’m adding my question here instead of opening a new thread.

    Just to confirm my understanding as I have 2 websites that are affected by the new update – I have to activate the XML module in order to avoid using the WordPress one?

    I was using another plugin from before and haven’t activated the XML module yet. I’ve also asked the other plugin the same question before I make the shift.

    Thanks in advance.

    • This reply was modified 8 months ago by vshukla.
    • This reply was modified 8 months ago by vshukla.
    Thread Starter omris83

    (@omris83)

    My issue is def caused by the plugin as if I disable the plugin I have no issues.

    If I enable the plugin the page /wp-sitemap.xml throws out a lot of WP Bakery style code. I’m guessing there’s a conflict between AIO SEO and WP Bakery. Is there a way a dev can take a look and fix in the next version?

    Plugin Support wpsmort

    (@wpsmort)

    @omris83 I have responded to your contact form submission you sent today. The problem is with WP Bakery, not All in One SEO.

    Plugin Support wpsmort

    (@wpsmort)

    @vshukla Yes, you should activate the XML Sitemap module in All in One SEO. You can find a guide to using our sitemap here – https://semperplugins.com/documentation/beginners-guide-to-xml-sitemaps/

    Thread Starter omris83

    (@omris83)

    I’ll reach out to them, thanks.

    vshukla

    (@vshukla)

    Thank you @wpsmort. I have the feature activated on one of my websites and will do the needful. There’s no description of Products Post Type though. Is it correct to assume we should not check that box if we have gated content or digital content like pdfs?

    Plugin Support wpsmort

    (@wpsmort)

    @vshukla If you have products on your site and you want Google to index them and they’re publicly visible, then include them in your sitemap.

    You don’t need to submit gated content to search engines because they can’t see it.

    Thread Starter omris83

    (@omris83)

    Spoke to wpbakery and they said…

    “The https://www.domainhidden.com/wp-sitemap.xml is a page generated by sitemap plugin and WPBakery Page Builder does not have any control over it. The WPBakery Page Builder can only work on static pages while the generated pages are controlled by the respective plugins and the theme.

    ————————————-

    I did mention before that if I disable AIO SEO, the issue goes away, i.e. wp-sitemap.xml doesnt throw out a load of gibberish.

    I love AIO SEO. I love WPBakery. But when both say ‘its not us, its them’ its very frustrating as I then have zero idea how to resolve.

    Plugin Support wpsmort

    (@wpsmort)

    @omris83 wp-sitemap.xml is generated by WordPress. It’s their new XML Sitemap that is part of the WordPress 5.5 release (https://wordpress.org/news/2020/08/eckstine/). It is not generated by a plugin.

    They also didn’t look closely enough otherwise they would have see that /wp-sitemap.xml on your site is a 404 page. Let them know this and hopefully they can help you.

    Thread Starter omris83

    (@omris83)

    Wpsmort, I’m not pointing blame. Im just trying to resolve. However if I do disable AIO SEO it goes away. It seems a conflict somewhere. Im just not sure who will resolve, or how.

    • This reply was modified 8 months ago by omris83.
Viewing 15 replies - 1 through 15 (of 17 total)
  • The topic ‘WordPress 5.5. Sitemap – Need to disable?’ is closed to new replies.