White label SEO: how to judge a delivery partner
Before you sign a white label SEO partner, ask for a short audit of your own site. Not a case study. A case study describes something that happened once, for someone else, with numbers you cannot verify. Ninety minutes spent on a domain you know intimately tells you far more than any deck will.
Give them your domain, not your brief
You know your own site’s history. You know which pages were rushed, which redirect chain never got cleaned up, which section the last developer left half-finished. When a prospective partner audits it, you can grade their work instantly, which you cannot do with a case study about a manufacturer in Ohio.
Watch for two things. Do they find the problems you already know about, and do they find one you did not? A partner who returns a list of generic recommendations has run a tool and reformatted the export. A partner who tells you your fourth-tier service pages are competing with each other has actually looked.
We ran this exercise on ourselves in September 2026 and published what came back. Our crawl returned 145 URLs, with 42 service pages spread across three overlapping page systems that had piled up over two years. Thirty-one title tags ran over 60 characters. Three URLs returned 404. Mobile Time to Interactive measured 12 seconds, caused by a developer CSS tool that shipped to production and stayed there. Domain authority 14. Ninety-two referring domains, not one of them new in 60 days. Fifty-nine organic visits a month.
That is an uncomfortable list to publish. It is also the fastest way to show an agency owner what our audits actually contain.
What their reporting has to survive
The test is simple: can you forward the report to your client without rewriting it? Most white label reporting fails this, because it is written for you, full of internal shorthand, or padded with charts that answer nothing a client asked.
A report that survives forwarding states what was done, what moved, what did not move and why, and what happens next month. It carries your logo, not theirs. It arrives before your client meeting rather than the morning after. When you evaluate Growthym or anyone else for delivery, ask to see a real anonymized monthly report, then read it as though you were the client receiving it. The reporting cadence and who writes what is worth settling in the first call, and the way they run reporting should be written down somewhere you can read before you sign.
Who owns the client relationship
This needs saying out loud on day one. The partner should never contact your client directly, appear on a call without your invitation, email your client’s team, or hold credentials your client gave you. If they want to join calls as your team member, agree on the naming and the email domain in advance.
Ask what happens if you stop working together. Who holds the Search Console access and the content drafts? Get the answer in the contract, because the version you agree verbally will not be the version you remember.
The volume trap
The failure mode in white label is a partner optimizing for deliverable count. Eight posts a month, 40 links a quarter, a tidy invoice. Volume is easy to sell and easy to measure, and it correlates weakly with outcomes.
We audited 20 posts produced under an arrangement like that. Zero external citations across all 20. An average of 1.3 statistics per post. Thirteen of the 20 carried no first-hand experience marker of any kind. Every deliverable was met. Nothing ranked.
What cheap delivery actually looks like
Cheap delivery does not arrive labeled as cheap. It arrives as content that reads fine and says nothing specific, written by someone with no access to a practitioner and no budget for research time. The tell is the absence of numbers and named sources. Ask who writes the drafts, whether they interview anyone, and what the research step costs in hours.
Send your own domain to two shortlisted partners this week and ask each for a one-page audit with three findings and the evidence behind them. Compare what they found. That comparison will be more useful than every reference call you could make.
