Alerts and digests
SEO alerts that surface real problems, not noise
Detect critical regressions quickly while collecting lower-priority changes into digest windows your team can actually read.
Issue priority table
Priority
Issues ranked by severity, impact, and affected URLs across the workspace
| 7-day | |||||
|---|---|---|---|---|---|
| Critical | Noindex on indexable pages Live pages send a noindex directive, dropping them from search. | +42% | High | 318URLs | |
| Critical | 5xx server errors URLs returning 5xx responses block crawling and indexing. | +18% | High | 124URLs | |
| Warning | Redirect chains Multi-hop redirects waste crawl budget and slow page loads. | −9% | Medium | 542URLs | |
| Warning | Canonical mismatch Declared canonical differs from the page Google likely indexes. | +7% | Medium | 287URLs | |
| Warning | Thin content Pages with little unique text are unlikely to rank or convert. | stable | Low | 196URLs | |
| Warning | Missing hreflang return tags Language variants don't reference each other, breaking targeting. | −4% | Low | 88URLs | |
| Info | Slow server response Pages over 1s TTFB reduce crawl rate and hurt Core Web Vitals. | −12% | Low | 64URLs | |
| Info | Missing Open Graph tags Pages without OG tags get poor previews on social and chat. | +3% | Low | 41URLs |
1
Severity first Critical incidents stay visually distinct from warning and informational changes.
2
Affected URLs Counts stay next to the issue so teams can judge impact before opening the drilldown.
The problem
SEO monitoring can become noisy when every temporary page change creates a separate notification.
The outcome
Crawle groups issue types, tracks incident lifecycle, supports alert windows, and keeps affected URLs close to the alert.
- Critical issues can remain real-time.
- Warnings and informational changes can be delivered daily, weekly, or monthly.
- Incidents show affected counts, top URL samples, severity, and status.
- Slack, Microsoft Teams, and email routing can be configured per workspace and site.
Workflow
From crawl signal to team action
01
Detect
Crawle watches status codes, indexability, titles, headings, canonical tags, hreflang, robots, links, and sitemap signals.
02
Group
Related URL-level changes are grouped into issue types and incidents instead of flooding every recipient.
03
Route
Send alerts to the channels that match the site, severity, teammate, or client workflow.
Where teams use it
Pages losing indexability.
Broken links increasing after a release.
Sitemap or robots.txt problems.
Metadata removed from important templates.
Related documentation
Related features
Keep exploring Crawle
Search status context
Google Search status alerts alongside your site incidents
Route official Google Search Status updates into the same email, Slack, Teams, and digest workflow as Crawle's technical SEO alerts.
ExploreContinuous monitoring
Monitoring SEO performance, continuously and in real time
Track SEO performance continuously across client sites with live crawl coverage, change detection, alerts, reports, and exports.
ExploreLinks and redirects
Link monitoring for broken links and redirect chains
Find broken internal links, links to redirects, insecure links, redirect chains, source pages, and final targets from one link explorer.
ExploreAI readiness
Know if AI agents can reach, read, and use your site
Collect every agent-relevant crawl signal on one page, score what is measurable from 0 to 100, and get an alert when a deploy or robots.txt change moves it.
ExploreContinuous monitoring
Put Crawle into your next client QA loop.
Continuous technical SEO monitoring with per-client workspaces, real-time alerts, and white-label reports.