Monitoring Module
Pin the pages that matter. See the moment they change.
Policy pages are high-signal. A silent Terms & Conditions rewrite often precedes a category pivot or a laundering front. Pinned-page drift monitoring locks each page to its current state and raises an alert the second the content moves.
How it works
Pin the page
Add a URL with a human label (e.g. Terms & Conditions). The platform captures and normalizes the current content and records a baseline.
Watch on every scan
On every scheduled merchant scan, pinned pages are fetched and compared against the recorded baseline. No page is ever silently dropped from monitoring.
Alert on change
When content diverges from the baseline, the pinned page is flagged in the merchant profile with a Last Changed timestamp and routed into the analyst queue for review.
Pinned Pages
Policy pages monitored for content changes across scans.
| Label | URL | Last Scanned | Last Changed | Status |
|---|---|---|---|---|
| Terms & Conditions | https://warungseribu.my/terms-and-conditions | 2h ago | 11d ago | Active |
| Refund Policy | https://warungseribu.my/refund-policy | 2h ago | No changes | Active |
| Shipping & Delivery | https://warungseribu.my/shipping-delivery | 2h ago | 3d ago | Active |
| Privacy Notice | https://warungseribu.my/privacy | 2h ago | No changes | Active |
| Product FAQ | https://warungseribu.my/faq | 2h ago | No changes | Inactive |
Policy pages are leading indicators
Merchants rarely announce a pivot. They rewrite the refund policy on a Sunday night, change the product catalog a week later, and start routing traffic to a new category. A pinned Terms & Conditions page catches the first move, days or weeks before the catalog change shows up in a full scan.
Fully configurable per merchant
Every merchant can have its own set of pinned URLs with human-readable labels. High-risk merchants can pin five or six policy and landing pages; standard retail merchants can pin just the refund page. Pins can be activated or deactivated per page without losing the change history.
Last scanned and last changed timelines
Every pinned page shows two timestamps: when it was last fetched and when it last changed. Analysts can tell at a glance whether a page is being watched on cadence and whether it has been stable or moving. Missed scan coverage is visible, not silently skipped.
Change logs become evidence
Every change is recorded with the scan that detected it and the content snapshot that backs it up. When a case is opened, the pinned-page history is already in the evidence bundle. No reconstruction needed, no chain-of-custody gaps.
Frequently asked questions
- How is this different from general web change detection?
- Web change detection scans whole websites broadly. Pinned-page drift zeroes in on a small number of pages you have explicitly said matter. These are the pages where a single-character change is worth waking an analyst up: the refund policy, the T&Cs, the privacy notice. Pinning raises the signal-to-noise ratio on the pages that predict bad outcomes.
- What happens when a pinned page disappears or returns a 404?
- A missing or 404 pinned page is itself a signal. The pinned page is marked as a scan failure in the merchant profile and routed into the analyst queue as a review item. Merchants removing their refund policy page entirely is often as meaningful as rewriting it.
- Can pinned pages be deactivated without losing their history?
- Yes. Pins have an active/inactive toggle. Deactivating a pin stops new scans from checking the page but preserves the existing history and last-scanned state. You can reactivate at any time.
- How quickly does the platform see a change?
- Pinned pages ride the merchant's configured scan cadence. High-risk merchants can be scanned daily, standard merchants weekly or monthly. Changes are detected on the next scan after they occur.