Features
Deployment awareness
Connect release context to eligible crawls, Health and Incidents without confusing timing correlation with causality.
Manual deployment records
Record a version or build manually and see the release context that was active when CrawlDrift observed a technical SEO change.
Linked CrawlRun
Review the first eligible crawl after a deployment, related crawl history and the deployment marker alongside Health and Incident trends.
Before and after context
See Health before and after an eligible crawl, plus New, Reopened and Resolved Incident counts observed after the deployment.
First detected after
Filter and inspect which Incidents were first detected after a version or build, or resolved after a later release.
Correlation, not causality
Deployment markers show timing correlation between releases and observed technical SEO changes. CrawlDrift does not claim that a deployment caused an Incident without additional evidence.
Automated deployment reporting
Connect your CI/CD pipeline to CrawlDrift with the official CLI, container image or deployment API. Send the version, build and commit context automatically, then start a deployment-linked crawl after your rollout delay.
Connect your pipeline
Official clients. Generic CI/CD compatibility.
No provider lock-in. Use the same deployment endpoint from GitHub Actions, GitLab CI, Bitbucket Pipelines, Jenkins or any pipeline that can run a container or make an HTTPS request.
Works with GitHub Actions through the official CrawlDrift Action. Works with GitLab CI using the official CrawlDrift container. Generic provider compatibility is not a native provider integration.
Start monitoring your technical SEO today
Set up your first project in minutes. Verify your domain, start a crawl, and see exactly what changed without the noise.
No credit card required. Starter plan limits apply.