How to Use Distill.io to Monitor Only One Part of a Webpage

To monitor one section of a webpage with Distill.io, add a web page monitor, choose Monitor Parts of Page, select the content in the visual selector, review the preview, and save. Then choose where checks run, set the schedule, and add alert actions. Distill saves a selector for the chosen content, so unrelated page changes are less likely to trigger the monitor.

You can do this in the Distill web app or with the browser extension. The web app defaults monitors to cloud checks; monitors added from the extension or desktop app default to local checks. The steps below use the web app first.

Set up a partial-page monitor in the web app

Open the Distill web app and choose Add monitor, then select Web Page.
Enter the page URL and load it. Choose Monitor Parts of Page. The separate Full Page option monitors the entire page.
Make sure selection mode is on. Hover over the target content and click it. In this mode, clicks select page elements rather than interacting with the page normally.
Check the selection preview to confirm it contains the content you care about and not surrounding sections.
Save the selection. On the options page, configure the device, schedule, monitor name, and notification actions, then save the monitor.

To inspect later changes, open the monitor preview in the Watchlist to view its change history. See Distill’s web app setup guide for the current interface flow.

Use the browser extension

Open the target webpage and click the Distill extension icon.
Choose Monitor parts of page.
Select the desired element, inspect the preview, and choose Save Selection.
On the options page, choose the device, check frequency, and notification actions. Save the monitor.

Distill’s extension guide uses a similar flow, though labels and controls can vary slightly by browser client. Subscription plan affects which notification actions are available. See the official Chrome extension guide.

Make the selection precise

A selection that is too broad can react to unrelated changes; a selection that is too narrow can miss meaningful updates. Preview the captured text before saving, then adjust the selection until it corresponds to the change you want to know about.

Start small: select the specific price, status, title, or announcement. Use Expand if you need to include a nearby label or context.
Narrow a broad selection: use Contract to shrink the selected region. Delete a selection and start again if it is easier.
Watch separate regions: make multiple selections when the relevant information is in distinct parts of the page.
Exclude nested content: select content within an already selected region to exclude it, such as a changing timestamp that should not trigger an alert.
Reopen an existing monitor: open its options, choose the webpage selector, load the page, and adjust the existing selection. The selector panel also exposes the saved selector configuration.

Distill’s Visual Selector documentation describes visual selections, exclusions, filters, and selector editing.

Use a text filter for noisy values

The visual selector supports a regular-expression text filter. For example, if the selected text includes labels and numbers but you only want numeric text, the JavaScript regular expression \d+ can extract number sequences. The selector’s default flags are global, case-insensitive, and multiline; you can change them to match the text you intend to capture. Test the preview after applying a filter, since a pattern that matches too much or too little can hide useful changes.

Monitor an attribute or property instead of visible text

Text is the default, but some changes are represented in an element’s attributes or properties. For example, select an image and monitor its src attribute to detect a changed image URL, or a link’s href to detect a destination change. A button’s class can matter when its state changes through a class name. Enable the relevant field in the selector configuration and verify that the preview shows the value you expect.

What selector does Distill save?

Distill supports CSS, XPath, and manually configured JavaScript selectors. Visual selection generates a CSS selector in the web app and XPath in browser extensions by default. You do not need to write a selector for the normal visual workflow, but you can edit selectors manually when the visual selection is ambiguous or needs refinement.

Choose local or cloud checks

The device setting determines where Distill checks the page. Choose based on whether the monitor must run while your computer is unavailable and whether the page needs a local browser environment.

Mode	Where it runs	Practical consideration
Cloud	Distill’s servers	Can continue while your computer is off or the browser is closed. Cloud checks count against plan limits; page access, proxies, and minimum intervals depend on plan and configuration.
Local	Your browser or computer	The device and browser or desktop app must be running for checks. Local monitoring is useful when the page works in your own browsing environment; local checks are not counted like cloud checks.

Monitors added from the web app default to cloud; those added from the extension or desktop app default to local. You can change the device from the monitor’s device control. Exact intervals and plan limits vary, so consult Distill’s current plan and device settings before relying on a particular schedule. Its local versus cloud guide explains the differences.

Set the schedule and notifications

On the monitor options page, set the check frequency that fits the importance of the change. A very frequent schedule can use more resources or cloud check allowance; a slow schedule can delay discovery. Local checks also depend on the browser or computer being available. Add one or more alert actions if you need to hear about changes, and confirm the desired action is available on your plan.

For local extension monitors, Distill’s advanced settings include choices for how checks open pages, such as a tab, window, background, or sticky window. Background checking is intended for static pages and may not work for dynamic content. The extension guide also documents concurrent workers; more workers can increase simultaneous checks while using more system resources.

Troubleshooting

Symptom	Likely cause	What to try
Unrelated page changes trigger alerts	The selected region contains extra content, or a changing nested item is included.	Reopen the selector, Contract the selection, or exclude the noisy nested element. Check the preview before saving.
A relevant change is missed	The selection is too narrow, the content is rendered later, or the page expresses the change in an attribute rather than text.	Expand the region, inspect the preview after loading, increase the configured wait duration if needed, or enable the relevant attribute/property.
The preview is empty	The page may not have loaded the target content yet, or the selected element may not contain text.	Confirm the content appears in the page, adjust the wait duration in the source configuration, and select the correct element or attribute.
Local monitor stops checking	The browser or computer is closed, offline, or local monitoring is turned off.	Keep the local device available and monitoring enabled, or switch the monitor to cloud if it should continue while the computer is off.
Local works but cloud does not	The site may restrict requests from cloud infrastructure or require a regional proxy.	Review Distill’s cloud monitor and proxy options for your plan, or use a local monitor if the page is accessible there.
Dynamic page content is missing in background checks	Background mode may not support the page’s dynamic rendering.	Use the default tab/window mode or the desktop app workflow, then confirm the captured preview contains the target content.
Alerts are unavailable	The action may require sign-in, account details, or a subscription tier that includes it.	Sign in, configure the required details, and check action availability for your current plan.
Selection is difficult to target	The desired content is nested in a larger element or visually crowded with neighboring content.	Start with a smaller selection and use Expand or Contract incrementally. Remove selections that do not belong.

Performance, reliability, and cost considerations

Reduce false alerts: select the smallest meaningful region and exclude volatile content such as timers or view counters when they are irrelevant.
Allow for rendering: pages that populate content after initial load may need a longer wait. Distill’s selector documentation describes a configurable wait duration, with a maximum of 30 seconds.
Pick an execution location deliberately: cloud checks run independently of your device but are subject to plan accounting and possible site restrictions. Local checks need the device running and available.
Balance frequency against resources: short intervals may use more cloud allowance or local system capacity. For local extension checks, concurrent worker settings affect parallelism and resource use.
Validate the captured result: the preview and change history help distinguish a true page change from a selector that has drifted after a site redesign.

These monitors detect changes in selected page content. They do not guarantee that a website exposes every update consistently: client-side rendering, login state, geography, anti-bot restrictions, and markup changes can affect what a check sees. Revisit the selection after the site changes its layout.

Or skip the browser setup

If your goal is to capture a clean screenshot of a webpage or a selected element for a script, report, or AI workflow, ScreenshotNeo is a website screenshot API and MCP server. It captures an image or PDF from one GET request. It is a screenshot tool rather than a scheduled change-monitoring service, so use Distill for ongoing alerts and ScreenshotNeo when you need a capture.

For API options and parameters, see the ScreenshotNeo documentation.

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

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. The free plan includes 1,000 screenshots a month with no card; paid plans start at $5 for 3,000.

FAQ

Can I monitor more than one part of a page?

Yes. Make multiple selections and review their combined preview before saving.

Can I monitor a price without tracking the product description?

Yes. Select the price element itself, then confirm the preview contains only the value and any useful context.

Will a local monitor run when my computer is off?

No. Local checks require the browser or computer to be available. Choose a cloud device if the monitor needs to keep checking while your computer is off.

Do I need to write CSS or XPath?

No. The visual selector creates a selector for you. Manual selector editing is optional.