White-label link health reports your clients see, not your tooling.
The deliverable is a PDF with your agency's logo, your colors, your contact info. The client reads "monthly link health from your agency," not "your agency forwarded a tool report. " Same engine, different surface.
Why white-label matters for retainer-based agencies
The agency-client relationship is built on the perception that the agency is doing the work. When a client opens an email and sees a Bulk URL Checker logo on the report, you've just answered the question "what tool did they use" instead of the question "what value did the agency provide."
The opposite happens with white-label: the client opens the PDF, sees your agency's brand, and the work attribution lands where it should — on you. The tool is invisible.
For retainer agencies billing $1,500 to $5,000 a month, that's not a small thing. The deliverables are the proof of work the retainer is paying for. They should be branded as if your team built them.
What gets branded
Customizable per workspace, set up once at onboarding:
Agency logo. Top of the cover page, top of every content page footer.
Agency primary color. Drives accent colors, chart colors, header bars across the report.
Agency contact info. Account manager name, email, phone if you use it. Appears on the cover page and the recommended-actions section.
Optional intro paragraph. A standard message you want every client report to open with. Editable per cycle if something needs to be called out.
Optional client-specific cover. Client logo (uploaded by you per workspace), client name, the period covered.
What the report contains
Standardized so the client knows what to expect each month, with enough detail to be useful and not so much that nobody reads it:
Cover page. Agency logo, client name, period covered, agency contact.
Executive summary. "X URLs checked, Y% healthy, Z newly broken since last cycle." The one number the client looks at first.
Trend over time. 12-cycle chart of healthy vs broken. Establishes that you've been doing this work consistently.
What changed since last cycle. Diff section: newly broken URLs, newly recovered URLs, redirect chain changes. The most actionable part of the report.
Detailed findings. Every broken URL with status code, redirect chain (if any), response time, and last-seen- healthy date. Sortable table for clients who want to dig.
Recommended actions. Pre-populated agency recommendations per finding type, editable as needed.
Appendix. Methodology section explaining what checks ran, what cadence, how proxy rotation handled rate limits. Builds credibility without overwhelming the executive reader.
How delivery works
Three options per workspace, choose what fits the client relationship:
Land in your inbox. Most agencies pick this. PDF generates at the end of the cycle, lands in your email, you forward it to the client with whatever cover note you want. Maximum control.
Auto-send to a list. If the client relationship is mature and you want to skip the forward step, configure a recipient list per workspace and the report goes directly. You get a copy.
Download from dashboard. Some agencies want to review before any email goes out. Generated PDFs sit in the workspace; download when ready.
The footer reference (and why it's tasteful)
A small "Powered by Bulk URL Checker" line sits in the report footer. It's tasteful, not invasive — comparable to the "Powered by Stripe" line on a checkout page or the Brevo footer on a transactional email.
When you turn on the referral program, that footer becomes your unique referral link. Every PDF a client opens is a passive marketing touch that pays you 30% recurring revenue if it converts another agency. Most agencies leave it on for that reason.
The math against doing it yourself
Some agencies build this in-house. Pulling URL lists, running a script, handling 429s, generating a branded PDF, scheduling the delivery, supporting it through dependency upgrades. The build is a couple of weeks of senior engineering time. The maintenance is ongoing.
For most agency owners, $499/month for the whole stack maintained by someone else, with proxy rotation already built in, is cheaper than the senior engineer-day per month they were spending keeping their internal version alive.