What a golden map checks, page by page
A golden map is a short list of public pages that must stay reachable and ungated. It is the cheapest useful check of a live product, and it catches failures an uptime ping misses.
Declaring one
A golden map is a list of site-relative paths, for example /, /pricing, /signup and /docs. NightlyQA can also propose one: discovery reads the homepage links and sitemap.xml, keeps same-origin pages and drops static assets. The proposal is left unconfirmed until you accept it.
The rules, in order
Each page is opened in Chromium. It fails on the first rule it breaks:
- HTTP error. The page itself returns 400 or higher.
- Login-wall redirect. A public page ends up on a path like
/login,/signinor/register. A page that is itself a login page is not flagged for being one. - Inline gate. The page renders, but shows an element marked
data-nightlyqa-gateor text matching the gate marker you configure. - Missing homepage marker. If you give a phrase your homepage should always show, its absence fails the check. This catches a site that was replaced or a section that was hidden.
- Subresource 5xx. Any script, stylesheet, image or API call on the page returns a server error.
- Console error or failed request. An unhandled console error or page error, or an xhr/fetch call that fails or returns 400 or higher. Generic "failed to load resource" noise on its own does not count.
Broken links (opt in)
With links: true in nightlyqa.yml, every link on a golden page that passed is probed once per run: same-origin links only, a HEAD request (GET if HEAD is refused), no cookies. A link to a page that answers 404 or 5xx is filed as a broken-link finding naming the source pages and link text. Mail, phone, fragment and logout links are skipped, a redirect to your login page counts as fine, and links: { max: 50, exclude: ["/blog/**"] } caps or narrows the probes.
What it does not do
A golden-map check only opens pages. It does not click, fill or submit forms, and it does not sign in. Logged-in paths and form submissions belong in declared workflows, which run separately with run-tagged test data.
What a failure produces
Each failing page gets an evidence pack (screenshot, video, console log, network log, DOM and repro steps), and the finding is filed as a deduplicated GitHub issue. Filing is a dry-run by default, so nothing reaches GitHub until you turn it on. See the redacted sample finding.
NightlyQA is an early-stage product in portfolio dogfood. Public onboarding is not open yet. Request early access.