Custom extraction
Custom extraction alerts for page-specific changes
Select a page element, test the extracted value, and route meaningful selector-based changes through Crawle's alerts, digests, webhooks, exports, and MCP/API context.
Custom extraction overview
Bounded monitoring Rule limits keep selector checks predictable for continuous crawls instead of creating an unlimited scraper path.
Visual selector Users can pick an element visually, then edit the generated selector when they need more control.
The problem
Some client risks do not live in standard SEO fields. Prices, stock labels, campaign badges, compliance copy, and template-specific text can change without touching title, canonical, robots, links, or status code.
The outcome
Crawle lets teams define bounded extraction rules from real page elements, test the matched value before saving, and treat meaningful changes as monitored signals inside the same alert workflow.
Visual element selection for users who do not want to start with a selector.
Advanced selector editing for technical SEO teams.
Test runs show matched value, HTTP status, and whether the rule would alert.
The first successful extraction becomes the baseline; later crawls compare normalized values.
Custom extraction signals can route through alert windows, Slack, Teams, email, webhooks, exports, and MCP/API context.
Per-site rule limits keep monitoring predictable for large continuous crawls.
Workflow
From crawl signal to team action
Choose the element
Enter a verified site URL and use the visual selector to pick the element Crawle should monitor, or edit the generated selector in advanced mode.
Test the extraction
Run a test before saving. Crawle shows the extracted value, HTTP status, match behavior, normalization, and alert simulation.
Monitor the baseline
The first successful extraction becomes the baseline. Later crawls compare the normalized value and only route changes that match the rule.
Selector workflow
Pick the element, test the value, then let Crawle monitor the baseline
Custom extraction is for page-specific signals that matter to SEO and client operations but do not belong in Crawle's standard metadata fields. The UI keeps the selector inspectable so teams can verify the rule instead of trusting a hidden extraction.
Visual first
Load a rendered page preview, pick the element from highlighted boxes, and keep the generated selector visible for review.
Test before saving
The test run shows HTTP status, extracted value, normalization, and whether the rule would alert before it joins monitoring.
Bounded by design
Rules use the normal crawl pipeline and per-site limits, so custom extraction adds signal without turning Crawle into an unlimited scraper.
Extraction rule builder
Operator Rules can watch for changes and evaluate alert behavior before they are enabled.
Preview page Teams can test against a specific page instead of configuring selectors blind.
Test first The test uses the same normalization and alert simulation as saved rules.
Visual selector
Rendered preview Element boxes are mapped over the rendered page so non-technical users can pick the value they care about.
Candidate list The candidate list gives keyboard-friendly selection and makes the chosen selector inspectable.
Selector evidence Selected text, HTTP status, render timing, and the generated selector stay visible before saving.
Where teams use it
Related documentation
Related features
Keep exploring Crawle
Turn SEO incidents into events for your own pipelines
Send Crawle incidents and site changes into customer-owned content, QA, CDN, CMS, and agent workflows through structured custom webhooks.
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.
The SEO MCP server for AI agents
Connect Claude, ChatGPT, Codex, Gemini, and internal agents to a live SEO MCP server backed by Crawle's continuous crawl data.