Wachete Alerts Triggered by Ads or Timestamps: How to Reduce False Positives

If ads, timestamps, counters, or other changing page regions keep triggering Wachete alerts, narrow the monitored area or exclude the volatile content. In the monitor preview, select the page section you care about, or use exclude mode to mark content to ignore. You can also edit the monitor’s advanced settings and enter an Exclude XPath. If the content you want to monitor is rendered by JavaScript, check it in Dynamic preview and use Dynamic mode when needed.

These controls help reduce irrelevant change notifications; Wachete does not publish a measured false-positive reduction rate. The right setup depends on the page’s markup and how its content loads.

1. First check what Wachete is monitoring

A monitor can watch a whole page or a selected part. If the alert is caused by content outside the section you care about, start by narrowing the monitor to the relevant text, number, or page area. This reduces the amount of unrelated page content that can trigger a change alert.

1. Open the monitor’s preview.
2. Check whether the preview shows the part of the page you intend to track.
3. Select that specific section if the whole page is currently monitored and you do not need whole-page coverage.
4. Save the monitor and review a future notification to confirm it refers to the chosen content.

For example, if you care about a product’s listed price, monitor the price area rather than the entire page, which may also include rotating promotions, ad placements, and dates.

2. Exclude ads, dates, counters, and other changing regions

Wachete documents two ways to exclude irrelevant page sections: mark them in preview using exclude mode, or enter an Exclude XPath in the monitor’s advanced settings.

Use preview exclude mode

1. Open the monitor preview.
2. Switch to exclude mode.
3. Mark the changing region, such as an ad block or date, that should not trigger content-change alerts.
4. Save the monitor.

This is a practical starting point when the preview lets you identify the changing area directly. Revisit the selection if the page redesigns or moves the content.

Use an Exclude XPath

For a page element with a class containing date, Wachete’s FAQ gives this example:

//div[contains(@class, 'date')]

This XPath selects div elements whose class attribute contains date. It is only an example: inspect the target page’s markup and adapt the element name and class to the actual changing region. A selector that matches nothing will not exclude the content; one that matches too broadly could hide content you meant to watch.

1. Edit the monitor and open its advanced settings.
2. Enter an XPath that matches the volatile element you want ignored.
3. Check the preview to make sure the intended content remains visible and the changing region is excluded.
4. Save the configuration and observe subsequent alerts.

3. Check whether the page needs Dynamic mode

Some pages add the content you need only after JavaScript runs. Wachete says most pages can be monitored as static, but JavaScript-generated content may require Dynamic mode.

1. Open the preview using its default options and locate the content you want to monitor.
2. If it is missing, switch the preview to Dynamic.
3. Confirm that the needed content appears in the Dynamic preview.
4. If it does, configure the monitor for Dynamic mode and confirm the monitor is still focused on the right page section.

Do not switch modes just because a page has ads or timestamps. The useful check is whether the content you intend to watch appears in the preview. If the preview does not load it correctly, Wachete suggests trying Dynamic mode, changing the monitoring location, or both.

4. Distinguish change alerts from check times and error notices

A displayed timestamp can be confusing: the monitor list may show when something last changed rather than when it was last checked. Open the monitor details to inspect the last check and last change separately before diagnosing delayed checks or duplicate alerts.

Also separate content-change notifications from error notices. Excluding an ad or timestamp addresses irrelevant page changes. Wachete’s error-notification controls address errors: its FAQ describes disabling all error notifications for a monitor or ignoring a particular error from its notification details. Changing those controls will not exclude volatile page content.

5. Troubleshooting

Symptom	Likely cause	What to check
Alerts continue after excluding an ad or date	The exclusion may not match the changing element, or another page region may be changing.	Inspect the preview and the page markup. Adjust the selected region or XPath to match the actual volatile element.
The content you care about is missing in preview	The page may add it with JavaScript.	Switch preview to Dynamic and confirm the content appears before choosing Dynamic monitoring.
The preview still does not load the page correctly	The rendering mode or monitoring location may affect what Wachete can see.	Try Dynamic mode, change the monitoring location, or test both adjustments.
The monitor shows Forbidden	The site may block automated bots; this is an access issue.	Treat it separately from a selector problem. A Forbidden response does not show that the XPath is wrong.
The listed time does not match when you think the page was checked	The list may show the last change time.	Open monitor details and compare the last check with the last change.
You still receive error notifications after excluding content	Error notices and content-change alerts use different controls.	Use the monitor’s error-notification options for errors; use preview exclusions or XPath for irrelevant content changes.
An XPath exclusion hides too much or nothing	The XPath may be too broad or may not match the page’s actual markup.	Inspect the target element and refine the XPath. Verify the resulting preview before relying on it.

6. Keep the monitor useful over time

• Watch the smallest useful region. Whole-page monitoring can include many changing areas unrelated to the information you need.
• Recheck exclusions after page changes. A site redesign can change element names, classes, or layout, so an old selection or XPath may stop matching.
• Validate the preview after each configuration change. Make sure the important content is still included and the noisy region is not.
• Use Dynamic mode based on evidence. Choose it when the needed content is absent in the default preview but present in Dynamic preview.
• Read monitor details before drawing conclusions from timestamps. Last check and last change answer different questions.

Or skip the browser setup

If your workflow needs a clean visual record of a page while you investigate changes, ScreenshotNeo is a website screenshot API and MCP server. It can capture a page as PNG, JPEG, WebP, or PDF, with options such as full-page capture, CSS selectors, custom waits, and custom headers. A screenshot is a visual snapshot; it does not replace Wachete’s change monitoring or its alert configuration.

One GET request captures a page. See the ScreenshotNeo API documentation for the parameters and response behavior:

curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webp

Python:

import requests

r = requests.get(
    "https://api.screenshotneo.com/v1/shot",
    params={"access_key": "YOUR_API_KEY", "url": "https://stripe.com"},
    timeout=90,
)
open("shot.webp", "wb").write(r.content)

Node.js:

const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);
if (!res.ok) throw new Error(`Screenshot request failed: ${res.status}`);
const image = Buffer.from(await res.arrayBuffer());
await import('node:fs/promises').then(fs => fs.writeFile('shot.webp', image));

ScreenshotNeo accepts cookie or consent banners like a visitor and removes more than 60 known consent platforms, newsletter popups, and chat widgets before the shot; each step can be turned off. Bot checks, blank pages, timeouts, failed loads, and cache hits cost nothing, and response headers report the page verdict and billing status. Its MCP server gives AI agents tools to take screenshots, get page information, and capture PDFs. The free plan includes 1,000 screenshots a month with no card; paid plans start at $5 for 3,000 screenshots.

Sign up for ScreenshotNeo’s free plan to get 1,000 screenshots a month with no card.

FAQ

Does excluding a timestamp stop Wachete from checking the page?

No. An exclusion tells the monitor to ignore matched content for change detection; it does not mean the page is no longer monitored.

Should I use preview exclusion or XPath?

Use preview exclude mode when it clearly identifies the unwanted section. Use an Exclude XPath when you need to specify the target element directly and can verify the page’s markup and preview.

Can I know how much false positives will decrease?

Wachete’s official materials do not provide a measured reduction rate. Check the preview and review later notifications to see whether the configuration addresses the specific noise on your page.

Does a screenshot service configure Wachete alerts?

No. ScreenshotNeo captures page images or PDFs; Wachete’s monitor settings control what changes trigger Wachete notifications.