Viewing 11 replies - 1 through 11 (of 11 total)
  • Michael Torbert

    (@hallsofmontezuma)

    WordPress Virtuoso

    Jetpack sitemaps should not be used when AIOSEOP is installed. You should use All in One SEO Pack sitemaps instead.

    Thread Starter Pavlos7

    (@pavlos7)

    did not know that! Thanks Michael.

    Is this a new thing? I’ve been updating my sites over the last few weeks – swapping out Yoast for All-In-One-SEO. Up till a few days ago I had no problems wth the Jetpack Sitemap Module, not it has disappeared.

    I actually really liked what the Jetpack one produced.

    Michael Torbert

    (@hallsofmontezuma)

    WordPress Virtuoso

    Michael,
    Both AIOSEOP and Jetpack try to detect each other, and both fall back on the AIOSEOP sitemap if it exists. Our checking got more aggressive with the most recent update. We’ll address that in the next version to make sure you can still use the Jetpack one if you prefer. There’s a github issue open for that here if you’d like to contribute to the discussion, or code.
    I’m curious, why do you prefer the Jetpack sitemap over AIOSEOP’s? As far as I’m aware, it doesn’t offer anything over AIOSEOP’s, and AIOSEOP offers a lot over Jetpack’s.

    Michael Torbert

    (@hallsofmontezuma)

    WordPress Virtuoso

    I prefer the Jetpack one because it seems to add info for Images and Mobile (AMP) Pages. They show up as seperate Items Indexes in Google Search Console. All I get from yours is a list of pages.

    Having the Images listed and indexed separately is very good. Having the AMP pages indexed separately is fantastic and probably one of the best SEO features in 2016 and beyond. You need to support them asap.

    As a side note – have you thought about what this action might have done for the 100’s of thousands of sites using AIOSEO but not your sitemap? This update has potentially broken their sitemap setting within Google Search Console and damaging their Search Results.

    I find it particularly frustrating it’s doing this even with the Sitemap Module disabled. Frankly I kinda expect this kind of thing from Yoast, but not you guys. It’s part of the reason I started switching all my sites from Yoast over to AIOSEO. Hoping this gets fixed within days – not weeks.

    Michael Torbert

    (@hallsofmontezuma)

    WordPress Virtuoso

    You need to support them asap.

    Both images sitemaps and AMP support are currently on the roadmap and/or actively being worked on. I could be mistaken, but I don’t think Jetpack sitemaps include AMP pages.

    have you thought about what this action might have done for the 100’s of thousands of sites using AIOSEO but not your sitemap

    Absolutely; though those numbers are probably a bit off, there was immediately an issue created, and is already a patch ready to go in the next version.

    damaging their Search Results

    This most likely won’t have any negative effect on most sites. Temporarily removing your sitemap doesn’t deindex URLs.

    I find it particularly frustrating it’s doing this even with the Sitemap Module disabled. Frankly I kinda expect this kind of thing from Yoast, but not you guys. It’s part of the reason I started switching all my sites from Yoast over to AIOSEO. Hoping this gets fixed within days – not weeks.

    I agree 100%. 2.3.6.1 will be out within days.

    In the meantime, you can bring back Jetpack’s sitemap by replacing the function remote_jetpack_sitemap() in /inc/compatability/compat-init.php with the following code:

    public function remove_jetpack_sitemap( $modules ) {
    
    			global $aioseop_options;
    			// Check if AIOSEOP's sitemap exists.
    			if ( isset( $aioseop_options['modules']['aiosp_feature_manager_options']['aiosp_feature_manager_enable_sitemap'] ) && $aioseop_options['modules']['aiosp_feature_manager_options']['aiosp_feature_manager_enable_sitemap'] === 'on' ) {
    				unset( $modules['sitemaps'] ); // Remove Jetpack's sitemap.
    			}
    
    			return $modules;
    		}

    If you aren’t sure how to edit the plugin files, you can download the latest development version here: https://github.com/semperfiwebdesign/all-in-one-seo-pack/archive/development.zip

    Thread Starter Pavlos7

    (@pavlos7)

    Michael Torbert, I believe Michael Quinn addressed couple of very important points here. Frankly, I was surprised by your action to block sitemaps of Jetpack. Anyway, this will be fixed now and that AIOSEOP remains a GREAT plugin.

    Regards,
    Pavlos

    Michael Torbert

    (@hallsofmontezuma)

    WordPress Virtuoso

    This should be resolved in 2.3.6.1 released today. Jetpack sitemap should only be disabled in the AIOSEOP sitemap module is enabled.

    Thread Starter Pavlos7

    (@pavlos7)

    great support Michael! thanks for all the good work! software developers are the key stones for all good e-services nowadays.

    regards,
    Pavlos

    Michael Torbert

    (@hallsofmontezuma)

    WordPress Virtuoso

    Thank you Pavlos!

    Michael

Viewing 11 replies - 1 through 11 (of 11 total)
  • The topic ‘conflict with sitemap module of Jetpack’ is closed to new replies.