--project when working with queues.
Commands Reference
Add Single URL
Bulk Add URLs
List Queue Items
- Default (5 pending)
- More Items
- All Statuses
- Filter by Status
- Count Only
Claim Next Item
Update Item Status
ID is globally unique, no
--project needed for status updatesCleanup Queue
Bulk File Formats
JSON Format
queue.json
Template available:
templates/queue-template.jsonCSV Format
queue.csv
Template available:
templates/queue-template.csvurl- Website URL (required)custom_instruction- Special instructions for this site (optional)priority- Higher number = higher priority (optional, default: 0)
Queue Processing Workflow
1
Claim next item
- ID (for status updates)
- URL (target website)
- Project name
- Custom instruction (if exists)
2
Process custom instruction
If
custom_instruction exists, use it to override default analysis behavior (e.g., focus on specific content types, custom selectors).3
Run analysis phases
Execute standard analysis workflow (Phases 1-4).Include
"source_url": "<queue_url>" in final_spider.json.4
Import spider
5
Run crawl
6
Update status on success
7
Update status on failure
Complete Example
1. Create Queue File
sites.json
2. Bulk Add to Queue
3. Check Queue
4. Process Queue
5. Handle Failure
6. Cleanup
Statistics
Check queue statistics:Best Practices
1
Use descriptive custom instructions
Help guide the analysis process with clear instructions:
2
Set meaningful priorities
Higher numbers processed first:
- 10: Urgent, high-value sites
- 5: Standard priority
- 1: Low priority, process when available
3
Always specify project
Prevent data mixing across projects:
4
Document failures
Help debug issues later:
5
Regular cleanup
Remove old completed items:
Related Guides
Checkpoint Resume
Pause and resume long crawls
Incremental Crawling
Skip unchanged pages