A Distill.io alternative when you hate babysitting CSS selectors
I used Distill for years. It worked. Until it didn’t.
Distill is great if you want pixel-level control. You pick a CSS selector, Distill watches that node, and you get a ping when the DOM changes. That is the whole pitch. For a price table in a fixed layout, it is hard to beat.
Then the site redesigns. Or the marketing team wraps the price in a new div. Or the careers page starts loading jobs through a script. Your selector goes quiet. You only find out after you notice the job yourself.
That is the tax of selector-based watching. You are not watching “the pricing page.” You are watching one brittle address inside it.
What Distill still does better
I am not going to pretend Distill is useless. It is not.
If you need to watch one exact span and ignore everything else on the page, Distill is built for that. Visual change tools and keyword alerts are noisier for that job. Distill also has a browser extension and a desktop app people already know. If your workflow is “this one DOM node, forever,” stay on Distill.
The problem shows up when the page is the unit you care about, not the selector.
Page meaning vs page markup
Most of the watches I actually want are messy:
- Did this SaaS change Pro pricing?
- Did a new role land on the careers page?
- Did the privacy policy grow a new clause?
- Did a competitor ship a feature page?
None of those questions are “did #price-pro > span.amount change.” They are “did the meaning of this page move.”
Get Evangelist Naval’s stories in your inbox
Join Medium for free to get updates from this writer.
Selector tools answer the first. Summary-style watchers answer the second.
A summary watch reads the page, keeps a short memory of what mattered last time, and alerts when that meaning shifts. You do not have to rebuild a selector after every redesign. You also do not get a ping every time an A/B test swaps a button color.
That tradeoff has a cost. You give up surgical DOM precision. You gain something closer to how a person would describe the change.
Where AyeWatch fits
I moved a few of those messier watches to AyeWatch. You describe the topic or paste a URL. It watches and alerts when something real changed. Free Preview is $0 with 3 topics and 6 lifetime runs. Pro is $9/mo.
I still keep Distill for the one pricing span that never moves. Everything else (careers pages, ToS dumps, competitor feature pages) sits on the summary side now.
Distill vs a summary watcher, bluntly
- Distill: pick a selector, get notified when that node changes. Best when the layout is stable.
- Summary watcher: watch the page or topic for meaningful change. Best when the layout is not your job.
If your selectors keep dying after redesigns, you do not need a better selector. You need a different kind of watch.
Distill is still the right tool for exact DOM nodes. For “tell me when this page actually changed,” a Distill.io alternative that watches meaning instead of markup is usually less work.
