How it works

How competitor tracking works in Content Radar

A six-step workflow from reviewed business context to content and product monitoring, reviewed changes, collaboration, and Workspace History with a seven-day restore window.

01

Step 1

Start with a Business Profile you can review

Create a Business Profile manually or analyze your website, then review the captured company, market, audience, and offering context before confirming it. This context anchors competitor discovery and can be edited or replaced later.

Define business context

  • Manual Business Profile creation
  • Website analysis with field review
  • Draft, confirm, edit, and replace states
  • Business context stays workspace-scoped
02

Step 2

Choose the competitor relationship and market scope

Run discovery for direct competitors, indirect competitors, or both. Choose All markets, Local, or Global scope, review the evidence and score for each candidate, then add relevant companies or reject the rest. Manual competitor creation remains available.

Discover competitors

  • Direct, indirect, or both relationships
  • All markets, Local, or Global scope
  • Website validation and deterministic scoring
  • Persistent rejection and eligible restoration
  • Manual competitor creation
03

Step 3

Discover public endpoints or add an ecommerce store

Use a competitor website as a bounded discovery starter for common RSS, Atom, and sitemap paths, or add a known structured source. You can also add a compatible public Shopify, WooCommerce, or structured custom ecommerce store, which runs a bounded compatibility check before it is monitored. Neither path crawls arbitrary pages or bypasses access controls.

Add sources or compatible stores

  • Bounded RSS, Atom, and sitemap discovery
  • Checks for compatible public Shopify, WooCommerce, and structured custom stores
  • Explicit source selection and promotion
  • Visible blocked and failed outcomes
  • No crawling, CAPTCHA bypass, or proxy evasion
04

Step 4

Keep content and product records distinct

Direct RSS, Atom, and sitemap ingestion normalizes and deduplicates entries before writing new Articles, while a Google Alerts RSS monitor and manual entry write Candidate URLs. Compatible ecommerce stores follow a separate path: a bounded catalog import fills Store Products, kept distinct from Articles and Candidate URLs.

Import content or a product baseline

  • Structured source entries create Articles
  • Google Alerts RSS creates Candidate URLs
  • Compatible stores import a baseline into Store Products
  • Workspace-wide URL deduplication
  • Bounded sitemap, catalog, and item limits
05

Step 5

Work through tracked content and product changes

Confirm, dismiss, or mark Candidate URLs as duplicates, and review Articles with New, Reviewed, Saved, and Archived states. Manual and daily scheduled store checks record Product Events for new and removed products, price changes, and stock changes, which appear in Recent changes and as in-app alerts. Source health, ingestion runs, and live seven-day summaries show where checks need attention.

Review content, products, and activity

  • Candidate confirmation and bulk review
  • Article status filters and search
  • Product Events, Recent changes, and product alerts
  • Source and monitor health states
  • Live seven-day summaries
06

Step 6

Share the workspace and recover eligible changes

Invite members with workspace roles so the team can work from the same competitors, sources, content, and stores. Workspace History separately groups supported entity changes by day and category, provides exact restore previews, and allows eligible entity restoration within seven days. Product Events remain outside that restore system.

Collaborate and preserve history

  • Workspace invitations and member roles
  • Month browsing and day grouping
  • Entity filters and cursor pagination
  • Exact restore previews
  • Seven-day eligible restore window

The full workflow at a glance

Every step stays connected. Business context guides competitor discovery, competitors anchor sources and compatible stores, sources create Articles or Candidate URLs, and stores create Store Products and Product Events. Detections appear in alerts and Recent changes. Workspace History separately records supported entity changes, with eligible restoration available for seven days.

Business ProfileCompetitorsContent or Product MonitoringArticles or Product EventsAlerts and Recent changesCollaboration

Ready to start the workflow?

Open the dashboard and start with your Business Profile, relevant competitors, and a supported content source or compatible store.