timwoolfson

Yup, nice1 – after resaving the theme options and reclearing all the caches – Rocket – CloudFlare etc. we’re good – thanks ??

Hi Greg,

Under Exclude from traditional sitemap, do you see Exclude Custom Post Type and Exclude Taxonomies – look very carefully at the custom post types and taxonomies that are there – make sure you understand what each one is and does.

Do you still have a problem?

Regards,

Tim Woolfson
Profitable Web Projects
https://www.profitableweebprojects.com

I guess we could just use text within the private content.
Maybe what we need is more a notes type plugin.

The default ordering is always DESC – this is because the default sort is by postdate. So most recent at the top makes sense. You can change the sort by using sort=”menu_order” or sort=”post_title”, these sorts work on custom post types as well as ordinary posts but the sort order parameter only works for ordinary posts, for custom posts when sorted by menu_order or post_title the ordering is always DESC, order=”ASC” has no effect. This would seem to be a bug!

Thanks catalysts – very much appreciate you taking the time to share that info.

And are you using all AIOWPS features?
We are using version 4.3.1 and score 225/500 – I have exported our settings.
Do you want me to send you our settings so you can compare? If so, contact me by email please.

The error message in search console is “Your Sitemap does not contain any URLs. Please validate and resubmit your Sitemap.” turning off AIOWPS yields “No errors found.”

The theme in question in my case is Avada. There are various plugins of course!

Are you using the free Yoast plugin or the premium/paid version? We are using the free version.

I have never run into this issue myself.

So, you have a site with AIOWPS and Yoast and you are using Google Search Console and you have submitted the yoast generated sitemap URL sitemap_index.xml via Google Search Console and when you test that URL no errors are generated – please confirm.

I have tested, and the error is happening with the firewall rules off in AIOWPS

In regards to the following comment. Can you provide more information as to how is AIOWPS plugin killing your sites organice search placement?

The supposition is that when AIOWPS blocks sitemap_index.xml for googlebot – Google penalises the site for having a submitted sitemap which is inaccessible. This is the same supposition as Catalysts made on the other thread, I have asked him to confirm that the Search rankings recovered after Search Console could read the sitemap – our have not yet – in any case – submitting a sitemap to google and then blocking access for the googlebot to it would not seem to be wise SEO practice!

@catalysts

Because of the error in Search Console and the critical drop in rankings, we’ve decided to remove the plugin completely.

Did the critical drop in rankings rectify itself once search console could read the sitemap file? How long did it take?

Do you not have a test site? If not, you should have… ??

If so, just install yoast (free) and activate – think the default settings will create the sitemap page

set-up google search console (takes 10 mins)
submit sitemap URL (takes 5 mins)

If you need help, I′m willing to help but I′d rather not use a production environment for testing and I′d rather leave you with a test environment you can use to test future releases quickly and easily. Add me to your test site as a WP user if you need help or pass me the URL and I will set-up Search Console for it and in time add your google account as a user so you can test.

I′ve contacted you via https://mbrsolution.com/contact-mbrsolution so you have my email etc..

I have reported the issue to AIOWPS https://www.ads-software.com/support/topic/aiowps-blocking-sitemap_index-xms-generated-by-yoast/

We left it running and a genuine user’s #Visitor gclid# has just come through so I′m not sure why it didn′t work for our test, perhaps it only works on user’s first visit?

There’s a setting that allows you to exclude IDs

To help you get to the bottom of this:

(Network) Install the wp crontorl plugin https://www.ads-software.com/plugins/wp-crontrol/
Activate
Go to /wp-admin/tools.php?page=crontrol_admin_manage_page
Using “Run Now” against wp_version_check should cause the autoupdate to occur
You can tell what version you have quickly via /readme.html

Hope this helps.

Note that by default wordpress doesn’t do ANY automatic updates when it detects that version control is in use as evidenced by the text “For Developers: To enable automatic updates even if a VCS folder (.git, .hg, .svn etc) was found in the WordPress directory or any of its parent directories:

add_filter( ‘automatic_updates_is_vcs_checkout’, ‘__return_false’, 1 );”

https://codex.www.ads-software.com/Configuring_Automatic_Background_Updates

Was that your issue?