Competitor Content Refresh Tracker
Pricing
from $11.50 / 1,000 content target checkeds
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
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
5 days ago
Last modified
Categories
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:
lowkeeps every supported field difference;mediumremoves small text-length movement while retaining structural changes;highfocuses 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
| Field | Purpose | Default / cap |
|---|---|---|
competitorUrls | Competitor pages eligible for explicit current-page retrieval | empty |
baselineSnapshots | Earlier HTML snapshots keyed by sourceUrl | empty |
currentSnapshots | Later HTML snapshots keyed by sourceUrl | empty |
fetchCurrent | Fetch competitorUrls as current snapshots | false |
changeSensitivity | low, medium, or high filtering | medium |
includeDiffSnippets | Include old-to-new evidence text | true |
maxTargets | Maximum paired competitor targets | 25 maximum |
maxComparisons | Maximum change rows per pair | 50 default, 250 maximum |
htmlInputs | Captured records with HTML or previous/current HTML | empty |
allowedDomains | Optional hostname allowlist for retrieval | empty |
maxPages | Maximum pages retrieved | 1 default, 25 maximum |
includeEvidence | Preserve evidence excerpts in dataset rows | true |
includeRawSnapshots | Store accepted raw snapshots in key-value storage | false |
maxChargeUsd | Stop before the next event exceeds this amount | 35 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:
competitorUrlfor the paired target;changeTypeasadded,removed,updated, orunchanged;fieldNamefor the observed signal;oldValueandnewValuefor the source-backed values;changeMagnitudefor a bounded structural or size indicator;dateChangedSignal,sectionAdded, andsectionRemovedflags;diffSnippetwhen evidence snippets are enabled;issueCode,severity,evidenceSnippet, andrecommendationfor 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
| Event | Price (USD) | When charged |
|---|---|---|
actor-start | 0.0350 | after successful startup |
content-target-checked | 0.0115 | once for each accepted competitor target |
content-snapshot-compared | 0.0115 | before a supported snapshot comparison is emitted |
content-change-detected | 0.0225 | before each paid observed-change row |
digest-generated | 0.0900 | before the change digest is stored |
executive-report-generated | 0.1800 | before 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.