Overview
This guide walks you through creating your first crawl job in Adapt. You’ll learn how to:- Create an account and authenticate
- Set up your first domain
- Create and run a crawl job
- View results and identify issues
Adapt integrates with Supabase Auth for authentication, supporting email/password and social login (Google, GitHub).
Prerequisites
Before you begin, ensure you have:- A website URL you want to monitor
- An email address for account creation
- (Optional) A sitemap.xml file for faster discovery
Step 1: Create Your Account
Sign Up
Click “Sign Up” and choose your authentication method:
- Email/Password: Enter your email and create a password
- Social Login: Use Google or GitHub for quick signup
Verify Your Email
Check your inbox for a verification email from Adapt and click the confirmation link.
Step 2: Create Your First Job
Once logged in, you’ll see the dashboard. Let’s create your first crawl job.Enter Domain Details
use_sitemap: Automatically discover URLs from sitemap.xmlfind_links: Crawl discovered pages for additional linksmax_pages: Maximum number of pages to crawl (0 = unlimited)concurrency: Number of parallel requests (default: 20)
Step 3: Monitor Job Progress
Adapt provides real-time updates on your crawl job via WebSockets.The dashboard updates automatically as tasks are processed. No need to refresh!
Using the API
You can also monitor progress programmatically:Step 4: View Results
Once the job completes, you can view detailed results and identify issues.Results Summary
Get a high-level summary of your crawl:- Total pages crawled and success rate
- Average response time and performance breakdown
- Cache hit ratio and warming effectiveness
- Issues detected: 404s, slow pages, server errors, redirects
Filtering Tasks
View specific subsets of tasks using query parameters:Export Results
Export full results for analysis:Step 5: Set Up Scheduled Crawls
Automate recurring crawls with schedulers:6hours - Frequent monitoring12hours - Twice daily24hours - Daily (recommended)48hours - Every other day
Common Issues and Solutions
Job Stuck in “Created” Status
Check worker status in your organisation settings. If no workers are available, contact support.High Failed Task Count
Common causes:- 404 errors: Pages no longer exist or URLs are incorrect
- Timeout issues: Pages taking too long to respond (>30s)
- Rate limiting: Your server is blocking requests (adjust concurrency)
- SSL errors: Certificate issues with HTTPS
Cache MISS on All Pages
If cache warming isn’t working:- Verify your CDN configuration supports cache warming
- Check if cache headers are set correctly on your origin server
- Ensure cache keys are consistent (no random query parameters)
Next Steps
API Reference
Explore all available API endpoints
Webflow Integration
Connect Adapt to your Webflow sites
Slack Notifications
Get notified when jobs complete or fail
Local Development
Set up Adapt for local development