Given only a domain or URL, PWARegistry:
- Fetches the HTTPS page.
- Discovers
<link rel="manifest">. - Fetches and parses the Web App Manifest.
- Resolves
start_url,scope, icons, screenshots, and other members against the manifest URL, as the specification requires. - Fetches icon and screenshot files to confirm they are reachable images.
- Looks for a service worker registration in HTML and same-origin scripts.
- Reads relevant HTML metadata (
<title>, description, theme-color, Open Graph) and Schema.org JSON-LD when the manifest omits equivalent fields. - Validates the result.
- Normalizes the result with documented rules.
- If the result is PASS or PASS WITH WARNINGS and the request was a submission, writes a public registry record.
PWARegistry does not execute JavaScript from submitted sites, does not run a full browser, and does not generate marketing copy.
Standards that are read
| Source | Used for |
|---|---|
| Web App Manifest | Identity, display, icons, screenshots, capabilities |
HTML <link rel="manifest"> |
Discovery |
HTML <title>, meta description, theme-color |
Fallbacks only |
Open Graph og:description, og:site_name |
Fallbacks only |
Schema.org SoftwareApplication / WebApplication |
Description fallback |
navigator.serviceWorker.register |
Service worker detection |
Authoritative how-to documentation lives elsewhere. Prefer MDN, web.dev, the W3C manifest spec, and OpenPWA.net when you need to implement a capability.