Skip to main content
Optional queue system for managing multiple website crawls. Use when explicitly needed. Always specify --project when working with queues.

Commands Reference

Add Single URL

Example:

Bulk Add URLs

Example:

List Queue Items

Shows 5 pending/processing items by default

Claim Next Item

Claims next highest-priority pending item and marks it as processing.

Update Item Status

ID is globally unique, no --project needed for status updates

Cleanup Queue

Cleanup commands require --force flag to prevent accidental deletion

Bulk File Formats

JSON Format

queue.json
Template available: templates/queue-template.json

CSV Format

queue.csv
Template available: templates/queue-template.csv
Required columns:
  • url - 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

Note the returned values:
  • 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

Always use --project matching the queue item’s project! Without it, spider defaults to “default” project, mixing data across projects.
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

Output:

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:

Checkpoint Resume

Pause and resume long crawls

Incremental Crawling

Skip unchanged pages