@cuboid hello
Thank you for report
There are no known issues with Cloudflare Argo, but can you disable it and test crawler?
Are you working in maintenance mode? This will limit guest user page access and stop the crawler from working as expected.
There is a blocklist page in LSC that will tell you the reason why blocklisted. More information can be foung by enabling LSC debug and see the Crawler logs(https://docs.litespeedtech.com/lscache/lscwp/toolbox/#log-view-tab).
Last thing you can do is test what Plugin or maybe the theme by disabling them one by one. First plugins that seems to be related to the issue: maintenance mode, disable-lazy-loading, wp-webhooks(this is a long shot, but maybe?!). Theme, you can switch to 20** theme from WP. These are themes that do not have any incompatibilties.
Please make a backup(be sure you have a point where you can restore the site) in case of any issue related to disabling plugins.
Thread Starter
cuboid
(@cuboid)
Thank you. Our hosting company has indicated that having these cookies in exclusion list caused pages going to blocklist:
wmc_current_currency
wmc_current_currency_old
wmc_ip_info
This switches currency automatically for customers.
The plugin developers are saying it needs to be excluded from cache.
Is there a way to exclude these but still make litespeed crawler work?
Plugin Support
qtwrk
(@qtwrk)
you should use the option cookie vary in Cache -> Advance , instead of using do not cache cookie in Cache -> Exclude
Thread Starter
cuboid
(@cuboid)
Thank you so much.
I added the 3 there.
Could you check if our crawler results looks ok?
https://prnt.sc/_A_GXQqMCUVd
Why is the green one always at ‘-‘ ?
Plugin Support
qtwrk
(@qtwrk)
I think it’s because when you vary cookie on currency , the first access will most likely always to be missed , in order for multi-currency to work properly
Thread Starter
cuboid
(@cuboid)
So are our pages being cached or is cache functionality not even working for our sites?
Thank you for support.
Plugin Support
qtwrk
(@qtwrk)
if you set “do not cache cookie” , then when such cookie exists , the page will not be cached
if you set “cache vary cookie” , then the page will still be cached, with different copies based on cookie values to properly display differnet languages or currencies
Thread Starter
cuboid
(@cuboid)
I have these cookies in ‘do not cache cookie’
woocommerce_cart_hash
woocommerce_items_in_cart
wp_woocommerce_session_
woocommerce_recently_viewed
Does this mean none of my pages will be cached because we are a WooCommerce store?
I don’t know if those 4 cookies existed when we installed litespeed or one of our devs put it.
Please guide us best way. Thank you.
Plugin Support
qtwrk
(@qtwrk)
yes, if you put these cookie into do not cache cookie field , that means when such cookie presetns , the page will be set to no-cache status
ideally for woocommerce , you only need to put the first one into vary cookie field if your mini-cart doesn’t work properly , a good theme would use ajax call to update the mini cart, so some theme doesn’t need to do this
the last will effect the recent viewed product widget or something , it’s trade-off you need to balance for cache efficiency and recent view feature
Thread Starter
cuboid
(@cuboid)
Thank you. If I put woocommerce_recently_viewed in ‘vary cookies’ section, will the pages be cached?
Plugin Support
qtwrk
(@qtwrk)
yes , it will be cached with cookie vary
Thread Starter
cuboid
(@cuboid)
Thank you. Then what is the trade-off?
Plugin Support
qtwrk
(@qtwrk)
I meant the “recent view product” function
if you want to make it work , then it will be very cache inefficient
or if you don’t use that feature, cache will work in a more efficient way
Thread Starter
cuboid
(@cuboid)
Thank you. When you say inefficient, does this mean, if I have ‘woocommerce_recently_viewed’ in vary cookie, the cached page will be created for each user? And will refresh each time they visit the page again?
Plugin Support
qtwrk
(@qtwrk)
it’s even worse than that
for example when user visited product A , the cookie contains this info , user opens page 1 , this cache is generated with info like “recent view list: product A” , now user opens product B , the cookie gets updated to like “recent view list: product A, product B” , user goes back to page 1 again , the changed cookie value will force it to generate again , instead of serving from cache
