Wachete Not Detecting Website Changes: Troubleshooting Steps

If Wachete is not detecting a website change, first open the monitor preview and confirm the content you expect to change is visible there. If it is missing, try Dynamic preview and another monitoring location. If it is visible, check that the monitor covers the right region, review its check and change history, and then inspect its alert settings.

Wachete checks pages on its servers, so your computer or phone does not need to stay online. A missing alert can therefore have several causes: the monitor has not checked yet, the server sees different page content, the changed content is outside the selected region, or a change was recorded but the notification did not arrive. Wachete documents these preview, selection, history, and alert controls in its FAQ and features overview.

1. Check what Wachete sees in the preview

Open the monitor and inspect its preview. Find the exact text, price, status, or other content you expect Wachete to track. If that content does not appear in the ordinary preview, the monitor cannot reliably compare it there.

Open the monitor’s preview.
Locate the content that should change.
If it is absent, switch to Dynamic preview and check again.
If it appears only in Dynamic preview, use Dynamic mode for that monitor.

Wachete says static monitoring can work for many pages, while JavaScript-generated content may need Dynamic mode. Treat the preview as the practical test: the page’s appearance in your own browser does not prove that the monitor sees the same content.

2. Troubleshoot missing content and Forbidden responses

If the preview shows a Forbidden response or the page loads incorrectly, try Dynamic preview, change the monitoring location, or test both changes together. Wachete identifies automated bot protection as a common cause of Forbidden responses. A site may serve different content or deny access to an automated request even though it works in your browser.

Switch between ordinary and Dynamic preview and see whether the target content appears.
Try another monitoring location offered by Wachete.
If needed, combine Dynamic preview with a different location.
Recheck the preview before changing the monitored region or alert settings.

Wachete’s FAQ mentions a rotating residential proxy as a possible option in some cases. That is not a guaranteed workaround, and the reviewed documentation does not establish that it will solve a particular site’s blocking. Follow the site’s access rules and use Wachete’s documented options first.

3. Verify the monitored region

Wachete can monitor a whole page or a selected portion. If the changed text or value falls outside the selected region, changes elsewhere on the page will not count for that monitor.

Review the selection in the preview.
Confirm it includes the changing text, number, or element.
If the target moved after a site redesign, update the selection and save the monitor.
Use whole-page monitoring when changes can occur in multiple areas and you need to track them all.

A selected region can reduce irrelevant changes, but it also narrows what the monitor can detect. Wachete describes monitoring the whole page and selected portions in its features overview.

4. Distinguish the last check from the last change

The time shown in “My Monitors” can be the time a change occurred, not the time of the most recent check. Open the monitor detail or history to find the last check time and last change time separately.

No recent check: The page may not have been checked since the expected update.
Recent check, no change recorded: Revisit the preview and selection to confirm the monitor can see the changing content.
Change recorded: Detection worked; investigate notification settings next.

Do not infer a check interval or alert delay from the change timestamp alone. Check the monitor’s details and recurrence configuration. Wachete’s API documentation also describes recurrence and alert configuration.

5. Reduce noisy changes carefully

Dates, counters, rotating banners, or other frequently changing areas can create noise that makes useful changes harder to spot. Wachete lets you mark regions to exclude in the preview or provide an Exclude XPath in advanced options.

Examples documented by Wachete include:

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

This XPath selects div elements whose class contains date.

//a

This XPath selects all links. Use it only if link changes are irrelevant to your monitoring goal. Before saving any exclusion, verify that it does not also hide the content you need to track. XPath matches can cover more of a page than intended.

6. Check alerts after confirming a change

A detected change and a delivered notification are separate things to diagnose. If monitor history records the change, review the monitor’s alert type and notification settings, including the configured endpoint or destination. Wachete supports configurable alerts and notification endpoints, but the public documentation cannot confirm whether a particular email, phone, or other destination received a specific message.

Confirm the change appears in monitor history.
Open the monitor’s alert and notification settings.
Check that the intended alert type and destination are configured.
Review the destination’s own filters or delivery logs if available.

Quick diagnostic checklist

The expected content is visible in the monitor preview.
Dynamic preview has been tried for JavaScript-generated content.
A different monitoring location has been tried if the page is blocked or incomplete.
The selection includes the content that is changing.
Monitor details show the last check separately from the last change.
Exclusions remove only irrelevant, noisy content.
Alert settings are checked only after history confirms a change.

Or skip the browser setup

For a one-off visual check of a page, ScreenshotNeo takes a screenshot with one API request. See the ScreenshotNeo API documentation for options and setup.

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

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)

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 fs = await import('node:fs/promises');
await fs.writeFile('shot.webp', Buffer.from(await res.arrayBuffer()));

ScreenshotNeo removes cookie banners, popups, and chat widgets before the shot. Bot checks, blank pages, and failed loads are never billed. Its MCP server lets AI agents take screenshots, and the free plan includes 1,000 screenshots a month with no card; paid plans start at $5 for 3,000. A screenshot is useful for inspecting a page, while ongoing change alerts still depend on a monitoring service.

Frequently asked questions

Does my computer need to stay on for Wachete to monitor a page?

No. Wachete says monitoring runs on its servers, so your computer or phone does not need to remain online. See the Wachete service overview.

Why does the monitor list show an old time when the page was checked recently?

The list time can represent when a change happened. Open the monitor detail or history to see the last check and last change independently.

Will Dynamic preview fix every page that Wachete cannot read?

No. It can help when content is generated with JavaScript, but access restrictions or other loading problems may remain. Test a different monitoring location as well and use the preview to verify the result.

Should I exclude all links to stop noisy alerts?

Only if link changes are outside what you need to monitor. The XPath //a excludes all links and can hide meaningful changes.