Title: Crawler keep missing?
Last modified: March 31, 2024

---

# Crawler keep missing?

 *  Resolved [nilssonab](https://wordpress.org/support/users/nilssonab/)
 * (@nilssonab)
 * [2 years, 2 months ago](https://wordpress.org/support/topic/crawler-keep-missing/)
 * My crawler keep missing, even though it finds sitemap OK and goes to the correct
   URLs.
 * The IP-adress is configured to the correct one of my server, and I do get a couple
   of hits which makes no sense to me.. Example for “Guest WebP Phone” is 3 Hit 
   and 252 Miss.
 * Created a report aswell: **XIKQTTCI**

Viewing 2 replies - 1 through 2 (of 2 total)

 *  Plugin Support [qtwrk](https://wordpress.org/support/users/qtwrk/)
 * (@qtwrk)
 * [2 years, 2 months ago](https://wordpress.org/support/topic/crawler-keep-missing/#post-17541723)
 * you can try set crawler interval to shorter time and try it out, see how it goes
   first
 *  Thread Starter [nilssonab](https://wordpress.org/support/users/nilssonab/)
 * (@nilssonab)
 * [2 years, 2 months ago](https://wordpress.org/support/topic/crawler-keep-missing/#post-17542292)
 * After allowing all the IPs on the quic.cloud/ips it seems to work fine.

Viewing 2 replies - 1 through 2 (of 2 total)

The topic ‘Crawler keep missing?’ is closed to new replies.

 * ![](https://ps.w.org/litespeed-cache/assets/icon-256x256.png?rev=2554181)
 * [LiteSpeed Cache](https://wordpress.org/plugins/litespeed-cache/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/litespeed-cache/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/litespeed-cache/)
 * [Active Topics](https://wordpress.org/support/plugin/litespeed-cache/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/litespeed-cache/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/litespeed-cache/reviews/)

 * 2 replies
 * 2 participants
 * Last reply from: [nilssonab](https://wordpress.org/support/users/nilssonab/)
 * Last activity: [2 years, 2 months ago](https://wordpress.org/support/topic/crawler-keep-missing/#post-17542292)
 * Status: resolved