Samples: artifacts instead of promises

Files you can open in Excel and check with curl. Samples are published only from real package runs, anonymized — the first ones come after the pilot. Until then, the free audit on your own domain is the proof.

Last updated: 2026-10-06

qa-report-sample.html in preparation
% restored, every miss with a reason and a source timestamp — the report your client sees. Will be anonymized from a real run.
redirects.csv in preparation
Open in Excel: 301/410 map, one row per URL (url, status, target, reason). This ships with every order.
install.md EN + RU · in preparation
Written for a non-technical VA: your project manager deploys without me.
sitemap.xml in preparation
Generated from live pages — not the archived one.
robots.txt in preparation
Generated robots.txt; the archived robots goes to the QA report instead.
package tree + screencast after the pilot
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 2–3 domains) produce the real artifacts. I 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 same or next business day.