Versionista Pricing for Monitoring Multiple Websites
Versionista does not publish current prices or multi-site limits. Here’s what its official documentation confirms and how to plan a reliable cost comparison.
Short answer: Versionista does not publish current prices, plan tiers, or multi-site subscription limits in the official sources reviewed here. Its homepage directs people seeking new accounts to Fluxguard and says existing Versionista accounts remain supported. For a current quote, start with the current Fluxguard offering or contact the appropriate account team, then compare the quote against your number of sites and pages, crawl frequency, alert needs, discovery requirements, and filtering controls. Versionista’s homepage is the place to confirm the account transition.
What Versionista pricing information is public?
The official Versionista pages cover how URLs are organized into sites, how newly discovered pages are handled, how alerts work, and how monitoring filters can reduce noise. They do not state current subscription prices or purchased limits for sites and monitored pages. That means there is no supported basis here for saying Versionista charges per site, per page, or at a particular monthly rate.
A TechRadar review published in 2021 reported a free plan and monthly prices from $99 to $379. Those figures are historical reporting, not current pricing, and should not be used to budget a new account today. Ask for a current quote and confirm which features and usage limits it includes.
Is Versionista still available for new accounts?
Versionista’s current homepage says new web change monitoring accounts are available through Fluxguard, while existing Versionista accounts continue to be supported. If you are choosing a service now, check the current Fluxguard offering first. Existing account holders should confirm their support and account options through the appropriate Versionista contact.
What to include in a multi-site quote request
Give the provider a concrete workload so the quote reflects what you will actually monitor. Prepare these details:
- Sites and pages: list the number of domains and the approximate number of pages you want monitored on each.
- Crawl cadence: state how often changes need to be detected. Do not infer a crawl interval from alert frequency; ask for the supported cadence and whether it varies by plan.
- Alerts: specify who needs summary and immediate notifications, how they should be routed, and which pages need instant alerts.
- Page discovery: say whether the system must find newly linked pages, and ask how discovery capacity is counted and what happens when its queue fills.
- Noise controls: describe page areas to ignore and any keywords whose additions or deletions should trigger a recorded version.
- History and access: confirm version-history retention, team seats, integrations, support, and any export or API needs that matter to your workflow.
Request the resulting quote in terms of the actual limits: monitored sites, monitored pages, scan cadence, history, alert configuration, and discovery. The public material reviewed does not establish those commercial limits.
How multi-site monitoring is organized
Versionista’s API generally places a submitted URL under an existing site when one exists. The optional new_site flag forces the URL into a new site. The documentation notes this can be useful when you want separate settings for the same domain, so a site count may not always be identical to a count of unique domains.
The API documentation labels the API experimental and subject to change. If you plan to automate onboarding or configuration for many sites, verify the current API behavior and test it against a small set of URLs before relying on it operationally.
Discovery, alerts, and filters across sites
New-page discovery
The Versionista tutorial says discovery is enabled by default. It describes up to 50 newly found URLs per scan and up to 150 newly found URLs per monitored site. These are discovery figures, not paid-plan allowances for the number of monitored pages. Newly found URLs can appear in email reports and then be activated for monitoring or paused. Account Settings can apply discovery settings across many sites.
Change alerts
Summary emails cover changes across all sites and are sent daily by default; their frequency can be changed in Account Settings. Instant alerts are off by default and are configured page by page. Confirm how these settings interact with your desired alert volume before enabling them broadly.
Filtering changes
Filters can limit which parts of a page count as monitored content. Keyword rules can record a new version when selected terms are added or deleted. Use filters to focus monitoring on meaningful content and reduce irrelevant changes, then validate the rules on pages with dynamic content.
Estimate the cost of monitoring several websites
Since current rates and quotas are not published in the sources available for this guide, use a quote comparison rather than a guessed per-site calculation. For each option, record:
| Cost or capacity item | What to confirm |
|---|---|
| Billing unit | Whether pricing depends on sites, pages, scans, users, or a combination |
| Included capacity | Maximum monitored sites and pages, and the cost of exceeding either |
| Scan cadence | Available intervals and whether faster checks incur additional cost |
| Discovery | Whether discovered URLs count toward monitored-page limits and what happens at the discovery cap |
| Alerts and history | Any plan restrictions on instant alerts, recipients, or saved versions |
| Administration | Seats, API access, support, and features needed for your team |
| Contract terms | Monthly versus annual billing, renewal, cancellation, and any overage rules |
Compare quotes using the same workload. A low starting price is not meaningful if it excludes the page count, scan schedule, or alert behavior you need.
ScreenshotNeo as an alternative for screenshot workflows
Versionista monitors website changes. If your actual need is to capture pages as images or PDFs for review, archiving, or downstream processing, try ScreenshotNeo first: it provides a website screenshot API and MCP server, removes consent banners and other specified overlays before capture, and bills only clean shots.
ScreenshotNeo does not replace change-monitoring alerts or page discovery. It is an alternative for the screenshot portion of a workflow, such as generating a visual record of a known URL on demand.
One-call screenshot example
See the ScreenshotNeo API documentation for request options and response details. This cURL call 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.webpCookie banners, popups, and chat widgets are removed before the shot. Bot checks, blank pages, and failed loads are never billed. An 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 shots. Sign up for 1,000 free screenshots a month, with no card required.
Troubleshooting a multi-site rollout
A URL appears under the wrong site
The API generally files a URL under an existing site when possible. If the same domain needs separate settings, check whether the request should use new_site=true, and verify the result before sending more URLs.
New pages are reported but are not being monitored
Discovery reports newly found URLs; the tutorial says they can then be activated or paused. Review the discovery report and activate the pages you want tracked. Do not treat the 150-per-site discovery figure as a monitored-page quota.
There are too many or too few email notifications
Summary email frequency is adjustable in Account Settings, while instant alerts are enabled page by page and are off by default. Check both settings and confirm that the relevant pages have instant alerts enabled where needed.
Changes are triggered by irrelevant page content
Use filters to narrow the page areas being monitored. For term-specific monitoring, configure keyword rules for additions or deletions, then check the resulting versions to ensure the rules match the intended content.
An old price appears in a comparison
Check the publication date and source. The $99–$379 figures came from a 2021 review and do not establish current pricing. Replace them with a current provider quote or state clearly that public current pricing was not available.
Performance, reliability, and operating cost
For a large portfolio, organize URLs deliberately and pilot the monitoring rules on representative pages before applying bulk settings. Discovery and alert configuration affect how much review work the system creates; filters can help focus that work. Ask the provider how scan cadence, page counts, retries, history, and any overages affect both coverage and cost. The official sources cited here do not publish current service-level figures, crawl performance benchmarks, or subscription limits, so those need confirmation for your account.
Frequently asked questions
Does Versionista charge per website or per page?
The official pricing information reviewed does not say. Ask the current provider to identify the billing unit and included quotas in a written quote.
Are the 50 and 150 URL figures plan limits?
No. The tutorial describes up to 50 new URLs per scan and up to 150 per monitored site as discovery behavior. It does not identify them as paid-plan site or monitored-page allowances.
Can I monitor the same domain with separate settings?
The API documentation says new_site can force a URL into a new site, which can be useful for separate settings on the same domain.
Where should a new customer start?
Versionista’s homepage directs prospects for new accounts to Fluxguard and says existing Versionista accounts remain supported.
Sources
- Versionista homepage — new-account transition and support for existing accounts.
- Versionista API documentation — URL placement,
new_site, and experimental API status. - New-page discovery tutorial — discovery behavior, figures, and bulk settings.
- Email alerts tutorial — summary and instant alert configuration.
- Keyword monitoring tutorial — filters and keyword rules.
- TechRadar review, September 3, 2021 — historical pricing only; not current pricing evidence.
