Cron Manager
Configure one central SEO Suite scheduler and understand every current background job.
One central scheduler manages SEO Suite background jobs instead of making you create a different server Cron command for every component.
The simple idea
Your server calls one HuntBee Cron URL regularly. Then the SEO Cron Manager checks which enabled jobs are due.
Recommended server schedule
If your host allows it, call the central Cron URL every minute. That does not mean every job runs every minute. HuntBee’s internal schedule decides whether a job is due.
wget --quiet --delete-after "YOUR_HUNTBEE_CRON_URL"If your host only allows every 5 minutes, use the closest available schedule. A “1 minute” HuntBee job cannot execute more often than the server calls the central URL.
Current SEO jobs
| Job | Default | Frequency | Batch / limit | Beginner advice |
|---|---|---|---|---|
| AI Product Feed Refresh | Off | 5 min | 200 (50–500) | Enable only if using automated feed refresh. |
| IndexNow Queue | On | 5 min | 200 (100–500) | Keep on after IndexNow is configured. |
| AI Content Generation | Off | 5 min | 5; runtime 45 sec | Enable after manual AI tests. |
| Image Rename & Organise | Off | 10 min | 25 products | Preview/backup/test before enabling. |
| Image Audit | Off | Daily | Audit settings | Optional maintenance. |
| Related Products Queue | On | 5 min | 10 | Keep on if using automatic relations. |
| Related Products Refresh | Off | Daily | 10 | Leave off until periodic rebuild is wanted. |
| Product Tags Queue | On | 5 min | 10 | Keep on if automatic tags are used. |
| Product Tags Refresh | Off | Daily | 10 | Leave off until periodic refresh is wanted. |
Available frequency choices
Current manager options include every minute, 5, 10, 15 or 30 minutes, hourly, every 6 hours, every 12 hours and daily.
How to know Cron works
- Copy the exact central command/URL shown by HuntBee. Do not type your own token.
- Create the server scheduler.
- Use a small enabled queue job or the component’s Run/Test action where available.
- Check the Cron Manager’s last-run/result information and the component queue/activity.
- If nothing runs, verify your hosting scheduler can reach the URL and that the token has not been altered.