Crawleprivate beta

Catch SEO issues before Google does.

Crawle crawls your clients' sites around the clock, compares what changed, and alerts your team the moment a technical SEO regression needs attention.

Workspace overview

Dashboards built for the work, not vanity charts

A live view across client sites: URL capacity, crawl progress, active incidents, link issues, and the technical SEO signals that actually need triage.

Workspace overview

WORKSPACE Crawle · 17.4k URLs · 12 issues · Last crawl 14m ago

Overview

Workspace health across 5 sites

Last crawl 14m ago

Critical issues

−21%

Pages crawled

+6.4%

Broken links

−8%

Index coverage

0.0%

+3.1%

Sites

5 sites in this workspace

DomainHealthOpen issuesURLs

crawle-demo.io86B84217,428
docs.crawle-demo.io94A18312
shop.crawle-demo.io72C2144,980
blog.crawle-demo.io58D911,264
staging.crawle-demo.iounverified———

Crawl activity

URLs crawled and errors over the last 30 days

Crawled
Errors

Site health

Weighted technical score

Open issues by type

Links To Redirect
Missing Meta Description
Broken Links
Canonical Changed
Title Removed

A live workspace overview across client sites, URL capacity, crawl progress, and active technical SEO signals.

Cloud crawler

Full-site crawling, no local machine

Screaming-Frog depth that runs in the cloud and never stops: shared crawl data, rendered-DOM support, exports, and workspace capacity sized around the client.

Open crawler feature

URL coverage summary

COVERAGE · 15.8k discovered · 3.2k crawled · 12.6k queued

Coverage

How much of the workspace Crawle has discovered and crawled

Crawling · 2m ago

Discovered URLs

0+1,204 today

Crawled

20% crawl coverage

In queue

awaiting crawl

Crawl coverage

of 15.8k discovered

Index coverage

Crawled · indexed · in sitemap

aOnly	286
bOnly	0
cOnly	412
ab	198
ac	0
bc	0
abc	2488

Crawled
Indexed
In sitemap

Coverage cards show how much of the workspace Crawle has discovered, crawled, queued, and flagged.

Real-time alerts

Catch the regression while the team still remembers the release

Critical incidents fire in real time. Warnings, informational changes, and resolved incidents can roll into digests for Slack, Teams, email, and webhooks.

See alert routing

Slack notification routing

SLACK · connected workspace · searchable channels · test delivery

Notification channels

Route alerts to the right Slack channels

Workspace connected

Slack

Active4 channels

Connected to Acme Workspace

Notification channel

alerts

growth
Indexability drops
migrations-qa
Migration QA
seo-alerts
Critical incidentsDefault
site-health
Daily digest

Currently sending to #seo-alerts

Send test

Alerts routed (30d)0

Channels wired0

Median delivery0.0s

Alert volume (12d)

Slack routing lets teams choose channels for critical incidents, digests, migration QA, and test notifications.

AI agents

Bring live crawl context into Claude, ChatGPT and Codex

Crawle exposes workspace-aware crawl data over OAuth MCP, so approved agents can inspect issues, links, alerts, exports, technology context, and client workspaces without stale screenshots.

Explore AI workflows

Claude MCP issue triage

Crawle demo workspace

Why is /pricing missing from Google?

Calling Crawle MCPMCPhttps://mcp.crawle.app/v1/sse

issues:readlinks:readsites:readread-only · scoped

Critical

Noindex on indexable page

X-Robots-Tag: noindex · app.crawle.io

High impact

Affected URLs7

Internal inlinks42

Trend (7d)+12%

7-day

Top affected pages

/pricing0.98
/pricing/teams0.81
/pricing/enterprise0.74

Recommended next actions

Remove the X-Robots-Tag: noindex header from /pricing
Re-crawl the 7 affected URLs to confirm the fix
Request indexing in Search Console once headers are clean

A real Claude session using Crawle's MCP connector to answer a specific SEO question from live workspace data.

Everything after the crawl starts

The workflows agencies actually need

Crawle is not just another crawl snapshot. It is shared monitoring, history, routing, exports, and agent context that stays alive after the audit.

Client workspaces
One operating context per client: capacity, team access, integrations, reports, and history kept separate.
Continuous crawling
Crawle keeps revisiting discovered URLs and compares what changed across status, metadata, links, robots, and canonicals.
2-year change history
Timelines prove when a change happened and what it affected — 2 years retained, full historical exports rolling out.
Migration monitoring
Detect mass redirects, verify target domains, export mappings, and clean up old URLs when the migration is stable.
Link monitoring
Broken links, redirect targets, source pages, and link exports stay grouped for action.
AI agent workflows
OAuth MCP gives Claude, ChatGPT, Codex, and internal agents live Crawle context instead of stale CSVs.
White label
Brand reports and client-facing surfaces when the agency needs Crawle to sit behind its own service model.
Exports and automation
Download current or historical datasets, send weekly summaries, or trigger customer-owned workflows with webhooks.

How it works

From client workspace to always-on monitoring

Create a client workspace

Keep each portfolio in its own context with capacity, team access, integrations, alerts, and reports.

Add and verify domains

Verify with Google Search Console when available, or use DNS/meta verification when needed.

Crawl continuously

Crawle compares status, metadata, links, robots, canonicals, rendering, indexability, and custom extraction values over time.

Route the right alerts

Critical incidents can interrupt immediately; lower-priority changes roll into digests for email, Slack, Teams, and webhooks.

Agency operating model

One workspace per client when separation matters

Use dedicated workspaces for clients that need their own capacity, permissions, alerts, integrations, exports, and reports. Group smaller sites only when that is the cleaner account structure.

Explore workspaces

Workspace clients and tags

CLIENTS · tags · bulk defaults · agency filters

Clients & tags

Organize agency domains and apply crawl defaults in bulk

Bulk crawl defaults

Save crawl defaults for a client, preview matching sites, then apply.

Target type

Client

Northwind Retail

JavaScript rendering

No change

Screenshots

Enabled

Cache headers

Respect

Crawl delay0.5s

0.5s (fast)30s (gentle)

Preview sitesSave & applyApplied to 14 sites

14 matching sites for Northwind Retail

northwind.com
shop.northwind.com
help.northwind.com
northwind.co.uk
northwind.de

Clients

Reuse clients across workspaces; defaults apply locally per assigned domain.

Client	Sites	Workspaces	Crawl defaults
Northwind Retail E-commerce storefront + regional microsites	14	2 shared	JS: AlwaysScreenshots1.5s delay
Harborlight Media Publishing network, high page volume	9	1	JS: AutoNo cache4s delay
Vantage SaaS Product, docs, and marketing domains	6	1	JS: Always2s delay
Meridian Health Regulated content, gentle crawl	4	1	None set

Tag	Sites	Workspaces
Priority	11	3 shared
Migration wave	7	2 shared
JS-heavy	5	1

Give AI agents the site's implementation context

Technology stack evidence, security-header posture, stack changes, and risk signals give teams and AI workflows the context needed before suggesting technical SEO fixes.

Open technology context

Stack changes and risk findings

STACK CHANGES · baseline · risk findings · developer context

Hover numbers for details

Technology & risk signals

Evidence-backed posture signals and stack deltas for crawle-demo.io

Last scan Jun 9Jun 9

High-risk open0critical + high

Open findings0of 4 total

Detected components0across the stack

Recent stack changes0since last baseline

Risk findings

High-severity findings require deterministic public evidence; informational rows are context for developers and agents.

4open


Critical	No Content-Security-Policy header Responses ship without a Content-Security-Policy. A baseline policy reduces the blast radius of injected or third-party script. CRAWLE-CSP-001	Site posture	Open	Jun 9
High	jQuery exposes known prototype-pollution advisory The detected jQuery version matches a published advisory. Upgrading clears the exposed surface on rendered pages. GHSA-gxr4-xjj5-5px2CVE-2020-11023	jQuery v3.4.1	Open	Jun 9
Warning	Missing Strict-Transport-Security header HSTS is not set, so browsers will not pin HTTPS for return visits. Add a long max-age once HTTPS is fully enforced.	Site posture	Open	Jun 9
Warning	Server version disclosed in response headers The Server header advertises an exact nginx build. Suppressing the version removes a low-effort fingerprinting signal.	nginx v1.21.6	Open	Jun 9

Recent stack changes

Compared against the previous completed scan. The first scan becomes the baseline.

Version changed

Next.js14.1.0 → 14.2.3Framework · npm

meta_generatorJun 8, 3:20 PM

Added

Plausible AnalyticsAnalytics & tags

script_srcJun 7, 10:02 AM

Removed

LodashJavaScript library · npm

script_srcJun 5, 6:47 PM

Baseline changes The first scan becomes the baseline; later scans can show added, removed, or changed technologies.

Risk language Findings are framed as posture signals with evidence, not as proof from an intrusive security test.

Stack changes and risk findings separate baseline changes from evidence-backed hardening signals that developers and AI agents can act on.

Free account · paid workspaces

Choose capacity around the client, not your backend

Most agencies use one workspace per larger client. The workspace size defines URL capacity and crawl throughput; prices exclude VAT.

Workspace capacity planner

Are you planning Crawle for one company or many clients?

Crawle accounts are free. Costs start when you add active workspaces. Agencies usually use one workspace per client so access, alerts, reports, historical exports, and crawl capacity stay cleanly separated.

Clients / workspacesEstimate one active workspace per customer/client.Total URLs across clientsWe divide this by clients for a first estimate. Size large outliers separately.Avg. domains per clientKeep related client domains together when permissions and reporting match.

Crawl rate and capacity

Suggested setup

10 x Small workspace

Estimated from 10,000 URLs and 2 domains per client.

€390

/mo, excluding VAT

Workspaces

URLs per workspace

10,000

Capacity

10,000 URLs / workspace

White label

Recommended add-on

This assumes clients are roughly similar. If one client is much larger, size that workspace separately and keep smaller clients on smaller workspaces.

Suggested fit

Small workspace

€39/mo

€351/year with annual billing

10,000URLs

3domains

Small business sites
Light JS rendering
SEO checks and change tracking

Join waitlist

Medium workspace

€79/mo

€711/year with annual billing

50,000URLs

10domains

Growing ecommerce
Faster continuous crawling
Advanced exports

Join waitlist

Large workspace

€149/mo

€1341/year with annual billing

150,000URLs

25domains

Large client accounts
Higher crawl throughput
API + email alerts

Join waitlist

X-Large workspace

€299/mo

€2691/year with annual billing

500,000URLs

100domains

Enterprise-scale sites
Maximum public workspace capacity
Separate alerts, exports, and reports

Join waitlist

Agency white label

Add-onRecommended

Workspace costs separate

Branded subdomain or custom domain
Own logo and branded emails
Applies across purchased workspaces

€99/mo

Join waitlist

Every paid workspace retains 2 years of change history: URL state, detected changes, issue lifecycle, and GSC signals where connected. Full historical exports for audits and reporting are rolling out.

Private beta

Put Crawle into your next client QA loop.

Join the beta and help shape the agency crawler we wish existed: continuous monitoring, useful exports, better alerts, and AI-ready SEO data.

Catch SEO issues before Google does.Catch SEO issues before Google does.

Dashboards built for the work, not vanity charts

Overview

Sites

Full-site crawling, no local machine

Catch the regression while the team still remembers the release

Notification channels

Slack

Bring live crawl context into Claude, ChatGPT and Codex

The workflows agencies actually need

Client workspaces

Continuous crawling

2-year change history

Migration monitoring

Link monitoring

AI agent workflows

White label

Exports and automation

From client workspace to always-on monitoring

Create a client workspace

Add and verify domains

Crawl continuously

Route the right alerts

One workspace per client when separation matters

Clients & tags

Bulk crawl defaults

Clients

Tags

Give AI agents the site's implementation context

Technology & risk signals

Risk findings

Recent stack changes

Choose capacity around the client, not your backend

Are you planning Crawle for one company or many clients?

Small workspace

Medium workspace

Large workspace

X-Large workspace

Agency white label

Put Crawle into your next client QA loop.

Catch SEO issues before Google does.