Samples: artifacts instead of promises
This audience doesn’t trust text — it trusts files you can open in Excel and curl. Every sample below comes from a real package run, anonymized: client domains replaced, names removed, everything else untouched.
Last updated: 2026-09-23
qa-report-sample.pdf
Open it: % restored, every miss with a reason and a source timestamp — this is what your client sees. Anonymized from a real run.
redirects.csv
Open in Excel: 301/410 map, one row per URL (url, status, target, reason). This ships with every order.
install.md
Written for a non-technical VA: your project manager deploys without me.
sitemap.xml
Generated from live pages — not the archived one.
robots.txt
Generated robots.txt; the archived robots goes to the QA report instead.
package tree + screencast
Full listing of a delivered package and a 3–5 minute screencast of the pipeline (screen only, no face).
Honesty note
Why files say “in preparation”
The first production runs (the pilot on 3–5 domains) produce the real artifacts. We publish files only from real runs — no fabricated demos. The pilot follows the tool’s test gate; the samples appear here within days of it.
Meanwhile: the free coverage audit already runs on the real pipeline — you can see the inventory report for your own domain within ~2-3 hours.