Find the right pages.
Catch the next update.
Use a feed or sitemap to discover pages worth monitoring, or watch the source itself for new entries. Choose the workflow that matches the update you want.
Start with the update you want
| Workflow | Use it when you want to… | Available on |
|---|---|---|
| Monitor a page | Track changes to a price, stock label, text, or list on an existing webpage. | All plans |
| Discover pages | Browse a feed or sitemap and import several existing pages for individual monitoring. | All plans |
| Watch for new entries | Get an alert when a feed or sitemap adds a new entry, optionally matching a phrase. | Pro |
RSS and Atom are feed formats. XML sitemaps are lists of URLs. All three work with both Discover pages and Watch for new entries; they are not separately priced features.
Find a feed or sitemap URL
Look for an RSS or Subscribe link on the site. A sitemap may be linked from its /robots.txt file. Common paths include /feed.xml, /atom.xml, and /sitemap.xml, but each site chooses its own location.
Discovery reads the RSS, Atom, or XML sitemap URL you supply. It does not crawl a homepage to find feeds or follow every linked webpage.
Sources must be public. PageFluxer checks them in the cloud and does not inherit your browser login or cookies. Feeds often contain only recent entries; sitemaps may omit some pages.
Discover and import existing pages
- Choose Discover pages, paste a source URL, and preview it.
- Filter by title or URL. Select the pages you want; URLs already monitored are marked so you can skip them.
- Review the selection and optional labels, then import. You can import up to 50 pages at a time, within your remaining monitor slots.
- Choose Finish setup for each imported page. Select its goal, confirm the cloud-captured content, choose its rules and schedule, and start monitoring.
Each imported page uses one monitor slot. No scheduled checks run until you finish that page’s setup. Pausing a monitor keeps its slot; deleting it frees the slot.
For example, filter a sitemap by /legal/, import its Terms and Privacy pages, then monitor their text for changes.
Watch a source for new entries
- Choose Watch for new entries and preview a source. You can try the preview on any plan; saving a recurring watch requires Pro.
- Choose any new entry, or entries containing a phrase. For RSS and Atom, search the title, description, URL, or all three. Sitemaps support URL matching.
- Review the rule, name, and check frequency. Confirm the starting baseline and select Start watching.
A job feed could alert on new titles containing senior developer. A sitemap could alert on new URLs containing /release-notes/. Matching ignores case and uses a literal phrase, not a regular expression. It examines up to the first 200 title characters and 500 description characters supplied by the feed. Linked page bodies are not searched.
The confirmed preview establishes the baseline. Only entries first seen afterward can alert. Edits to known entries, sitemap modification dates, disappearing entries, and returning known entries do not trigger another alert. Newly seen does not necessarily mean newly published.
Matches appear in change history and use your existing email, digest, quiet-hours, and enabled webhook settings. Emails show a short list linking to the complete captured matches. To watch future changes inside an entry, create an individual page monitor from it.
Editing a watch establishes a fresh baseline and clears the seen-entry list while retaining alert history. An older entry absent from the new baseline may alert if it later returns. Pausing preserves the baseline; unseen entries present after resuming can alert.
Usage and source limits
Each watch uses one shared monitor slot and one HTML check per scheduled source scan, including failed attempts and bounded child sitemaps. Checks default to hourly and can run every 15 minutes or slower, subject to service capacity and account allowances. Source watches use no browser checks or AI credits.
| Allowance | Limit |
|---|---|
| Source preview requests | 20/hour and 100/day per account; separate from page previews and scheduled checks |
| Entries per scan | 1,000 distinct entries |
| Sitemap index | Up to 8 documents, with same-origin child sitemaps |
| Source downloads | 2 MiB per document; 8 MiB for the collection |
| Saved source data | 1 MiB of normalized entry data |
| Remembered identities | 20,000 stable entry IDs per watch; retained until deletion or baseline reset |
These are XML-source limits. Individual page monitors have separate HTML capture limits. Alert history follows your plan’s retention and shared storage allowance. How usage works →
When a source needs attention
The source is too large
Use a smaller feed or a child sitemap. Failed or partial scans do not advance the seen-entry baseline. No entries are silently truncated to fit a limit.
No entries match my phrase
You can still save a watch for future matches. Check the selected field and wording; a feed description may differ from the full article or job page.
An expected entry did not alert
It may already have been in the baseline, or appeared and disappeared between scans. A publisher changing an entry’s ID can also make an older item appear new. Review the source’s actual entries and your monitor’s check status.
The watch has reached its identity limit
PageFluxer keeps known IDs so returning entries do not alert again. At 20,000 identities, confirm a fresh baseline before scans can advance. The review screen explains the reset before saving.
My plan changed
Leaving Pro pauses source watches. Upgrade to resume them; page discovery and imports remain available on every plan.
This release supports UTF-8 RSS 2.0, Atom, and XML sitemaps. RSS 1.0/RDF, text sitemaps, feed pagination, browser-only sources, and signed-in feeds are not supported.