Versionista Not Detecting Changes on a Website: Troubleshooting
If Versionista missed an expected website change, check the monitored URL, filters, focus phrases, crawl history, and alert settings in that order.
If Versionista did not record an expected website change, first confirm that the exact URL is actively monitored. Then check filters and focus phrases, which can exclude changes from version recording. If the version exists but no email arrived, investigate notification settings separately: page-level instant alerts are off by default, and account summaries can be suppressed when no changes are detected.
These checks can narrow down the cause, but public Versionista guidance cannot diagnose a particular account or URL without its configuration and crawl history.
1. Confirm the exact URL is being monitored
- Open the page list in your Versionista account.
- Find the exact URL where the change occurred. Check the full path and relevant query parameters; a different URL may be a different monitored page.
- Confirm the URL is active for monitoring, rather than only listed as a newly discovered page or paused page.
- Review its crawl or version history and identify the latest completed scan. Compare that timestamp with when the website change became available.
Versionista can discover links from monitored pages, but discovery does not automatically mean the newly found URL is being monitored for changes. Its guidance says users choose whether to monitor or pause discovered URLs. It also documents discovery limits of up to 50 new URLs per scan and 150 per monitored site, and says newly found pages can be configured to pause automatically after three weeks. Versionista’s homepage and its new-page notification guidance describe the product’s account support and page discovery; check the current in-account settings for your specific page.
2. Check filters and focus phrases
Versionista says it monitors all changes by default, but site filters can exclude page regions. Inspect the configured filters for areas that contain the expected change, such as a page section that was excluded because it changes frequently.
Focus phrases can narrow detection further. When configured, Versionista records a new version only if one of the specified phrases is added or deleted; unrelated changes may therefore be ignored for version recording. Matching is case-insensitive. Filters are applied before focus-phrase matching. The feature applies to HTML and plain text, not images, PDFs, Word files, or other content types.
If you need broad coverage, consider whether focus phrases are necessary. Versionista’s tutorial suggests monitoring all changes and using filters to exclude irrelevant regions as a simpler alternative to maintaining a keyword list. Review the official instructions for monitoring specific word additions or deletions before changing a production monitor.
3. Establish whether detection or notification failed
A missing email does not prove that Versionista missed the change. Check whether a new version appears in the page’s history first. If it does, the change was recorded and the remaining issue is notification delivery or configuration.
| Notification path | Scope and default | Where to check |
|---|---|---|
| Summary email | Account-level report, daily by default. A report may be omitted when there were no detected changes unless the no-change option is enabled. | Account Settings: report frequency, content, and whether to send reports with no changes. |
| Instant alert | Page-specific alert; off by default and enabled separately for each page. | The page’s Crawl section: inspect its instant-alert switch and alert content settings. |
Versionista documents these as separate notification paths. Its email-alert tutorial explains the page-level switch and account-level summary settings. If the version is present but the expected email is absent, check both paths and your mail filtering before treating the event as a detection failure.
4. Check whether the changed page was newly discovered
If the content is on a URL recently linked from another monitored page, look in the new-pages list. A discovery notification means Versionista found a URL; it does not mean that URL is already monitored for its future changes. Activate the page for monitoring if you want its changes tracked. Also check whether the account is configured to pause newly found pages automatically after three weeks.
Versionista documents discovery of up to 50 new URLs per scan and 150 per monitored site. These are product limits, not a guarantee that every link on a site will be discovered. See its new-page notification guidance for configuration details.
5. Use a focused diagnostic checklist
- URL: Record the exact URL and confirm it is active, not merely discovered or paused.
- Timing: Note when the change went live and the latest crawl or version timestamp. A scan before publication cannot record a later change.
- Scope: Identify whether the expected change is text, HTML, an image, a PDF, or another content type. Focus phrases do not cover all content types.
- Filters: Check whether the changed region is excluded.
- Focus phrases: Check whether a phrase was configured and whether the change added or deleted it. Other edits may not produce a version under this setting.
- Version history: Determine whether a new version exists. This separates recording from email delivery.
- Alerts: Check the page’s instant-alert switch and the account’s summary schedule and no-change preference.
- Discovery: If the URL is new, activate it for monitoring and review any auto-pause setting.
If these checks do not explain the issue, collect the URL, relevant crawl and version timestamps, current filter and focus-phrase settings, and a concise description of the expected versus observed change. These are useful diagnostic details inferred from the documented settings, not an official statement of support requirements. Contact Versionista support with that evidence. Public guidance cannot establish whether a particular crawl succeeded, whether a target page was accessible, or what happened in a specific account.
6. Understand Versionista’s current account notice
Versionista’s homepage says existing customer accounts remain supported and directs prospective new accounts to Fluxguard. That notice does not diagnose an individual missed change or establish that a product-wide outage caused it. Existing users should troubleshoot their page and account settings first; prospective users can follow the homepage’s current direction when looking for a new monitoring account.
Or skip the browser setup
If your goal is to inspect what a page currently renders, ScreenshotNeo is a website screenshot API and MCP server from Yorker Media. A screenshot can help you review the current rendered state, but it does not replace Versionista’s change history or diagnose why a prior crawl did not record a change. See the ScreenshotNeo API documentation for request options.
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://example.com -o shot.webpimport requests
r = requests.get(
"https://api.screenshotneo.com/v1/shot",
params={"access_key": "YOUR_API_KEY", "url": "https://example.com"},
timeout=90,
)
r.raise_for_status()
open("shot.webp", "wb").write(r.content)const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://example.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);
if (!res.ok) throw new Error(`ScreenshotNeo returned ${res.status}`);
const fs = await import('node:fs/promises');
await fs.writeFile('shot.webp', Buffer.from(await res.arrayBuffer()));ScreenshotNeo accepts a URL in one GET request and can return PNG, JPEG, WebP, or PDF. Its capture can accept cookie and consent banners and remove more than 60 known consent platforms, newsletter popups, and chat widgets before taking the shot; each of those steps can be turned off. Bot checks and CAPTCHAs, blank pages, timeouts, failed loads, and cache hits are not billed, and responses include X-Page-Verdict and X-Billed headers. Its MCP server offers take_screenshot, get_page_info, and capture_pdf for Claude, Cursor, and other MCP clients. The free plan includes 1,000 shots per month without a card; paid plans start at $5 for 3,000 shots. Every feature is available on every plan.
Sign up for ScreenshotNeo’s free plan: 1,000 screenshots a month, no card required.
Frequently asked questions
Does Versionista monitor every change by default?
Versionista says it monitors all changes by default, but filters and focus phrases can limit which changes produce a recorded version.
Can focus phrases detect changes in images or PDFs?
No. The documented focus-phrase feature covers HTML and plain text, not images, PDFs, Word files, or other content types.
Does no email mean no change was detected?
No. Check the page’s version history. Summary reports and page-level instant alerts have separate settings, and instant alerts are off by default.
Does Versionista’s homepage notice mean existing accounts must move to Fluxguard?
The homepage says existing customer accounts remain supported and directs people seeking new accounts to Fluxguard. It does not say existing users must migrate.
