← Back to Tools

Source Health

Configured RSS, search, and alert feeds with recent monitor outcomes

This page groups recently stored articles by the feed that found them. The latest source check distinguishes a working-but-quiet feed from a fetch failure once operational logging is active.

⇄ Compare 🔍 Audit Log Articles
Add New RSS/Search Feed

Add a new ingestion source and route it to a specific client and workflow. The scoped source becomes available to future monitor runs without changing the legacy feed CSV or publisher registry.

Stored in Supabase: source type, URL, label, optional publisher domain, client/workflow route, optional category, priority, failed-scrape visibility, and routing note. Leaving category unassigned lets workflow keyword rules choose the article category. With no category, failed-scrape visibility remains off because the system cannot safely classify a page it could not read.
Publisher trust is a separate decision. Use the scoped publisher-tier panel below after the feed is saved when the domain should receive a trust tier.
Add or Change a Scoped Publisher Tier

Classify a publisher as Verified, Discovery, or Watchlist for one client and workflow. This does not change feed ingestion, and the same domain may have different tiers in different workflows.

Saved in Supabase for the selected scope. Category-specific tiers override workflow-wide tiers. When no scoped tier exists, only Mozilla Client Coverage may fall back to the legacy Mozilla registry.
Standardize a Publication Name

Set one display name for a publisher domain across every client, workflow, report, export, and Report Mule transfer. The original feed label remains stored for auditing.

Enter a domain to check its current standard name.
Loading sources...

Feed Health

Feed-level view grouped by the configured source label that discovered recent articles.