Source types
Each source type below is a directory page covering what it is, why it matters, and how Content Radar helps you turn it into a usable signal.
RSS feeds
Detect new competitor articles and updates from RSS and Atom feeds.
Learn moreSitemaps
Discover new competitor URLs from XML sitemaps and sitemap indexes.
Learn moreCompetitor blogs
Track new posts, topics, and publishing patterns from competitor blogs.
Learn moreChangelogs
Monitor competitor changelogs for product, feature, and roadmap signals.
Learn moreNewsrooms
Track competitor press pages for launches, partnerships, and market news.
Learn moreProduct updates
Collect newly published competitor product-update entries from supported sources.
Learn moreResource hubs
Track competitor guides, reports, templates, and webinars for content gaps.
Learn moreSource monitoring covers what competitors publish. To track product, price, and stock changes on compatible ecommerce stores, use Product Monitoring, the separate pillar for competitor stores.
Why it matters
Competitor content movement is spread across many surfaces: a blog post here, a changelog entry there, a new resource page that never makes it into a newsletter. Checking each of these manually, across every competitor, does not scale.
Source monitoring brings supported structured endpoints into one workspace. Successful feed and sitemap checks create Articles directly, while Google Alerts RSS and manual discovery create Candidate URLs for review.
Choose the publishing surface you need to review, then find its supported feed or sitemap. A blog helps you follow topics and publishing cadence. A changelog records releases, while a newsroom collects company announcements. A sitemap can expose resource pages and guides that are missing from a blog feed.
How it works
Add competitor sources
Discover or attach public RSS, Atom, and sitemap endpoints, or use an explicit manual URL path.
Check supported structured sources
Run a source check manually or use the configured daily ingestion schedule. Plain pages are not watched for arbitrary changes.
Detect new content movement
New feed and sitemap entries are normalized, deduplicated, and written directly to Articles.
Review signals and act
Review Article statuses. Confirm or dismiss Candidate URLs from Google Alerts RSS and manual discovery.
Built for different teams
Review Articles from supported feeds and sitemaps alongside the SEO tools and planning process the team already uses.
Review public publishing evidence from supported product-update, changelog, and newsroom endpoints.
Monitor competitor blogs and resource hubs to plan editorial calendars around real publishing patterns.
Get a lightweight, structured view of what your market is publishing without manual research overhead.
Organize a focused set of competitor sources and review them with members in one shared workspace.
Trust and compliance
Content Radar is designed around public, user-approved, and structured source monitoring.
Public RSS and Atom feeds, XML sitemaps, and content surfaces such as blogs, changelogs, newsrooms, product updates, and resource hubs when they expose a supported structured endpoint. Specific URLs can also be imported manually.
No. Content Radar is designed around public, user-approved, and structured source monitoring. There is no proxy rotation, CAPTCHA bypass, browser automation, deceptive user agents, or robots.txt bypass.
Successful RSS, Atom, and sitemap checks add unseen supported entries directly to Articles. Google Alerts RSS and manual Candidate URL entry require confirmation before becoming Articles. You can also import a selected Article URL directly, without Candidate URL review.
Yes. You can attach a sitemap, or add specific URLs manually. Google Alerts RSS is also available as a compliant discovery fallback.
Start with a public blog feed for new posts, a changelog feed for release entries, or a newsroom feed for company announcements. Add a sitemap if you also need pages outside those feeds. Blogs, changelogs, and newsrooms need a supported feed or sitemap for recurring checks; adding a plain page URL does not make it a page-change monitor.
Source monitoring is built for founders and builders, growth, SEO, and content teams, and agencies that monitor competitor publishing for clients.