bot for wp super cache?

Hi,
I suggest to you ask to cache plugin creator.
Then, you can disable it.
Anyway, if your site works fine, don’t worry about.
If not, enable notifications by email, load your page and check your inbox.
Cheers,
Bill

Thanks, Bill! Have also asked in WP Super Cache forum.

I am having IO Errors. Trying to find source. Also, trying to better understand the best way to manage my bots table…should I disable blocking for bots that never show up, or leave the blocking for those enabled? Are there resource implications in thus choice?

Is the bot nicknamed “crawl” a known problem or a helpful friend?

Site is https://ages.ca and it has been “limited” several times by the web host (hostpapa) due to IO errors. Not sure if site is being subjected to attacks.

Related: Does it present a bot load (or other load) on the site server if I generate a report from from the google analytics site that involves today’s visitors?

If you’d prefer that I post these as individual questions so that others can better find your answers, I will do so.

You are welcome.
I suggest let all bots enabled in the table. Disable only that you really need allow access to your site.

About Crawl bot, please, take a look in our bot’s table, find the bot’s creator and ask to them why they want crawl your page.
Here is the URL:
https://stopbadbots.com/bots-table/

About analytics, please, take a look our FAQ page about Analytics SPAM Referral:
https://stopbadbots.com/faq/

About your site with IO errors, i suggest disable the cache plugin to test. Update wordpress and all yours plugins and check your memory available. Our plugin can tel to you about your free memory and give suggestions.
Go to Dashboard => Stop Bad Bots => Dashboard (memory tab)

Thank you very much for your kind attention!

It is so good to see the online bots table! Thank you for showing me how to find the answer instead of providing the answer. It is much more useful to both of us!

Memory function in Stop Bad Bots has already helped identify a memory issue, so thanks for that as well.

Chris