Competitor Website Change Briefing

This Actor turns website changes into competitive intelligence.

Track what competitors changed on their websites, understand why it may matter, and turn that into a briefing your team can actually use.

This Actor monitors competitor and SaaS websites across recurring runs, detects meaningful changes, groups them into business signals, and produces decision-ready output for product marketing, sales enablement, founder, strategy, and competitive intelligence teams.

It is built for practical questions such as:

• Did a competitor change pricing, packaging, or plans?
• Did they reposition their homepage or value proposition?
• Are they pushing harder into AI, enterprise, security, or a new buyer workflow?
• Did they add new partner, integration, or solution pages worth flagging internally?

What It Does

The Actor crawls one or more websites, stores normalized snapshots, compares each run against prior history, and publishes grouped business signals instead of raw page diffs.

It is designed to surface meaningful website change intelligence, not just scraped pages.

Why It Is Different

This is not a generic site crawler and not a page-diff dump.

The Actor is optimized for monitoring:

• focused crawl mode prioritizes homepage, pricing, product, trust, case studies, and other commercial pages first
• repeated runs use persistent snapshot memory so the Actor behaves like a monitor, not a first-run scraper every time
• findings are grouped into business signals such as pricing_update, homepage_repositioning, partner_expansion, and ai_positioning_expansion
• evidence is filtered and condensed so the output is readable by operators and stakeholders

Why This Actor Stands Out

Most Apify Actors are built for one-time extraction. This one is built for recurring competitive monitoring.

What makes it different:

• built for change detection across runs, not one-off scraping
• produces grouped business signals, not raw page-level crawl output
• includes baseline-vs-monitoring logic so first runs are framed credibly
• outputs briefings and review-ready artifacts, not just data you still need to interpret manually

This makes it meaningfully different from:

• generic crawlers
• one-site content scrapers
• raw website data extractors
• Actors that collect pages but do not explain what changed and why it may matter

Why Not Just Use A Crawler?

A crawler can tell you which pages were fetched. It usually cannot tell you which website changes are commercially meaningful.

Most teams do not need:

• a pile of page HTML
• hundreds of low-signal diffs
• one dataset row for every crawled URL

They need:

• a short list of meaningful changes
• evidence tied to those changes
• language that helps someone decide whether to care

This Actor is opinionated around that outcome. It compares runs, reduces boilerplate noise, groups related changes, and produces business-facing output instead of crawl exhaust.

First Run Vs Monitoring Runs

The Actor distinguishes baseline capture from true monitoring:

• On the first run, findings are framed as baseline discovery, for example:
  • Baseline pricing structure captured
  • Initial homepage positioning captured
  • Initial partner footprint discovered
• On later runs, the Actor compares against stored snapshots and emits actual added, updated, or removed changes when it has enough evidence

This makes the output much more credible for recurring competitive monitoring.

Best For

• Product marketing teams tracking competitor positioning changes
• Sales enablement teams updating battlecards and objections
• Founders and leadership teams reviewing weekly market movement
• Strategy, corp-dev, and market intelligence teams monitoring GTM shifts and expansion signals
• Teams tracking enterprise messaging, trust, and AI positioning

Common Use Cases

• Weekly competitor briefings for product marketing
• Pricing and packaging monitoring for revenue and leadership reviews
• Battlecard refresh inputs for sales enablement
• Tracking AI, enterprise, trust, and integration messaging shifts
• Monitoring solution, use-case, and partner ecosystem expansion
• Detecting when a competitor starts speaking to a new buyer segment

How Teams Use This

• Replace manual competitor checks across multiple websites
• Replace Slack threads like "did anyone notice X changed pricing?"
• Feed weekly briefings into product, sales, or leadership syncs
• Provide structured inputs for battlecards, strategy docs, and market reviews

Typical Signals

The Actor can publish signals such as:

• pricing_update - detect plan, packaging, or enterprise motion changes
• homepage_repositioning - detect shifts in value proposition or target audience
• partner_expansion - track integration and ecosystem growth
• solution_expansion - surface new use-case, workflow, or solution coverage
• ai_positioning_expansion - identify AI-related messaging changes
• product_capability_expansion - highlight broader platform or capability emphasis
• customer_proof_update - monitor case studies, testimonials, and proof points
• compliance_update - flag security, trust, and enterprise-readiness updates
• announcement_activity - capture launch and announcement-oriented content changes

Why It Is Cost-Efficient

This Actor is designed to spend compute on signal quality, not broad crawl volume.

Cost efficiency comes from:

• focused mode prioritizing commercially important sections first
• family caps that prevent partner, integration, or similar page clusters from consuming the whole crawl budget
• grouped output that produces one public signal for a business theme instead of one record per page
• persistent monitoring memory, so recurring runs compare against prior snapshots instead of acting like full rediscovery every time

For most competitor-monitoring workflows, that is a better tradeoff than paying to crawl large portions of a site just to produce noisy page-level output.

Input

Minimum input:

{
  "startUrls": [
    "https://competitor-a.com/",
    "https://competitor-a.com/pricing",
    "https://competitor-b.com/"
  ]
}

Recommended recurring-monitoring input:

{
  "monitorId": "weekly-saas-monitor",
  "startUrls": [
    "https://competitor-a.com/",
    "https://competitor-a.com/pricing",
    "https://competitor-b.com/",
    "https://competitor-b.com/pricing"
  ],
  "allowedDomains": [
    "competitor-a.com",
    "competitor-b.com"
  ],
  "crawlMode": "focused",
  "prioritySections": [
    "homepage",
    "pricing",
    "product",
    "case-studies",
    "security"
  ],
  "watchKeywords": [
    "enterprise",
    "SOC 2",
    "usage-based pricing",
    "AI agents"
  ],
  "changeThreshold": "medium",
  "enableBriefing": true,
  "enableHtmlDashboard": true
}

Important inputs:

• monitorId: use this for scheduled recurring runs so the same monitor keeps stable history
• crawlMode: focused is recommended for weekly monitoring; sitewide is broader but noisier
• changeThreshold: medium is the best default for buyer-readable output
• watchKeywords: highlights terms you care about in the final dataset and briefing

Output

The Actor produces:

• dataset items grouped by business signal
• SUMMARY for quick review
• BRIEFING_MD for email, Slack, Notion, or human review
• BRIEFING_JSON for automations
• DASHBOARD for browser-friendly visual review

The dataset is intentionally not one row per page.

Instead, each item is a grouped signal with fields such as:

• siteKey
• signalType
• severity
• status
• summary
• whyItMatters
• evidence
• evidenceUrls
• relatedPagesCount
• confidence

Example Output

Example baseline discovery item:

{
  "siteKey": "example.com",
  "signalType": "pricing_update",
  "severity": "medium",
  "status": "baseline",
  "summary": "example.com baseline pricing structure captured across 1 pricing page.",
  "whyItMatters": "Establishes the current pricing structure for future monitoring.",
  "evidence": [
    "Starter: $29 / month",
    "Business: $199 / month",
    "Contact sales for enterprise"
  ],
  "evidenceUrls": [
    "https://example.com/pricing"
  ],
  "relatedPagesCount": 1,
  "confidence": 0.74
}

Example true monitoring update:

{
  "siteKey": "example.com",
  "signalType": "homepage_repositioning",
  "severity": "medium",
  "status": "updated",
  "summary": "example.com repositioned homepage messaging toward AI agents and enterprise use cases.",
  "whyItMatters": "Suggests a change in market messaging or strategic positioning.",
  "evidence": [
    "The data platform for AI agents",
    "Trusted by enterprise data teams",
    "Connect workflows with real-time web data"
  ],
  "evidenceUrls": [
    "https://example.com/"
  ],
  "relatedPagesCount": 1,
  "confidence": 0.83
}

How It Works

Each run:

1. Crawls seeded sites with a focused or sitewide strategy
2. Extracts normalized text, headings, sections, nav labels, and structured clues
3. Loads prior snapshots from persistent state
4. Detects meaningful changes between runs
5. Aggregates related page findings into grouped business signals
6. Writes dataset items plus briefing artifacts

Noise reduction includes:

• filtering weak first-run claims into baseline wording
• suppressing weak or low-proof public signals
• deduplicating repetitive snippets
• capping partner and similar page families in focused mode

Scheduling Tips

Recommended schedule:

• run daily for fast-moving competitors
• run weekly for broader market monitoring

Recommended setup:

• create one saved task per monitoring group
• set a stable monitorId
• review SUMMARY for triage
• share BRIEFING_MD or DASHBOARD with stakeholders
• use BRIEFING_JSON or dataset output for internal workflows

Good Monitoring Practices

• seed both homepage and pricing pages when possible
• keep allowedDomains narrow
• use focused mode unless you truly need wider discovery
• keep watchKeywords short and decision-oriented
• schedule recurring runs instead of treating the Actor as a one-off crawl

Limitations

• This Actor monitors public websites only
• It does not monitor social channels, ads, email, or app-store changes
• First-run output is baseline discovery, not proof of historical change
• Very aggressive page caps can suppress edge-case additions or removals until they recur across runs

Stored Artifacts

Key-Value Store records include:

• SUMMARY
• BRIEFING_MD
• BRIEFING_JSON
• DASHBOARD
• persistent monitor state and snapshot records used for recurring monitoring

Compliance

Use responsibly and in line with target-site terms, privacy law, and internal monitoring policy.

Support

If you want to monitor a specific competitor set or tune the Actor for a particular workflow, adapt the task input with your own monitorId, domains, page caps, and watch keywords.