Independent public-page QA
We inspect one authorized public page and return a precise, client-ready record of what passed, failed, or remained unknown—without asking for a login or adding another meeting.
The handoff gap
Internal QA says your team looked. A launch receipt records what the public site actually returned at a specific time: redirects, broken destinations, metadata, indexability signals, headings, image text, form labels, and a rendered screenshot.
It is deliberately narrower than a full visual, transactional, or cross-browser audit. That bounded scope keeps it fast, repeatable, and safe to run without touching the client’s CMS, store admin, analytics, or private staging environment.
One quiet workflow
Provide a release name, one authorized public URL, and one priority concern. No login, analytics access, credential, or call is required.
Bounded checks capture observed responses, redirects, links, page signals, one rendered screenshot, and any inconclusive result.
Share the priority summary and screenshot with the client, keep the JSON and CSV evidence, and use the clarification round if needed.
What arrives
Every file comes from the same accepted URL set and recorded run. Failed checks remain failed. Unfinished checks remain unknown.
A concise record of the most important observed results, with exact pass, fail, or unknown states and stated boundaries.
One capture of the audited public page so the evidence includes what rendered, not only response codes.
Portable records for review, spreadsheets, internal notes, and comparison after a public fix.
One clarification round about the delivered evidence is included. Remediation and a second run are not part of the public service.
The boundary
Inspect before ordering
The public example is explicitly synthetic. It demonstrates the receipt structure and evidence states without pretending a fictional brand is a customer.
Open the synthetic receiptFixed scope · one launch
One public URL, up to 20 same-origin link probes, one 1440 × 900 screenshot, a priority summary, JSON and CSV evidence, and one clarification round. Checkout and private delivery are handled through Contra.
Before ordering
After the public URL and priority concern are accepted and Contra confirms payment. A pending transfer or incomplete intake does not start the clock.
It covers questions about the delivered observations and evidence. It does not add another URL, a rerun, remediation, or new testing scope.
No. The service makes bounded read-only requests to authorized public HTTP or HTTPS pages. It does not place orders, submit forms, sign in, or inspect admin configuration.
The receipt records the observed block or an unknown result. It is not converted into a pass or misreported as a broken link.
No. This is an observation-only launch receipt. Remediation, development, security testing, and certification are outside the fixed scope.
A receipt for the handoff