PWA Manifest Checker | Installability & Icons avatar

PWA Manifest Checker | Installability & Icons

Pricing

from $2.80 / 1,000 results

Go to Apify Store
PWA Manifest Checker | Installability & Icons

PWA Manifest Checker | Installability & Icons

Inspect website manifest data, launch URLs, icon assets and service-worker signals for web app installation and release-readiness issues.

Pricing

from $2.80 / 1,000 results

Rating

0.0

(0)

Developer

Rafael Barreto Haddad

Rafael Barreto Haddad

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

10 days ago

Last modified

Security

Limited permissions

Share

Web App Installability & Release Readiness Checker

PWA release-readiness intelligence that validates manifest identity, launch URL, scope, service worker, install icons/assets and regression evidence before deployment. Returns structured, machine-readable results for repeatable research, monitoring, automation, Apify Tasks, API.

Quick start

Start with this working example and replace the target values with your own:

{
"urls": [
"https://www.pwabuilder.com"
],
"previousSnapshots": {}
}

The Actor writes structured results to the default Apify Dataset and can be used from the Store, API, schedules, Tasks, automations and MCP-compatible AI workflows.

Input

  • urls — Web app URLs: Public web app or website URLs to inspect for installability and release readiness.
  • previousSnapshots — Previous readiness snapshots: Optional prior snapshots keyed by input or final URL to detect manifest and service-worker regressions.
  • maxUrls — Maximum URLs: Maximum web app URLs processed in one run.
  • concurrency — Concurrency: Maximum parallel web app checks.
  • failRunOnReadiness — Fail run on low readiness: Fail after writing evidence if any releaseReadinessScore is below the minimum.
  • minimumReadinessScore — Minimum readiness score: Minimum acceptable releaseReadinessScore when failRunOnReadiness is enabled.

All integration and advanced analysis fields are optional. The default example is intentionally runnable without configuring MCP or a previous-run baseline.

Output

The Dataset exposes predictable machine-readable output. Representative fields include dataset.

Pricing

This Actor uses Pay Per Event. The current factory base price is $0.004000 per result event. The Apify Store remains the source of truth for the price and plan/tier details shown to the buyer.

Use cases

  • Run the buyer-ready workflows exposed as Apify Tasks without preparing a custom integration first.
  • Use the Actor from API or schedules for recurring collection, comparison or monitoring.
  • Feed the structured Dataset output into spreadsheets, databases, automations or AI agents.
  • Compare repeat runs when the product supports snapshots or previous-run inputs.

Automation and AI

Use the same Actor through Apify API, schedules, public Tasks and the Apify MCP server. Outputs are structured for downstream workflows and AI agents rather than requiring manual copy/paste.

Limitations

  • Public websites and upstream APIs can change markup, access rules, rate limits or field availability without notice.
  • Fields that are not publicly available are returned as unavailable or omitted rather than fabricated.
  • Analytical outputs depend on the quality and coverage of the supplied or collected source data.
  • Treat marketplace, reputation, workforce, safety or commercial signals as decision support and validate material decisions against the underlying source evidence.

Detailed documentation

Detailed documentation

Audit whether a modern web app has the public evidence needed for reliable installation and release readiness. Instead of validating manifest JSON in isolation, this Actor combines manifest discovery, service-worker evidence, icon readiness, HTTPS and snapshot-based regression detection.

Why use this Actor

PWAs and installable web apps often fail because one small release removes a service worker, breaks the manifest path, drops a required icon or changes configuration. Browser-based audit stacks can be heavy for simple recurring checks. This Actor provides a lightweight structured gate that frontend teams and AI agents can run continuously.

Key features

  • Discover a manifest from HTML or common manifest paths.
  • Validate name, start URL, display mode and icons.
  • Check 192x192 and 512x512 icon coverage plus maskable icon evidence.
  • Discover service-worker registration or common service-worker paths.
  • Verify HTTPS and public page availability.
  • Record manifest fingerprint and compare with previous snapshots.
  • Detect manifest or service-worker regressions.
  • Produce installabilityScore, releaseReadinessScore, releaseGate and agentAction.
  • HTTP-first 256 MB runtime with no Lighthouse service or paid AI dependency.

Input

Provide one or more public web app URLs. Add previous snapshots for recurring release monitoring.

{"urls":["https://www.pwabuilder.com"],"previousSnapshots":{}}

Output

Each URL returns manifest and service-worker evidence, icon readiness, installability and release scores, regression fields, a reusable snapshot and a recommended action.

Example

A release that loses its service worker can move from PASS to REVIEW or BLOCK, surface service_worker_disappeared, and recommend REVIEW_WEB_APP_REGRESSION.

Use cases

PWA release gates, frontend CI, agency QA, ecommerce PWAs, SaaS web apps, manifest regressions, service-worker monitoring, installability audits and AI-agent release validation.

Pricing

Pay per result. The base configured price is $0.004 USD per web app result, with tiered discounts where supported.

Limitations

The Actor uses public HTTP evidence and heuristics rather than a full interactive browser. Browser-specific installation prompts and runtime service-worker behavior can differ. A PASS is strong release evidence, not a guarantee that every browser will offer installation.

Input reliability — 25 October 2026

Target lists are validated before network work, trimmed and deduplicated. Empty lists and malformed baselines are rejected rather than silently auditing a default website. Exact duplicate targets produce one result. Existing output fields and prices are preserved.