← Shop · integration kit for agencies · branded client deliverable · free sample and pilot · copy-paste examples · Markdown: /agency/client-report-howto.md

From site report to a branded client deliverable

Service status: available; price: US$0.01 per report (x402, USDC on Base).

A site report already comes as two finished documents: report.md (Markdown) and report.html (one self-contained HTML file with print styles). This page shows how an agency turns them into a deliverable under its own name.

1. Ask for the white-label version

Send your agency name (and optionally a logo) in the request:

"scope": {
  "audience": "agency",
  "brand": { "name": "Your Agency", "logo_url": "https://your-agency.example/logo.png" },
  "format": "all"
}

What changes with brand:

• the HTML header shows your logo and name; both documents say "Prepared by Your Agency";
• there is no Lordevo name, no link to Lordevo and no "Generated by" line anywhere in the documents;
• the logo (PNG, JPEG, GIF or WebP, public https URL, up to 150 KB) is fetched once and embedded in the HTML, so the file shows it offline and in email attachments. If it cannot be used, the header shows your name only and the report lists "Brand logo not used" under "Needs human review" with the reason. Fix the logo URL and order again if you need it.

brand needs audience: "agency". Without brand, the documents say "Prepared for the client" and end with one neutral "Generated by Lordevo site-report (site-report/1)." line.

2. Download the files and send them yourself

report_html_url and report_markdown_url are private links on shop.lordevo.com (the key is in the URL) and expire after 30 days. For a white-label deliverable, do not forward these links: download the files (the Node and Python examples save report.json, report.html and report.md) and deliver them from your own systems.

• HTML: open it in a browser and print to PDF ("Save as PDF"). The print styles keep findings on one page where possible. Or host the file on your own portal.
• Markdown: paste it into your own template (Google Docs, Notion, Word via pandoc, your CMS). Headings are stable: Executive summary, Findings (one "### F01 · title" per finding), Implementation plan, Needs human review, Coverage, Limitations.
• JSON (site-report/1): build your own layout. Each finding has severity, priority, effort, impact, evidence[], fix.summary, fix.where, fix.example and verify; the plan has three phases with owner_role and depends_on. The schema is OpenAPI components.schemas.SiteReport1.

3. Review before you send

The report is automated. Before it goes to your client:

• read Needs human review: inferred findings (for example DKIM at a custom selector) and business choices (blocked AI crawlers, noindex pages, DMARC policy) need your judgement or the client's;
• read Coverage: which pages were read, which were blocked by robots.txt or failed, which areas were not checked. Do not present an unchecked area as clean;
• keep the "not a guarantee" text. The report is a passive, point-in-time assessment, not a penetration test, and it promises no rankings, traffic or security outcome.

What the client's team will see in their own logs: requests from the User-Agent LordevoQuickCheck/1.0 at the time of the report. Tell them in advance if they monitor traffic.

4. SAMPLE

sample/lordevo-com-whitelabel.html and sample/lordevo-com-whitelabel.md (JSON: sample/lordevo-com-whitelabel.json).

This is a SAMPLE. It is the real passive run against lordevo.com (a site Lordevo owns) from 30 Oct 2026, rendered with audience: "agency" and the placeholder name "Your Agency Name (SAMPLE)" and no logo. The findings, evidence and coverage are unchanged from that run; only the white-label fields differ. It was made offline with node tools/agency-sample.mjs (no new requests to the site). No third-party site was assessed for it.