Competitor Content Refresh Tracker avatar

Competitor Content Refresh Tracker

Pricing

from $11.50 / 1,000 content target checkeds

Go to Apify Store
Competitor Content Refresh Tracker

Competitor Content Refresh Tracker

Track competitor content pages for title, heading, date, section, FAQ, media, and CTA changes between snapshots.

Pricing

from $11.50 / 1,000 content target checkeds

Rating

0.0

(0)

Developer

junipr

junipr

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

5 days ago

Last modified

Share

Compare two captured versions of a competitor content page and receive source-linked change records. The Actor checks titles, meta descriptions, structured or visible dates, headings, FAQ questions, calls to action, embedded media counts, and visible text size. Each dataset row identifies the exact observed field, old value, new value, change direction, and evidence excerpt.

Use it for recurring editorial monitoring, competitor research, content refresh digests, and change alerts. The Actor describes observable differences between supplied snapshots. It does not infer why a publisher made a change or assign business impact without source evidence.

How comparison works

Provide matching sourceUrl values in baselineSnapshots and currentSnapshots. The Actor pairs those records, extracts the supported signals from each HTML document, and emits added, removed, updated, or unchanged rows. A captured HTML record may instead include previousHtml and currentHtml in htmlInputs.

changeSensitivity controls which observable differences are returned:

  • low keeps every supported field difference;
  • medium removes small text-length movement while retaining structural changes;
  • high focuses on title, date, heading, and FAQ-question differences.

Missing pairs, access-denied responses, and absent snapshots return diagnostic rows. They never become fabricated change records.

Input

FieldPurposeDefault / cap
competitorUrlsCompetitor pages eligible for explicit current-page retrievalempty
baselineSnapshotsEarlier HTML snapshots keyed by sourceUrlempty
currentSnapshotsLater HTML snapshots keyed by sourceUrlempty
fetchCurrentFetch competitorUrls as current snapshotsfalse
changeSensitivitylow, medium, or high filteringmedium
includeDiffSnippetsInclude old-to-new evidence texttrue
maxTargetsMaximum paired competitor targets25 maximum
maxComparisonsMaximum change rows per pair50 default, 250 maximum
htmlInputsCaptured records with HTML or previous/current HTMLempty
allowedDomainsOptional hostname allowlist for retrievalempty
maxPagesMaximum pages retrieved1 default, 25 maximum
includeEvidencePreserve evidence excerpts in dataset rowstrue
includeRawSnapshotsStore accepted raw snapshots in key-value storagefalse
maxChargeUsdStop before the next event exceeds this amount35 USD maximum

Example:

{
"baselineSnapshots": [
{
"sourceUrl": "https://publisher.example/guide",
"html": "<html><title>2025 Guide</title><h1>Annual planning</h1></html>"
}
],
"currentSnapshots": [
{
"sourceUrl": "https://publisher.example/guide",
"html": "<html><title>2026 Guide</title><h1>Quarterly planning</h1></html>"
}
],
"changeSensitivity": "medium",
"maxComparisons": 20,
"maxChargeUsd": 5
}

The Store default performs no network request and returns a nonempty snapshots_required diagnostic. Enable fetchCurrent only when the supplied competitor URLs should be retrieved during the run.

Dataset output

Every row includes provenance fields such as sourceUrl, canonicalUrl, httpStatus, and scannedAt. Comparison fields include:

  • competitorUrl for the paired target;
  • changeType as added, removed, updated, or unchanged;
  • fieldName for the observed signal;
  • oldValue and newValue for the source-backed values;
  • changeMagnitude for a bounded structural or size indicator;
  • dateChangedSignal, sectionAdded, and sectionRemoved flags;
  • diffSnippet when evidence snippets are enabled;
  • issueCode, severity, evidenceSnippet, and recommendation for audit use.

An unchanged row means that no difference crossed the chosen sensitivity. It is not a claim that the entire page is identical outside the supported extraction fields.

Reports

When includeReport is enabled, key-value storage receives a Markdown digest, full CSV records, issue rows in JSON, bounded evidence excerpts, and run metadata. Raw HTML is stored only when includeRawSnapshots is explicitly enabled.

Pay-per-event pricing

EventPrice (USD)When charged
actor-start0.0350after successful startup
content-target-checked0.0115once for each accepted competitor target
content-snapshot-compared0.0115before a supported snapshot comparison is emitted
content-change-detected0.0225before each paid observed-change row
digest-generated0.0900before the change digest is stored
executive-report-generated0.1800before the executive report artifacts are stored

Apify platform usage pass-through is off. Higher-tier Store discounts are reserved in the pricing policy. maxChargeUsd is checked before every event; rejected, partial, or over-budget charges stop the related output write.

Safety and interpretation

Only HTTP and HTTPS URLs are accepted for optional retrieval. Loopback and private IPv4 targets are rejected, domain allowlists can narrow accepted hosts, and page counts, timeouts, and comparison counts stay bounded. Discovered links are not crawled. Authentication walls and human-verification responses are recorded as diagnostics.

HTML comparison cannot observe browser state, content omitted from the response, or business intent. Retain dated snapshots, review the evidence excerpt, and validate material editorial decisions against the source page.