Firecrawl Keeping track of web page updates is a surprisingly tedious job. For pages you want to know about when they change, such as a competitor’s pricing page, a tool’s changelog, or revisions to terms of service, checking them every day is a hassle, and most of the time nothing has changed.
Firecrawl Monitor (/monitor), released by Firecrawl on May 27, 2026, takes over this “change detection” entirely. You decide which pages to watch and on what schedule, write in plain text “what kind of change you want to be told about,” and it notifies you with a diff only when a change occurs.
In this article, I summarize what Firecrawl Monitor can do, how notifications work, credit usage and pricing, and who it is and isn’t for, based on the official documentation and pricing page (information as of October 2026).
What Is Firecrawl Monitor?
Firecrawl Monitor is a feature that checks specified pages or an entire site at regular intervals, detects differences from the previous check, and notifies you. It is built on the engine of Firecrawl, a web scraping and crawling API, so existing Firecrawl users can use it without an additional contract.
If you tried to build page change monitoring yourself, you would generally need the following:
- A scheduling mechanism (cron)
- A place to store snapshots of the content you fetched last time
- Diff processing to compare old and new
- A webhook to send notifications (including resending on failure)
- Removing “noise” that changes every time, such as ads, timestamps, and session tokens
Firecrawl Monitor bundles these into a single endpoint. According to the official explanation, an AI agent receives only “the parts that changed,” so LLM token usage can be reduced by up to 90% compared with rereading the whole page.
Main Features of Firecrawl Monitor
Scheduled Checks from 5-Minute Intervals and Diff Detection
You can specify the check interval in natural language such as “every 30 minutes,” “hourly,” “daily at 9am,” or “weekly,” or with a cron expression. The shortest interval is 5 minutes.
At each check, it fetches the target page as Markdown and compares it with the previous snapshot. The result is recorded for each page with one of these statuses.
| Status | Meaning |
|---|---|
| same | No change since last time |
| changed | The content changed |
| new | A newly found page |
| removed | A page that no longer exists |
| error | The fetch failed |
Pages with changes come with a diff (in unified diff format) showing which lines were added and removed. A fixed URL (permalink) is also issued for each check, which makes it easy to share a specific change with team members or agents.
Notify Only “Meaningful Changes” with Goals and AI Judgment
A distinguishing feature of Firecrawl Monitor is the Goal. If you write in plain text what you want to know, such as “notify me when the price of a pricing plan changes,” the AI judge compares the detected diffs against the Goal and decides whether the change should be notified.
The judgment result includes whether the change is meaningful, a confidence level, and the reason. For example, changes like these are less likely to be notified:
- The year in the footer copyright notice changed
- A timestamp was updated
- Rotating reviews were swapped out
For email notifications, if all changed pages are judged as “noise,” no email is sent at all.
Note that the Goal examples in the official documentation are all in English. The official documentation doesn’t say anything about accuracy when you write Goals in other languages, so if you monitor pages in a language other than English, I recommend testing a little before running it in earnest.
Three Types of Monitoring Targets
One monitor can register 1 to 50 targets, and you can mix types.
| Type | What it monitors | Where to use it |
|---|---|---|
| Page monitoring (scrape) | Changes to a specified URL | Pricing pages, changelogs, terms pages |
| Site monitoring (crawl) | Additions, changes, and removals across all pages found by crawling | An entire documentation site, new blog posts |
| Web-wide monitoring (search) | New results that match a search query | Competitors’ new products, release information for new models |
Web-wide monitoring is like waiting for pages that don’t exist yet. Search results are judged one by one against the Goal, and a result that has already been notified is not notified again in later runs. A Goal is required for this type (unless you turn AI judgment off).
JSON Mode to Monitor Only Specific “Fields” Such as Prices
If you want to monitor only specific fields rather than text differences across the whole page, use JSON mode. When you specify fields such as plan names, prices, and feature lists with a schema (or a prompt), it extracts those fields at each check and returns only the fields that changed, as “previous value → current value.”
For example, you can receive it in the form: the pricing page’s plans[0].price changed from $19/mo to $24/mo. It isn’t affected by layout changes or updates to unrelated text, so it suits uses like price monitoring where you only want to watch a particular value. If you also want text diffs at the same time, there is a mixed mode that combines JSON and git-diff.
Notifications via Webhook, Email, and Slack
There are three notification destinations, and you can use them together.
- Webhook: You can choose between two kinds of events:
monitor.page, sent each time a result is available for a page, andmonitor.check.completed, sent when the whole check completes. It is signed, and you can also set custom headers. The receiving side must return a 2xx within 10 seconds, and failures are retried after 1 minute, 5 minutes, and 15 minutes - Email: A summary including diffs is delivered. You can specify up to 25 recipients, and a confirmation email is sent to newly added recipients
- Slack: Notifies the channel you specify. It can be set up only from the dashboard, not from the API or SDK
Monitor history is kept for 30 days by default, and can be extended up to 365 days.
How Firecrawl Monitor Works
The overall flow is these four steps.
- Create a monitor targeting one or more pages (or an entire site)
- Firecrawl fetches the pages on schedule and saves them as snapshots
- At each check, it compares the new content with the immediately preceding snapshot and takes a diff
- If there is a change, it sends the structured diff and a permalink by webhook or email
How to Use Firecrawl Monitor
This is the basic flow for creating a monitor from the dashboard. Screen labels may change, so match the detailed names to your actual screen.
:::steps
- Open “Monitoring” in the Firecrawl dashboard
Log in to your Firecrawl account, open the monitoring page of the dashboard, and create a new monitor.
- Enter the URLs to monitor
You can set a single page, multiple URLs, or an entire site. For an entire site, you can also specify paths to include and exclude.
- Write the Goal
Briefly and specifically write the change you want to be notified about, such as “notify me when the price of a pricing plan changes.” If there is a scope (only the top 10 items, only a specific plan, and so on) or something you want to exclude, mention that too, and accuracy improves.
- Decide the schedule
Choose a frequency such as hourly or daily. For pages that rarely change, widening the interval saves credits.
- Set the notification destination
Choose from webhook, email, and Slack. Even if you aren’t an engineer, you can run it with just email or Slack.
- Check the estimated monthly credits and enable it
The estimated monthly credit usage based on your settings is displayed, so enable it once you are comfortable with it.
pros:
- You don’t have to build cron, snapshot storage, diff processing, webhook retries, and so on yourself
- With a Goal, you can exclude “meaningless changes,” such as ads, dates, and rotating reviews, from notifications
- Supports three kinds of monitoring: a single page, an entire site, and web search
- JSON mode lets you monitor only specific fields such as prices
- Supports webhook, email, and Slack, and with only email or Slack you can run it without code
- You can check the estimated monthly credits before enabling it
- You can try it with a free allowance of 1,000 credits per month cons:
- It consumes credits at every check, so it can balloon with short intervals and many pages
- Because pages are converted to Markdown for comparison, purely visual changes in CSS or images may not show up in the diff
- The official Goal examples are in English, and accuracy when written in other languages isn’t stated officially
- Slack notifications can be set up only in the dashboard, not from the API or SDK
- It is a new feature released in May 2026, and there is still little long-term operating track record
