firecrawl-monitor

Detect website content changes and send webhook or email notifications on a schedule.

Updated Apr 18, 2026
One-click install
npx skills add https://github.com/webdevarif/claude-skills --skill firecrawl-monitor-webdevarif
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: firecrawl-monitor
Source: https://github.com/webdevarif/claude-skills/tree/main/firecrawl-monitor
Command: npx skills add https://github.com/webdevarif/claude-skills --skill firecrawl-monitor-webdevarif

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Tracking changes on websites normally requires wiring together cron jobs, scrapers, diff libraries, and email infrastructure yourself. This Skill replaces that stack with a single Firecrawl monitor that fetches pages on a schedule, diffs them against snapshots, filters out noise with an AI judge, and notifies you only when real content changes. ## Core Features & Use Cases - Page, batch, and site monitoring: Watch a single URL, a list of URLs, or every page discovered by a recurring site crawl, with each page labeled same, new, changed, removed, or error. - Web monitors: Monitor the whole web via search queries plus a goal to get alerted on new results such as product launches, funding rounds, papers, or brand mentions. - AI noise filtering and structured diffs: A plain-language --goal makes the judge ignore formatting, timestamps, and tracking-param churn, while JSON-mode change tracking returns per-field diffs like plans[0].price: "$19/mo" → "$24/mo". - Use Case: Watch a competitor's pricing page hourly and receive an email only when plan prices or features actually change, with no cron server or diff scripts to maintain. ## Quick Start Ask the AI to create a Firecrawl monitor on a URL with a schedule and goal, for example: monitor https://example.com/pricing every 30 minutes and email [email protected] when pricing changes.

Frequently Asked Questions about firecrawl-monitor

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I monitor a website for changes and get notified?

Create a Firecrawl monitor with firecrawl monitor create, passing --page with the URL, --schedule such as "every 30 minutes", a --goal describing what counts as a change, and --email or --webhook-url for notifications. Firecrawl handles fetching, diffing, and alerting server-side.

How do I monitor the web for new results instead of a specific URL?

Use a web monitor by passing --queries with comma-separated search queries plus a required --goal. Each check runs the searches and alerts only on new results matching the goal, with --search-window controlling recency and --max-results capping results per query.

What is the difference between a page monitor and a web monitor in Firecrawl?

Page monitors watch URLs you already have and label pages same, new, changed, removed, or error. Web monitors run search queries against the whole web and alert only on new results matching your goal, never reporting changed or removed.

Can I get structured per-field diffs instead of a text diff?

Yes, use JSON-mode change tracking by passing a JSON body to firecrawl monitor create with a changeTracking format, a prompt, and a schema. Changed pages then return keyed diffs like plans[0].price with previous and current values, plus a full snapshot.

What are the limitations of Firecrawl monitors?

The minimum schedule interval is 15 minutes, and monitoring is not available for zero-data-retention teams. External email recipients must confirm an opt-in email before receiving alerts, and monitor-triggered scrapes default maxAge to 0 for fresh fetches.