Configuration
Configuration File
Section titled “Configuration File”Create crawlkit.toml in the working directory:
[crawl]seed_urls = ["https://example.com"]max_pages = 200max_depth = 10max_redirect_hops = 20max_concurrent_requests = 64request_timeout_secs = 30crawl_delay_default_ms = 1000user_agent = "crawlkit/0.4.0"respect_robots_txt = true
[crawl.scope]allowed_domains = ["example.com"]blocked_patterns = ["/wp-admin/*", "/api/*"]
[analyzers]enabled = ["meta", "links", "security", "accessibility", "content", "ai", "wasm"]
[output]formats = ["json", "sqlite", "html"]output_dir = "./crawl-results"Feature Flags
Section titled “Feature Flags”Feature flags are configured in the [features] section of crawlkit.toml:
[features]js_rendering = falseai_analyzers = truewasm_analyzers = truebacklink_analysis = trueencryption_at_rest = falseaudit_trail = trueobservability = truerum_integration = falseCLI flags --enable-ai, --enable-wasm, and --javascript override configuration file values.
CLI Flags
Section titled “CLI Flags”All configuration file options can be overridden via CLI flags:
crawlkit crawl https://example.com \ --max-pages 500 \ --delay 200 \ --concurrency 8 \ --output crawl-dataEnvironment Variables
Section titled “Environment Variables”| Variable | Description | Default |
|---|---|---|
CRAWLKIT_DB_PATH |
SQLite database path (API mode) | crawlkit-api.db |
CRAWLKIT_ENCRYPTION_KEY |
AES-256-GCM key (hex or base64) | none |
RUST_LOG |
Log level filter | crawlkit=info |
NODE_PATH |
Node.js module path (Playwright) | system default |