1
Currently if you try to do multiple site crawls subsequently, you get the following message:
Engines cooling down. It might take a moment before we are ready for another crawl.
Would it be possible to provide a cooldown timer for the next crawl? Sometimes a crawl report will point out an error, but we have to wait an arbitrary amount of time before being able to test again to find out if our fixes were successful.
Hummingbird does this with the performance scans, and it’s useful to know how long to wait to scan again.
