How to Set Up Wachete to Monitor a Specific Part of a Web Page

To monitor one section of a page with Wachete, create a monitor, choose Single page or part of it, password protected page or media file, enter the page URL, and select the desired region in the preview. Then choose how often Wachete checks it and what change should trigger a notification, and save the monitor. Wachete runs monitoring on its servers, so your computer does not need to stay on.

Set up a monitor for one page

1. In Wachete, choose Create new monitor.
2. Select Single page or part of it, password protected page or media file, then enter the page URL.
3. Wait for the preview and select the specific content you want to follow. Choose a meaningful region, such as a product price, a service status, or an announcement, rather than unrelated page furniture.
4. Choose a check frequency available for your account.
5. Choose a notification condition. Depending on what you need to know, this can be a general change, particular text appearing, or a numeric value crossing a threshold.
6. Save the monitor. Open its edit screen afterward to review or adjust the selected content and notification settings.

Wachete can monitor a whole page or a selected part. Selecting only the relevant region helps avoid alerts caused by unrelated changes elsewhere on the page. Wachete also describes an option to ignore parts that change often.

Choose the right section and alert

Make the selected area as specific as needed to capture the information you care about, but broad enough that the content still appears when the page layout changes. For example, if you care about a listed price, select the price or its nearby product detail rather than the entire page. If the alert should only happen under a condition, use a text or numeric rule where available instead of treating every change as equally important.

Goal	Selection and notification approach
Know whenever an announcement changes	Select the announcement region and notify on a change.
Know when a phrase appears	Select the relevant content and use a text condition for that phrase.
Know when a measurement crosses a limit	Select the numeric value and configure a threshold condition.
Avoid noisy updates from dynamic page areas	Refine the selected region and, where useful, ignore frequently changing parts.

Monitor the same section across linked pages

If you need the corresponding region on several linked pages, this is a crawling setup rather than a single-URL monitor. Wachete’s FAQ describes selecting crawling for the root page and sub-pages, then using Change selected content to select the region on the root page. The corresponding region should be in the same place on the sub-pages. Wachete says crawling can reach the third level and may discover many pages, so check the likely page count and whether your plan fits before enabling it.

Wachete’s FAQ instructs users to “Select the area on the root page which appears on same place also on sub-pages.” If the site uses different layouts across its pages, one root-page selection may not identify the intended content consistently; review the resulting coverage.

Verify and maintain the monitor

• Confirm the saved monitor points to the intended URL and selected region.
• Check that the notification condition matches the change you actually care about.
• If alerts are too frequent, narrow the selection, ignore areas that change often, or use a more specific text or numeric condition.
• If monitoring linked pages, review the discovered page count and verify that the selected region maps to the same content across them.
• Edit the monitor when the site redesigns its layout or the information you want to track changes.

Because Wachete performs monitoring on its servers, you can close your browser or turn off your device after setup.

Common problems and fixes

Problem	Likely cause	What to do
Alerts include changes you do not care about	The selected region is too broad, or the notification condition is too general.	Edit the monitor, select a narrower region, and use a specific text or numeric condition if appropriate.
Expected changes are missed	The selected region does not include the changing content, or the page structure changed.	Open the edit screen, review the preview selection, and select the current location of the content again.
Monitoring sub-pages gives inconsistent results	The selected region is not in the same place or structure on those pages.	Check representative sub-pages and confirm the root-page selection corresponds to the desired area. Consider whether crawling is suitable for those layouts.
Crawling covers more pages than expected	Linked pages can expand the crawl, which may reach the third level.	Review crawl settings and the expected page count before saving or keeping the configuration.
No alert arrives after a change	The change may not match the configured condition, or the selected area may not include it.	Review both selection and notification rule in the monitor’s edit screen; use a general change rule if every change should notify.

Performance, reliability, and cost considerations

Choose a check frequency that suits how quickly the information matters and that is available on your account. More frequent checks are useful only when a quicker alert changes what you can do. The research sources do not establish a universal check interval, delivery time, or plan price, so consult Wachete’s current account options and plan details for those specifics.

Server-side monitoring means your own device does not have to remain connected. For multiple pages, crawling increases coverage and may discover many URLs; account for that scope when reviewing plan suitability. A focused selection and a condition that matches your actual goal can also reduce irrelevant notifications.

Or skip the browser setup

If your goal is to capture a page as an image or PDF rather than receive change alerts, ScreenshotNeo is a website screenshot API and MCP server. One GET request returns a PNG, JPEG, WebP, or PDF. It captures a page; it does not replace Wachete’s ongoing monitoring and notifications.

For example, this cURL request saves a WebP screenshot:

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

See the ScreenshotNeo API documentation for request options. Equivalent runnable examples:

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}`);
await Bun.write('shot.webp', res);

ScreenshotNeo removes cookie banners, newsletter popups, and chat widgets before a capture. Bot checks, blank pages, and failed loads are never billed. Its MCP server lets AI agents take screenshots, and 1,000 screenshots a month are free with no card; paid plans start at $5 for 3,000. Sign up free for 1,000 screenshots a month.

FAQ

Does Wachete monitor the whole page if I select a section?

The setup described here selects a specific part of the page to monitor. Choose the whole-page option only when changes anywhere on the page matter.

Do I need to keep my browser open?

No. Wachete says monitoring runs on its servers after configuration.

Can one monitor follow a section on several pages?

Wachete describes crawling from a root page and selecting the corresponding region there. The content should appear in the same place on sub-pages, and you should review how many pages the crawl may include.

Can ScreenshotNeo notify me when a page changes?

No. ScreenshotNeo returns a screenshot or PDF for a request; Wachete is the service in this guide for monitoring changes and sending notifications.

Sources

• Wachete FAQ — monitor setup, selection, alerts, crawling, and server-side monitoring.
• Wachete Features — selected-area monitoring and ignoring frequently changing parts.
• Wachete homepage — service and plan context.