Google Search Console Errors

Hey @heesea,

This is intended behaviour of the robots.txt file as you do not want your /wp-admin/ pages to be indexed for security reasons. Do you have any idea how Google is finding those? You definitely don’t want those to be included in your sitemap for example.

As for the 404 errors, does the issue go away after you deactivate AIOSEO?

To disable SEO for those post types, you’ll now have to hook into one of our filters. You can add the code snippet below to your theme’s functions.php file in order to do this –

add_filter( 'aioseo_disable', 'aioseo_disable_loomisoft' );

function aioseo_disable_loomisoft( $disabled ) {
	$disabledPostTypes = array(
		'postType1',
		'postType2'
	);

	if ( is_singular() ) {
		$post = get_post();
		if ( is_object( $post ) && in_array( $post->post_type, $disabledPostTypes, true ) ) {
			return true;
		}
	}

	return $disabled;
}

The only thing you’d have to do is replace postType1 (and postType2 and so on) with the slug of the post types you’d like to disable meta data for.

If you don’t know what their slug is, then you can easily find this by going to the Sitemaps menu of All in One SEO, scrolling down to the setting that allows you to select the post types you want to include, and hovering over the icons next to them. You’ll see a tooltip that shows you the slug.

– Arnaud

Hey @heesea,

It’s definitely not a result of the update.

As far as the other issue goes, we’ll definitely consider adding back a visual option to exclude certain post types, although I personally can’t make any promises right now.

Here’s a code snippet that should work (tested it myself):

add_filter( 'aioseo_disable', 'aioseo_disable_loomisoft' );

function aioseo_disable_loomisoft( $disabled ) {
	if ( is_singular( 'lscontentblock' ) ) {
		return true;
	}

	return $disabled;
}

– Arnaud