WhatIsLeaving Alert Utility
Turning streaming-removal data into a repeat-use utility.
Data confidence: Verified
Overview
WhatIsLeaving tests whether a focused streaming-removal utility can turn recurring search demand into repeat visits, email alerts, and monetization. The core user job is simple: I do not want to miss a movie or show before it disappears. Most streaming content is marketed around what is new — WhatIsLeaving focuses on what is expiring, which creates deadline-driven urgency. As of mid-2026 the experiment has widened: GamesLeaving.com now runs the same Platform × Time × Entity structure for game libraries, sharing chrome, cross-links, and network header. The operating question is no longer whether one utility works — it is whether a small network of leaving-focused utilities compounds brand queries and repeat behavior across both domains.
Operating question
Can structured leaving-soon data become a repeat-use utility — and can a small network of leaving-focused sites compound that behavior across streaming and games?
Current signal
Core thesis
Platform × Time × Entity creates more durable search coverage than one chronological list. The core bet is that streaming-removal demand should not be handled as a single feed.
Active sub-tests
Platform × Time × Entity Structure
Validated enough to continue- Hypothesis
- Three orthogonal axes — platform, time, and entity — will outperform a single feed because they match how users search.
- What changed
- WhatIsLeaving now uses platform hubs, platform-month pages, leaving-soon hubs, title pages, monthly archives, and data index pages.
- Metric to watch
- Daily visitors, GSC clicks, platform page traffic, monthly page traffic, title page traffic.
- Next check
- Continue monitoring, but stop debating the base structure.
This is the main validated thesis so far.
Title Page Expansion
Waiting for data- Hypothesis
- Entity-intent title pages can capture branded/title-specific searches without cannibalizing monthly pages.
- What changed
- Title pages are expanding through a policy-driven approach for a small but expanding percentage of titles with stronger entity signals.
- Metric to watch
- Title-page impressions, clicks, CTR, average position, and monthly page cannibalization.
- Next check
- Run a 14-day GSC review after the latest activation.
Platform Page Rails
Waiting for data- Hypothesis
- Adding Leaving This Month, Coming Up Next, and Recently Left rails to platform pages will reduce bounce and move users deeper into the site.
- What changed
- Platform pages now include new rails and improved title-link behavior.
- Metric to watch
- Platform-to-monthly clickthrough, pages per visit, bounce rate, and title clicks.
- Next check
- Read 14 days of analytics data.
Owned Audience
Running- Hypothesis
- Deadline-driven streaming removals can convert search visitors into email subscribers.
- What changed
- Weekly, Last Chance, and What Left newsletter formats are live.
- Metric to watch
- Subscriber growth, opens, clicks, unsubscribes, and signup conversion by placement.
- Next check
- Surface open/click reporting before changing cadence or templates.
Owned audience is over 40% of the way to the first sponsor-readiness threshold.
Monetization Readiness
Running- Hypothesis
- Once the utility crosses the traffic threshold, display ads can establish a first RPM baseline without changing the core user experience.
- What changed
- The display-ad readiness threshold has been met. Ad activation is the next monetization step.
- Metric to watch
- Ad approval, RPM, revenue, bounce, pages per visit, and site experience.
- Next check
- Finalize the ad activation path and record the first RPM baseline.
Affiliate Slot Measurement
Internal instrumentation- Hypothesis
- Affiliate placements should only expand after impression, click, and placement-level reporting is visible.
- What changed
- Affiliate slots exist, but reporting needs a clearer admin rollup before expansion.
- Metric to watch
- Slot impressions, clicks, CTR, placement, and revenue.
- Next check
- Add or surface affiliate CTR reporting before increasing affiliate placement.
Leaving Network header + GamesLeaving integration
Running- Hypothesis
- Shared network chrome and cross-links between WhatIsLeaving and GamesLeaving will compound brand queries and repeat behavior across both domains.
- What changed
- A shared Leaving Network header now links WhatIsLeaving and GamesLeaving, with cross-domain navigation and a consistent visual identity.
- Metric to watch
- GSC brand queries across both domains, sitelinks appearance, and cross-domain referral traffic.
- Next check
- Read GSC and referral data in 2 weeks.
First step toward treating the network as one operating surface.
Desktop nav overhaul — Platforms dropdown
Running- Hypothesis
- A dedicated Platforms dropdown will distribute nav clicks more evenly across platform hubs and reduce hub-page bounce.
- What changed
- Desktop nav rebuilt around a Platforms dropdown.
- Metric to watch
- Nav click distribution and hub-page bounce.
- Next check
- Read analytics in 2 weeks.
Mobile platform pill sub-header
Running- Hypothesis
- A persistent platform pill sub-header on mobile will lift platform-to-platform navigation without forcing users into the hamburger menu.
- What changed
- Mobile sub-header added with platform pills below the main header.
- Metric to watch
- Platform-to-platform navigation events on mobile and hamburger open rate.
- Next check
- Read analytics in 2 weeks.
Platform page sectioning — Last chance / Recently left / Coming up
Running- Hypothesis
- Three time-based sections on each platform page will move users deeper into the grid and lift section-level clicks.
- What changed
- Platform pages now split into Last chance, Recently left, and Coming up sections.
- Metric to watch
- Section click events, time on page, and grid scroll depth.
- Next check
- Read analytics in 2 weeks.
Title page CTA + search-answer redesign
Running- Hypothesis
- Rewriting title pages around a clear search-answer and stronger recovery CTAs will improve CTR from GSC and downstream affiliate clicks.
- What changed
- Title pages redesigned around a top-of-page answer block and recovery CTAs.
- Metric to watch
- recovery-* click-through on /title/* and GSC CTR on /title/*.
- Next check
- Read analytics in 2 weeks.
Sitemap — phased title inclusion + same-origin fix
Waiting for data- Hypothesis
- A phased top-150 title inclusion in the sitemap, plus a same-origin fix, will improve indexed pages count without triggering coverage errors.
- What changed
- Sitemap now includes the top 150 title pages in phases and serves same-origin.
- Metric to watch
- GSC indexed pages, coverage errors, and sitemap read status.
- Next check
- GSC weekly.
Multi-platform / multi-date title-page activation waves
Waiting for data- Hypothesis
- Activating title pages in structured waves across platforms and dates will produce cleaner GSC read-outs than one bulk activation.
- What changed
- Title-page activation is now sequenced in waves across multiple platforms and dates.
- Metric to watch
- GSC impressions and clicks on /title/*, indexed count.
- Next check
- GSC weekly.
Amazon affiliate optimization + verification queue
Waiting for data- Hypothesis
- Better ASC subtagging plus a verification queue will lift Amazon conversion attribution and reduce broken affiliate links.
- What changed
- Amazon affiliate links now carry structured ascsubtag values and route through an internal verification queue.
- Metric to watch
- recovery-amazon-click events, Amazon Associates conversion by ascsubtag, and verified-link count.
- Next check
- Read in 30 days.
Removal Index — new modules + history-wide stats fix
Running- Hypothesis
- New modules and a corrected history-wide stats calculation on /data will lift entrances and dwell time on the data property.
- What changed
- Added new modules to the Removal Index and fixed history-wide stats.
- Metric to watch
- /data impressions, dwell, and entrances.
- Next check
- GSC + Umami monthly.
Sticky header split — static count, sticky filters
Running- Hypothesis
- Splitting the header so the count stays static while filters stick will improve filter usage without hurting scroll behavior.
- What changed
- Header split into a static count row and a sticky filter row.
- Metric to watch
- Bounce, scroll depth, and filter usage events.
- Next check
- Read analytics in 1 week.
What we're measuring
- →platform page traffic
- →monthly page traffic
- →title page impressions and clicks
- →pages per visit
- →bounce rate
- →platform → monthly clickthrough
- →title page cannibalization or lift
- →newsletter opens and clicks
- →affiliate slot impressions and clicks
- →ad RPM once display ads are live
What is intentionally on hold
- →aggressive title-page expansion beyond the current policy
- →region expansion
- →newsletter sponsorship before the sponsor-readiness threshold
- →heavier affiliate placement before CTR reporting
- →major new UX features before the platform-rails read
- →social automation as a primary growth channel
Current result
Since launching in December 2025, WhatIsLeaving has grown from a near-zero baseline into a meaningful daily utility. The strongest signal is not a single spike, but the continued rise in baseline traffic and brand queries — now extending across the Leaving Network as GamesLeaving comes online. The property has crossed the internal display-ad readiness threshold and is moving from prove the structure into measure retention, monetization, and network compounding.
Next decision
The next decision is not whether the core URL structure works — it has enough signal to continue. The current wave adds a second front: a Leaving Network with GamesLeaving as the second node, a platform-page redesign across nav, sectioning, and title pages, and a sitemap + affiliate instrumentation pass. The next read should answer: is network chrome compounding brand queries across domains, did the platform-page redesign lift depth and section clicks, did the title-page redesign improve CTR from GSC, and did the phased sitemap and affiliate verification produce cleaner indexing and attribution.
Monthly updates
Update pending — to be filled at the end of the month.
Update pending — to be filled at the end of the month.
Update pending — to be filled at the end of the month.
Final takeaway
WhatIsLeaving is the portfolio's active data-utility experiment. The current lesson: a focused utility does not need to cover everything — it needs a recurring user job, clean URL structure, freshness, capture, and a clear monetization threshold. For BEHOLDINGS, the operating rule is: once the structure works, stop overbuilding and start measuring retention and monetization.