# Leaving Soon Alerts: Track Streaming Catalog Removals

Source: PageCrawl.io Blog
URL: https://pagecrawl.io/blog/streaming-catalog-leaving-soon-alerts
Published: 4 September, 2026

---

A film studies lecturer builds her spring syllabus in December around eleven films her university can stream through its library platform. In February, three of them are gone. Not moved, not behind a different tier, gone. The licences expired at the end of January, the platform removed the records without notice, and she found out when a student emailed to say the link in the reading list returned nothing. She had to rebuild two weeks of teaching in four days.

The same thing happens to ordinary viewers on a smaller scale every month. You add a documentary to your list in June, decide to watch it "next weekend" six weekends in a row, and by August the title page reads "currently unavailable to stream." Streaming catalogs are not archives. They are rented shelves, and the rental terms are invisible unless you go looking for them.

Both problems have the same fix. Streaming services publish leaving-soon lists, and individual title pages change when availability changes. Neither will email you. But a monitor pointed at those pages tells you on the next check that a title you care about has been flagged for removal, which is usually the only warning window you get.

This guide covers why titles leave, which pages carry the removal signal, how much notice you get in practice, how to set up leaving-soon monitoring, and how libraries and media teams can turn the same setup into a licence-expiry early warning system.

<iframe src="/tools/streaming-catalog-leaving-soon-alerts.html" style="width: 100%; height: 500px; border: none; border-radius: 4px;" loading="lazy"></iframe>

### Why do titles disappear from streaming catalogs?

Titles leave because the streaming service licensed them for a fixed term and that term ran out. The [Netflix Help Center explanation of why shows and movies leave](https://help.netflix.com/en/node/60541) says renewal depends on availability, cost, and how much a title is watched. Nothing about that decision is announced in advance to subscribers.

#### Licences are term deals, not purchases

A streaming service rarely owns the film you are watching. It has bought the right to stream it in a specific country for a set period, often one, two, or three years. When the term ends, three things can happen: the service renews, the rights holder sells the window to a competitor, or the title goes dark everywhere while the next deal is negotiated. Only the first outcome leaves the catalog page looking the same, and that is why an apparently stable library quietly reshuffles every month.

#### Rights holders now compete with the platforms

Studios that once licensed their back catalog to whoever paid most now run their own services and pull titles home when the contract lapses. A film can leave a large general service and reappear weeks later on a narrower branded one, or on nothing at all in your country. [JustWatch](https://www.justwatch.com) exists precisely because a title's location changes often enough to need a lookup service.

#### Curated services rotate on purpose

Not every removal is a failed renewal. Specialist services build rotation into their programming. [The Criterion Channel](https://www.criterionchannel.com) runs limited engagements alongside its permanent collection and publishes a leaving list for each month, so a short-run title may only ever have been scheduled for three or six months. The removal is not a surprise to the service. It is only a surprise to you, because you never read the leaving page.

#### Library platforms expire by checkout count as well as by date

Library streaming works differently again. Public and academic library platforms commonly license titles under terms that expire after a fixed number of checkouts, or after a fixed number of months, whichever comes first. A popular documentary can vanish from a library catalog because it was borrowed too many times, not because a calendar date passed. That makes the expiry effectively unpredictable from the outside and makes monitoring the catalog record the only reliable signal.

### What should you monitor to catch removals before they happen?

Monitor two page types: the service's own leaving-soon or last-chance list, and the individual title pages for the handful of films you genuinely intend to watch or teach. The list catches broad changes across the catalog. The title page catches the ones the list misses, and the lists miss plenty.

#### The service's leaving-soon list

Most large services surface departing titles somewhere. Netflix groups them under a "Last Chance to Watch" style category rather than a plain URL, and the exact route to that category has changed more than once, so the practical approach is to monitor whichever browse or search view currently shows it in your account and region. Curated services are easier: The Criterion Channel publishes a dated leaving page each month, which is a clean, stable target for a monitor.

Note: leaving lists are regional. A title expiring in the United States may have another year to run in the United Kingdom or Germany, and vice versa. Monitor the list as it appears in the region where you actually watch, and treat any roundup you read elsewhere as a hint rather than a fact about your account.

#### Individual title pages for the things you care about

The list is a summary, and summaries drop things. Netflix's own last-chance grouping has been documented as incomplete by trackers who follow it closely. If a specific film matters, monitor its title page directly. Availability changes show up there as concrete text: a leaving date badge, a change from a play button to a "not available" state, or the provider row disappearing from an aggregator page. That is a small, unambiguous change a monitor can watch for reliably.

| Page type | What it tells you | Best for |
|-----------|-------------------|----------|
| Service leaving-soon list | Batch of departures, usually with dates | Broad awareness, monthly planning |
| Individual title page | Availability state for one title | The 5 to 20 titles you actually need |
| Aggregator title page | Which services carry it right now, per country | Tracking a film across providers |
| Library catalog record | Licence terms and current availability | Reading lists, teaching, collections |

#### Aggregator pages when you follow the film, not the service

If your question is "can I still watch this anywhere," the per-service page is the wrong target. An aggregator title page lists every provider currently offering the film in your country, so a change there tells you both that one service dropped it and that another picked it up.

#### Library catalog records

For an academic or public library collection, the catalog record is the authoritative page. Licence notes, streaming terms, and availability all live there, and when a licence lapses the record either disappears or flips to unavailable. Monitoring the record for each title on a syllabus turns a silent removal into a dated alert.

### How much warning do you actually get before a title leaves?

In practice, roughly a month, and only if the service flags it. Netflix has typically surfaced a leaving label around 30 days before a title departs. Curated services publish a leaving page at the start of the month the titles depart. Library platforms often give no visible warning at all, because a checkout-count expiry has no announced date.

#### The 30-day pattern on large services

A month is enough time to watch a film and nowhere near enough to reorganise a course, negotiate a replacement licence, or source a physical copy through interlibrary loan. It is also a convention rather than a guarantee: titles have left with less notice, and been re-added days later when a deal closed late. Treat 30 days as a best case, not a promise.

#### No warning at all in library platforms

The hardest case is the one with the highest stakes. A title licensed for a set number of checkouts can expire in the middle of a semester with no advance flag anywhere in the interface. The only external signal is the catalog record changing. This is why a media librarian monitoring 40 reading-list records will catch expiries that no vendor notification would ever have surfaced, and it is the same logic behind monitoring any page whose owner has no incentive to tell you it changed.

### How do you set up leaving-soon alerts with PageCrawl?

You point PageCrawl at the leaving list and at each title page you care about, choose a tracking mode that watches text rather than the whole rendered page, set a check frequency that matches how much notice you need, and route alerts to a channel you actually read. Setup takes a few minutes per monitor.

1. **Add the URL.** For a service leaving page, use the exact URL as it appears when you are signed in and in your own region. For a title page, use the canonical title URL rather than a search result link, which can expire. For a library catalog record, copy the permalink the catalog offers rather than the session URL.
2. **Pick the tracking mode.** Content or text tracking is the right default here. It watches the meaningful text of the page and ignores layout, so a reshuffled carousel does not fire an alert. Full-page visual tracking is a poor fit for streaming interfaces, which repaint constantly with personalised rows and rotating artwork.
3. **Set the check frequency.** Leaving lists update in monthly waves, so a daily or hourly cycle is plenty and the free tier's 60-minute checks are genuinely sufficient. Individual title pages for something you are actively planning around justify the 15-minute Standard frequency, since a page can flip state on any day of the month.
4. **Choose your notification channels.** Email, Slack, Discord, Teams, Telegram, and webhooks are all available. A personal watchlist is well served by [Telegram](/blog/telegram-website-monitoring-alerts-setup) or [Discord](/blog/discord-website-change-alerts) because they reach your phone. A library or media team should route alerts into the shared Slack or Teams channel where collection decisions already get made, so the alert lands next to the person who can renew the licence.
5. **Add keyword and threshold rules.** This is what turns the setup from noisy to useful. Set a keyword condition on phrases like "leaving", "last chance", "no longer available", or "expires" so only real availability language triggers an alert. Our walkthrough on [conditional alerts using price, keyword, and threshold rules](/blog/conditional-alerts-price-keyword-threshold-rules) covers the syntax and the common traps.
6. **Exclude the noisy regions.** Streaming pages carry recommendation rows, "because you watched" strips, trending counters, and personalised artwork that change on every load. Click any detected change and tell the monitor to ignore that region. Two or three passes trains out nearly all of it. Our guide to [reducing monitoring false positives](/blog/reduce-website-monitoring-false-positives) goes deeper on this.
7. **Turn on screenshots and grouping.** A screenshot lets you confirm from the alert itself whether the leaving badge appeared or a recommendation row simply reshuffled. Group the monitors into a folder named for the service or the semester so a month of alerts reads as one coherent list rather than scattered notifications.

Start with one leaving-soon list for the service you use most plus the three or four title pages you would genuinely be annoyed to lose. That is five monitors, comfortably inside the free tier's six.

### How should libraries and media teams handle licence expirations?

Treat the catalog record as the monitored object and the alert as a workflow trigger. Monitor every title on an active reading list, route alerts to the shared channel where collection development happens, and build the renewal decision into the alert rather than discovering the gap when a student reports a dead link.

#### Monitor by reading list, not by whim

The unit that matters is the course, not the individual film. Create a folder per module or per semester, add a monitor for each catalog record on that reading list, and let the folder mirror the syllabus. When an alert fires, you know which teaching week is affected before you have opened anything. This is the same structure that works for any collection where a set of pages has to stay valid together.

#### Route alerts to the person who can act

An email to a personal inbox during annual leave is a lost alert. Send catalog alerts to a shared Slack or Teams channel that acquisitions, the subject librarian, and the module lead all watch. The value of the alert is not that someone knows. It is that the person who can buy another licence, request an interlibrary loan, or substitute a title knows in time to do it.

#### Keep a record of what changed and when

Monitoring history doubles as documentation. When a vendor claims a title was available all term, or when a budget conversation turns on how often licences lapsed, a dated record of catalog changes with screenshots settles the argument in a minute. Platforms like [Kanopy](https://www.kanopy.com) are widely used across public and academic libraries, and their availability behaviour differs by institution and licence model, so a locally captured history of your own catalog is worth more than any general advice about how the platform behaves.

### What goes wrong when you monitor streaming catalog pages?

Three things: personalised pages that never look the same twice, sign-in walls on the views that carry the leaving information, and regional differences that make a monitor report something true for a different country. All three are manageable once you know to expect them.

#### Personalisation makes full-page tracking useless

A signed-in streaming home page is rebuilt for you on every visit. Row order changes, artwork changes, the "continue watching" strip changes after every session. Visual or full-page tracking on such a page produces an alert every check and teaches you to ignore alerts. Use text or content tracking scoped to the part of the page carrying the leaving information, and exclude the recommendation regions explicitly.

#### Some views need you to be signed in

Leaving lists that live inside a browse category exist only for a signed-in session. PageCrawl supports authenticated monitoring: you capture the session once and checks reuse it, the same setup described in our [guide to monitoring pages behind a login form](/blog/monitor-website-behind-login-form-steps-automation). Where a public equivalent exists, such as a curated service's published leaving page or a library catalog permalink, prefer the public URL because it needs no maintenance.

#### Regional catalogs diverge

Availability is licensed country by country, and the same title URL can show different states depending on where the page is fetched from. If you monitor a title page and the alert disagrees with what your app shows, region is the first thing to check. PageCrawl lets you set the monitoring location per monitor, so pin it to the country you actually watch in and the results will line up.

#### Removal is not always permanent

A title can leave, sit dark for a few weeks, and return under a new deal, sometimes on the same service. Keep the monitor running after a removal fires rather than deleting it. The return is a change too, and it is the alert that saves you from buying a copy you did not need. This is the same reasoning behind watching a page continuously rather than checking it once, which also applies when you track [streaming service price changes](/blog/streaming-service-price-change-monitoring) across the same subscriptions.

### How do you build a watchlist that survives catalog churn?

Tier it. Put your fastest checks on the few titles with a real deadline attached, keep a slower monitor on each service's leaving list for general awareness, and let an aggregator page handle "is this anywhere" questions. The goal is a small number of alerts that each mean something.

#### Tier 1: titles with a deadline

A film on next month's syllabus, a documentary you promised to discuss with someone, a series you are three episodes from finishing. These get individual title-page monitors with keyword rules on availability language and a push channel that reaches your phone. There should never be many of these, which is what makes them worth checking often.

#### Tier 2: service leaving lists

One monitor per service you subscribe to, checked daily, alerting to email or a digest. This is your monthly planning input. When the list changes, you scan it, promote anything you care about to Tier 1, and forget the rest. Low effort, low noise, high coverage.

#### Tier 3: discovery and cross-provider

Aggregator pages for films you would watch if they ever appeared on something you already pay for. These can check slowly and report weekly. Treat them like a wishlist that occasionally rings, in the same spirit as watching a cinema listings page for a [one-off screening you would otherwise miss](/blog/movie-showtime-ticket-alerts).

Watchlists rot, so prune them. Titles get watched, courses end, subscriptions get cancelled. At the end of each quarter or teaching term, delete the monitors whose reason has expired. Twelve live monitors you trust beat sixty stale ones you have learned to swipe away.

### Choosing your PageCrawl plan

PageCrawl's **Free plan** lets you monitor **6 pages** with **220 checks per month**, which is enough to validate the approach on your most critical pages. Most teams graduate to a paid plan once they see the value.

| Plan | Price | Pages | Checks / month | Frequency |
|------|-------|-------|----------------|-----------|
| Free | $0 | 6 | 220 | every 60 min |
| Standard | $8/mo or $80/yr | 100 | 15,000 | every 15 min |
| Enterprise | $30/mo or $300/yr | 500 | 100,000 | every 5 min |
| Ultimate | $99/mo or $999/yr | 1,000 | 100,000 | every 2 min |

Annual billing saves two months across every paid tier. Enterprise and Ultimate scale up to 100x if you need thousands of pages or multi-team access.

If monitoring helps you land one sold-out concert ticket pair, one limited sneaker drop, or one in-demand product at retail instead of resale, Standard at $80/year is already paid for. 100 monitored pages covers every major retailer you care about, and the 15-minute check frequency catches most drops the moment they go live.

### Getting Started

Pick the service you use most and set up one monitor on its leaving-soon list, using content tracking and a daily check. Then add title-page monitors for the three or four films or series you would actually be annoyed to lose, with a keyword rule on availability language so only real changes reach you.

If you work in a library or media team, start with a single reading list. Add a monitor for each catalog record, route the alerts into the shared channel where acquisitions decisions get made, and run it for one term. The first expiry you catch with weeks to spare rather than days will make the case for expanding to the rest of the collection.

Streaming catalogs will keep shrinking and reshuffling without telling you. Put a monitor on the pages that carry the warning, and let the removal notice come to you while there is still time to do something about it.

---

Need more? The complete PageCrawl.io help center, with every article, is available as a single document at https://pagecrawl.io/llms-full.txt. Read it for context on anything this page does not cover.
